Enable VolumeSnapshotDataSource Feature Gate and update e2e tests for VolumeSnapshot CRD v1beta1#80058
Conversation
|
/assign @msau42 |
|
/retest |
|
/retest |
e9ee7cb to
f115c5d
Compare
f115c5d to
8fcc9ef
Compare
|
/retest |
|
/test pull-kubernetes-conformance-kind-ipv6 |
|
/test pull-kubernetes-e2e-gce-alpha-features |
|
/test pull-kubernetes-e2e-gce-storage-slow |
1 similar comment
|
/test pull-kubernetes-e2e-gce-storage-slow |
There was a problem hiding this comment.
Should this be "kube-system", as in volume-snapshot-controller-deployment.yaml?
There was a problem hiding this comment.
Yes, see my comment about updating the RBAC file in this PR... personally I would prefer an "upstream" first approach: always make changes in the individual repo first (because that is the canonical definition of the RBAC files!), then copy into k/k.
With the CRDs it's going to be worse if they aren't even 1:1 copies from upstream. All I can think of is making changes upstream, overwrite the file in k/k, then use "git add -i" to commit only those changes that were made upstream since the last import.
cluster/gce/config-default.sh
Outdated
There was a problem hiding this comment.
I'm not familiar with how "cluster/addons" is used. Looking at this change makes it sound like those addons explicitly have to be enabled?
Can that be done when using hack/local-up-cluster.sh? I ran it from your branch for this PR, but the resulting cluster didn't have the snapshot CRDs.
There was a problem hiding this comment.
That needs a separate PR. I'll work on that.
9efc9b3 to
0386fcf
Compare
|
/test pull-kubernetes-e2e-kind |
saad-ali
left a comment
There was a problem hiding this comment.
I remember we had a large discussion about CSI CRDs and how, when, and by who they should be installed. We ended up moving them to core types because of the tight dependency with core controllers. In this case, all our controllers are external, so that is not a concern here.
For the CSI CRDs we initially had the controller install CRDs, but that was frowned upon. So overall this seems reasonable to me.
/approve
Will let @yuxiangqian review and LGTM
|
/test pull-kubernetes-e2e-gce-alpha-features |
|
@msau42 will LGTM on this one. Thanks Saad! |
There was a problem hiding this comment.
I would put the rbac in the same folder as snapshot controller manifest
cluster/gce/gci/configure-helper.sh
Outdated
There was a problem hiding this comment.
Looking at wait-for-apiserver-and-update-fluentd above, it seems to be waiting for some objects to be initialized before applying some modification. I'm not sure we need to do the same for snapshots. Especially because this function is run in the background, I'm not really sure how useful it is. We can probably remove it and not wait for anything.
There was a problem hiding this comment.
Sure, I'll give a try.
There was a problem hiding this comment.
Removed it but then everything is failing. Nothing from cluster addon manager gets installed. I don't even see logs from cluster addon. So I have to add it back.
There was a problem hiding this comment.
Does provisioner rbac need to be updated to read the new beta snapshot objects?
There was a problem hiding this comment.
No changes are needed. It's the same API group and resource names.
|
/retest |
|
/test pull-kubernetes-e2e-gce |
cluster/gce/gci/configure-helper.sh
Outdated
There was a problem hiding this comment.
Can you update the comment and the function name here, we're not actually updating anything, only waiting
|
/assign @zmerlynn |
|
@msau42 addressed your comments. PTAL. |
|
/test pull-kubernetes-node-e2e-containerd |
|
/test pull-kubernetes-integration |
|
/test pull-kubernetes-node-e2e-containerd |
1 similar comment
|
/test pull-kubernetes-node-e2e-containerd |
…ate and update e2e tests
|
/test pull-kubernetes-conformance-kind-ipv6 |
|
/lgtm |
|
/assign @dims |
|
/approve |
|
/priority important-soon |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, msau42, saad-ali, xing-yang, zmerlynn The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test pull-kubernetes-kubemark-e2e-gce-big |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR enables VolumeSnapshotDataSource feature gate and updates e2e tests.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: