How to Install and Uninstall golang-k8s-sigs-structured-merge-diff-dev Package on Kali Linux

Last updated: December 27,2024

1. Install "golang-k8s-sigs-structured-merge-diff-dev" package

This guide let you learn how to install golang-k8s-sigs-structured-merge-diff-dev on Kali Linux


    
        
            $
        

        
            
                sudo apt update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt install
            
                        
                golang-k8s-sigs-structured-merge-diff-dev
            
                    
    
    Copied

2. Uninstall "golang-k8s-sigs-structured-merge-diff-dev" package

Here is a brief guide to show you how to uninstall golang-k8s-sigs-structured-merge-diff-dev on Kali Linux:


    
        
            $
        

        
            
                sudo apt remove
            
                        
                golang-k8s-sigs-structured-merge-diff-dev
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt autoclean && sudo apt autoremove
            
                    
    
    Copied

3. Information about the golang-k8s-sigs-structured-merge-diff-dev package on Kali Linux

Package: golang-k8s-sigs-structured-merge-diff-dev
Source: golang-k8s-sigs-structured-merge-diff
Version: 4.4.1+ds1-1
Installed-Size: 2241
Maintainer: Debian Go Packaging Team
Architecture: all
Depends: golang-github-json-iterator-go-dev, golang-gopkg-yaml.v2-dev, golang-github-google-go-cmp-dev
Size: 151520
SHA256: b0f057f19f5207fa035d87135bb7c30d46bf758a1a53c09f974c85bff489d1ae
SHA1: 6f5d0bc3d049e0009331030a5a3dca6a843c4556
MD5sum: 949b83799cc4c53e79cc37361a0f09da
Description: implementation for "server-side apply" (library)
What is the apply operation?
.
It models resources in a control plane as having multiple
"managers". Each manager is typically trying to manage only one
aspect of a resource. The goal is to make it easy for disparate
managers to make the changes they need without messing up the things
that other managers are doing. In this system, both humans and
machines (aka "controllers") act as managers.
.
To do this, it explicitly tracks (using the fieldset data structure)
which fields each manager is currently managing.
.
Now, there are two basic mechanisms by which one modifies an object.
.
PUT/PATCH: This is a write command that says: "Make the object look
EXACTLY like X".
.
APPLY: This is a write command that says: "The fields I manage should
now look exactly like this (but I don't care about other fields)".
.
For PUT/PATCH, it deduces which fields will be managed based on what
is changing. For APPLY, the user is explicitly stating which fields
they wish to manage (and therefore requesting deletion of any fields
that they used to manage but stop mentioning).
.
Any time a manager begins managing some new field, that field is removed
from all other managers. If the manager is using the APPLY command, it
calls these conflicts, and will not proceed unless the user passes the
"force" option. This prevents accidentally setting fields which some
other entity is managing.
.
PUT/PATCH always "force". They are mostly used by automated systems,
which won't do anything productive with a new error type.
Description-md5:
Multi-Arch: foreign
Homepage: https://github.com/kubernetes-sigs/structured-merge-diff
Section: golang
Priority: optional
Filename: pool/main/g/golang-k8s-sigs-structured-merge-diff/golang-k8s-sigs-structured-merge-diff-dev_4.4.1+ds1-1_all.deb