pplease help me i am getting this error for nginx-ingress-test...
because i am deploying ingress in 2 environments.. dev and test...
i have succesfully created in default namespace..
i am getting these errors when i tried for dev and test environments..
once i used same hostport 8080 for dev and test also.. but i didnt select node.. showing error prehostfits.. after that i deleted hostport line on the configuration then it was successfully assigned to my node..
but i am getting crashloopbackoff error..
logs are
&{NGINX 0.9.0-beta.15 git-a3e86f2 https://github.com/kubernetes/ingress}
I1120 17:22:04.422818 7 launch.go:116] Watching for ingress class: nginx
I1120 17:22:04.423086 7 launch.go:291] Creating API client for https://10.96.0.1:443
I1120 17:22:04.439874 7 launch.go:304] Running in Kubernetes Cluster version v1.8 (v1.8.2) - git (clean) commit bdaeafa71f6c7c04636251031f93464384d54963 - platform linux/amd64
F1120 17:22:04.441257 7 launch.go:136] ✖ It seems the cluster it is running with Authorization enabled (like RBAC) and there is no permissions for the ingress controller. Please check the configuration...
can u help me why i am getting this issue.. we cant create same configuration file in different namespaces..
Hi @vamsi248 , this repo is for documentation and website issue. Please try to ask your problem here
This issue sounds more like a request for support and less like an issue specifically for docs. I encourage you to bring your question to the #kubernetes-users channel in Kubernetes slack. You can also search resources like Stack Overflow for answers to similar questions.
You can also open issues for Kubernetes functionality in https://github.com/kubernetes/kubernetes.
If this is a documentation issue, please re-open this issue.
@vamsi248, I see the same error in kubectl logs. How did you resolve the error?
F0109 18:02:17.347897 6 launch.go:136] ✖ It seems the cluster it is running with Authorization enabled (like RBAC) and there is no permissions for the ingress controller. Please check the configuration
I've added all the info in https://github.com/kubernetes/ingress-nginx/issues/1531#issuecomment-356355924.
I was able to enable RBAC using helm (--set rbac.create=true) and this error is not seen anymore, and the nginx ingress controller is working as expected!
helm install --name my-release stable/nginx-ingress --set rbac.create=true
Hey,
i am new to Helm.. can i ask you a dum Question???
is Helm having any UI... or if i want to delploy apps using Helm Charts
from UI ( example for everydeployment how my app gets deployed to
particular namespace without triggeting or running any commands)..
On Wed, Jan 10, 2018 at 11:21 PM Vikram Hosakote notifications@github.com
wrote:
I was able to enable RBAC using helm (--set rbac.create=true) and this
error is not seen anymore, and the nginx ingress controller is working as
expected!helm install --name my-release stable/nginx-ingress --set rbac.create=true
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/website/issues/6390#issuecomment-356847739,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfvuC8ZpPsY87FdbL71jMY0_69sAuCfYks5tJbZjgaJpZM4Qkrjp
.
Most helpful comment
I was able to enable RBAC using helm (
--set rbac.create=true) and this error is not seen anymore, and the nginx ingress controller is working as expected!