The following diagram illustrates the desired SDN-C cluster deployment (as described in ) from POD and SERVICE view, which will have:
See details from SDN-C DB (MySQL) Clustered Deployment.
You can use Rancher or kubeadm to deploy your Kubernetes cluster:
Usually, this is caused by init-container malfuntion. You can troubleshoot it by the following steps:
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
| Init container is defined under spec.template.spec.initContainers
|
When a pod is dead, Kubernetes automatically starts a new one to replace the dead pod.
Examples:
|
The source code is currently temporary shared through gerrit topic SDNC-163 until it is commited into gerrit.