k8s-ci-robot
commented
3 days ago 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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
longwuyuan
little-helper-001
What happened:
I setup a fresh Kubernetes cluster using kubeadm on baremetal hosts, with Calico as a networking solution. I have downloaded the baremetal manifest and only made two small modifications to it, and exposed the two ports of the ingress-nginx-controller service to unprivileged ports on the nodes.
Deploying an ingress now fails with the following error message:
Error from server (InternalError): error when creating "ingress.yaml": Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": failed to call webhook: Post "https://ingress-nginx-controller-admission.ingress-nginx.svc:443/networking/v1/ingresses?timeout=10s": context deadline exceededWhat you expected to happen:
The ingress file should have been validated and deployed.
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):
NGINX Ingress controller Release: v1.12.0-beta.0 Build: 80154a3694b52736c88de408811ebd1888712520 Repository: https://github.com/kubernetes/ingress-nginx nginx version: nginx/1.25.5
Kubernetes version (use
kubectl version):Client Version: v1.29.9 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.31.2
Environment:
Cloud provider or hardware configuration: Baremetal
OS (e.g. from /etc/os-release): Fedora Server 41
Kernel (e.g.
uname -a): 6.11.6-300.fc41.x86_6Install tools:
Basic cluster related info:
kubectl get nodes -o wideHow was the ingress-nginx-controller installed:
I have downloaded the baremetal manifest and only made two small modifications to it, and exposed the two ports of the ingress-nginx-controller service to unprivileged ports on the nodes.
kubectl describe ingressclasseskubectl -n <ingresscontrollernamespace> get all -A -o widekubectl -n <ingresscontrollernamespace> describe po <ingresscontrollerpodname>Current state of ingress object, if applicable: Not applicable
Others:
I can deploy ingresses by manually removing the admission controller, but instead of hacking this issue I would prefer to understand and fix it the proper way.
How to reproduce this issue:
Install Base OS
Install RHEL or Fedora based system. Disable SELinux, open Firewall. Install containerd + kubernetes tools.
Create cluster with kubeadm
sudo kubeadm init --upload-certs --control-plane-endpoint "kubernetes-loadbalancer.my-domain.com" --pod-network-cidr 10.0.0.0/16
kubernetes-loadbalancer.my-domain.com points to a haproxy that forwards port 80 to 30100 on the worker, port 443 to 30101 on the worker and port 6443 to port 6443 on the controlplane node.
Join a worker node with the command provided in the output.
Install Calico
Install the ingress controller
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/main/deploy/static/provider/baremetal/deploy.yaml with a modification to expose the HTTP and HTTPS port as unprivileged node ports.
Try to create an ingress e.g.
apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: test-ingress spec: rules:
path: /* pathType: Prefix backend: service: name: service-test port: number: 80