Open shipperizer opened 2 months ago
- relation-id: 14
endpoint: ingress
related-endpoint: ingress
application-data:
model: '"stg-identity-jaas-dev"'
name: '"login-ui"'
port: "8080"
redirect-https: "false"
scheme: '"http"'
strip-prefix: "true"
related-units:
login-ui/0:
in-scope: true
data:
egress-subnets: 10.152.183.219/32
host: '"login-ui-0.login-ui-endpoints.stg-identity-jaas-dev.svc.cluster.local"'
ingress-address: 10.152.183.219
private-address: 10.152.183.219
- relation-id: 49
endpoint: ingress
related-endpoint: ingress
application-data:
model: '"stg-identity-jaas-dev"'
name: '"admin-ui"'
port: "8080"
redirect-https: "false"
scheme: '"http"'
strip-prefix: "true"
related-units:
admin-ui/0:
in-scope: true
data:
host: '"admin-ui-0.admin-ui-endpoints.stg-identity-jaas-dev.svc.cluster.local"'
these are the differences between a login-ui and an admin-ui ingress
login-ui uses lib 2.5
, admin 2.6
issue seems to be resolving when upgrading to the latest traefik library 2.13
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/IAM-1011.
This message was autogenerated
when integrating with
traefik-k8s
a validation issue seems to be happening on the ingress side due to our sent payloadto reproduce simply deploy admin-ui and
traefik-k8s
and relate them