Merge pull request #12479 from sbueringer/pr-follow-up-v1beta1-rename

🌱 Remove old godoc comment, remove unnecessary cast in KCP

Author: k8s-ci-robot

api/controlplane/kubeadm/v1beta2/kubeadm_control_plane_types.go

@@ -495,7 +495,6 @@ type KubeadmControlPlaneMachineTemplate struct {
 	// This field can be used e.g. to instruct the machine controller to include in the computation for Machine's ready
 	// computation a condition, managed by an external controllers, reporting the status of special software/hardware installed on the Machine.
 	//
-	// NOTE: This field is considered only for computing v1beta2 conditions.
 	// +optional
 	// +listType=map
 	// +listMapKey=conditionType

api/core/v1beta2/cluster_types.go

@@ -639,7 +639,6 @@ type ControlPlaneTopology struct {
 	//
 	// If this field is not defined, readinessGates from the corresponding ControlPlaneClass will be used, if any.
 	//
-	// NOTE: This field is considered only for computing v1beta2 conditions.
 	// NOTE: Specific control plane provider implementations might automatically extend the list of readinessGates;
 	// e.g. the kubeadm control provider adds ReadinessGates for the APIServerPodHealthy, SchedulerPodHealthy conditions, etc.
 	// +optional
@@ -749,7 +748,6 @@ type MachineDeploymentTopology struct {
 	//
 	// If this field is not defined, readinessGates from the corresponding MachineDeploymentClass will be used, if any.
 	//
-	// NOTE: This field is considered only for computing v1beta2 conditions.
 	// +optional
 	// +listType=map
 	// +listMapKey=conditionType

api/core/v1beta2/clusterclass_types.go

@@ -204,7 +204,6 @@ type ControlPlaneClass struct {
 	// This field can be used e.g. to instruct the machine controller to include in the computation for Machine's ready
 	// computation a condition, managed by an external controllers, reporting the status of special software/hardware installed on the Machine.
 	//
-	// NOTE: This field is considered only for computing v1beta2 conditions.
 	// NOTE: If a Cluster defines a custom list of readinessGates for the control plane,
 	// such list overrides readinessGates defined in this field.
 	// NOTE: Specific control plane provider implementations might automatically extend the list of readinessGates;
@@ -335,7 +334,6 @@ type MachineDeploymentClass struct {
 	// This field can be used e.g. to instruct the machine controller to include in the computation for Machine's ready
 	// computation a condition, managed by an external controllers, reporting the status of special software/hardware installed on the Machine.
 	//
-	// NOTE: This field is considered only for computing v1beta2 conditions.
 	// NOTE: If a Cluster defines a custom list of readinessGates for a MachineDeployment using this MachineDeploymentClass,
 	// such list overrides readinessGates defined in this field.
 	// +optional

api/core/v1beta2/machine_types.go

@@ -439,7 +439,6 @@ type MachineSpec struct {
 	// Another example are external controllers, e.g. responsible to install special software/hardware on the Machines;
 	// they can include the status of those components with a new condition and add this condition to ReadinessGates.
 	//
-	// NOTE: This field is considered only for computing v1beta2 conditions.
 	// NOTE: In case readinessGates conditions start with the APIServer, ControllerManager, Scheduler prefix, and all those
 	// readiness gates condition are reporting the same message, when computing the Machine's Ready condition those
 	// readinessGates will be replaced by a single entry reporting "Control plane components: " + message.