You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently using vcluster in our production environment, and we encountered an occasional problem where the <vcluster-id>-certs secret was not created after the vcluster was created, which ultimately resulted in apiserver, controller-manager, and etcd not being Running.
Our guess is that it is a k8s cluster network issue that causes the syncer container to fail when creating the secret.
Which solution do you suggest?
We modified the Initialize method in pkg/setup/initialize.go to set the timeout to 5 minutes, which I think alleviates the problem.
And we created a 30s context in the initialize method, mainly to solve the problem of calling k8s resources due to network problems that cause the request to get stuck, and the PollUntilContextTimeout can't go to the next loop.
Which alternative solutions exist?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
We are currently using vcluster in our production environment, and we encountered an occasional problem where the
<vcluster-id>-certs
secret was not created after the vcluster was created, which ultimately resulted in apiserver, controller-manager, and etcd not being Running.Our guess is that it is a k8s cluster network issue that causes the syncer container to fail when creating the secret.
Which solution do you suggest?
We modified the Initialize method in
pkg/setup/initialize.go
to set the timeout to 5 minutes, which I think alleviates the problem.And we created a 30s context in the initialize method, mainly to solve the problem of calling k8s resources due to network problems that cause the request to get stuck, and the
PollUntilContextTimeout
can't go to the next loop.Which alternative solutions exist?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: