Helm chart deploying the cloudify-services stack, including the following services:

• api-service
• composer-backend
• composer-frontend
• execution-scheduler
• fileserver
• mgmtworker
• nginx
• postgresql
• prometheus
• rabbitmq
• rest-service
• stage-backend
• stage-frontend

• Helm installed >=3.7 (https://helm.sh/docs/intro/install/).
• AWS CLI tool installed (https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html).
• Running Kubernetes cluster.
• Sufficient resources on Kubernetes worker nodes.
• Access to ECR registry with helm chart package.
• Cloudify Services valid license.

1. Deployment of Cloudify services

2. (Optional) Ensure UI access to the manager upon installation

3. (Optional) Extra configuration options

4. Uninstallation of helm charts

This step isn't necessary but can be useful if you want to get default values.yaml file for customize it.

• In case you don't have Git installed - https://github.com/git-guides/install-git

$ git clone https://github.com/cloudify-cosmo/cloudify-helm.git && cd cloudify-helm

You need to have installed AWS CLI tool and have access to "cloudify-automation" AWS account (AWS account ID: 163877087245). Then you need to execute following for get ECR temporary credentials and authenticate helm in it:

$ aws --profile cloudify-automation ecr get-login-password --region eu-west-1 | helm registry login --username AWS --password-stdin 163877087245.dkr.ecr.eu-west-1.amazonaws.com

You can use k8s ingress for expose UI outside the k8s cluster. Make sure you have one of the ingress controllers installed and confiogured inside your k8s cluster.

Example of the "ingress" configuration section in the values.yaml file:

ingress:
  enabled: true
  host: cloudify-services.example.com
  ingressClassName: alb
  annotations:
    alb.ingress.kubernetes.io/target-type: "ip"
    alb.ingress.kubernetes.io/scheme: "internal"
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}]'

In this example we using "alb" ingress class (provided by "AWS Load Balancer Controller), which creates private Application Load Balancer, listening on port 80/HTTP and forwarding all the traffic for host "cloudify-services.example.com" to cloudify-services stack.

$ helm install cloudify-services oci://163877087245.dkr.ecr.eu-west-1.amazonaws.com/cloudify-services-helm --version 0.1.0 -f VALUES_FILE -n NAMESPACE

When deploying on an IPv6-only cluster, additional settings must be applied to make RabbitMQ compatible. See values-ipv6.yaml for the changed parameters, or use this values file directly when installing the chart.

Remember that when using an IPv6 cluster, the ingress controller must support IPv6 as well.

There's several components you might want to scale up:

• RabbitMQ: the RabbitMQ chart provides out-of-the-box clustering, and the amount of replicas can be controlled via the rabbitmq.replicaCount setting.
• PostgreSQL: the PostgreSQL chart allows primary/replica replication (active/passive replication scheme with read replicas). To enable it, set postgresql.architecture to replication. When doing so, point the DB clients at the DB primary by setting db.host to postgresql-primary (read replicas are unused by Cloudify).
• Management worker: set mgmtworker.replicas to a number higher than 1, to start multiple mgmtworker instances, allowing better operation concurrency.

For an example of a scaled-up deployment, see the scaled-up-values.yaml example values file.

Uninstall helm release:

$ helm uninstall cloudify-services -n NAMESPACE