fix: update namespace creation and deletion logic #72
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes the way the namespace creation process occurs from asynchronous to synchronous. This is to ensure that the underlying Docker network is always created first before any validation of namespace and creation of resources happens.
It also updates the DELETE resource operation to remove the namespace validation. This is a temporary fix while we keep the current controller logic. It is being removed because most of the clients such as kubectl will call DELETE operations sequentially and the namespace is usually the first item to be deleted from a manifest - causing other subsequent DELETE operations to fail on the namespace validation.
Related to #68