longwuyuan
commented
5 months ago /remove-kind bug
Lets add the bug label after triaging is completed
-
You have been succint and cryptic in your issue description. It does not help
-
Please answer the questions that are asked in a new issue template exactly as is because that info is input for a reader to understand and reproduce
-
For example, the simple question is how did you install so the expectation is you copy paste the exact command executed and the complete values file used. In your case, since you use ArgoCD, then it is expected that at least the complete values as is from the original install be presented as is. Providing the later modifications is great
-
At this stage for a problem like this, its not going to be possible to test ArgoCD in the CI. So please do a helm install command using the same values file and update the results. This will know if using ArgoCD introduces the problem or not
/triage needs-information /kind support
ducnm0711
k8s-ci-robot
jlm0x017
mykaua
Pilotindream
tl;dr: nginx fails to start in controller:
What happened:
Using helm-chart 4.9.1 we experience no issues.
In updating to helm-chart 4.10.0 (and in 4.10.1) we have failures. The deployment for ingress-nginx-controller pods fail with these events:
What you expected to happen:
I expect helm-chart versions to upgrade cleanly, or with well-advertised required configuration changes.
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):
version from running 4.9.1 helm chart: $ /nginx-ingress-controller --version
NGINX Ingress controller Release: v1.9.6 Build: 6a73aa3b05040a97ef8213675a16142a9c95952a Repository: https://github.com/kubernetes/ingress-nginx nginx version: nginx/1.21.6
From failing 4.10.0 helm chart:
*Kubernetes version
Client Version: v1.28.2 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.28.8-eks-adc7111
Environment:
AWS EKS 1.28
Bottlerocket OS 1.19.4 (aws-k8s-1.28)
Kernel 6.1.82
Install tools:
Basic cluster related info:
kubectl get nodes -o wideHow was the ingress-nginx-controller installed:
Current State of the controller:
Current state of ingress object, if applicable:
Others:
pod logs
logs from a failing pod:
How to reproduce this issue:
These should suffice to install working and non-working versions: ``` $ cat Chart.yaml. apiVersion: argoproj.io/v1alpha1 kind: application name: nginx-internal version: 0.0.1 dependencies: - name: ingress-nginx alias: nginx-internal # https://github.com/kubernetes/ingress-nginx?tab=readme-ov-file#supported-versions-table version: 4.10.0 repository: https://kubernetes.github.io/ingress-nginx $ cat values.yaml nginx-internal: controller: service: annotations: service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:acm:us-east-1:444444444:certificate/eca520df-333333-3333 helm dependency build && helm template --name-template foo --namespace foo --values values.yaml . --debug > foo-4.10.0 kubectl apply -f foo-4.10.0 # you should see the pod under the RS in a crashloopbackoff state kubectl delete -f foo-4.10.0 $ downgrade Chart.yaml to 4.9.1 helm dependency build && helm template --name-template foo --namespace foo --values values.yaml . --debug > foo-4.9.1 kubectl apply -f foo.4.9.1 # all resources should be created successfully kubectl delete -f foo-4.9.1 # final clean-up ```Anything else we need to know:
Checking recent issues, this appears to be the only close complaint: https://github.com/kubernetes/ingress-nginx/issues/11254. That said, the versions are different. They're on controller-1.9.4 and a bump to 1.9.6 fixes their issue. I did not try providing an emptydir for geoip configuration, or other stub files, as he did.
attempted work-arounds I tried to alternate specifcations:
1) in this attempt, I added the following to values.yaml:
the chart still failed with crashloopbackoff
2) in this attempt, I added the following to values.yaml:
the chart still failed with crashloopbackoff