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 request: Governance configurations #166

Open
arthurdm opened this issue Jan 11, 2021 · 1 comment
Open

Feature request: Governance configurations #166

arthurdm opened this issue Jan 11, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@arthurdm
Copy link
Member

Similar to the way the Appsody Operator has default and constant configurations, RCO should have the ability to specify defaults (if value is not set) and constants (overriding any values). The difference will be that RCO should have these configured per namespace (1..N), instead of requiring a value such as stack to be put into the CR.

The scenario here is: the architecture team will come up with defaults and constants for the deployments of a particular team(s) and want those to be enforced for a particular set of namespaces.

@leochr leochr added help wanted Extra attention is needed enhancement New feature or request labels Jan 11, 2021
@arthurdm
Copy link
Member Author

Another suggestion for this feature is to document how someone can use kubectl to setup the appropriate namespace rbac that would restrict certain developers or groups to only creating a certain type of CR (e.g. RuntimeComponent), to prevent folks from going around the defaults/constants by creating things like Deployment directly.

@leochr leochr removed the help wanted Extra attention is needed label Aug 23, 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

2 participants