-
Notifications
You must be signed in to change notification settings - Fork 2k
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
expected type *v1beta1.Deployment, but watch event object had type *v1.Deployment #719
Comments
Thanks for reporting this issue. We used If we are to move the apiGroup to core Thoughts @brancz? |
Is that so? Workloads went v1 in 1.9 if I recall correctly, so our compatibility matrix is correct as is (it says we don't even make any support claims about 1.9 at this point). Is the |
So I checked It doesn't seem to explain this error though. Will have to dig deeper. |
Please disregard my earlier comments. This should be fixed by #720 |
I think this can be closed now. |
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
Deployed
quay.io/coreos/kube-state-metrics:v1.6.0-rc.0
I keep getting these messages in logs, over and over:
What you expected to happen:
It shouldn't log errors.
How to reproduce it (as minimally and precisely as possible):
This my deployment yaml file:
kube-state-metrics.yaml.txt
Anything else we need to know?:
Environment:
kubectl version
): v1.13.3The text was updated successfully, but these errors were encountered: