-
Notifications
You must be signed in to change notification settings - Fork 439
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
Panic applying virtual status patch #2293
Comments
@yankcrime thanks for reporting this! Strange, the panic actually occurs in the Kubernetes controller-manager itself, this might be a Kubernetes problem or something that has to do with our configuration |
Thanks @FabianKramm - it's an interesting one for sure. Let me know if I can provide you with any more details 👍 |
An additional datapoint: I tested this today with an older version of vCluster - |
@yankcrime I tried installing Kamaji Tenant control plane resource on host cluster without vcluster being installed on host cluster and I got same error in the I am suspecting this is an issue with the The error that was observed in kamaji controller when the
Questions:
|
What happened?
I'm seeing vCluster panic when it's applying a virtual status patch as a result of updates to a LoadBalancer Service in a virtual cluster. The output is as follows:
At this point no resources in the virtual cluster are synchronised, however if I kill the Pod for this virtual cluster then eventually everything restarts and resources start synchronising again.
What did you expect to happen?
I do not expect vCluster to panic, at worst an error but a yield so that resources continue to synchronise so that further actions in the virtual cluster aren't blocked.
How can we reproduce it (as minimally and precisely as possible)?
This is being triggered when creating a Kamaji TenantControlPlane resource in my virtual cluster. As part of this resource's creation it creates a Service of type LoadBalancer, and once this has been instantiated that's when I see the panic in vCluster. It's consistent and repeatable albeit a bit involved, happy to provide more details to assist with troubleshooting if it's not clear from the trace.
Anything else we need to know?
No response
Host cluster Kubernetes version
vcluster version
VCluster Config
Nothing special, the virtual cluster was created with the following command:
The text was updated successfully, but these errors were encountered: