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

GKE tests failing due to legacy logging and monitoring defaults in autogen #384

Closed
bharathkkb opened this issue Dec 18, 2019 · 1 comment · Fixed by #387
Closed

GKE tests failing due to legacy logging and monitoring defaults in autogen #384

bharathkkb opened this issue Dec 18, 2019 · 1 comment · Fixed by #387
Assignees
Labels
bug Something isn't working P1 highest priority issues triaged Scoped and ready for work

Comments

@bharathkkb
Copy link
Member

GKE tests failing to converge due to defaults that point to the old monitoring/logging api.
I was able to fix it by defaulting to logging/monitoring.googleapis.com/kubernetes
Error 400: Legacy monitoring is not supported in clusters running Kubernetes 1.15 or above

@morgante morgante added the bug Something isn't working label Dec 18, 2019
@morgante morgante added triaged Scoped and ready for work P1 highest priority issues labels Dec 18, 2019
@jasonbisson
Copy link

Updating to logging/monitoring.googleapis.com/kubernetes worked for me too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working P1 highest priority issues triaged Scoped and ready for work
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants