eks-anywhere
eks-anywhere copied to clipboard
aws
Run Amazon EKS on your own infrastructure 🚀
When provisioning an EKS-A cluster using the bare metal provider we deploy the Tinkerbell stack. The stack includes `boots`, a component that requires L2 connectivity to deal in broadcast traffic....
**What happened**: **Scenario:** I have a bare metal cluster. 1 control plane node and 3 worker nodes. One worker node fails. It becomes "NotReady" and triggers CAPI to attempt to...
**What happened**: Tring to deploy EKS anywhere cluster on bare metal, using created with the image-builder ubuntu image. Cluster hangs on "Creating new workload cluster". Thinkerbell boot finishes successfully. OS...
*Issue #, if available:* https://github.com/aws/eks-anywhere/issues/8517 *Description of changes:* Added verbiage about infra-specific commands capc-system vs capv-system (CloudStack vs vSphere - for example) *Testing (if applicable):* *Documentation added/planned (if applicable):* By...
**What happened**: N/A - troubleshooting may not be clear when the examples provide "capv-system" and they user is deploying using another provider ("capc-system" for CloudStack, as an example) **What you...
Currently, EKS Anywhere uses secrets in many places. The Bare metal provider has BMC credentials in the hardware.csv file, vSphere provider has vSphere credentials in the cluster config yaml file,...
**What would you like to be added**: Currently versioning of curated package bundle is not allowed because of by default latest curated package bundle gets activated on the cluster. I...
*Issue #, if available:* I believe the vSphere Preparation doc may be inconsistent. If this is a suggestion to allow a different value, then it should indicate that if you...
*Issue #, if available:* *Description of changes:* *Testing (if applicable):* *Documentation added/planned (if applicable):* By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this...
