-
Notifications
You must be signed in to change notification settings - Fork 161
Update to use csi proxy beta #607
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
Conversation
a8b7683
to
441a01d
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.
Are we deploying the beta csi proxy in our CI cluster?
@@ -43,6 +43,7 @@ spec: | |||
# Don't change base image without changing pdImagePlaceholder in | |||
# test/k8s-integration/main.go | |||
image: gke.gcr.io/gcp-compute-persistent-disk-csi-driver-win | |||
imagePullPolicy: Always |
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.
We usually only set to always for dev environments where we're rebuilding the same image, but in general, we leave it unset (default)
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.
updated.
|
||
diskv1alpha1 "github.com/kubernetes-csi/csi-proxy/client/api/disk/v1alpha1" | ||
diskclientv1alpha1 "github.com/kubernetes-csi/csi-proxy/client/groups/disk/v1alpha1" | ||
diskv1beta1 "github.com/kubernetes-csi/csi-proxy/client/api/disk/v1beta1" |
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.
if we alias it to some common name, like "diskapi", then there's potentially less lines that need changing if we have to change api versions again
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.
updated. thanks!
diskv1alpha1 "github.com/kubernetes-csi/csi-proxy/client/api/disk/v1alpha1" | ||
diskclientv1alpha1 "github.com/kubernetes-csi/csi-proxy/client/groups/disk/v1alpha1" | ||
diskv1beta1 "github.com/kubernetes-csi/csi-proxy/client/api/disk/v1beta1" | ||
diskclientv1beta1 "github.com/kubernetes-csi/csi-proxy/client/groups/disk/v1beta1" | ||
|
||
fsv1alpha1 "github.com/kubernetes-csi/csi-proxy/client/api/filesystem/v1alpha1" |
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.
These apis don't need to be updated to beta?
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.
so because filesystem and smb api groups do not have any changes since alpha, so we didn't move it to beta, considering they not as mature as others. We think the version of the software/code is independent of the version of the API groups.
I discuss with @ddebroy and we will plan on moving them to beta too as post-beta action.
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.
From an API perspective, alpha has no guarantee of backwards compatibility or upgrade support. I would be wary of using an alpha api in production.
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.
right, i agree. I think I should not say "they not as mature as others. " because there is no change. I support moving them to beta, the APIs are working fine with all the current drivers for windows. I will address it in csi-windows meetup.
for diskNum, diskInfo := range diskIDsMap { | ||
klog.V(4).Infof("found disknum %s, diskInfo %v", diskNum, diskInfo) | ||
idValue, found := diskInfo.Identifiers[id] | ||
if found && strings.Contains(idValue, deviceName) { |
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.
Can you add a comment with an example format of idValue and deviceName?
strings.Contains
is prone to substring matching. Do we have that issue here?
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.
I added comment. From the tests, it seems working fine.
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.
What if the idValue is something like "pvc-123", but the device name is "pvc-12"?
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.
good point. I should use exact match
yes, my change to install beta csi proxy is in 1.20. |
This PR updates driver to use csi-proxy beta version.
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jingxu97, msau42 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 |
|
This PR updates driver to use csi-proxy beta version.
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: