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.

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

Include custom resource information also in operator namespace #13

Open
pebrc opened this issue Sep 1, 2021 · 0 comments
Open

Include custom resource information also in operator namespace #13

pebrc opened this issue Sep 1, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@pebrc
Copy link
Collaborator

pebrc commented Sep 1, 2021

We are currently treating the operator namespace as a special case and are not extracting information about the ECK custom resources in that namespace. This is done because we understand that elastic-system is a special namespace reserved for the operator and we do not recommend deploying workloads into that namespace.

In practice however we see users time and again deploying into elastic-system. We should therefore also extract full diagnostics from the operator namespace to avoid having to go back and having to ask for another diagnostic that declares elastic-system (or any other operator namespace) as a resource namespace.

@pebrc pebrc added the enhancement New feature or request label Sep 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant