fix: new clusterrole not created

Author: cjc7373

apis/apps/v1/cluster_types.go

@@ -439,7 +439,7 @@ type ClusterComponentSpec struct {
 	// it will also be bound to a default cluster role named
 	// "kubeblocks-cluster-pod-role", which is installed together with KubeBlocks.
 	//
-	// Before KubeBlocks 1.0.2, the automatically created serviceaccount is named "kb-{componentdefinition.name}".
+	// Before KubeBlocks 1.1, the automatically created serviceaccount is named "kb-{componentdefinition.name}".
 	// To reduce unintended pod restart, old pods still use old serviceaccount. New serviceaccount will be used
 	// when a workload has been restarted.
 	//

apis/apps/v1/component_types.go

@@ -202,7 +202,7 @@ type ComponentSpec struct {
 	// it will also be bound to a default cluster role named
 	// "kubeblocks-cluster-pod-role", which is installed together with KubeBlocks.
 	//
-	// Before KubeBlocks 1.0.2, the automatically created serviceaccount is named "kb-{componentdefinition.name}".
+	// Before KubeBlocks 1.1, the automatically created serviceaccount is named "kb-{componentdefinition.name}".
 	// To reduce unintended pod restart, old pods still use old serviceaccount. New serviceaccount will be used
 	// when a workload has been restarted.
 	//

config/crd/bases/apps.kubeblocks.io_clusters.yaml

@@ -4178,7 +4178,7 @@ spec:
                         "kubeblocks-cluster-pod-role", which is installed together with KubeBlocks.
 
 
-                        Before KubeBlocks 1.0.2, the automatically created serviceaccount is named "kb-{componentdefinition.name}".
+                        Before KubeBlocks 1.1, the automatically created serviceaccount is named "kb-{componentdefinition.name}".
                         To reduce unintended pod restart, old pods still use old serviceaccount. New serviceaccount will be used
                         when a workload has been restarted.
 
@@ -15569,7 +15569,7 @@ spec:
                             "kubeblocks-cluster-pod-role", which is installed together with KubeBlocks.
 
 
-                            Before KubeBlocks 1.0.2, the automatically created serviceaccount is named "kb-{componentdefinition.name}".
+                            Before KubeBlocks 1.1, the automatically created serviceaccount is named "kb-{componentdefinition.name}".
                             To reduce unintended pod restart, old pods still use old serviceaccount. New serviceaccount will be used
                             when a workload has been restarted.
 

config/crd/bases/apps.kubeblocks.io_components.yaml

@@ -4404,7 +4404,7 @@ spec:
                   "kubeblocks-cluster-pod-role", which is installed together with KubeBlocks.
 
 
-                  Before KubeBlocks 1.0.2, the automatically created serviceaccount is named "kb-{componentdefinition.name}".
+                  Before KubeBlocks 1.1, the automatically created serviceaccount is named "kb-{componentdefinition.name}".
                   To reduce unintended pod restart, old pods still use old serviceaccount. New serviceaccount will be used
                   when a workload has been restarted.
 

controllers/apps/componentdefinition_controller.go

@@ -75,12 +75,10 @@ func (r *ComponentDefinitionReconciler) Reconcile(ctx context.Context, req ctrl.
 	rctx := intctrlutil.RequestCtx{
 		Ctx:      ctx,
 		Req:      req,
-		Log:      log.FromContext(ctx).WithValues("component", req.NamespacedName),
+		Log:      log.FromContext(ctx).WithValues("componentdefinition", req.NamespacedName),
 		Recorder: r.Recorder,
 	}
 
-	rctx.Log.V(1).Info("reconcile", "component", req.NamespacedName)
-
 	cmpd := &appsv1.ComponentDefinition{}
 	if err := r.Client.Get(rctx.Ctx, rctx.Req.NamespacedName, cmpd); err != nil {
 		return intctrlutil.CheckedRequeueWithError(err, rctx.Log, "")
@@ -112,11 +110,6 @@ func (r *ComponentDefinitionReconciler) reconcile(rctx intctrlutil.RequestCtx,
 		return *res, err
 	}
 
-	if cmpd.Status.ObservedGeneration == cmpd.Generation &&
-		slices.Contains([]appsv1.Phase{appsv1.AvailablePhase}, cmpd.Status.Phase) {
-		return intctrlutil.Reconciled()
-	}
-
 	if err = r.validate(r.Client, rctx, cmpd); err != nil {
 		if err1 := r.unavailable(r.Client, rctx, cmpd, err); err1 != nil {
 			return intctrlutil.CheckedRequeueWithError(err1, rctx.Log, "")

deploy/helm/crds/apps.kubeblocks.io_clusters.yaml

@@ -4178,7 +4178,7 @@ spec:
                         "kubeblocks-cluster-pod-role", which is installed together with KubeBlocks.
 
 
-                        Before KubeBlocks 1.0.2, the automatically created serviceaccount is named "kb-{componentdefinition.name}".
+                        Before KubeBlocks 1.1, the automatically created serviceaccount is named "kb-{componentdefinition.name}".
                         To reduce unintended pod restart, old pods still use old serviceaccount. New serviceaccount will be used
                         when a workload has been restarted.
 
@@ -15569,7 +15569,7 @@ spec:
                             "kubeblocks-cluster-pod-role", which is installed together with KubeBlocks.
 
 
-                            Before KubeBlocks 1.0.2, the automatically created serviceaccount is named "kb-{componentdefinition.name}".
+                            Before KubeBlocks 1.1, the automatically created serviceaccount is named "kb-{componentdefinition.name}".
                             To reduce unintended pod restart, old pods still use old serviceaccount. New serviceaccount will be used
                             when a workload has been restarted.
 

deploy/helm/crds/apps.kubeblocks.io_components.yaml

@@ -4404,7 +4404,7 @@ spec:
                   "kubeblocks-cluster-pod-role", which is installed together with KubeBlocks.
 
 
-                  Before KubeBlocks 1.0.2, the automatically created serviceaccount is named "kb-{componentdefinition.name}".
+                  Before KubeBlocks 1.1, the automatically created serviceaccount is named "kb-{componentdefinition.name}".
                   To reduce unintended pod restart, old pods still use old serviceaccount. New serviceaccount will be used
                   when a workload has been restarted.
 

docs/developer_docs/api-reference/cluster.md

@@ -720,7 +720,7 @@ with other Kubernetes resources, such as modifying Pod labels or sending events.
 <code>policyRules</code> field. If needed (currently this means if any lifecycleAction is enabled),
 it will also be bound to a default cluster role named
 &ldquo;kubeblocks-cluster-pod-role&rdquo;, which is installed together with KubeBlocks.</p>
-<p>Before KubeBlocks 1.0.2, the automatically created serviceaccount is named &ldquo;kb-&#123;componentdefinition.name&#125;&rdquo;.
+<p>Before KubeBlocks 1.1, the automatically created serviceaccount is named &ldquo;kb-&#123;componentdefinition.name&#125;&rdquo;.
 To reduce unintended pod restart, old pods still use old serviceaccount. New serviceaccount will be used
 when a workload has been restarted.</p>
 <p>If the field is not empty, the specified ServiceAccount will be used, and KubeBlocks will not
@@ -3362,7 +3362,7 @@ with other Kubernetes resources, such as modifying Pod labels or sending events.
 <code>policyRules</code> field. If needed (currently this means if any lifecycleAction is enabled),
 it will also be bound to a default cluster role named
 &ldquo;kubeblocks-cluster-pod-role&rdquo;, which is installed together with KubeBlocks.</p>
-<p>Before KubeBlocks 1.0.2, the automatically created serviceaccount is named &ldquo;kb-&#123;componentdefinition.name&#125;&rdquo;.
+<p>Before KubeBlocks 1.1, the automatically created serviceaccount is named &ldquo;kb-&#123;componentdefinition.name&#125;&rdquo;.
 To reduce unintended pod restart, old pods still use old serviceaccount. New serviceaccount will be used
 when a workload has been restarted.</p>
 <p>If the field is not empty, the specified ServiceAccount will be used, and KubeBlocks will not
@@ -6812,7 +6812,7 @@ with other Kubernetes resources, such as modifying Pod labels or sending events.
 <code>policyRules</code> field. If needed (currently this means if any lifecycleAction is enabled),
 it will also be bound to a default cluster role named
 &ldquo;kubeblocks-cluster-pod-role&rdquo;, which is installed together with KubeBlocks.</p>
-<p>Before KubeBlocks 1.0.2, the automatically created serviceaccount is named &ldquo;kb-&#123;componentdefinition.name&#125;&rdquo;.
+<p>Before KubeBlocks 1.1, the automatically created serviceaccount is named &ldquo;kb-&#123;componentdefinition.name&#125;&rdquo;.
 To reduce unintended pod restart, old pods still use old serviceaccount. New serviceaccount will be used
 when a workload has been restarted.</p>
 <p>If the field is not empty, the specified ServiceAccount will be used, and KubeBlocks will not