How to Install and Uninstall kubectl-view-allocations Package on openSuSE Tumbleweed

Last updated: June 27,2024

1. Install "kubectl-view-allocations" package

Please follow the guidelines below to install kubectl-view-allocations on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                kubectl-view-allocations
            
                    
    
    Copied

2. Uninstall "kubectl-view-allocations" package

In this section, we are going to explain the necessary steps to uninstall kubectl-view-allocations on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                kubectl-view-allocations
            
                    
    
    Copied

3. Information about the kubectl-view-allocations package on openSuSE Tumbleweed

Information for package kubectl-view-allocations:
-------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : kubectl-view-allocations
Version : 0.18.1-1.2
Arch : x86_64
Vendor : openSUSE
Installed Size : 4.1 MiB
Installed : No
Status : not installed
Source package : kubectl-view-allocations-0.18.1-1.2.src
Upstream URL : https://github.com/davidB/kubectl-view-allocations
Summary : kubectl plugin to list allocations
Description :
kubectl plugin lists allocations for resources (cpu, memory, gpu,...) as
defined into the manifest of nodes and running pods. It doesn't list usage like
kubectl top. It can provide result grouped by namespaces, nodes, pods and
filtered by resources'name.
Columns displayed :
* Requested : Quantity of resources requested by the container in the pod's manifest. It's the sum group by pod, namespace, node where container is running. With percentage of resources requested over what is allocatable in the group.
* Limit : Quantity of resources max (limit) requestable by the container in the pod's manifest. It's the sum group by pod, namespace, node where container is running. With percentage of resources max / limit over what is allocatable in the group.
* Allocatable : Allocatable resources defined (or detected) on nodes.
* Free : Allocatable - max (Limit, Requested)
* Utilization : Quantity of resources (cpu & memory only) used as reported by Metrics API. It's disable by default, metrics-server is optional and should be setup into the cluster.