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

Custom namespace results in excessive logs to kubeapi #1090

Open
deefdragon opened this issue Sep 26, 2024 · 1 comment
Open

Custom namespace results in excessive logs to kubeapi #1090

deefdragon opened this issue Sep 26, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@deefdragon
Copy link

deefdragon commented Sep 26, 2024

What version of redis operator are you using?
redis-operator version: 0.18

Does this issue reproduce with the latest release?
yes

What operating system and processor architecture are you using (kubectl version)?

Client Version: v1.28.9
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.31.1

What did you do?
Deployed the operator to a namespace other than redis-operator (such as op-redis). Thus resulted in the api-server being unable to hit my webhook service. During my testing, I had to use the full domain name to get an IP address, and as I also have a custom cluster domain, this should be taken into consideration.

Someone in #955 had similar errors, and suggested editing the CRDs to remove certain conversion sections. Editing the CRDs is obviously not ideal.

What did you expect to see?
Normal operation of kube-apiserver such that there are no extraneous error logs.

What did you see instead?
Excess logs in the kube-apiserver logs about ListAndWatch errors. The following outputs approximatly once a second.

W0926 03:36:48.762752       1 reflector.go:561] storage/cacher.go:/redis.redis.opstreelabs.in/redis: failed to list redis.redis.opstreelabs.in/v1beta1, Kind=Redis: conversion webhook for redis.redis.opstreelabs.in/v1beta2, Kind=Redis failed: Post "https://webhook-service.redis-operator.svc:443/convert?timeout=30s": service "webhook-service" not found
E0926 03:36:55.870301       1 cacher.go:478] cacher (redis.redis.redis.opstreelabs.in): unexpected ListAndWatch error: failed to list redis.redis.opstreelabs.in/v1beta1, Kind=Redis: conversion webhook for redis.redis.opstreelabs.in/v1beta2, Kind=Redis failed: Post "https://webhook-service.redis-operator.svc:443/convert?timeout=30s": service "webhook-service" not found; reinitializing...
@deefdragon deefdragon added the bug Something isn't working label Sep 26, 2024
@ktzsolt
Copy link

ktzsolt commented Dec 13, 2024

In your case it is HTTP 404 because it tries to connect to the webhook service in redis-operator, no matter where you install the operator, but in #955 it is installed in redis-operator namespace and gives 502 for some other reason.

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
None yet
Development

No branches or pull requests

2 participants