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

the calico-apiserver namespace frequently get stuck for a long time in terminating status when upgrading to enterprise - v1.34 pick of (#3439) #3443

Open
wants to merge 1 commit into
base: release-v1.34
Choose a base branch
from

Conversation

gcosgrave
Copy link
Contributor

  • the calico-apiserver namespace frequently get stuck for a long time in terminating status when upgrading to enterprise

  • remove all references to status.variant

  • update the not-ready message

(cherry picked from commit b63136c)

Description

For PR author

  • Tests for change.
  • If changing pkg/apis/, run make gen-files
  • If changing versions, run make gen-versions

For PR reviewers

A note for code reviewers - all pull requests must have the following:

  • Milestone set according to targeted release.
  • Appropriate labels:
    • kind/bug if this is a bugfix.
    • kind/enhancement if this is a a new feature.
    • enterprise if this PR applies to Calico Enterprise only.

…n terminating status when upgrading to enterprise (tigera#3439)

* the calico-apiserver namespace frequently get stuck for a long time in terminating status when upgrading to enterprise

* remove all references to status.variant

* update the not-ready message

(cherry picked from commit b63136c)
@gcosgrave gcosgrave force-pushed the calico-apiserver-stuck-terminating-v1.34 branch from 43ad076 to c6ab6cc Compare July 23, 2024 09:06
@danudey danudey modified the milestones: v1.34.2, v1.34.3 Jul 24, 2024
@danudey danudey modified the milestones: v1.34.3, v1.34.4 Jul 31, 2024
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