Closed francesco-di-marcantonio closed 9 months ago
Adding some images from console
From inside the container if we ping the host we receive no answer.
(but the host is correctly redirecting to the internal ip)
@francesco-di-marcantonio Ingress configuration varies on managed K8S services. Check the K8S provider's documentation on how to configure incoming traffic and if ingress is managed outside of K8S.
In the ingress configuration always reference the service varnish
or magento
, never the pod or deployment.
ping
usually doesn't work with K8S services. Use nslookup magento
instead. It should resolve the service IP.
Hi there, so finally we deployed the infrastructure. Now we are trying to connect to application but the ingress is not managing the domain.
we changed values in this files:
+++ values
ingress:
Set to true to enable ingress record generation
enabled: true
ingressClassName: nginx
certManager: true useProxyProtocol: true annotations: {}
hosts:
name: domain.it paths:
Set this to true in order to enable TLS on the ingress record
tls: true
Optionally specify the TLS hosts for the ingress record
Useful when the Ingress controller supports www-redirection
If not specified, the above host name will be used
tlsHosts:
tlsSecret: site-cert
+++values_gke
managedCert: enabled: true domains:
ingress: enabled: true certManager: true hosts:
Uncomment this section and update with your values
k get ingress
return this:
NAME CLASS HOSTS ADDRESS PORTS AGE magento <none> domain.it 34.149.75.162 80 2d4h
the application looks deployed but we receive
Error: Client network socket disconnected before secure TLS connection was established
for https
and no answer for http