ACM Policy fails to apply Secret with error 'illegal base64 data'
Issue
- Some
Secret
object are failing to apply via ACM Policy objects dueillegal base64 data
errors
[{"Compliant":"NonCompliant","Validity":{},"conditions":[{"lastTransitionTime":"2024-03-19T15:31:02Z","message":"Error updating the object admission-control-tls, the error is Secret in version \"v1\" cannot be handled as a Secret: illegal base64 data at input byte 0","reason":"K8s update template error","status":"True","type":"violation"}]}]
- The
Secret
object in your ACM Policy uses unencodedstringData
instead of base64 encodeddata
Environment
- Red Hat Advanced Cluster Management for Kubernetes 2.7.10
- Red Hat Advanced Cluster Management for Kubernetes 2.8.0 to 2.8.4
- Red Hat Advanced Cluster Management for Kubernetes 2.9.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.