feat: add initContainers support to RisingWaveNodePodTemplateSpec

Author: stex-docto

apis/risingwave/v1alpha1/risingwave_node_group.go

@@ -290,6 +290,15 @@ type RisingWaveNodePodTemplateSpec struct {
 	// Additional containers to run in the same Pod. The containers will be appended to the Pod's containers array in order.
 	// + optional
 	AdditionalContainers []corev1.Container `json:"additionalContainers,omitempty"`
+
+	// List of initialization containers belonging to the pod.
+	// Init containers are executed in order prior to containers being started. If any
+	// init container fails, the pod is considered to have failed and is handled according
+	// to its restartPolicy. The name for an init container or normal container must be
+	// unique among all containers.
+	// More info: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/
+	// +optional
+	InitContainers []corev1.Container `json:"initContainers,omitempty"`
 }
 
 // RisingWaveNodePodTemplate determines the Pod specs of a RisingWave node.

apis/risingwave/v1alpha1/zz_generated.deepcopy.go

@@ -3443,6 +3443,25 @@ This field is alpha-level and is only honored by servers that enable the UserNam
 <p>Additional containers to run in the same Pod. The containers will be appended to the Pod&rsquo;s containers array in order.</p>
 </td>
 </tr>
+<tr>
+<td>
+<code>initContainers</code><br/>
+<em>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.24/#container-v1-core">
+[]Kubernetes core/v1.Container
+</a>
+</em>
+</td>
+<td>
+<em>(Optional)</em>
+<p>List of initialization containers belonging to the pod.
+Init containers are executed in order prior to containers being started. If any
+init container fails, the pod is considered to have failed and is handled according
+to its restartPolicy. The name for an init container or normal container must be
+unique among all containers.
+More info: <a href="https://kubernetes.io/docs/concepts/workloads/pods/init-containers/">https://kubernetes.io/docs/concepts/workloads/pods/init-containers/</a></p>
+</td>
+</tr>
 </table>
 </td>
 </tr>
@@ -4012,6 +4031,25 @@ This field is alpha-level and is only honored by servers that enable the UserNam
 <p>Additional containers to run in the same Pod. The containers will be appended to the Pod&rsquo;s containers array in order.</p>
 </td>
 </tr>
+<tr>
+<td>
+<code>initContainers</code><br/>
+<em>
+<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.24/#container-v1-core">
+[]Kubernetes core/v1.Container
+</a>
+</em>
+</td>
+<td>
+<em>(Optional)</em>
+<p>List of initialization containers belonging to the pod.
+Init containers are executed in order prior to containers being started. If any
+init container fails, the pod is considered to have failed and is handled according
+to its restartPolicy. The name for an init container or normal container must be
+unique among all containers.
+More info: <a href="https://kubernetes.io/docs/concepts/workloads/pods/init-containers/">https://kubernetes.io/docs/concepts/workloads/pods/init-containers/</a></p>
+</td>
+</tr>
 </tbody>
 </table>
 <h3 id="risingwave.risingwavelabs.com/v1alpha1.RisingWaveS3Credentials">RisingWaveS3Credentials

config/crd/bases/risingwave.risingwavelabs.com_risingwaves.yaml

@@ -1714,6 +1714,7 @@ func newPodSpecFromNodeGroupTemplate(template *risingwavev1alpha1.RisingWaveNode
 		SetHostnameAsFQDN:             template.Spec.SetHostnameAsFQDN,
 		OS:                            template.Spec.OS,
 		HostUsers:                     template.Spec.HostUsers,
+		InitContainers:                template.Spec.InitContainers,
 	}
 
 	return podTemplateSpec