RELEASED: Public: May 28, 2025
Resolved issues
- If
Agents.SeparateNamespace.Enabled=trueall agents are installed to the same namespace (BEE-58050) -
Setting
Agents.SeparateNamespace.Enabled=truedid not work well in conjunction with managed controllers in another namespace or cluster (Master.OperationsCenterNamespace), as the agents were all directed to a single namespace regardless of the managed controller location. Now each managed controller namespace will get its own corresponding agent namespace.
If upgrading from a prior release, you may need to set Agents.SeparateNamespace.Create=true to create the per-managed controller namespace. If some projects were relying on special service accounts (typically tied to cloud identities) in the old global namespace, those service accounts should be duplicated or moved to the new per-managed controller namespace(s). You should also delete the predefined Kubernetes shared cloud configuration snippet defined in operations center if using this system rather than CasC: {{https://your.domain/cjoc/view/All/job/kubernetes-shared-cloud/delete}} before letting operations center be restarted during the upgrade. Alternately, Configure it and ensure that Kubernetes Namespace is blank, as this would otherwise override the agent namespace selected by a specific managed controller.