Fewer long-lived keys
CloudFormation stacks, Helm values, and machines no longer hold a key that never expires. Each gets a code that expires, and what runs in the environment trades it for its own short-lived key and renews that key itself.
- AWS CloudFormation: a new stack holds a deployment ID and a one-use code, never a token. An older stack moves over with one update from the portal's update link.
- Kubernetes:
values.yamlholds a one-use, one-hour enrollment code. The Operator trades it for its own key on first start, so a laterhelm upgradewith the expired code is fine. - Kubernetes with Terraform: for a new install on EKS, GKE, or AKS,
TF_VAR_tokenis a one-use setup key that expires after two hours. The admin issues a new one in the portal with Issue a new setup key before each later apply. - Deploy CLI reruns on Kubernetes: the admin runs the same command again without a token. The CLI gets a 15-minute key from the Operator through
kubectl exec, and never saves it. - Machines: cloud machines use one-hour sessions. Machines you run yourself join with a join command, then keep a key they replace every day.
- Containers on machines get their commands credential from the machine's session instead of a deployment token.