When testing the "on-your-own" portion of the workshop today, I noticed that the AWS CLI, although installed, wasn't the default CLI until I re-sourced my .bashrc. This causes the aws eks update-kubeconfig command (that's run after the cluster is installed) to write an invalid context to our config file (it uses the incorrect API version -- alpha1 vs. beta1).
tobuck-aws
commented
1 year ago
When testing the "on-your-own" portion of the workshop today, I noticed that the AWS CLI, although installed, wasn't the default CLI until I re-sourced my .bashrc. This causes the
aws eks update-kubeconfigcommand (that's run after the cluster is installed) to write an invalid context to our config file (it uses the incorrect API version -- alpha1 vs. beta1).