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
I create a JobSet before installing the jobset controller/webhook, which means the JobSet is not mutated by the webhook, then I install the jobset and the controller panics:
In the recent days, I was testing the Helm chart, installed it and then uninstalled it. The CRD still exists in the cluster after I uninstalled the Helm chart, so I was able to create a JobSet without controller/webhook. Then I install the Helm chart again, I found that the controller panics due to nil pointer exception.
I found that there are some fields that will be nil if they are not defaulted by webhook (like js.Spec.Network), but the controller code assumes it to be non-nil, for example:
What happened:
I create a JobSet before installing the jobset controller/webhook, which means the JobSet is not mutated by the webhook, then I install the jobset and the controller panics:
What you expected to happen:
The controller should not panic even when reconciling a JobSet which is not mutated by webhook.
How to reproduce it (as minimally and precisely as possible):
Create a JobSet without defining
.spec.network.enableDNSHostnames
before installing the jobset controller/webhook.Anything else we need to know?:
Environment:
kubectl version
):git describe --tags --dirty --always
):The text was updated successfully, but these errors were encountered: