CA and Client x509 generation is currently manual about k8s-dev-helm HOT 5 CLOSED

Added cert-manger in ac700c6

from k8s-dev-helm.

https://cert-manager.readthedocs.io/en/latest/index.html

from k8s-dev-helm.

You can now create a Certificate object and it will create a k8s secret with a signed public and private key from the cert-manager root ca

from k8s-dev-helm.

This will allow the CA key pair to be generate once, stored in a secure remote location accessible to the kubernetes cluster, and used to generate key pairs on both the client and server side.

One option would be to use KMS or S3

from k8s-dev-helm.

Cert is now created locally. Encrypted using an existing KMS key and then uploaded to an existing S3 bucket. The TF manifests created a script which pulls down the encrypted private key and then decrypts it using IAM policy attached via TF. Public key is included as plaintext in TF

from k8s-dev-helm.