Skip to content

Feature request: Governance configurations #166

Open

Description

@arthurdm

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.

Activity

  1. arthurdm commented on Jan 11, 2021

    @arthurdm
    MemberAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions