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
Bug 1912237: Rebase to v2.2.0 for OCP 4.7 #19
Bug 1912237: Rebase to v2.2.0 for OCP 4.7 #19
Conversation
Document the process for releasing a new sidecar
fix incorrect link
This relies on a slightly different deployment script: a "deploy.sh" must exist which knows that it has to dump a test driver configurion into the file pointed to with CSI_PROW_TEST_DRIVER, if that env variable is set. That way, we no longer need to know what capabilities the installed driver has.
That this hasn't been done before is an oversight. Apparently it hasn't been a problem because there never have been feature gates that mattered?
prow.sh: also configure feature gates for kubelet
prow.sh: generic driver installation
Change 'make test-vet' back to call 'go vet'
The final 1.3.0 release of the hostpath driver really uses the 1.3.0 driver image in its deployment, in contrast to the previous -rc candidates which still used 1.2.0.
prow.sh: use 1.3.0 hostpath driver for testing
Commit summary: 7c5a89c prow.sh: use 1.3.0 hostpath driver for testing fdb3218 Change 'make test-vet' to call 'go vet' 5f74333 prow.sh: also configure feature gates for kubelet 84f78b1 prow.sh: generic driver installation fa90abd fix incorrect link ac8a021 Document the process for releasing a new sidecar
master: update release-tools
Developers should not be forced to build for all platforms by default. We also don't want to copy-and-paste the go invocation for each new platform. To address both, the target platform(s) are now configurable via BUILD_PLATFORMS and additional platforms are only enabled in the Prow CI. For now this serves as a test that the source actually compiles for multiple platforms. Building images for different target platforms is a different problem.
build for multiple platforms only in CI, add s390x
…ndows Add Dockerfile.windows
Signed-off-by: Grant Griffiths <grant@portworx.com>
…pdate Update snapshotter to version 2.0.1
To clarify what the version means.
Add links to version in README
update release tools instructions
Signed-off-by: Grant Griffiths <grant@portworx.com>
…ter_rbac_version_set Fix csi-snapshotter RBAC yaml version
Update patch release notes generation command
Fix leak memory and upgrade csi-lib-util dependency
Introducing http-endpoint
Update all dependency to latest version
Add changelog for release v2.2.0
@jsafrane: This pull request references Bugzilla bug 1912237, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
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. |
861d9a0
to
e0850c1
Compare
This requires new golang in CI jobs: openshift/release#14560 |
/retest |
/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 |
Probably in another PR, but do we need to update the golang version here as well? |
/retest Please review the full test history for this PR and help us cut down flakes. |
@jsafrane: Some pull requests linked via external trackers have merged: The following pull requests linked via external trackers have not merged: These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with Bugzilla bug 1912237 has not been moved to the MODIFIED state. 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. |
Diff to upstream v2.2.0:
kubernetes-csi/livenessprobe@v2.2.0...jsafrane:rebase-v2.2.0
@openshift/storage