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

Exclude namespaces from being managed by operator #8396

Open
1davidmichael opened this issue Jan 7, 2025 · 0 comments
Open

Exclude namespaces from being managed by operator #8396

1davidmichael opened this issue Jan 7, 2025 · 0 comments
Labels
discuss We need to figure this out >feature Adds or discusses adding a feature to the product

Comments

@1davidmichael
Copy link

We have a case where we have ECK running in a cluster and would like to use it to manage a cluster in a given namespace. But we also would like to have another operator that manages all other Elastic resources.

For example: prod namespace resource are managed by one operator.

Other ephemeral environments are managed by a separate operator and the namespaces of these are generated and change over time. As a result we can't use the managedNamespaces to pin to specific namespaces. To accomplish this it would be really nice to have something like ignoredNamespaces so we can use one operator to manage that ignored namespace and a separate operator to manage all the others.

@botelastic botelastic bot added the triage label Jan 7, 2025
@kvalliyurnatt kvalliyurnatt added discuss We need to figure this out >feature Adds or discusses adding a feature to the product labels Jan 8, 2025
@botelastic botelastic bot removed the triage label Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss We need to figure this out >feature Adds or discusses adding a feature to the product
Projects
None yet
Development

No branches or pull requests

2 participants