You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
We are trying to make communication from kong ingress to upstream services as mtls. here is my service file : apiVersion: v1 kind: Service metadata: annotations: konghq.com/client-cert: tls-ingress konghq.com/protocol: https name: account-information-clusterip namespace: core spec: ports: - name: http port: 8551 protocol: TCP targetPort: 8551 - name: https port: 8443 protocol: TCP targetPort: 8443 selector: application: account-information sessionAffinity: None type: ClusterIP --- tls secret is alredy created: [ec2-user@ip-10-74-191-55 ~]$ k get secret -n core NAME TYPE DATA AGE cvv-client-ssl-store Opaque 1 40h nexus-docker-secret kubernetes.io/dockerconfigjson 1 17d oauth-token-client-ssl-store Opaque 1 40h ssl-store Opaque 1 40h tls kubernetes.io/tls 2 40h tls-ingress kubernetes.io/tls 2 5d22h --- after applying configuration kong ingress controller gives error time="2024-06-09T04:21:21Z" level=debug msg="no configuration change, skipping sync to Kong" url="https://127.0.0.1:8444/" time="2024-06-09T04:21:21Z" level=debug msg="due to errors in the current config, the last valid config has been pushed to Gateways" time="2024-06-09T04:21:21Z" level=error msg="could not update kong admin" error="performing update for https://127.0.0.1:8444/ failed: failed posting new config to /config: got status code 400" subsystem=dataplane-synchronizer time="2024-06-09T04:21:21Z" level=debug msg="successfully applied Kong configuration to https://127.0.0.1:8444/" logger=events object="{"kind":"Pod","namespace":"kong-app","name":"ingress-kong-796548b7cc-tqp58","apiVersion":"v1"}" reason=KongConfigurationSucceeded type=Normal
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Description
We are trying to make communication from kong ingress to upstream services as mtls. here is my service file : apiVersion: v1 kind: Service metadata: annotations: konghq.com/client-cert: tls-ingress konghq.com/protocol: https name: account-information-clusterip namespace: core spec: ports: - name: http port: 8551 protocol: TCP targetPort: 8551 - name: https port: 8443 protocol: TCP targetPort: 8443 selector: application: account-information sessionAffinity: None type: ClusterIP --- tls secret is alredy created: [ec2-user@ip-10-74-191-55 ~]$ k get secret -n core NAME TYPE DATA AGE cvv-client-ssl-store Opaque 1 40h nexus-docker-secret kubernetes.io/dockerconfigjson 1 17d oauth-token-client-ssl-store Opaque 1 40h ssl-store Opaque 1 40h tls kubernetes.io/tls 2 40h tls-ingress kubernetes.io/tls 2 5d22h --- after applying configuration kong ingress controller gives error time="2024-06-09T04:21:21Z" level=debug msg="no configuration change, skipping sync to Kong" url="https://127.0.0.1:8444/" time="2024-06-09T04:21:21Z" level=debug msg="due to errors in the current config, the last valid config has been pushed to Gateways" time="2024-06-09T04:21:21Z" level=error msg="could not update kong admin" error="performing update for https://127.0.0.1:8444/ failed: failed posting new config to /config: got status code 400" subsystem=dataplane-synchronizer time="2024-06-09T04:21:21Z" level=debug msg="successfully applied Kong configuration to https://127.0.0.1:8444/" logger=events object="{"kind":"Pod","namespace":"kong-app","name":"ingress-kong-796548b7cc-tqp58","apiVersion":"v1"}" reason=KongConfigurationSucceeded type=Normal
Beta Was this translation helpful? Give feedback.
All reactions