Skip to content
This repository has been archived by the owner on Oct 1, 2024. It is now read-only.

Ingress route for tib uses wrong service port #301

Open
codingWombat opened this issue Mar 11, 2024 · 0 comments
Open

Ingress route for tib uses wrong service port #301

codingWombat opened this issue Mar 11, 2024 · 0 comments

Comments

@codingWombat
Copy link

codingWombat commented Mar 11, 2024

If you use the helm chart to deploy the identy broker in the stand alone version, the ingress route will be created with the service port of the dashboard.
With the service port of the dashboard the tib does not work, only if overwrite the port, when redeploying the ingress with the port configured for tib in the values.yaml

See:
https://github.com/TykTechnologies/tyk-helm-chart/blob/29ddaea0dc3a5ee1ab2770def2820f2adf3bf575/tyk-pro/templates/ingress-tib.yaml#L3C1-L3C46

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant