...
- An initContainer that waits for the other components that the service component needs, such as AAF and Consul In the current Cloudify implementation, we can guarantee that a service component won't be deployed before these other components are ready. We can't make that guarantee for Helm.
- An initContainer that puts the component configuration into Consul (see next section for details).
The configuration parameters for the component (the image name, log directory, TLS parameters) currently come from the Cloudify blueprint–either directly or through an inputs file. With Helm deployment, these parameters will move into the values.yaml file for the component.
Because there is a common structure to the Kubernetes Deployments for all service components, we should create a Helm template for a DCAE service component Deployment. The Deployment will be configured for a specific service component through the parameters in the values.yaml file. The OOM common Helm templates do not include a template for a Deployment, but they do include templates for various parts of a deployment (for instance, a logging sidecar). The DCAE service component Deployment template should use OOM common templates wherever possible.
Setting up the component configuration in Consul
...