We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What happened: when deploying a VirtualMachine like https://github.com/jkleinlercher/test9-repo/blob/master/helm/chart/templates/VirtualMachine.yaml via ArgoCD, the virt-launcer pod stays in status "progressing" forever.
What you expected to happen: I want to see the pod in status "healthy"
How to reproduce it (as minimally and precisely as possible): deploy a VirtualMachine with argocd and you will immediatly see the same behaviour
Additional context:
The reason is because the vm-launcher has set "restartPolicy: Never":
kubevirt/pkg/virt-controller/services/template.go
Line 583 in a565ade
and according to argoproj/argo-cd#15317 and https://github.com/argoproj/gitops-engine/blob/187312fe86ed627b1cf4147c13dccf9ff331424b/pkg/health/health_pod.go#L30 when setting "restartPolicy: never", argocd doesn't set the pod state to healthy.
Does kubevirt need to set "restartPolicy: never" on the vm-launcher pod, or can we make this configurable?
Environment:
virtctl version
kubectl version
uname -a
The text was updated successfully, but these errors were encountered:
/cc @DMajrekar
Sorry, something went wrong.
I am experiencing the same issue with OpenShift virtualization while using ArgoCD version 2.10
No branches or pull requests
What happened:
when deploying a VirtualMachine like https://github.com/jkleinlercher/test9-repo/blob/master/helm/chart/templates/VirtualMachine.yaml via ArgoCD, the virt-launcer pod stays in status "progressing" forever.
What you expected to happen:
I want to see the pod in status "healthy"
How to reproduce it (as minimally and precisely as possible):
deploy a VirtualMachine with argocd and you will immediatly see the same behaviour
Additional context:
The reason is because the vm-launcher has set "restartPolicy: Never":
kubevirt/pkg/virt-controller/services/template.go
Line 583 in a565ade
and according to argoproj/argo-cd#15317 and https://github.com/argoproj/gitops-engine/blob/187312fe86ed627b1cf4147c13dccf9ff331424b/pkg/health/health_pod.go#L30 when setting "restartPolicy: never", argocd doesn't set the pod state to healthy.
Does kubevirt need to set "restartPolicy: never" on the vm-launcher pod, or can we make this configurable?
Environment:
virtctl version
): v1.2.0kubectl version
): 1.28uname -a
): N/AThe text was updated successfully, but these errors were encountered: