-
Notifications
You must be signed in to change notification settings - Fork 189
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
Use v1.CSINode in the external-attacher #193
Conversation
1a834e1
to
712af6c
Compare
712af6c
to
32102db
Compare
go.mod
Outdated
k8s.io/klog v1.0.0 | ||
) | ||
|
||
replace k8s.io/api => k8s.io/api v0.0.0-20190918195907-bd6ac527cfd2 | ||
replace k8s.io/api => k8s.io/api v0.0.0-20191122220107-b5267f2975e0 |
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.
Which version of Kubernetes is that? Can you record that in the commit message?
I assume all code coming from Kubernetes is at that version?
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 vaguely remember seeing a script that can update all k8s dependencies. Was that something you wrote?
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 took some snippet that was posted in one of the Kubernetes discussions around semantic versioning and added it to csi-release-tools, so it's now in all of our repos: https://github.com/kubernetes-csi/csi-release-tools/blob/master/go-get-kubernetes.sh
But it's impossible to tell from the result whether that script was used and thus whether the new replacements are consistent. We basically have to trust the PR submitter that they did the right thing. To reproduce it, the version given to the scripts needs to be documented, hence me question about the commit message.
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.
Which version of Kubernetes is that? Can you record that in the commit message?
It was v1.17.0-rc.1
, but today I updated it to v1.17.0-rc.2
(which was released yesterday). I also updated the commit message to record both the k8s version and how the dependencies were updated (using the go-get-kubernetes.sh
script).
cmd/csi-attacher/main.go
Outdated
@@ -147,7 +147,7 @@ func main() { | |||
pvLister := factory.Core().V1().PersistentVolumes().Lister() | |||
nodeLister := factory.Core().V1().Nodes().Lister() | |||
vaLister := factory.Storage().V1beta1().VolumeAttachments().Lister() |
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.
Hm we should use v1 VolumeAttachment too.
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 can create another PR to address that...
b652ad2
to
f599fff
Compare
/hold Checking how to support older k8s releases |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
@bertinatto, with Kubernetes 1.19, IMO we don't need to worry about supporting v1beta1 of CSINode. We can require Kubernetes 1.17. Can you please continue with this PR? |
Done, rebased PR. I think it's ready for review. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bertinatto, jsafrane 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 |
/release-note-action-required |
@jsafrane: the
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR changes to attacher to use the GA version of the CSINode object.
Which issue(s) this PR fixes:
Fixes #197
Does this PR introduce a user-facing change?: