Skip to content

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

Merged
merged 1 commit into from
Sep 10, 2020

Conversation

jingxu97
Copy link
Contributor

@jingxu97 jingxu97 commented Sep 8, 2020

This PR updates driver to use csi-proxy beta version.

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

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?:

NONE

@k8s-ci-robot k8s-ci-robot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Sep 8, 2020
@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Sep 8, 2020
@jingxu97
Copy link
Contributor Author

jingxu97 commented Sep 8, 2020

cc @msau42 @verult

@jingxu97 jingxu97 force-pushed the sep/vendor branch 2 times, most recently from a8b7683 to 441a01d Compare September 8, 2020 20:57
Copy link
Contributor

@msau42 msau42 left a 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
Copy link
Contributor

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)

Copy link
Contributor Author

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"
Copy link
Contributor

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

Copy link
Contributor Author

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"
Copy link
Contributor

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?

Copy link
Contributor Author

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.

Copy link
Contributor

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.

Copy link
Contributor Author

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) {
Copy link
Contributor

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?

Copy link
Contributor Author

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.

Copy link
Contributor

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"?

Copy link
Contributor Author

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

@jingxu97
Copy link
Contributor Author

jingxu97 commented Sep 8, 2020

Are we deploying the beta csi proxy in our CI cluster?

yes, my change to install beta csi proxy is in 1.20.

This PR updates driver to use csi-proxy beta version.
@jingxu97
Copy link
Contributor Author

/retest

@msau42
Copy link
Contributor

msau42 commented Sep 10, 2020

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 10, 2020
@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jingxu97
Copy link
Contributor Author

This PR updates driver to use csi-proxy beta version.

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:
/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

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?:


@jingxu97 jingxu97 closed this Sep 10, 2020
@jingxu97 jingxu97 reopened this Sep 10, 2020
@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Sep 10, 2020
@k8s-ci-robot k8s-ci-robot merged commit d18dba1 into kubernetes-sigs:master Sep 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants