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.

Sign up for GitHub

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

Jump to bottom

Bump csi versions #675

Merged
merged 4 commits into from
Jan 14, 2022
Merged

Bump csi versions #675

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
606ae36
Added two CSI READMEs
kschumy Jan 14, 2022
6c0b6dc
Bumped CSI project versions and added READMEs
kschumy Jan 14, 2022
1614273
Fixed copy paste error
kschumy Jan 14, 2022
edd21c4
Plz accept this offering, CHECKSUMS gods
kschumy Jan 14, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions projects/kubernetes-csi/external-attacher/CHECKSUMS
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
91cd3944137f85807d5f4db8f26acbc40d47edc4cf9784873599995e28cc6a62 _output/bin/external-attacher/linux-amd64/csi-attacher
dd388434c3f7d637d16fe74e811942976cd1251d8eb28e77ddfbb00a39e95222 _output/bin/external-attacher/linux-arm64/csi-attacher
e235e9ef0f8d1d567026d6ca49a098308317e8c2ffcdd67f19284076a9e10f24 _output/bin/external-attacher/linux-amd64/csi-attacher
e0e58a58f5900cafe1fa5834074f15a529596615b65dfc76e1f9aea0d9e3fe2a _output/bin/external-attacher/linux-arm64/csi-attacher
2 changes: 1 addition & 1 deletion projects/kubernetes-csi/external-attacher/GIT_TAG
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v3.1.0
v3.2.0
2 changes: 1 addition & 1 deletion projects/kubernetes-csi/external-attacher/Makefile
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
BASE_DIRECTORY=$(shell git rev-parse --show-toplevel)
GIT_TAG?=$(shell cat GIT_TAG)
GOLANG_VERSION?="1.15"
GOLANG_VERSION?="1.16"

REPO=external-attacher
REPO_OWNER=kubernetes-csi
Expand Down
36 changes: 36 additions & 0 deletions projects/kubernetes-csi/external-attacher/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
## CSI external-attacher

