Nginx uses previous configuration #306
Comments
|
I see that controller has new config file. But nginx uses previous config file. I fixed it by |
|
|
|
@kobrinartem I'm trying to reproduce this issue. Can you provide me with logs from the Ingress controller? I don't see the git commit |
|
Logs right after updating selector tags in service. Nginx has newest version in config but uses previous version |
|
@kobrinartem Sorry, I should have asked for this previously, but can you please set logging verbosity to 3 and provide me with those logs? |
|
@Dean-Coakley upstream blue-green-demo-external-echoheaders-sticky-ingress-plus-plus.example.com-echoheaders-blue-80 { I0713 11:55:33.564482 1 nginx.go:284] Writing NGINX conf to /etc/nginx/conf.d/blue-green-demo-default-nginx-ingress-plus.conf } } } server { } upstream blue-green-demo-external-echoheaders-sticky-ingress-plus-plus.example.com-echoheaders-blue-80 { } } } server { } |
|
/nginx-ingress -version |
|
it's command to switch blue to green: blue pods: green pods: |
|
@kobrinartem I have been able to recreate this issue. I am working on resolving this for you as soon as possible. Thanks for reporting this issue and providing all these logs for me. They were very helpful in finding the issue. |
|
We're still working to fix this issue. |
|
@kobrinartem quick update: we're still working on this. |
|
Hi @kobrinartem, We've merged in #365 which should fix this issue. Sorry for the delay. It's not in a release yet, but we do Edge versions now if you'd like to test with a built image. Thanks |
|
Merged #380 which should prevent this type of issue from happening in any case. |
I am swapping between two version of application.
Master Ingress
`---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: default-nginx-ingress-plus
namespace: blue-green-demo
annotations:
kubernetes.io/ingress.class: "external-plus-ingress"
nginx.org/mergeable-ingress-type: "master"
spec:
rules:
`
App Config
`---
apiVersion: v1
kind: Service
metadata:
name: echoheaders-blue
namespace: blue-green-demo
labels:
app: echoheaders-blue
spec:
type: NodePort
ports:
targetPort: 8080
protocol: TCP
name: http
targetPort: 8443
protocol: TCP
name: https
selector:
app: echoheaders
version: blue
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: echoheaders-blue
namespace: blue-green-demo
labels:
app: echoheaders
version: blue
spec:
replicas: 3
selector:
matchLabels:
app: echoheaders
version: blue
template:
metadata:
labels:
app: echoheaders
version: blue
spec:
containers:
- name: echoheaders
image: gcr.io/google_containers/echoserver:1.10
ports:
- containerPort: 8080
- containerPort: 8443
env:
- name: NODE_NAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName
- name: POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: POD_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
- name: POD_IP
valueFrom:
fieldRef:
fieldPath: status.podIP
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: external-echoheaders-sticky-ingress-plus
namespace: blue-green-demo
annotations:
kubernetes.io/ingress.class: "external-plus-ingress"
nginx.org/mergeable-ingress-type: "minion"
nginx.com/sticky-cookie-services: "serviceName=echoheaders-blue srv_id expires=1h path=/echo"
spec:
rules:
http:
paths:
serviceName: echoheaders-blue
servicePort: 80
path: /echo`
kubectl patch -n blue-green-demo svc echoheaders-blue -p "{"spec":{"selector": {"app": "echoheaders", "version": "green"}}}"
The text was updated successfully, but these errors were encountered: