-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
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
crd-check.go invocation should be idempotent in case of exising CRDs #630
Comments
Also this is not happens with previous version of HAProxy ingress controller with v1alpha2 CRD api version:
I suppose that this may be an incorrect handling during CRD versions comparison after switching to API v1. |
Description of the problem I am using haproxy-ingress via helm-chart. Expected behavior After that Kubernetes evaluated this batch job as failed, it's not the end of the world everything works correctly.
Steps to reproduce the problem
Environment information
|
Encountering this same issue on k8s 1.28.5, same helm version. |
hi @eugenebzht thx for reporting, fix incoming with next version of ingress controller |
Currently multiple executions of /haproxy-ingress-controller --job-check-crd on the same cluster leads to an error as follows:
2024/03/13 13:37:19 ERROR runtime/proc.go:271 customresourcedefinitions.apiextensions.k8s.io "defaults.ingress.v1.haproxy.org" already exists
As this job also included into Helm chart and executed on every ArgoCD sync, all next sync operations failing after initial install.
Kubernetes version: 1.26.5
HAproxy version:
Full command output:
The text was updated successfully, but these errors were encountered: