To install the KRM Agent in a custom namespace, you’ll need to make manual changes before running the script.

Step 1: Modify install.sh

1. Open the following file in a text editor such as vi or nano:

krm-<version>/install.sh

2. Locate this line:

$KUBECTL rollout status -w -n flexera deployments/krm-controller;

3. Replace flexera with your custom namespace:

$KUBECTL rollout status -w -n <your-namespace> deployments/krm-controller;

Step 2: Update namespace references in configuration files

Edit the following files to replace all instances of:

namespace: flexera

with

namespace: <your-namespace>

Files to update:

• krm-<version>/config/rbac/controller_clusterrolebindings.yaml
• krm-<version>/config/rbac/agent_clusterrolebindings.yaml
• krm-<version>/config/pre1.16/kustomization.yaml
• krm-<version>/config/openshift/clusterrolebinding.yaml
• krm-<version>/config/namespace/namespace.yaml
• krm-<version>/config/ibm-licensing-rbac/clusterrolebinding.yaml
• krm-<version>/config/ibm-licensing/clusterrolebinding.yaml
• krm-<version>/config/default/kustomization.yaml
• krm-<version>/config/collect-storage/clusterrolebinding.yaml

Step 3: Run the install script

After making the edits above, run the modified install.sh script. This will:

• Create your custom namespace
• Deploy the controller and agent components into that namespace
• Use your defined namespace for ServiceAccounts and bindings

Step 4: Add namespace to your KRM YAML

If you're deploying a KRM.yaml file afterward, add the following under the spec section to ensure the deployment references your custom namespace:

namespace: <your-namespace>

Apply the file using:

kubectl apply -f KRM.yaml

Step 5: Verify deployment

To confirm that the KRM Agent is running in your custom namespace, run:

kubectl get pods -n <your-namespace>