Uploaded image for project: 'Red Hat Advanced Cluster Security'
  1. Red Hat Advanced Cluster Security
  2. ROX-29464

Enforce spec.clusterName presence in SC CRs

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • OpenShift Operator
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False

      According to ROX-8046 (need to verify this) even though spec.clusterName is required, it is possible to create a SecuredCluster CR without it, by omitting spec altogether.

      IIRC we do fail validation in this case but it would be nice to give feedback earlier.
      Perhaps it is possible to do this by making spec itself required?

      Caveats about adding new required fields apply (not a backwards compatible change) but perhaps it could be acceptable (see CRD ratcheting) given that spec is in practice already required for the above reason. TBD if OLM will let such change through.

              Unassigned Unassigned
              mowsiany@redhat.com Marcin Owsiany
              ACS Install
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: