Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Operator config map isn't read when the operator is watching another namespace #590

Open
3 tasks done
idlewis opened this issue Nov 10, 2023 · 0 comments · Fixed by #591
Open
3 tasks done

Operator config map isn't read when the operator is watching another namespace #590

idlewis opened this issue Nov 10, 2023 · 0 comments · Fixed by #591
Assignees
@idlewis
Labels
1.3.0 bug Something isn't working zenhub-dev

Comments

@idlewis
Copy link
Collaborator

idlewis commented Nov 10, 2023 •
edited by leochr
Loading

When the operator is installed in one namespace, but is watching a different namespace, it doesn't read the operator config map.
This means that changing the config map to non-default values, does not get reflected in the resources created by the operator.

Needs fixing in:

  • RCO
  • OLO
  • WLO
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@idlewis idlewis

Labels
1.3.0 bug Something isn't working zenhub-dev
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use reader client to get operator config map application-stacks/runtime-component-operator
2 participants
@idlewis @leochr