-
Notifications
You must be signed in to change notification settings - Fork 173
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
Determine cluster distribution server version & type using kubernetes API server version #2404
Determine cluster distribution server version & type using kubernetes API server version #2404
Conversation
a83b981
to
04eb779
Compare
04bbe75
to
8589611
Compare
Started Vanilla block pre-checkin pipeline... Build Number: 2198 |
/ok-to-test |
b9152ea
to
58433be
Compare
Started Vanilla block pre-checkin pipeline... Build Number: 2201 |
|
58433be
to
9e5d4c2
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.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chethanv28, divyenpatel The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
… API server version (kubernetes-sigs#2404) * Determine cluster distribution server version & type using kubernetes API server version * Exit the container if we are not able to fetch the k8s client * break the loop as soon as we find the distribution type
… API server version (kubernetes-sigs#2404) * Determine cluster distribution server version & type using kubernetes API server version * Exit the container if we are not able to fetch the k8s client * break the loop as soon as we find the distribution type
… API server version (kubernetes-sigs#2404) * Determine cluster distribution server version & type using kubernetes API server version * Exit the container if we are not able to fetch the k8s client * break the loop as soon as we find the distribution type
… during attach/detach. (#2573) * Determine cluster distribution server version & type using kubernetes API server version (#2404) * Determine cluster distribution server version & type using kubernetes API server version * Exit the container if we are not able to fetch the k8s client * break the loop as soon as we find the distribution type * skip adding node to cache during attach or detach operation (#2546) --------- Co-authored-by: Divyen Patel <divyenp@vmware.com>
…related to AttachVolumes and also the nodes cache fix during attach/detach. (#2561) * Determine cluster distribution server version & type using kubernetes API server version (#2404) * Determine cluster distribution server version & type using kubernetes API server version * Exit the container if we are not able to fetch the k8s client * break the loop as soon as we find the distribution type * skip adding node to cache during attach or detach operation (#2546) * Return volume path as part of ListVolumes response for migrated volumes (#2558) --------- Co-authored-by: Divyen Patel <divyenp@vmware.com> Co-authored-by: Aditya Kulkarni <adkulkarni@vmware.com>
What this PR does / why we need it:
This PR is attempting to set cluster distribution type based on the k8s API server version by fetching it from the k8s cluster.
This PR is still in-works. Please do not review.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #Testing done:
Here is a cluster with the cluster-distribution field set to empty string:
With the changes from this PR, the cluster distribution is set dynamically to Vanillak8s as the API server version is empty
Special notes for your reviewer:
Release note: