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

[FEATURE] Deprecate Target Namespace Feature #241

Open
1 task done
adambkaplan opened this issue Feb 5, 2025 · 0 comments
Open
1 task done

[FEATURE] Deprecate Target Namespace Feature #241

adambkaplan opened this issue Feb 5, 2025 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Milestone

Comments

@adambkaplan
Copy link
Member

Is there an existing feature request for this?

  • I have searched the existing feature requests

Is your feature request related to a problem or use-case? Please describe.

The Target Namespace feature grants the Shipwright operator permission to create any namespace. This is considered a highly privileged permission in Kubernetes.

Describe the solution that you would like.

When OLM installs the Shipwright operator in a given namespace, all operands (such as the Build controller) are installed in the same namespace.

Describe alternatives you have considered.

No response

Anything else?

No response

@adambkaplan adambkaplan added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 5, 2025
@adambkaplan adambkaplan added this to the Backlog milestone Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
Status: No status
Development

No branches or pull requests

1 participant