Skip to content

fix(security): skip OpenShift ETCD monitoring when CR namespace differs from operator namespace - #553

Draft
cvrkota wants to merge 1 commit into
mainfrom
fix-etcd-namespace-guard
Draft

fix(security): skip OpenShift ETCD monitoring when CR namespace differs from operator namespace#553
cvrkota wants to merge 1 commit into
mainfrom
fix-etcd-namespace-guard

Conversation

@cvrkota

@cvrkota cvrkota commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Only copy ETCD credentials when the InstanaAgent CR is deployed in the same namespace as the operator. Read the operator namespace from POD_NAMESPACE (Downward API). If the namespaces do not match, or if POD_NAMESPACE is unset, skip ETCD monitoring and return early.

Why

What

References

Checklist

  • Backwards compatible?
  • unit/e2e test coverage added or updated?

Note: Remember to run a helm chart release after the the operator release to make the changes available thru helm.

…rs from operator namespace

Only copy ETCD credentials when the InstanaAgent CR is deployed in the
same namespace as the operator. Read the operator namespace from
POD_NAMESPACE (Downward API). If the namespaces do not match, or if
POD_NAMESPACE is unset, skip ETCD monitoring and return early.

Signed-off-by: Milica Cvrkota <milica.cvrkota@ibm.com>
@cvrkota
cvrkota requested review from a team as code owners July 27, 2026 14:03
@cvrkota
cvrkota marked this pull request as draft July 27, 2026 14:03
@Ferenc-
Ferenc- self-requested a review July 27, 2026 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants