argo-workflows: Workflow controller v3 fails to start on OpenShift 3.11

Summary

When tying to upgrade to Argo workflows 3, startup of the workflow controller on OpenShift 3.11 failes, because the underlying api for leader election is not available.

A configuration for disabling leader election might mitigate the situation.

Diagnostics

What Kubernetes provider are you using?

OpenShift 3.11 which is running on Kubernetes 1.11

What version of Argo Workflows are you running?

v3.0.1

The issue can be reproduced by running the default namespace install manifest

E0409 12:01:04.539406       1 leaderelection.go:329] error initially creating leader election record: the server could not find the requested resource (post leases.coordination.k8s.io)
time="2021-04-09T12:01:09.671Z" level=info msg="Get leases 404"
time="2021-04-09T12:01:09.672Z" level=info msg="Create leases 404"

Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 9
  • Comments: 20 (18 by maintainers)

Commits related to this issue

Most upvoted comments

I also encountered the same issue as @vbarbaresi in Openshift 3.11 (Argo v3.0.2).

time="2021-04-22T08:23:06.630Z" level=info msg="Get leases 404"
time="2021-04-22T08:23:06.631Z" level=info msg="Create leases 404"
E0422 08:23:06.631986       1 leaderelection.go:329] error initially creating leader election record: the server could not find the requested resource (post leases.coordination.k8s.io)