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

hidden infra provider support #717

Open
Tracked by #549
Unix4ever opened this issue Oct 30, 2024 · 0 comments
Open
Tracked by #549

hidden infra provider support #717

Unix4ever opened this issue Oct 30, 2024 · 0 comments

Comments

@Unix4ever
Copy link
Member

Unix4ever commented Oct 30, 2024

Infra provider used for managed control planes shouldn't be usable by the user.
Validation should block using the infra provider in the machine classes/machine requests/machine request sets.

The provider should be readonly.
We can filter some data from the infra provider status if we have secrets there.

Managed control planes infra provider logs shouldn't be available to the end user when we get them implemented.

The infra provider will be labeled with omni.sidero.dev/managed and it will make it readonly and not usable by machine classes and machine requests.

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

No branches or pull requests

1 participant