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

eksctl-anywhere v0.19.0 doesn't honor custom machine template in the cluster config file #7816

Closed
ygao-armada opened this issue Mar 9, 2024 · 2 comments
Assignees

Comments

@ygao-armada
Copy link

ygao-armada commented Mar 9, 2024

What happened:

I try to createe EKS anywhere cluster for bare metal with following versions:

  • Admin Ubuntu 20.04
  • eksctl 0.173
  • eksctl-anywhere v0.19.0

While in old environments (eksctl-anywhere v0.18.2 and v0.18.7), everything works.
However, in new environment (eksctl-anywhere v0.19.0), I find the machine template in the cluster config is ignored, and the default template is used instead.
Here is the code piece of the config:

---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: TinkerbellMachineConfig
metadata:
  name: mgmt03-cp
spec:
  hardwareSelector:
    type: cp
  osFamily: ubuntu
  templateRef:
    kind: TinkerbellTemplateConfig
    name: mgmt03
  users:
  - name: ec2-user
    sshAuthorizedKeys:
    - ssh-rsa AAA...

---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: TinkerbellTemplateConfig
metadata:
  name: mgmt03
spec:
  template:
    global_timeout: 6000
    id: ""
    name: mgmt03
    tasks:
    - actions:
      - environment:
...

v0.19.2 has the same issue.

What you expected to happen:

custom machine template is used.

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

Anything else we need to know?:

Environment:

  • EKS Anywhere Release: v0.19.0 -- v0.19.2
  • EKS Distro Release:
@ygao-armada ygao-armada changed the title eksctl-anywhere v0.19.0 doesn't honor actionImage in the machine template eksctl-anywhere v0.19.0 doesn't honor custom machine template in the cluster config file Apr 10, 2024
@jacobweinstock
Copy link
Member

Hey @ygao-armada , thanks for the report. I will investigate and report back here!

@mitalipaygude
Copy link
Member

mitalipaygude commented Apr 11, 2024

Hello @ygao-armada, we are working on a fix for this issue and will have it out in the next patch release. Thank you for the report.

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