Open MikeSpreitzer opened 1 month ago
The cmupdate command fails if the Secret named "vc-vcluster" is not present when the command starts. See https://github.com/kubestellar/kubeflex/blob/v0.6.2/cmd/cmupdate/main.go#L178-L179 .
That command is run in a Pod that is not configured to depend on the vc-vcluster Secret. That Pod is specified by a Job constructed in https://github.com/kubestellar/kubeflex/blob/v0.6.2/pkg/reconcilers/shared/job.go .
I have, in one attempt use that Job, observed the cmupdate command to fail in every Pod (there were two) created for that Job. See https://github.com/kubestellar/kubestellar/issues/2373 .
See https://github.com/kubestellar/kubestellar/issues/2373 .
No timing splinters.
No response
Describe the bug
The cmupdate command fails if the Secret named "vc-vcluster" is not present when the command starts. See https://github.com/kubestellar/kubeflex/blob/v0.6.2/cmd/cmupdate/main.go#L178-L179 .
That command is run in a Pod that is not configured to depend on the vc-vcluster Secret. That Pod is specified by a Job constructed in https://github.com/kubestellar/kubeflex/blob/v0.6.2/pkg/reconcilers/shared/job.go .
I have, in one attempt use that Job, observed the cmupdate command to fail in every Pod (there were two) created for that Job. See https://github.com/kubestellar/kubestellar/issues/2373 .
Steps To Reproduce
See https://github.com/kubestellar/kubestellar/issues/2373 .
Expected Behavior
No timing splinters.
Additional Context
No response