Skip to content

Conversation

@Zerpet
Copy link
Member

@Zerpet Zerpet commented Jun 14, 2022

Note to reviewers: remember to look at the commits in this PR and consider if they can be squashed
Note to contributors: remember to re-generate client set if there are any API changes

Summary Of Changes

  • Update Kubernetes version to latest available and lowest supported (N-2)
  • Match Go version with our go.mod
  • Check cert-manager api readiness before deploying Top-Op

Additional Context

Cert Manager Pods may become ready before Cert Manager API is ready. This results in a failed Top-Op deployment with an error like x509: certificate signed by unknown authority. The workaround is to check and wait for Cert Manager API to become ready.

Update Kubernetes version to latest available and lowest supported (N-2).
Match Go version with our `go.mod`.

Bump Cert Manager to 1.7.0 because 1.8.0 has breaking changes, and we
have not tested whether we are compatible with those changes.

Sometimes, Cert Manager Pods become ready, however Cert Manager itself
is not ready to serve requests. If Topology Operator is deployed at that
time, Cert Manager will not inject the certificate into the Webhooks,
causing an error of the kind "x509: certificate signed by unknown
authority". The solution is to wait for the API to be ready, using their
new CLI `cmctl`.
@Zerpet Zerpet force-pushed the update-pr-workflow branch from 4779e90 to a97917a Compare June 14, 2022 12:30
@ChunyiLyu ChunyiLyu merged commit 3858fac into main Jun 14, 2022
@ChunyiLyu ChunyiLyu deleted the update-pr-workflow branch June 14, 2022 14:08
Zerpet added a commit that referenced this pull request Jun 14, 2022
Follow up to #395 PR. Make targets that use cmctl CLI should `make` it as a
dependency.

Signed-off-by: Aitor Perez Cedres <[email protected]>
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.

5 participants