-
Notifications
You must be signed in to change notification settings - Fork 10
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
Deployment error #31
Comments
If you are running a Kubernetes >= v1.22 this may be related to my issue #30. I see the skipper ingress is also not ready which happened to my setup as well. Did you check the pod logs for errors? |
Hi - I was able to deploy the operator after a fresh install on Ubuntu 18.4 . Request the moderator to edit the " kustomize build . | k apply -f - " to " kustomize build . | kubectl apply -f - " as the previous one isn't working. |
Hi I changed the documentation to always use the full |
Hi, Thanks for the reply. I was able to short out this problem. Now stuck with another issue. I am making the changes to the yaml file ""shinyproxy-operator/docs/deployment/overlays/1-namespaced-hpa/shinyproxy/shinyproxy.yaml"" But not able to see any changes on the home page. It is still showing the default one. ( after running the kubectl apply -f shinyproxy.yaml, I am getting the success message "shinyproxy configured". ) Even have made changes on other locations, but no changes on the home page. Even after clearing the cache or even on the incognito mode. Thanks |
Hello - Was trying to deploy the operator on my ubuntu test machine (20.04.4). Have tried this on two test machine, but the pods were not running even after a long time. (screenshot attached).
The text was updated successfully, but these errors were encountered: