Hi,
We have installed ISVA 10.0.0.0 in a kubernetes Cluster.
We would like to expose the isva-config cli port through an Ingress controller.
we're using the following definition (yaml)
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: isva.xxx.yyy.net
spec:
rules:
- host: isva.xxx.yyy.net
http:
paths:
- backend:
serviceName: verify-access-isvaconfig
servicePort: 9443
path: /
pathType: ImplementationSpecific
status:n
loadBalancer:
ingress:
- ip: 10.yyy.nn.1
- ip: 10.yyy.nn.2
- ip: 10.yyy.nn.3
And as far as we can tell Ingress has no problems with the syntax.
But all we get when going to the host ivsa.xxx.yyy.net is
<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.17.10</center>
</body>
</html>
Simple question -- why is this? Shouldn't the 9443 port be made accessible via Ingress??
Thanks in advance
------------------------------
Anders Domeij
CGI Sweden AB
------------------------------