Version v6.0.0 released!
- CRDs have been updated
- If you are updating the helm chart, please run
kubectl apply -f https://github.com/Contrast-Security-OSS/agent-operator/releases/latest/download/crds.yamlbefore upgrading to update the CRDs. https://docs.contrastsecurity.com/en/helm-upgrades.html#major-upgrades-292514
- If you are updating the helm chart, please run
- Add support for setting AgentConnection and AgentConfiguration on ClusterAgentInjector
- Referenced AgentConnection or AgentConfiguration need to be in the same namespace as the ClusterAgentInjector
- Upgrade to .NET 10 and dotnet-operator-sdk 10.x
- Setting
CONTRAST_AGENT_TELEMETRY_OPTOUT=1on the agent-operator will now opt-out agents from telemetry collection - Fixed a regression where the internal state would go out of sync
- Missing operator settings are now exposed in the helm chart:
| Agent Operator Setting | Helm Chart Setting |
|---|---|
| CONTRAST_EVENT_QUEUE_MERGE_WINDOW_SECONDS | operator.eventQueueMergeWindowSeconds |
| CONTRAST_AGENT_TELEMETRY_OPTOUT | operator.telemetryOptOut |
| CONTRAST_LOG_LEVEL | operator.operatorLogLevel |
| CONTRAST_RUN_INIT_CONTAINER_AS_NON_ROOT | operator.initContainer.nonRoot |
| CONTRAST_WATCHER_TIMEOUT_SECONDS | operator.watcherTimeout |
Breaking Changes
- Docker image base changed from Debian to Ubuntu Platforms for .NET 10 container images dotnet/dotnet-docker#6539, because of this the operator-user/operator-group ids have changed to 1001
- If the
spec.connection.nameorspec.configuration.nameon a AgentInjector (created by a ClusterAgentInjector) was edited manually; those references will now be overwritten when the ClusterAgentInjector updates the AgentInjector.
contrast/agent-operator:6.0.0
contrast/agent-operator@sha256:add8aa999e215c9e622ec4474714f53fc95462b117e78fec2a89949969c1166c
quay.io/contrast/agent-operator:6.0.0
quay.io/contrast/agent-operator@sha256:add8aa999e215c9e622ec4474714f53fc95462b117e78fec2a89949969c1166c