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
Ensure namespace exists #1747
Ensure namespace exists #1747
Conversation
* We need to call createNamespace during the apply phase for k8s otherwise the namespace might not exist. Need to patch into 0.3
/assign @richardsliu |
Test failed
I thought kfctl was changed to call get-server-config? |
Looks like we should be doing it here Line 99 in 84020a3
|
Looks like it failed during the init step
|
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: richardsliu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* Ensure namespace exists * We need to call createNamespace during the apply phase for k8s otherwise the namespace might not exist. Need to patch into 0.3 * Fix get-server-config; it was failing because ZONE wasn't being set. * Run gcloud as a separate command so that if it errors out the script will fail. * * Fix bug in updateDeployment we should be using NAME not DEPLOYMENT_NAME
* Pin jupyter-console to 0.6.0 (#1746) * Ensure namespace exists (#1747) * Ensure namespace exists * We need to call createNamespace during the apply phase for k8s otherwise the namespace might not exist. Need to patch into 0.3 * Fix get-server-config; it was failing because ZONE wasn't being set. * Run gcloud as a separate command so that if it errors out the script will fail. * * Fix bug in updateDeployment we should be using NAME not DEPLOYMENT_NAME
* Ensure namespace exists * We need to call createNamespace during the apply phase for k8s otherwise the namespace might not exist. Need to patch into 0.3 * Fix get-server-config; it was failing because ZONE wasn't being set. * Run gcloud as a separate command so that if it errors out the script will fail. * * Fix bug in updateDeployment we should be using NAME not DEPLOYMENT_NAME
* Ensure namespace exists * We need to call createNamespace during the apply phase for k8s otherwise the namespace might not exist. Need to patch into 0.3 * Fix get-server-config; it was failing because ZONE wasn't being set. * Run gcloud as a separate command so that if it errors out the script will fail. * * Fix bug in updateDeployment we should be using NAME not DEPLOYMENT_NAME
otherwise the namespace might not exist.
Need to patch into 0.3
Related to #1675
This change is