Certificate revocation issues can occur with the Flexera Kubernetes agent when applying a custom CA certificate bundle. When using a custom CA certificate bundle, a volume is mounted within the container at /var/opt/managesoft/etc/ssl. When the storage volume is a Secret or a ConfigMap, that volume is mounted as read-only. Because it's read-only, the write fails when the upload agent (ndupload) downloads revocation list files and attempts to write them to that volume.
You may see the following such errors in this situation:
Error 0xE0000002: No such file or directory 2
Error 0xE0500454: Failed to write local file /var/opt/managesoft/etc/ssl/ocsp/4f2f13d0.ocsp 3
Error 0xE0000002: No such file or directory 4
Error 0xE0500454: Failed to write local file /var/opt/managesoft/etc/ssl/crls/1f6380c7.r0 5
Error 0xE050057C: HTTPS certificate revocation status could not be determined
- Create an INI file containing the following:
NOTE: You can use any file name (example: patch.ini).
- Create a ConfigMap within the Flexera namespace to store the patch files using the following command:
kubectl create configmap krm-config --namespace flexera --from-file=patch.ini
- Within the YAML file, add the ConfigMap within the spec.monitor.configPatch. For example:
- After you redeploy the updated YAML file or instantiate the monitor pod, it should be able to read the INI file you created. Check the logs to validate that the INI file was read using the following command:
kubectl exec -n flexera krm-instance-monitor-0 -- cat /var/opt/managesoft/log/uploader.log
For more details, see Patching config.ini through Flexera Kubernetes Inventory Agent.