1. Run the following command:

   kubectl get ibmlicensings.operator.ibm.com -o json

   Review the output under spec and look for the instanceNamespace value. For example:

   "spec": {
     "apiSecretToken": "ibm-licensing-token",
     "datasource": "datacollector",
     "httpsEnable": true,
     "instanceNamespace": "ibm-licensing",
     "resources": {},
     "version": "4.2.16"
   }

2. Determine whether the instanceNamespace attribute is present.

   If instanceNamespace is present, verify that it matches the namespace where IBM License Service is installed.

   In some environments, the instanceNamespace attribute is missing. When this occurs, the KRM agent falls back to the default namespace:

   ibm-common-services

   If IBM License Service is installed in a different namespace, the KRM agent will not be able to locate the service and the error will occur.

3. If IBM License Service is installed in a namespace other than ibm-common-services, explicitly configure the namespace used by the KRM agent.

   For KRM agent deployments, update the KRM custom resource and reapply the configuration.

   Example:

   apiVersion: agents.flexera.com/v1
   kind: KRM
   metadata:
     name: instance
   spec:
     ibmLicensing:
       enable: true
       namespace: my-ibm-namespace-example
     monitor:
       beaconURL: https://beacon.example.org

   For Helm chart deployments, add the following setting to your values.yaml file:

   ibmLicensing.namespace: "my-ibm-namespace-example"

4. Reapply the updated configuration.

If the issue was caused by an incorrect namespace configuration, the KRM agent should be able to locate IBM License Service successfully.