-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
when the service port changes, the ingress cannot detect the change and adjust the upstream port. #12209
Comments
This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The 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-sigs/prow repository. |
Once the information in the issue description is helpful to readers here, then you can re-open this issue. I will close it for now as there is no action item here. /remove-kind bug |
@longwuyuan: Closing this issue. In response to this:
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-sigs/prow repository. |
What happened:
To illustrate this problem in a simple example,
deploy.yaml:
apiVersion: apps/v1
kind: Deployment
metadata:
name: tony
namespace: test
spec:
replicas: 1
selector:
matchLabels:
app: tony
version: v1
template:
metadata:
labels:
app: tony
version: v1
spec:
containers:
- image: nginx:latest
imagePullPolicy: IfNotPresent
name: container-0
imagePullSecrets:
- name: default-secret
restartPolicy: Always
schedulerName: default-scheduler
service.yaml:
apiVersion: v1
kind: Service
metadata:
labels:
app: tony
name: tony
namespace: test
spec:
internalTrafficPolicy: Cluster
ports:
port: 80
protocol: TCP
targetPort: 81
selector:
app: tony
type: ClusterIP
ingress.yaml:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: test
namespace: test
spec:
rules:
http:
paths:
service:
name: tony
port:
number: 80
path: /
pathType: ImplementationSpecific
service.yaml:
apiVersion: v1
kind: Service
metadata:
labels:
app: tony
name: tony
namespace: test
spec:
internalTrafficPolicy: Cluster
ports:
port: 80
protocol: TCP
targetPort: 81
selector:
app: tony
type: ClusterIP
What you expected to happen:
when I modify a service, the ingress should reload the service to ensure the correctness of the forwarding result.
i wonder, is this a normal situation? or ingress cannot be supported this feature for some reason
maybe the ingress cannot identify service changes
NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):
Kubernetes version (use
kubectl version
):Environment:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release): Centos 7.6
Kernel (e.g.
uname -a
):Linux 192-168-0-174 3.10.0-862.14.4.el7.x86_64 Basic structure #1 SMP Wed Sep 26 15:12:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Install tools:
kubeadm
Basic cluster related info:
kubectl version
kubectl get nodes -o wide
192.168.0.121 Ready 3d21h v1.23.15 192.168.0.121 CentOS Linux 7 (Core) 3.10.0-862.14.4.el7.x86_64 docker://18.9.0
192.168.0.174 Ready etcd,master 4d1h v1.23.15 192.168.0.174 CentOS Linux 7 (Core) 3.10.0-862.14.4.el7.x86_64 docker://18.9.0
192.168.0.185 Ready etcd,master 4d1h v1.23.15 192.168.0.185 CentOS Linux 7 (Core) 3.10.0-957.el7.x86_64 docker://18.9.0
192.168.0.57 Ready etcd,master 4d1h v1.23.15 192.168.0.57 CentOS Linux 7 (Core) 3.10.0-957.el7.x86_64 docker://18.9.0
How was the ingress-nginx-controller installed: helm
Current State of the controller: running
The text was updated successfully, but these errors were encountered: