Flexera Kubernetes Inventory Agent Configuration Examples

IT Asset Management (Cloud)

The following brief examples illustrate setting resource attributes for the Flexera Kubernetes Inventory Agent in a file using the YAML language.

Note: For employing Helm chart templates to accelerate Flexera Kubernetes Inventory Agent deployments, two predefined Kubernetes Helm chart templates are available and can be pulled from repositories hosted on Flexera AWS ECR - https://gallery.ecr.aws/flexera/:

• For the Full Flexera Kubernetes Inventory Agent—https://gallery.ecr.aws/flexera/krm-chart
• For the Lightweight Flexera Kubernetes Inventory Agent—https://gallery.ecr.aws/flexera/lwk-chart.

For each Helm chart, the majority of options within the values.yaml file are predefined and each option has a descriptive comment. Customers are required to specify the FlexNet Beacon URL and persistent storage options for the Full Flexera Kubernetes Inventory Agent, and the FlexNet Beacon URL for the Lightweight Flexera Kubernetes Inventory Agent. For configuration and installation steps for the Full Flexera Kubernetes Inventory Agent, see Full Flexera Kubernetes Agent Helm chart configuration and installation in the Online Help. For configuration and installation steps for the Lightweight Kubernetes Inventory Agent, see Lightweight Kubernetes Agent Helm chart configuration and installation in the Gathering FlexNet Inventory user guide.

1. Specifying agent storage

This simple configuration uses a dynamically-provisioned storage class named default to allocate the volume for use by the Flexera Kubernetes Inventory Agent.

apiVersion: agents.flexera.com/v1
kind: KRM
metadata:
  name: instance
spec:
  monitor:
    beaconURL: https://beacon.example.org
    storage:
      storageClassName: default
      resources:
        requests:
          storage: 2Gi

2. Excluding some Kubernetes resources

Extending the previous simple example, here the Flexera Kubernetes Inventory Agent is configured to ignore:

• All resources in the testing namespace
• Any other resources that are labeled with staging set to true.

apiVersion: agents.flexera.com/v1
kind: KRM
metadata:
  name: instance
spec:
  monitor:
    beaconURL: https://beacon.example.org
    storage:
      storageClassName: default
      resources:
        requests:
          storage: 2Gi
    excludeNamespaces:
      - testing
    excludeLabels:
      staging: "true"

3. Special cases

In the following example:

• A custom registry is used that requires authentication. An ImagePullSecrets value is specified that refers to an existing secret. (This uses an array list format where each array member has the leading dash, although the array here has only one member.)
• The IBM License Service integration is enabled.
• Collecting software inventory from container images is disabled.
• Increased storage to be used by the Flexera Kubernetes Inventory Agent is on an existing PersistentVolume, selected by using a label selector.

apiVersion: agents.flexera.com/v1
kind: KRM
metadata:
  name: instance
spec:
  image:
    registry: images.example.org
  imagePullSecrets:
    - name: myregistry
  ibmLicensing:
    enable: true
  monitor:
    beaconURL: https://beacon.example.org
    storage:
      selector:
        matchLabels:
          volume: pv003
      resources:
        requests:
          storage: 3Gi
    imageInventory: false