add args in registrationConfiguration for operator APIs

Signed-off-by: ZhiweiYin <[email protected]>

Author: zhiweiyin318

operator/v1/0000_00_operator.open-cluster-management.io_klusterlets.crd.yaml

@@ -93,6 +93,11 @@ spec:
                   description: RegistrationConfiguration contains the configuration of registration
                   type: object
                   properties:
+                    args:
+                      description: Args is list of valid flag arguments that are accepted in registration. The format is only allowed --arg1=xxx.
+                      type: array
+                      items:
+                        type: string
                     featureGates:
                       description: "FeatureGates represents the list of feature gates for registration If it is set empty, default feature gates will be used. If it is set, featuregate/Foo is an example of one item in FeatureGates:   1. If featuregate/Foo does not exist, registration-operator will discard it   2. If featuregate/Foo exists and is false by default. It is now possible to set featuregate/Foo=[false|true]   3. If featuregate/Foo exists and is true by default. If a cluster-admin upgrading from 1 to 2 wants to continue having featuregate/Foo=false,  \the can set featuregate/Foo=false before upgrading. Let's say the cluster-admin wants featuregate/Foo=false."
                       type: array

operator/v1/0000_01_operator.open-cluster-management.io_clustermanagers.crd.yaml

@@ -124,6 +124,11 @@ spec:
                   description: RegistrationConfiguration contains the configuration of registration
                   type: object
                   properties:
+                    args:
+                      description: Args is list of valid flag arguments that are accepted in registration. The format is only allowed --arg1=xxx.
+                      type: array
+                      items:
+                        type: string
                     featureGates:
                       description: "FeatureGates represents the list of feature gates for registration If it is set empty, default feature gates will be used. If it is set, featuregate/Foo is an example of one item in FeatureGates:   1. If featuregate/Foo does not exist, registration-operator will discard it   2. If featuregate/Foo exists and is false by default. It is now possible to set featuregate/Foo=[false|true]   3. If featuregate/Foo exists and is true by default. If a cluster-admin upgrading from 1 to 2 wants to continue having featuregate/Foo=false,  \the can set featuregate/Foo=false before upgrading. Let's say the cluster-admin wants featuregate/Foo=false."
                       type: array

operator/v1/0001_00_operator.open-cluster-management.io_klusterlets.crd.yaml

@@ -93,6 +93,11 @@ spec:
               description: RegistrationConfiguration contains the configuration of registration
               type: object
               properties:
+                args:
+                  description: Args is list of valid flag arguments that are accepted in registration. The format is only allowed --arg1=xxx.
+                  type: array
+                  items:
+                    type: string
                 featureGates:
                   description: "FeatureGates represents the list of feature gates for registration If it is set empty, default feature gates will be used. If it is set, featuregate/Foo is an example of one item in FeatureGates:   1. If featuregate/Foo does not exist, registration-operator will discard it   2. If featuregate/Foo exists and is false by default. It is now possible to set featuregate/Foo=[false|true]   3. If featuregate/Foo exists and is true by default. If a cluster-admin upgrading from 1 to 2 wants to continue having featuregate/Foo=false,  \the can set featuregate/Foo=false before upgrading. Let's say the cluster-admin wants featuregate/Foo=false."
                   type: array

operator/v1/types.go

@@ -69,6 +69,10 @@ type RegistrationConfiguration struct {
 	//  	he can set featuregate/Foo=false before upgrading. Let's say the cluster-admin wants featuregate/Foo=false.
 	// +optional
 	FeatureGates []FeatureGate `json:"featureGates,omitempty"`
+
+	// Args is list of valid flag arguments that are accepted in registration.
+	// The format is only allowed --arg1=xxx.
+	Args []string `json:"args,omitempty"`
 }
 
 type FeatureGate struct {