Comments (4)
oktalz
commented on June 20, 2024
2
hi @eugenebzht thx for reporting, fix incoming with next version of ingress controller
from kubernetes-ingress.
tkcontiant
commented on June 20, 2024
1
Description of the problem
I am using haproxy-ingress via helm-chart.
After the initial deployment, I notice CRD Checker JOB exit with an ERROR state.
A version of the image: haproxytech/kubernetes-ingress:1.11.0
Expected behavior
After that Kubernetes evaluated this batch job as failed, it's not the end of the world everything works correctly.
But I think a simple EXIT code change could prevent many people from wondering if and how there is a problem with CDS's.
│ 2024/03/13 20:08:40 INFO src/main.go:85 HAProxy Ingress Controller CRD Updater v1.11.0 13fc60b9.dirty
│ 2024/03/13 20:08:40 INFO src/main.go:86 Build from: github.com/haproxytech/kubernetes-ingress
│ 2024/03/13 20:08:40 INFO src/main.go:87 Build date: 2024-03-08T10:47:39Z
│ 2024/03/13 20:08:40 INFO src/main.go:89 checking CRDS
│ 2024/03/13 20:08:40 INFO src/main.go:89
│ 2024/03/13 20:08:40 INFO job/crd-check.go:50 checking CRD ingress.v1.haproxy.org_defaults.yaml
│ 2024/03/13 20:08:40 INFO job/crd-check.go:57 CRD ingress.v1.haproxy.org_defaults.yaml does not exist
│ 2024/03/13 20:08:40 ERROR runtime/proc.go:271 customresourcedefinitions.apiextensions.k8s.io "defaults.ingress.v1.haproxy.org" already exists
│ 2024/03/13 20:26:34 INFO job/crd-check.go:50 checking CRD ingress.v1.haproxy.org_globals.yaml
│ 2024/03/13 20:26:34 INFO job/crd-check.go:57 CRD ingress.v1.haproxy.org_globals.yaml does not exist
│ 2024/03/13 20:26:34 ERROR runtime/proc.go:271 customresourcedefinitions.apiextensions.k8s.io "globals.ingress.v1.haproxy.org" already exists
Steps to reproduce the problem
- helm upgrade --install haproxy-ingress . -n haproxy-ingress --create-namespace
- repeated the command and watch the pod's statuses in k9s or lens
Environment information
haproxytech/kubernetes-ingress:1.11.0
name: kubernetes-ingress
sources:
- https://github.com/haproxytech/kubernetes-ingress
type: application
version: 1.38.2
from kubernetes-ingress.
apalmatier
commented on June 20, 2024
1
Encountering this same issue on k8s 1.28.5, same helm version.
from kubernetes-ingress.
eugenebzht
commented on June 20, 2024
Also this is not happens with previous version of HAProxy ingress controller with v1alpha2 CRD api version:
Autoscroll:On FullScreen:Off Timestamps:Off Wrap:Off │
│ 2024/03/13 14:04:00 maxprocs: Leaving GOMAXPROCS=4: CPU quota undefined │
│ 2024/03/13 14:04:00 src/main.go:75 │
│ _ _ _ ____ │
│ | | | | / \ | _ \ _ __ _____ ___ _ │
│ | |_| | / _ \ | |_) | '__/ _ \ \/ / | | | │
│ | _ |/ ___ \| __/| | | (_) > <| |_| | │
│ |_| |_/_/ \_\_| |_| \___/_/\_\\__, | │
│ _ __ _ |___/ ___ ____ │
│ | |/ / _| |__ ___ _ __ _ __ ___| |_ ___ ___ |_ _/ ___| │
│ | ' / | | | '_ \ / _ \ '__| '_ \ / _ \ __/ _ \/ __| | | | │
│ | . \ |_| | |_) | __/ | | | | | __/ || __/\__ \ | | |___ │
│ |_|\_\__,_|_.__/ \___|_| |_| |_|\___|\__\___||___/ |___\____| │
│ │
│ │
│ 2024/03/13 14:04:00 src/main.go:76 │
│ ____ ____ ____ _ _ _ _ │
│ / ___| _ \| _ \ | | | |_ __ __| | __ _| |_ ___ _ __ │
│ | | | |_) | | | | | | | | '_ \ / _` |/ _` | __/ _ \ '__| │
│ | |___| _ <| |_| | | |_| | |_) | (_| | (_| | || __/ | │
│ \____|_| \_\____/ \___/| .__/ \__,_|\__,_|\__\___|_| │
│ |_| │
│ │
│ │
│ 2024/03/13 14:04:00 INFO src/main.go:77 HAProxy Ingress Controller CRD Updater v1.10.11 dfa911b.dirty │
│ 2024/03/13 14:04:00 INFO src/main.go:78 Build from: https://github.com/haproxytech/kubernetes-ingress │
│ 2024/03/13 14:04:00 INFO src/main.go:79 Build date: 2024/02/13 15:55:08 │
│ │
│ 2024/03/13 14:04:00 INFO job/crd-check.go:30 checking CRDS │
│ 2024/03/13 14:04:00 INFO job/crd-check.go:49 │
│ 2024/03/13 14:04:00 INFO job/crd-check.go:50 checking CRD defaults.core.haproxy.org │
│ 2024/03/13 14:04:00 INFO job/crd-check.go:66 CRD defaults.core.haproxy.org exists │
│ 2024/03/13 14:04:00 INFO job/crd-check.go:75 CRD defaults.core.haproxy.org exists as v1alpha2, nothing to do │
│ 2024/03/13 14:04:00 INFO job/crd-check.go:49 │
│ 2024/03/13 14:04:00 INFO job/crd-check.go:50 checking CRD globals.core.haproxy.org │
│ 2024/03/13 14:04:00 INFO job/crd-check.go:66 CRD globals.core.haproxy.org exists │
│ 2024/03/13 14:04:00 INFO job/crd-check.go:75 CRD globals.core.haproxy.org exists as v1alpha2, nothing to do │
│ 2024/03/13 14:04:00 INFO job/crd-check.go:49 │
│ 2024/03/13 14:04:00 INFO job/crd-check.go:50 checking CRD backends.core.haproxy.org │
│ 2024/03/13 14:04:00 INFO job/crd-check.go:66 CRD backends.core.haproxy.org exists │
│ 2024/03/13 14:04:00 INFO job/crd-check.go:75 CRD backends.core.haproxy.org exists as v1alpha2, nothing to do │
│ 2024/03/13 14:04:00 INFO job/crd-check.go:89 │
│ 2024/03/13 14:04:00 INFO job/crd-check.go:90 CRD update done
I suppose that this may be an incorrect handling during CRD versions comparison after switching to API v1.
from kubernetes-ingress.
Related Issues (20)
- Prometheus metrics of the pods in MAINT state HOT 1
- annotation "haproxy.org/load-balance: uri path-only" causes configuration reloads HOT 2
- Access logs settings get overridden if using a Global Custom Resource HOT 6
- constant prometheus reloading HOT 4
- default backend not working when --ingress.class defined HOT 2
- Regular expressions in "path" do not appear to work HOT 1
- docs: `haproxy.org/server-ssl` tip is misleading HOT 1
- Ingress reloading almost all the time with v1.11.1 HOT 1
- Add ability to use oauth2 authentication. HOT 3
- Use existing NLB for HAProxy ingress HOT 2
- questions about request headers HOT 3
- http -> https default redirect not working by default HOT 10
- Deployment yaml still point to privileged port after s6 upgrade HOT 3
- frontend tcp-514: cannot bind socket (Permission denied) for [0.0.0.0:514] HOT 2
- haproxy ingress 1.11.2 reloads when number of backend pods scales HOT 9
- When specifying a server-proto annotation the check parameter is omitted
- Using both annotations "haproxy.org/cr-backend" and "haproxy.org/<parameter>" HOT 3
- Docs: when adjusting --sync-period, must also adjust initialDelaySeconds HOT 4
- Controller restarts haproxy every 5 minutes with message "restart required : Global config updated: " HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kubernetes-ingress.