| Release | Version |
| --- | --- |
| 1-18 | ![Version](https://img.shields.io/badge/version-v3.2.0-blue) |
| 1-19 | ![Version](https://img.shields.io/badge/version-v3.2.0-blue) |
| 1-20 | ![Version](https://img.shields.io/badge/version-v3.2.0-blue) |
| 1-21 | ![Version](https://img.shields.io/badge/version-v3.2.0-blue) |


### Updating

1. Determine the version of CSI external-attacher to use.
1. Consult the EKS team and consider options among the
[supported versions](https://kubernetes-csi.github.io/docs/external-attacher.html#supported-versions).
2. Review [releases](https://github.com/kubernetes-csi/external-attacher/releases),
[tags](https://github.com/kubernetes-csi/external-attacher/tags),
and [changelogs](https://github.com/kubernetes-csi/external-attacher/tree/master/CHANGELOG),
carefully looking for updates that may affect EKS-Distro or downstream
projects like EKS-Anywhere.
2. Update the `GIT_TAG` file to have the new, desired version based on the
`external-attacher` release tags.
3. Compare the old tag to the new one, looking specifically for Makefile changes.
For example:
[v3.1.0 compared to v3.2.0](https://github.com/kubernetes-csi/external-attacher/compare/v3.1.0...v3.2.0).
Check the `external-attacher` target for any build flag changes, tag changes,
dependencies, etc. Check that the manifest target, which is called from the
EKS-D Makefile, has not changed.
4. Verify the Golang version has not changed. The version specified in
[`go.mod`](https://github.com/kubernetes-csi/external-attacher/blob/master/go.mod)
seems to be kept up to date. Be sure to select the correct branch for the
release when checking the Golang version.
5. Update CHECKSUMS and attribution by using
`make update-attribution-checksums-docker PROJECT=kubernetes-csi/external-attacher RELEASE_BRANCH=<release_branch>`
from the root of the EKS-Distro repo.
6. Update the version at the top of this README.
4 changes: 2 additions & 2 deletions projects/kubernetes-csi/external-provisioner/CHECKSUMS
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
0ca83456964cb30b61ba387b63bdb9bfba0557b6be959353d222d1ec3adf2b5b _output/bin/external-provisioner/linux-amd64/csi-provisioner
970cab85afc3397bf53a60edd563fc506bc4d9fb2451691f4ee7c6d8d3bb5728 _output/bin/external-provisioner/linux-arm64/csi-provisioner
79d2225b9676d2075def5b97abec079f0d11234f382c73f559ca70881c30be55 _output/bin/external-provisioner/linux-amd64/csi-provisioner
20930d02e74a3b42a5540e8cb11e59c830a1409bdcb36b5978487db4d900fa56 _output/bin/external-provisioner/linux-arm64/csi-provisioner
2 changes: 1 addition & 1 deletion projects/kubernetes-csi/external-provisioner/GIT_TAG
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v2.1.1
v2.2.2
2 changes: 1 addition & 1 deletion projects/kubernetes-csi/external-provisioner/Makefile
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
BASE_DIRECTORY=$(shell git rev-parse --show-toplevel)
GIT_TAG?=$(shell cat GIT_TAG)
GOLANG_VERSION?="1.15"
GOLANG_VERSION?="1.16"

REPO=external-provisioner
REPO_OWNER=kubernetes-csi
Expand Down
36 changes: 36 additions & 0 deletions projects/kubernetes-csi/external-provisioner/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
## CSI external-provisioner

| Release | Version |
| --- | --- |
| 1-18 | ![Version](https://img.shields.io/badge/version-v2.2.2-blue) |
| 1-19 | ![Version](https://img.shields.io/badge/version-v2.2.2-blue) |
| 1-20 | ![Version](https://img.shields.io/badge/version-v2.2.2-blue) |
| 1-21 | ![Version](https://img.shields.io/badge/version-v2.2.2-blue) |


### Updating

1. Determine the version of CSI external-provisioner to use.
1. Consult the EKS team and consider options among the
[supported versions](https://kubernetes-csi.github.io/docs/external-provisioner.html#supported-versions).
2. Review [releases](https://github.com/kubernetes-csi/external-provisioner/releases),
[tags](https://github.com/kubernetes-csi/external-provisioner/tags),
and [changelogs](https://github.com/kubernetes-csi/external-provisioner/tree/master/CHANGELOG),
carefully looking for updates that may affect EKS-Distro or downstream
projects like EKS-Anywhere.
2. Update the `GIT_TAG` file to have the new, desired version based on the
`external-provisioner` release tags.
3. Compare the old tag to the new one, looking specifically for Makefile changes.
For example:
[v2.1.1 compared to v2.2.2](https://github.com/kubernetes-csi/external-provisioner/compare/v2.1.1...v2.2.2).
Check the `external-provisioner` target for any build flag changes, tag
changes, dependencies, etc. Check that the manifest target, which is called
from the EKS-D Makefile, has not changed.
4. Verify the Golang version has not changed. The version specified in
[`go.mod`](https://github.com/kubernetes-csi/external-provisioner/blob/master/go.mod)
seems to be kept up to date. Be sure to select the correct branch for the
release when checking the Golang version.
5. Update CHECKSUMS and attribution by using
`make update-attribution-checksums-docker PROJECT=kubernetes-csi/external-provisioner RELEASE_BRANCH=<release_branch>`
from the root of the EKS-Distro repo.
6. Update the version at the top of this README.
4 changes: 2 additions & 2 deletions projects/kubernetes-csi/external-resizer/CHECKSUMS
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
0dbefaf7bfed082e38972a4bf1681c54dad2d602176aa61affc1c90958c52c6c _output/bin/external-resizer/linux-amd64/csi-resizer
9abf47f25340dc17bc128b6bdb123b4627ca35ff77c27a26b3454c24e7c1c95a _output/bin/external-resizer/linux-arm64/csi-resizer
6d26e125d3e9543c7ccad7b050f374e0340fd74ecf54ac50388c8a751ee82550 _output/bin/external-resizer/linux-amd64/csi-resizer
54ec43c497cd7194e62fed56ccbf1a20a364084f98a20cf860d7ecfb5193c852 _output/bin/external-resizer/linux-arm64/csi-resizer
2 changes: 1 addition & 1 deletion projects/kubernetes-csi/external-resizer/GIT_TAG
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v1.1.0
v1.2.0
2 changes: 1 addition & 1 deletion projects/kubernetes-csi/external-resizer/Makefile
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
BASE_DIRECTORY=$(shell git rev-parse --show-toplevel)
GIT_TAG?=$(shell cat GIT_TAG)
GOLANG_VERSION?="1.15"
GOLANG_VERSION?="1.16"

REPO=external-resizer
REPO_OWNER=kubernetes-csi
Expand Down
36 changes: 36 additions & 0 deletions projects/kubernetes-csi/external-resizer/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
## CSI external-resizer

| Release | Version |
| --- | --- |
| 1-18 | ![Version](https://img.shields.io/badge/version-v1.2.0-blue) |
| 1-19 | ![Version](https://img.shields.io/badge/version-v1.2.0-blue) |
| 1-20 | ![Version](https://img.shields.io/badge/version-v1.2.0-blue) |
| 1-21 | ![Version](https://img.shields.io/badge/version-v1.2.0-blue) |


### Updating

1. Determine the version of CSI external-resizer to use.
1. Consult the EKS team and consider options among the
[supported versions](https://kubernetes-csi.github.io/docs/external-resizer.html#supported-versions).
2. Review [releases](https://github.com/kubernetes-csi/external-resizer/releases),
[tags](https://github.com/kubernetes-csi/external-resizer/tags),
and [changelogs](https://github.com/kubernetes-csi/external-resizer/tree/master/CHANGELOG),
carefully looking for updates that may affect EKS-Distro or downstream
projects like EKS-Anywhere.
2. Update the `GIT_TAG` file to have the new, desired version based on the
`external-resizer` release tags.
3. Compare the old tag to the new one, looking specifically for Makefile changes.
For example:
[v1.1.0 compared to v1.2.0](https://github.com/kubernetes-csi/external-resizer/compare/v1.1.0...v1.2.0).
Check the `external-resizer` target for any build flag changes, tag
changes, dependencies, etc. Check that the manifest target, which is called
from the EKS-D Makefile, has not changed.
4. Verify the Golang version has not changed. The version specified in
[`go.mod`](https://github.com/kubernetes-csi/external-resizer/blob/master/go.mod)
seems to be kept up to date. Be sure to select the correct branch for the
release when checking the Golang version.
5. Update CHECKSUMS and attribution by using
`make update-attribution-checksums-docker PROJECT=kubernetes-csi/external-resizer RELEASE_BRANCH=<release_branch>`
from the root of the EKS-Distro repo.
6. Update the version at the top of this README.
36 changes: 36 additions & 0 deletions projects/kubernetes-csi/external-snapshotter/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
## CSI external-snapshotter

| Release | Version |
| --- | --- |
| 1-18 | ![Version](https://img.shields.io/badge/version-v3.0.3-blue) |
| 1-19 | ![Version](https://img.shields.io/badge/version-v3.0.3-blue) |
| 1-20 | ![Version](https://img.shields.io/badge/version-v3.0.3-blue) |
| 1-21 | ![Version](https://img.shields.io/badge/version-v3.0.3-blue) |


### Updating

1. Determine the version of CSI external-snapshotter to use.
1. Consult the EKS team and consider options among the
[supported versions](https://kubernetes-csi.github.io/docs/external-snapshotter.html#supported-versions).
2. Review [releases](https://github.com/kubernetes-csi/external-snapshotter/releases),
[tags](https://github.com/kubernetes-csi/external-snapshotter/tags),
and [changelogs](https://github.com/kubernetes-csi/external-snapshotter/tree/master/CHANGELOG),
carefully looking for updates that may affect EKS-Distro or downstream
projects like EKS-Anywhere.
2. Update the `GIT_TAG` file to have the new, desired version based on the
`external-snapshotter` release tags.
3. Compare the old tag to the new one, looking specifically for Makefile changes.
For example:
[v3.0.3 compared to v4.2.0](https://github.com/kubernetes-csi/external-snapshotter/compare/v3.0.3...v4.2.0).
Check the `external-snapshotter` target for any build flag changes, tag
changes, dependencies, etc. Check that the manifest target, which is called
from the EKS-D Makefile, has not changed.
4. Verify the Golang version has not changed. The version specified in
[`go.mod`](https://github.com/kubernetes-csi/external-snapshotter/blob/master/go.mod)
seems to be kept up to date. Be sure to select the correct branch for the
release when checking the Golang version.
5. Update CHECKSUMS and attribution by using
`make update-attribution-checksums-docker PROJECT=kubernetes-csi/external-snapshotter RELEASE_BRANCH=<release_branch>`
from the root of the EKS-Distro repo.
6. Update the version at the top of this README.
4 changes: 2 additions & 2 deletions projects/kubernetes-csi/livenessprobe/CHECKSUMS
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
d1c26a70871e6767b75a8f112e005152eeb1a8ac64d1aeceb7d4b51272e454aa _output/bin/livenessprobe/linux-amd64/livenessprobe
55f446d1e380634dcf08764efac80bfd5b0e8e79cded96646a7bd14f57c29a2b _output/bin/livenessprobe/linux-arm64/livenessprobe
e64d0a9d31cf9f61b7a09b58afae1e9e3e422e2d29a816c86b5640e8111b61cb _output/bin/livenessprobe/linux-amd64/livenessprobe
86b6094d551d8ed55b8383458ff4832440bb6a8c0227a6f42506f4de5879fd38 _output/bin/livenessprobe/linux-arm64/livenessprobe
2 changes: 1 addition & 1 deletion projects/kubernetes-csi/livenessprobe/GIT_TAG
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v2.2.0
v2.3.0
2 changes: 1 addition & 1 deletion projects/kubernetes-csi/livenessprobe/Makefile
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
BASE_DIRECTORY=$(shell git rev-parse --show-toplevel)
GIT_TAG?=$(shell cat GIT_TAG)
GOLANG_VERSION?="1.15"
GOLANG_VERSION?="1.16"

REPO=livenessprobe
REPO_OWNER=kubernetes-csi
Expand Down
36 changes: 36 additions & 0 deletions projects/kubernetes-csi/livenessprobe/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
## CSI livenessprobe

| Release | Version |
| --- | --- |
| 1-18 | ![Version](https://img.shields.io/badge/version-v2.3.0-blue) |
| 1-19 | ![Version](https://img.shields.io/badge/version-v2.3.0-blue) |
| 1-20 | ![Version](https://img.shields.io/badge/version-v2.3.0-blue) |
| 1-21 | ![Version](https://img.shields.io/badge/version-v2.3.0-blue) |


### Updating

1. Determine the version of CSI livenessprobe to use.
1. Consult the EKS team and consider options among the
[supported versions](https://kubernetes-csi.github.io/docs/livenessprobe.html#supported-versions).
2. Review [releases](https://github.com/kubernetes-csi/livenessprobe/releases),
[tags](https://github.com/kubernetes-csi/livenessprobe/tags),
and [changelogs](https://github.com/kubernetes-csi/livenessprobe/tree/master/CHANGELOG),
carefully looking for updates that may affect EKS-Distro or downstream
projects like EKS-Anywhere.
2. Update the `GIT_TAG` file to have the new, desired version based on the
`livenessprobe` release tags.
3. Compare the old tag to the new one, looking specifically for Makefile changes.
For example:
[v2.2.0 compared to v2.3.0](https://github.com/kubernetes-csi/livenessprobe/compare/v2.2.0...v2.3.0).
Check the `livenessprobe` target for any build flag changes, tag
changes, dependencies, etc. Check that the manifest target, which is called
from the EKS-D Makefile, has not changed.
4. Verify the Golang version has not changed. The version specified in
[`go.mod`](https://github.com/kubernetes-csi/livenessprobe/blob/master/go.mod)
seems to be kept up to date. Be sure to select the correct branch for the
release when checking the Golang version.
5. Update CHECKSUMS and attribution by using
`make update-attribution-checksums-docker PROJECT=kubernetes-csi/livenessprobe RELEASE_BRANCH=<release_branch>`
from the root of the EKS-Distro repo.
6. Update the version at the top of this README.
4 changes: 2 additions & 2 deletions projects/kubernetes-csi/node-driver-registrar/CHECKSUMS
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
8c95e80196f6e6c89aa67bedf09e772ac3b754a08ef99e2cb917a8e32a0fd1c7 _output/bin/node-driver-registrar/linux-amd64/csi-node-driver-registrar
6a51dee81d4baba833b645b3d03a21dc0889597ca8eb5572ce787abf6b01272d _output/bin/node-driver-registrar/linux-arm64/csi-node-driver-registrar
b8209b5a1bc1426a0a493e4c913ddf7370e330b03c81c95af57c19bb6bcf1eab _output/bin/node-driver-registrar/linux-amd64/csi-node-driver-registrar
073711be41589b6793484d5ee7f20ac5a5f6d9e51e7c9997a6c086e7bb0f0aef _output/bin/node-driver-registrar/linux-arm64/csi-node-driver-registrar
2 changes: 1 addition & 1 deletion projects/kubernetes-csi/node-driver-registrar/GIT_TAG
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
v2.1.0
v2.2.0
2 changes: 1 addition & 1 deletion projects/kubernetes-csi/node-driver-registrar/Makefile
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
BASE_DIRECTORY=$(shell git rev-parse --show-toplevel)
GIT_TAG?=$(shell cat GIT_TAG)
GOLANG_VERSION?="1.15"
GOLANG_VERSION?="1.16"

REPO=node-driver-registrar
REPO_OWNER=kubernetes-csi
Expand Down
36 changes: 36 additions & 0 deletions projects/kubernetes-csi/node-driver-registrar/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
## CSI node-driver-registrar

| Release | Version |
| --- | --- |
| 1-18 | ![Version](https://img.shields.io/badge/version-v2.2.0-blue) |
| 1-19 | ![Version](https://img.shields.io/badge/version-v2.2.0-blue) |
| 1-20 | ![Version](https://img.shields.io/badge/version-v2.2.0-blue) |
| 1-21 | ![Version](https://img.shields.io/badge/version-v2.2.0-blue) |


### Updating

1. Determine the version of CSI node-driver-registrar to use.
1. Consult the EKS team and consider options among the
[supported versions](https://kubernetes-csi.github.io/docs/node-driver-registrar.html#supported-versions).
2. Review [releases](https://github.com/kubernetes-csi/node-driver-registrar/releases),
[tags](https://github.com/kubernetes-csi/node-driver-registrar/tags),
and [changelogs](https://github.com/kubernetes-csi/node-driver-registrar/tree/master/CHANGELOG),
carefully looking for updates that may affect EKS-Distro or downstream
projects like EKS-Anywhere.
2. Update the `GIT_TAG` file to have the new, desired version based on the
`node-driver-registrar` release tags.
3. Compare the old tag to the new one, looking specifically for Makefile changes.
For example:
[v2.1.0 compared to v2.2.0](https://github.com/kubernetes-csi/node-driver-registrar/compare/v2.1.0...v2.2.0).
Check the `node-driver-registrar` target for any build flag changes, tag
changes, dependencies, etc. Check that the manifest target, which is called
from the EKS-D Makefile, has not changed.
4. Verify the Golang version has not changed. The version specified in
[`go.mod`](https://github.com/kubernetes-csi/node-driver-registrar/blob/master/go.mod)
seems to be kept up to date. Be sure to select the correct branch for the
release when checking the Golang version.
5. Update CHECKSUMS and attribution by using
`make update-attribution-checksums-docker PROJECT=kubernetes-csi/node-driver-registrar RELEASE_BRANCH=<release_branch>`
from the root of the EKS-Distro repo.
6. Update the version at the top of this README.