How to Install and Uninstall golang-k8s-sigs-structured-merge-diff-dev Package on Ubuntu 20.10 (Groovy Gorilla)

Last updated: November 25,2024

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

This guide covers the steps necessary to install golang-k8s-sigs-structured-merge-diff-dev on Ubuntu 20.10 (Groovy Gorilla)


    
        
            $
        

        
            
                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

Please follow the step by step instructions below to uninstall golang-k8s-sigs-structured-merge-diff-dev on Ubuntu 20.10 (Groovy Gorilla):


    
        
            $
        

        
            
                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 Ubuntu 20.10 (Groovy Gorilla)

Package: golang-k8s-sigs-structured-merge-diff-dev
Architecture: all
Version: 3.0.0+ds1-2
Priority: optional
Section: universe/devel
Source: golang-k8s-sigs-structured-merge-diff
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Go Packaging Team
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 1176
Depends: golang-github-json-iterator-go-dev, golang-gopkg-yaml.v2-dev
Filename: pool/universe/g/golang-k8s-sigs-structured-merge-diff/golang-k8s-sigs-structured-merge-diff-dev_3.0.0+ds1-2_all.deb
Size: 109652
MD5sum: 26530a5fa39b04d510c7af9dfbd01d72
SHA1: 0d51eff8730adce8eaa4c42a117a00fbb0740f92
SHA256: 0402618abc29206817d5c2fea79c3e1afe031530a2797f931839c282912ce0ae
SHA512: 8308cb241f0c274816638cc2517dc0931f73911fdfca2125e217c2064e799d5175680a4e9b3a7d5d71c5011942bad879db681e4542f989af6ab2a7fdc25f9425
Homepage: https://github.com/kubernetes-sigs/structured-merge-diff
Description-en: 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: d7e1df2e566111bfc5a91d4180197476