-
Notifications
You must be signed in to change notification settings - Fork 71
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
feat: report both old and new styles of node OS information #479
Conversation
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## master #479 +/- ##
==========================================
+ Coverage 42.91% 44.02% +1.11%
==========================================
Files 50 50
Lines 5735 5944 +209
==========================================
+ Hits 2461 2617 +156
- Misses 3017 3071 +54
+ Partials 257 256 -1
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
I'd rather go with just "beta.kubernetes.io/os" label, the current k8s API version of VK is still low. |
Hi @Fei-Guo The The labels on node defines the capabilities for a node. When we are in such kind of label deprecation, the node should declare it supports both labels for best compatibility, so that the users who want to schedule pods to VK can choose any one of the following:
When we only provide |
Thanks. I think the "beta.kubernetes.io/os" label already exists in vNode object. We just miss the ""kubernetes.io/os" label. Since Heba is working on remove node cli dependency from azure-aci repo and I think she can add the new label in the change. |
@allxiao may I ask you to rebase your PR? |
5cc7a1d
to
1a8c7cf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
To maintain compatibility, the virtual node should declare both styles of OS information, so that the Pod being scheduled to the virtual node can choose any of the following options
beta.kubernetes.io/os
nodeSelectorkubernetes.io/os
nodeSelector before thebeta
one is dropped completely from API serverCurrently, we only report
beta.kubernetes.io/os
, which will block the users from working on the nodeSelector migration.