Installation helm chart failed with "error getting secret"

[pankajjoshi32]

We are tying to deploy Nginx ingress opensource version on AKS cluster using Helm chart.

I got below log using kubectl logs 'ingress-nginx-admission-create-wpfmj' -n 'pqn'
We are getting below error:

W1202 11:10:06.761214 1 client_config.go:615] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
{"err":"Get "https://10.236.0.1:443/api/v1/namespaces/pcc/secrets/ingress-nginx-admission\": dial tcp 10.236.0.1:443: i/o timeout","level":"fatal","msg":"error getting secret","source":"k8s/k8s.go:232","time":"2023-12-02T11:10:36Z"}

However I am able to deployNginx ingress on dev environment but failing for test environment with above error
Could you please let us know what could be the issue?

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[pankajjoshi32]

Please see another log for command kubectl logs 'ingress-nginx-admission-create-wpfmj' -n 'pcc'

W1202 11:10:06.761214 1 client_config.go:615] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
{"err":"Get "https://10.236.0.1:443/api/v1/namespaces/pcc/secrets/ingress-nginx-admission\": dial tcp 10.236.0.1:443: i/o timeout","level":"fatal","msg":"error getting secret","source":"k8s/k8s.go:232","time":"2023-12-02T11:10:36Z"}

kubectl describe pod -n pqn ingress-nginx-admission-create-wpfmj
Name: ingress-nginx-admission-create-wpfmj
Namespace: pqn
Priority: 0
Service Account: ingress-nginx-admission
Node: aks-system-15906107-vmss000002/10.149.177.55
Start Time: Sat, 02 Dec 2023 16:36:33 +0530
Labels: app.kubernetes.io/component=admission-webhook
app.kubernetes.io/instance=ingress-nginx
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=ingress-nginx
app.kubernetes.io/part-of=ingress-nginx
app.kubernetes.io/version=1.8.1
controller-uid=3acde167-ba69-4940-a0ed-365a4ee949dd
helm.sh/chart=ingress-nginx-4.7.1
job-name=ingress-nginx-admission-create

Annotations:
Status: Running
IP: 10.149.177.61
IPs:
IP: 10.149.177.61
Controlled By: Job/ingress-nginx-admission-create
Containers:
create:
Container ID: containerd://a5dc244a10b3542b43a52bbd2c0e2b9b7fd01b312db55cd7e851707a4c5b3f6e
Image: p-nexus-3.development.nl.eu.xxxxxxx.com:18445/ingress-nginx/kube-webhook-certgen:v20230407@sha256:543c40fd093964bc9ab509d3e791f9989963021f1e9e4c9c7b6700b02bfb227b
Image ID: p-nexus-3.development.nl.eu.xxxxxxx.com:18445/ingress-nginx/kube-webhook-certgen@sha256:543c40fd093964bc9ab509d3e791f9989963021f1e9e4c9c7b6700b02bfb227b
Port:
Host Port:
Args:
create
--host=ingress-nginx-controller-admission,ingress-nginx-controller-admission.$(POD_NAMESPACE).svc
--namespace=$(POD_NAMESPACE)
--secret-name=ingress-nginx-admission
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Sat, 02 Dec 2023 16:38:44 +0530
Finished: Sat, 02 Dec 2023 16:39:14 +0530
Ready: False
Restart Count: 3
Environment:
POD_NAMESPACE: pqn (v1:metadata.namespace)
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-wqhg4 (ro)
Conditions:
Type Status
Initialized True
Ready False
PodScheduled True
Volumes:
kube-api-access-wqhg4:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional:
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors: kubernetes.io/os=linux
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message

---

QoS Class: BestEffort
Node-Selectors: kubernetes.io/os=linux
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message

---

Events:
Type Reason Age From Message

---

Normal Scheduled 3m12s default-scheduler Successfully assigned pcc/ingress-nginx-admission-create-wpfmj to aks-system- Normal Scheduled 3m12s default-scheduler Successfully assigned pcc/ingress-nginx-admission-create-wpfmj to aks-system-15906107-vmss000002
15906107-vmss000002
Normal Pulled 61s (x4 over 3m12s) kubelet Container image "p-nexus-3.development.nl.eu.xxxxxxx.com:18445/ingress-nginx/kube-webhook-certgen:v20230407@sha256:543c40fd093964bc9ab509d3e791f9989963021f1e9e4c9c7b6700b02bfb227b" already present on machine
Normal Created 61s (x4 over 3m12s) kubelet Created container create
Normal Started 61s (x4 over 3m12s) kubelet Started container create
Warning BackOff 4s (x6 over 2m10s) kubelet Back-off restarting failed container create in pod ingress-nginx-admission-create-wpfmj_pcc(1cb675af-a5bc-4dc7-8772-306f415b8d48)

[longwuyuan]

/remove-kind bug

Hi, please check the questions that are asked in a new issue template and edit your issue description by providing thise answers. It helps to get some actionable comments.

Kindly format your issue description as markdown so the info is readable

/triage needs-information

[strongjz]

/assign @longwuyuan