Skip to content
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

Ingress configuration not work in GKE. #230

Closed
tharangar opened this issue Jun 17, 2019 · 2 comments
Closed

Ingress configuration not work in GKE. #230

tharangar opened this issue Jun 17, 2019 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@tharangar
Copy link
Contributor

Error. : Kubernetes required roll and cluster level access to some pods. This is not provided in local implementation but it worked.

no service with name copper/default-http-backend found: services "default-http-backend" is forbidden: User "system:serviceaccount:copper:
default" cannot get services in the namespace "copper"

@tharangar tharangar added the bug Something isn't working label Jun 17, 2019
@tharangar tharangar added this to the Milestone 18 May milestone Jun 17, 2019
@tharangar tharangar self-assigned this Jun 17, 2019
@tharangar tharangar added this to To do in Copper email solution via automation Jun 17, 2019
@tharangar tharangar modified the milestones: Milestone 18 May, June 20th Jun 17, 2019
@tharangar
Copy link
Contributor Author

This is due to GKE wanted special permission for ingress configurations.

@tharangar
Copy link
Contributor Author

It is enalbled through permission giving to cluster creation.

Copper email solution automation moved this from To do to Done Jun 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

No branches or pull requests

1 participant