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

Check if the target namespace is terminating and abort installation #1649

Merged
merged 1 commit into from
Aug 21, 2020

Conversation

ANeumann82
Copy link
Member

Signed-off-by: Andreas Neumann aneumann@mesosphere.com

Fixes #1627

… installation

Signed-off-by: Andreas Neumann <aneumann@mesosphere.com>
Copy link
Contributor

@zen-dog zen-dog left a comment

Choose a reason for hiding this comment

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

Ship it! 🚢


// If either custom or default ns is terminating, we can't install
if err == nil {
if ns.Status.Phase == v1.NamespaceTerminating {
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not sure but wdyt about putting this check in the health.go? E.g. a healthy namespace has the NamespaceActive phase?

Copy link
Member Author

Choose a reason for hiding this comment

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

Phase can currently only be Active or Terminating, so we don't need a health check for NS (at the moment)

@ANeumann82 ANeumann82 merged commit 88295ec into main Aug 21, 2020
@ANeumann82 ANeumann82 deleted the an/pre-install-check-ns-terminating branch August 21, 2020 07:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Better checks in kudo init for namespaces
3 participants