eksctl icon indicating copy to clipboard operation
eksctl copied to clipboard

[Bug] "non-functional in v1.16+; use the "priorityClassName" field instead" warning during eksctl deployment

Open jackylu0124 opened this issue 1 year ago • 2 comments

What were you trying to accomplish?

I am trying to create a EKS cluster with the eksctl create cluster -f cluster.yaml command (see my cluster.yaml file content in the reproduction section).

What happened?

I saw the following warning in the log during cluster creation:

4400 warnings.go:70] spec.template.metadata.annotations[scheduler.alpha.kubernetes.io/critical-pod]: non-functional in v1.16+; use the "priorityClassName" field instead

How to reproduce it?

Run eksctl create cluster -f cluster.yaml on the following config file (cluster.yaml):

apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig

metadata:
  name: test-cluster-001
  region: us-east-1

vpc:
  autoAllocateIPv6: false
  cidr: 10.108.0.0/16

managedNodeGroups:
- name: ng-0
  desiredCapacity: 1
  maxSize: 1
  minSize: 1
  instanceType: g4dn.xlarge
  volumeSize: 50

Logs

Warning log:

4400 warnings.go:70] spec.template.metadata.annotations[scheduler.alpha.kubernetes.io/critical-pod]: non-functional in v1.16+; use the "priorityClassName" field instead

Anything else we need to know?

My OS is Windows 11, and I used the downloaded binary. Versions

$ eksctl info
eksctl version: 0.175.0
kubectl version: v1.27.2
OS: windows

jackylu0124 avatar Apr 18 '24 23:04 jackylu0124

Hello jackylu0124 :wave: Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website

github-actions[bot] avatar Apr 18 '24 23:04 github-actions[bot]

Hi @jackylu0124 - we only keep scheduler.alpha.kubernetes.io/critical-pod annotation for backwards compatibility purposes. https://github.com/eksctl-io/eksctl/blob/02294680c0d7fb5843383c1aff654bf07729870d/pkg/addons/assets/nvidia-device-plugin.yaml#L28-L31

But the daemonset also has priorityClassName configured. https://github.com/eksctl-io/eksctl/blob/02294680c0d7fb5843383c1aff654bf07729870d/pkg/addons/assets/nvidia-device-plugin.yaml#L43-L47

TiberiuGC avatar Apr 26 '24 16:04 TiberiuGC

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar Jun 15 '24 01:06 github-actions[bot]

This issue was closed because it has been stalled for 5 days with no activity.

github-actions[bot] avatar Jun 21 '24 01:06 github-actions[bot]