Kubernetes deployments

Stacks can now target Kubernetes. A deployment runs your stack as pods in one namespace of the customer's cluster, on-prem or in EKS, GKE, or AKS:

alien onboard customer-2 --platforms kubernetes

The customer's admin installs one Helm chart from the deployment portal. It runs the Operator, which connects out to Alien and applies every release after that. Nobody runs helm upgrade, and nothing in the cluster accepts inbound connections.

Frozen resources map to infrastructure the customer already runs. The admin binds them in values.yaml:

infrastructure:
  files:
    type: storage
    service: s3
    bucketName: customer-2-files

• New clusters: the portal can create an EKS cluster with CloudFormation or Terraform, or a GKE or AKS cluster with Terraform
• PostgreSQL and named endpoints: bind any PostgreSQL the customer provides, and expose named endpoints
• Existing nodes: compute pools schedule onto the cluster's own capacity by CPU architecture
• Logs: logCollector.mode reads Pod logs through the Kubernetes API or runs a Fluent Bit DaemonSet
• Registration: each deployment reports its Helm release name

Read the docs →