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
This inconsistency results in a CrashLoopBackOff, as the health check is looking for the service on port 8080, while the actual service runs on port 8888.
What you expected to happen:
Both ports are hardcoded and should be aligned to avoid this issue.
How to reproduce it (as minimally and precisely as possible):
What happened:
External-dns uses a hardcoded port (8888) for Webhook providers:
external-dns/main.go
Line 371 in b336c52
However, the Helm chart defines a liveness probe for the webhook provider on port 8080:
external-dns/charts/external-dns/templates/deployment.yaml
Line 162 in b336c52
This inconsistency results in a CrashLoopBackOff, as the health check is looking for the service on port 8080, while the actual service runs on port 8888.
What you expected to happen:
Both ports are hardcoded and should be aligned to avoid this issue.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
external-dns --version
): external-dns-helm-chart-1.15.0The text was updated successfully, but these errors were encountered: