List of common problems we’ve encountered and their solutions.
Chamber expects to find a KMS key with alias parameter_store_key
Quick fix: helm delete --purge the release and try again.
If your getting a TLS error for a service leveraging kube-lego, then try deleting the TLS secret to let kube-lego generate a new one.
Make sure your TLS certificates match the kiam-server hostname and that no orphaned iptable rules exist for legacy IAM metadata service such as kube2iam
Assuming roles are properly configured, this usually happens due to AWS API rate limiting.
Ensure scheme is http and that service does not return a 301 or 302 redirect to an https:// scheme.
Fix is to most likely increase the number of worker nodes so they are evenly spread across all availability zones.
Make sure that your GitHub SSH public key has been added to your geodesic ssh-agent
This is most likely caused by not setting the kubectl context to use the kops cluster.
This usually happens due to time drift when running under Docker for Mac