fixed clusterserviceversion

Author: cchen-vertica

config/manifests/bases/verticadb-operator.clusterserviceversion.yaml

@@ -1266,6 +1266,15 @@ spec:
         path: clientServerTLS
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
+      - description: |-
+          This field defines the common-name that should be required for the TLS certificate of this TLS secret.
+          The operator will validate that your certificate contains this value in the common-name field.
+          If not specified, it will use the Vertica DB admin username, defined by annotation vertica.com/superuser-name.
+        displayName: Common Name
+        path: clientServerTLS.commonName
+        x-descriptors:
+        - urn:alm:descriptor:com.tectonic.ui:text
+        - urn:alm:descriptor:com.tectonic.ui:advanced
       - description: |-
           This field configures the Vertica's connection mode for HTTPS/NMA or client-server TLS.
           Choose one of the following TLSMODEs, listed in ascending security:
@@ -1278,7 +1287,11 @@ spec:
         displayName: Mode
         path: clientServerTLS.mode
         x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:hidden
+        - urn:alm:descriptor:com.tectonic.ui:select:disable
+        - urn:alm:descriptor:com.tectonic.ui:select:enable
+        - urn:alm:descriptor:com.tectonic.ui:select:TRY_VERIFY
+        - urn:alm:descriptor:com.tectonic.ui:select:VERIFY_CA
+        - urn:alm:descriptor:com.tectonic.ui:select:VERIFY_FULL
       - description: |-
           A secret that contains the TLS credentials; this can be used either by Vertica's
           embedded https service and node management agent (NMA) or to authenticate Vertica
@@ -1404,6 +1417,15 @@ spec:
         path: httpsNMATLS
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
+      - description: |-
+          This field defines the common-name that should be required for the TLS certificate of this TLS secret.
+          The operator will validate that your certificate contains this value in the common-name field.
+          If not specified, it will use the Vertica DB admin username, defined by annotation vertica.com/superuser-name.
+        displayName: Common Name
+        path: httpsNMATLS.commonName
+        x-descriptors:
+        - urn:alm:descriptor:com.tectonic.ui:text
+        - urn:alm:descriptor:com.tectonic.ui:advanced
       - description: |-
           This field configures the Vertica's connection mode for HTTPS/NMA or client-server TLS.
           Choose one of the following TLSMODEs, listed in ascending security:
@@ -1416,7 +1438,11 @@ spec:
         displayName: Mode
         path: httpsNMATLS.mode
         x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:hidden
+        - urn:alm:descriptor:com.tectonic.ui:select:disable
+        - urn:alm:descriptor:com.tectonic.ui:select:enable
+        - urn:alm:descriptor:com.tectonic.ui:select:TRY_VERIFY
+        - urn:alm:descriptor:com.tectonic.ui:select:VERIFY_CA
+        - urn:alm:descriptor:com.tectonic.ui:select:VERIFY_FULL
       - description: |-
           A secret that contains the TLS credentials; this can be used either by Vertica's
           embedded https service and node management agent (NMA) or to authenticate Vertica
@@ -1573,8 +1599,9 @@ spec:
           When set, the secret must have the following keys defined: tls.key,
           tls.crt and ca.crt.  To store this secret outside of Kubernetes, you can
           use a secret path reference prefix, such as gsm://. Everything after the
-          prefix is the name of the secret in the service you are storing.
-          This field has been deprecated. HTTPSNMATLSSecret field is the replacement.
+          prefix is the name of the secret in the service you are storing. Once
+          TLS authentication is enabled, this secret will be ignored; HTTPSNMATLS.secret
+          will be used instead.
         displayName: NMATLSSecret
         path: nmaTLSSecret
         x-descriptors:
@@ -1605,6 +1632,8 @@ spec:
           All incoming connections to the subclusters will be routed through the proxy pods
         displayName: Proxy
         path: proxy
+        x-descriptors:
+        - urn:alm:descriptor:com.tectonic.ui:advanced
       - description: The docker image name that contains the Vertica proxy server.
         displayName: Image
         path: proxy.image
@@ -1729,7 +1758,7 @@ spec:
           Indicates the type of subcluster in a sandbox. Valid values are: primary,
           secondary. Types are case-sensitive.
           You must have at least one primary subcluster in the sandbox.
-          If type is omitted, it will default to a primary.
+          If type is omitted, it will default to secondary.
         displayName: Type
         path: sandboxes[0].subclusters[0].type
         x-descriptors:
@@ -2291,6 +2320,13 @@ spec:
       - description: Conditions for VerticaDB
         displayName: Conditions
         path: conditions
+      - description: |-
+          Deployment method used to operate the database.
+          Determined by the "vertica.com/vcluster-ops" annotation:
+            - "true" → use "vclusterops"
+            - any other value → use "admintools".
+        displayName: Deployment Method
+        path: deploymentMethod
       - description: The details about the last created restore point
         displayName: Restore Point
         path: restorePoint