kubernetes-ingress: add crdjob enablement configuration - #379
Conversation
|
Sadly, this has to be rejected. We want to maintain a well-defined and consistent state in which the CRD job has always been run and the CRDs have always been upgraded to the latest version. Introducing a toggle here could lead to inconsistent states and various issues that we specifically want to avoid for our users and customers. |
|
What about configuring |
|
The CRD upgrade should typically complete within a few seconds at most, so there is little to be gained from changing |
|
I understand your question; we are seeing our argocd instance sometimes keep hanging indefinitely on the job. This might be verry specific to our environment, and most likely not the root cause But If we can set the activedeadline seconds we can at least limit the sympton |
|
I understand. Please send a PR for this, and I’ll get it merged and released as soon as possible. |
Make it possible to disable the crdjob, as some users will not need or want to use the crds.