| Table of Contents |
|---|
...
- Do a describe of the pod using command kubectl describe pod <pod-name>, to ensure the Init Container section is presented as your defined in your yaml template.
If it does not exist, it is possible that your Kubernetes version supports a different format for the init-containers:
init-containers syntax supported by Kubernetes 1.5, 1.6 and 1.7 and not supported by Kubernetes 1.8 and greater initContainers syntax supported from Kubernetes 1.6 and greater Init container is defined under
spec.template.metadata.annotations."pod.beta.kubernetes.io/init-containers
Code Block language xml title An example of init container by beta annotation linenumbers true collapse true apiVersion: apps/v1beta1 kind: StatefulSet metadata: name: sdnc ... spec: ... template: metadata: ... annotations: pod.beta.kubernetes.io/init-containers: '[ { "args": [ "--container-name", "sdnc-db-container" ], "command": [ "/root/ready.py" ], "env": [ { "name": "NAMESPACE", "valueFrom": { "fieldRef": { "apiVersion": "v1", "fieldPath": "metadata.namespace" } } } ], "image": "{{ .Values.image.readiness }}", "imagePullPolicy": "{{ .Values.pullPolicy }}", "name": "sdnc-readiness" } ]' spec: containers: ...Init container is defined under spec.template.spec.initContainers
Code Block language xml title An example of init container by spec.initContainers linenumbers true collapse true apiVersion: apps/v1beta1 kind: StatefulSet metadata: name: sdnc ... spec: ... template: ... spec: initContainers: - command: - /root/ready.py - "--container-name" - "sdnc-db-container" env: - name: NAMESPACE valueFrom: fieldRef: apiVersion: v1 fieldPath: metadata.namespace image: "{{ .Values.image.readiness }}" imagePullPolicy: {{ .Values.pullPolicy }} name: sdnc-readiness containers: ...
...
...