Skip to content
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

🌱 Upgrade CSI driver to v3.1.0 #2364

Merged
merged 1 commit into from
Nov 2, 2023

Conversation

laozc
Copy link
Member

@laozc laozc commented Sep 18, 2023

What this PR does / why we need it:
We're still using 2.1.0 in the templates while the latest CSI driver now is 3.1.0 with more features.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #2331

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Sep 18, 2023
@k8s-ci-robot k8s-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Sep 18, 2023
@codecov
Copy link

codecov bot commented Sep 18, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (47e62f1) 63.60% compared to head (e86f148) 63.58%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2364      +/-   ##
==========================================
- Coverage   63.60%   63.58%   -0.03%     
==========================================
  Files         123      123              
  Lines        8773     8773              
==========================================
- Hits         5580     5578       -2     
- Misses       2777     2778       +1     
- Partials      416      417       +1     

see 6 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@killianmuldoon
Copy link
Contributor

/test

@k8s-ci-robot
Copy link
Contributor

@killianmuldoon: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

  • /test pull-cluster-api-provider-vsphere-conformance-main
  • /test pull-cluster-api-provider-vsphere-e2e-full-main
  • /test pull-cluster-api-provider-vsphere-e2e-main
  • /test pull-cluster-api-provider-vsphere-test-integration-main
  • /test pull-cluster-api-provider-vsphere-test-main
  • /test pull-cluster-api-provider-vsphere-verify-main

The following commands are available to trigger optional jobs:

  • /test pull-cluster-api-provider-vsphere-apidiff-main

Use /test all to run the following jobs that were automatically triggered:

  • pull-cluster-api-provider-vsphere-apidiff-main
  • pull-cluster-api-provider-vsphere-e2e-main
  • pull-cluster-api-provider-vsphere-test-integration-main
  • pull-cluster-api-provider-vsphere-test-main
  • pull-cluster-api-provider-vsphere-verify-main

In response to this:

/test

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.

Copy link
Contributor

@killianmuldoon killianmuldoon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/test pull-cluster-api-provider-vsphere-e2e-full-main

Copy link
Member

@chrischdi chrischdi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One question but no bigger opinion on this.
As of that:

/lgtm

packaging/flavorgen/flavors/crs/csi.go Outdated Show resolved Hide resolved
Comment on lines 703 to 627
- name: GODEBUG
value: x509sha1=1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add a comment why this one is needed? Or is this simply copy/paste?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's copied from the CSI manifest.
The flag is used to enable the deprecated SHA1 certificate support in some enterprise environment for on-prem Kubernetes installations.
https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/616f90f7e38a24fceda3673819abafd20da08859/manifests/vanilla/vsphere-csi-driver.yaml#L367C1-L368C32

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

LGTM label has been added.

Git tree hash: 268c1bb64fe38acd284fe0db03d3197d1b39d0de

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 19, 2023
Copy link
Member

@chrischdi chrischdi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wondering of it makes sense to copy all this over and make go code out of it, or if we should instead use go embed and only add the things we need (e.g. csi-config-secret)

However for now its good as it is.

/lgtm

chrischdi

This comment was marked as duplicate.

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

LGTM label has been added.

Git tree hash: 1ce3dc3431be1fd94de71457661c3a5da5c5776f

@sbueringer
Copy link
Member

sbueringer commented Sep 19, 2023

Wondering of it makes sense to copy all this over and make go code out of it, or if we should instead use go embed and only add the things we need (e.g. csi-config-secret)

This seems pretty hard to maintain / keeping in sync going forward. @randomvariable WDYT? Should we follow the route to convert everything to go code and somehow try to keep this in sync or should we follow a more direct copying YAML over & diffing approach?

The latter seems a lot more maintainable to me

Q: In which format is CSI providing the YAML? Is there an all-in-one YAML or a Helm chart or both?

@laozc
Copy link
Member Author

laozc commented Sep 19, 2023

There is a full manifest at
https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/manifests/vanilla/vsphere-csi-driver.yaml

I believe the CSI driver image in the file is generated for their CI.
For long term maintenance, it would be better to replicate the manifest content from CSI driver with our own customization.

@chrischdi
Copy link
Member

Maybe a copy + kustomize patches for things we need to change could be a good way forward.

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 25, 2023
@laozc laozc force-pushed the csi-upgrade branch 3 times, most recently from d487184 to 453e24e Compare October 25, 2023 03:44
@sbueringer
Copy link
Member

Okay let's go ahead with this. I took a look and I didn't see anything suspicious, but I also didn't diff it which seems a crazy amount of work. I'm fine with merging this PR after rebase & when all e2e tests are green.

But we have to find another way to do this. Let's create an issue to move this to using the upstream YAML + kustomizations on top. This is absolutely not sustainable (already wasn't before this PR, which is why I'm fine with merging this for now)

@laozc
Copy link
Member Author

laozc commented Nov 1, 2023

/retest-required

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Nov 1, 2023

@laozc: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-cluster-api-provider-vsphere-apidiff-main e86f148 link false /test pull-cluster-api-provider-vsphere-apidiff-main

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

@sbueringer
Copy link
Member

/test pull-cluster-api-provider-vsphere-e2e-full-main

@sbueringer
Copy link
Member

/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 Nov 2, 2023
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 499534c46a5a56cb82f6787c11267d1a1d473bfc

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 2, 2023
@k8s-ci-robot k8s-ci-robot merged commit 0984b05 into kubernetes-sigs:main Nov 2, 2023
17 of 18 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.9 milestone Nov 2, 2023
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. 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.

CSI controller crashes in deployments using current templates
5 participants