-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
kfctl.sh apply platform #820
Comments
I guess you saw this in the last step
Could you double check the cluster and see if secret is there
|
Yes, we run the kfctl.sh apply k8s script and the secret was not in the cluster. |
could you retry the apply command? the error message says it's not found in the cluster but the command should create it. |
I'm not sure if it helps, but when deploying to GKE, the kubeflow-oauth secret is created when applying platform rather than k8s. It will also only be created if CLIENT_SECRET and CLIENT_ID are exported in the shell environment. |
Resolving since this issue as been inactive for a while. Please reopen as needed. |
Created a cluster following the command line instructions on a Mac OS and saw the following error, but the cluster seems to have been created correctly.
++ kubectl get secret --namespace=kubeflow kubeflow-oauth
The text was updated successfully, but these errors were encountered: