Skip to content

Conversation

@maelvls
Copy link
Member

@maelvls maelvls commented Nov 2, 2021

I did not release 1.6.0-gcm.0 since 1.6.1 was released the same day I did the GCM update. So I went directly to 1.6.1.

Signed-off-by: Maël Valais <mael@vls.dev>
Commands run:

  # From the jetstack-secure-gcm repo.
  cd chart/jetstack-secure-gcm/charts/
  rm -rf cert-manager
  helm pull jetstack/cert-manager --version 1.6.0 --untar
  find cert-manager -type f -print0 | xargs -0 perl -i~ -pe 's/app\.kubernetes\.io\/name:(.*\")[a-z-._]+\.name(\".*)/app.kubernetes.io\/name:$1cert-manager.name$2/g'
  find cert-manager -type f -print0 | xargs -0 perl -i~ -nle 'print if !/^ *app:/'

and then, do:

  git add -p

and make sure not to remove any ubbagent-specific stuff.

Signed-off-by: Maël Valais <mael@vls.dev>
This change is required due to the following error:

  Error: container has runAsNonRoot and image will run as root
  (pod: "cert-manager-apptest-1234, container: ubbagent)

Signed-off-by: Maël Valais <mael@vls.dev>
…ests

Signed-off-by: Maël Valais <mael@vls.dev>
@maelvls
Copy link
Member Author

maelvls commented Nov 3, 2021

1.4.4-gcm.0, 1.5.4-gcm.1 and 1.6.1-gcm.0 have been accepted!

@wallrj Would you like to review this PR?

Copy link
Member

@wallrj wallrj left a comment

Choose a reason for hiding this comment

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

Sorry for the delay in reviewing this.
There are some 1.6.0 references still in here,
and the "Draft release" link in the PR description no longer works for me.

@maelvls maelvls force-pushed the release-1.6 branch 2 times, most recently from 178f2b9 to 0ed6462 Compare February 18, 2022 11:45
@maelvls
Copy link
Member Author

maelvls commented Feb 18, 2022

I changed the references from 1.6.0 to 1.6.1. Since this branch was never merged into master, I don't think anyone has ever tried to use the Helm chart for 1.6.1-gcm.0, so I expect no breakage.

We are good to go.

Signed-off-by: Maël Valais <mael@vls.dev>
I changed all the references to 'sed -i~' (which was due to the need for
compatibility between BSD sed on macOS and GNU sed on Linux) to perl,
which is identical on both platforms.

Signed-off-by: Maël Valais <mael@vls.dev>
Copy link
Member

@wallrj wallrj left a comment

Choose a reason for hiding this comment

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

Thanks for the updates @maelvls

/lgtm

@wallrj wallrj merged commit 33d2fa0 into main Feb 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants