-
Notifications
You must be signed in to change notification settings - Fork 702
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
Switch dashboard to use checkNamespaceExists. #3911
Conversation
await this.resourcesClient().CreateNamespace({ | ||
context: { | ||
cluster, | ||
namespace, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks cleaner than before :)
One more step to abstract away from direct K8s API calls. Thanks! |
plugin. Signed-off-by: Michael Nelson <minelson@vmware.com>
Signed-off-by: Michael Nelson <minelson@vmware.com>
b19eb6e
to
8a8547d
Compare
Signed-off-by: Michael Nelson <minelson@vmware.com>
Signed-off-by: Michael Nelson <minelson@vmware.com>
ca92864
to
f12f974
Compare
Thanks for the approval. Just note that I can't land this as the previous PR isn't yet approved. If it's easier, you can see the whole series of PRs for this work on #3896 |
Signed-off-by: Michael Nelson minelson@vmware.com
Description of the change
Updates the dashboard to use the resources plugin to check if a namespace exists (rather than the more generic getNamespace which was hitting the k8s API server directly from the dashboard).
Also updates the
Namespace.create
shared helper to use the resources client.Benefits
See #3896
Possible drawbacks
Applicable issues
Additional information