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

K8s issues #268

Merged
merged 1 commit into from
May 31, 2024
Merged

K8s issues #268

merged 1 commit into from
May 31, 2024

Conversation

TiagoTAlves
Copy link
Contributor

Added more information on how to fix problem in creating a namespace that already exists if exited incorrectly and changed debug message to when deleting namespaces

… how to proceed, and gave an info message to say if a namespace has already been deleted
@TiagoTAlves
Copy link
Contributor Author

We are not catching api errors in nanorc when a namespace already exists, we're comparing it to the namespace list, so all we had to do was add an info message

Copy link
Contributor

@plasorak plasorak left a comment

Choose a reason for hiding this comment

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

LGTM, thanks.

@plasorak plasorak merged commit ddc9a25 into production/v4 May 31, 2024
1 check passed
@plasorak plasorak deleted the titavare/k8s-namespace branch May 31, 2024 16:47
@plasorak plasorak restored the titavare/k8s-namespace branch June 4, 2024 11:41
This was referenced Jun 4, 2024
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.

2 participants