As can be seen, there is a double slash in the UI code for the stylesheets.
This renders fine when run as a standalone Docker container, but when placed behind an Ingress Controller, the pages do not render properly. Note: In the image provided, the certificate is shown as invalid only because the Let's Encrypt server is the staging server and not PROD.
This has been tested on a Kubernetes 1.5.2 cluster, but it is expected to be the same for a pending Kubernetes 1.6.4 cluster implementation.
Deployed to K8s, using the following image:
Containers
reshifter-app
Image:
quay.io/mhausenblas/reshifter:0.3.9
Environment variables:
ACCESS_KEY_ID
:
Q3AM3UQ867SPQQA43P2F
SECRET_ACCESS_KEY
:
zuf+tfteSlswRu7BJ86wekitnifILbZam1KYY3T
Commands:
-
Args:
-
The Ingress config:
[centos@master deployments]$ cat reshifter-ingress.yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: reshifter-ingress
namespace: kube-system
annotations:
kubernetes.io/ingress.class: "traefik"
ingress.kubernetes.io/ssl-redirect: true
spec:
rules:
- host: reshifter.eupraxialabs.com
http:
paths:
- path:
backend:
serviceName: reshifter
servicePort: 8080
As can be seen, there is a double slash in the UI code for the stylesheets.
This renders fine when run as a standalone Docker container, but when placed behind an Ingress Controller, the pages do not render properly. Note: In the image provided, the certificate is shown as invalid only because the Let's Encrypt server is the staging server and not PROD.
This has been tested on a Kubernetes 1.5.2 cluster, but it is expected to be the same for a pending Kubernetes 1.6.4 cluster implementation.
Deployed to K8s, using the following image:
The Ingress config: