You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Activity
arthurdm commentedon Jan 11, 2021
Another suggestion for this feature is to document how someone can use
kubectlto 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 likeDeploymentdirectly.