-
-
Notifications
You must be signed in to change notification settings - Fork 242
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
kube-api log ListAndWatch error: failed to list redis.redis.opstreelabs.in/v1beta1, Kind=RedisReplication: conversion webhook for redis.redis.opstreelabs.in/v1beta2 #955
Comments
We had same issue on multiple clusters, redis operator helm chart version 0.15.9 We edited redis crd's: redis.redis.redis.opstreelabs.in And deleted this part:
|
We're also dealing with this issue. Thanks a lot, @MoZadro, for sharing your workaround! |
I was able to upgrade to 0.18.0 chart now that the image is pushed to quay.io and the issue (error messages in kube-api pods) is gone now |
I am reopening this. In dev cluster the issue went away after upgrading the operator to The version of the api for redis resources are
TBH I don't know what the difference is between the 2 cluster that makes this happen. |
based on @MoZadro comment, I found the difference in our clusters,
but in test we had this:
We installed the |
What version of redis operator are you using?
redis-operator chart 0.15.10 version from https://ot-container-kit.github.io/helm-charts
Does this issue reproduce with the latest release?
latest helm chart is not available, only 0.15.10.
Latest image published to quay is 0.15.1
What did you do?
What did you expect to see?
No errors by the kube-api pods
What did you see instead?
E0529 10:31:11.738631 1 cacher.go:470] cacher (redisreplications.redis.redis.opstreelabs.in): unexpected ListAndWatch error: failed to list redis.redis.opstreelabs.in/v1beta1, Kind=RedisReplication: conversion webhook for redis.redis.opstreelabs.in/v1beta2, Kind=RedisReplication failed: Post "https://webhook-service.redis-operator.svc:443/convert?timeout=30s": proxy error from 127.0.0.1:9345 while dialing 10.42.118.14:9443, code 502: 502 Bad Gateway; reinitializing...
The text was updated successfully, but these errors were encountered: