Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bare Metal] Workload cluster scale out CLI validations fails with generated ssh keys #7991

Open
jacobweinstock opened this issue Apr 15, 2024 · 0 comments
Assignees
Milestone

Comments

@jacobweinstock
Copy link
Member

jacobweinstock commented Apr 15, 2024

What happened:
I have a running workload cluster with 1 node in total. 1 control plane. When I create this cluster i did not define an SSH public key. As such, EKS Anywhere created one for me. When scaling up this workload cluster from 1 control plane node to 1 control plane by adding the following to the cluster yaml for the workload the eksctl anywhere cluster upgrade command fails.

The following was added to my successful 1 node cluster cluster.yaml:

workerNodeGroupConfigurations:
  - count: 1
    machineGroupRef:
      kind: TinkerbellMachineConfig
      name: workload-test-worker
    name: md-0

AND

apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: TinkerbellMachineConfig
metadata:
  name: workload-test-worker
spec:
  hardwareSelector:
    type: worker-wl
  osFamily: ubuntu
  templateRef: {}
  users:
  - name: ec2-user

I get the following error:

V0	❌ Validation failed	{"validation": "SSH Keys present", "error": "[workload-test-cp TinkerbellMachineConfig is invalid: it should contain at least one SSH key, workload-test-worker TinkerbellMachineConfig is invalid: it should contain at least one SSH key]", "remediation": "Please include at least one SSH key per machine config. If your keys were autogenerated during the create cluster operation, make sure you include them in your cluster config for all lifecycle operations"}
.
.
.
V0	❌ Validation failed	{"validation": "validate immutable fields", "error": "spec.Users[0].SshAuthorizedKeys[0] is immutable. Previous value ssh-rsa ... ,   New value ssh-rsa ... ", "remediation": ""}

What you expected to happen:
Once an SSH public key has been provided to a cluster, either by the user or auto-generated by EKSA, the CLI should not require me to provide them. The cluster already has them/knows about them. Just use them.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • EKS Anywhere Release: cli version v0.19.2
  • EKS Distro Release:
@jacobweinstock jacobweinstock changed the title [Bare Metal] Workload cluster scale out fails with generated ssh keys [Bare Metal] Workload cluster scale out CLI validations fails with generated ssh keys Apr 15, 2024
@sp1999 sp1999 self-assigned this Apr 29, 2024
@ndeksa ndeksa added this to the v0.21.0 milestone Jun 12, 2024
@ndeksa ndeksa modified the milestones: v0.21.0, v0.22.0 Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants