Skip to content

[Backport release-1.5] fix(keycloak): point HTTPRoute backends at the service port - #3356

Open
github-actions[bot] wants to merge 1 commit into
release-1.5from
backport-3235-to-release-1.5
Open

github-actions[bot] wants to merge 1 commit into
release-1.5from
backport-3235-to-release-1.5

Conversation

@github-actions

Copy link
Copy Markdown

Description

Backport of #3235 to release-1.5.

@github-actions

Copy link
Copy Markdown
Author

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin backport-3235-to-release-1.5
git worktree add --checkout .worktree/backport-3235-to-release-1.5 backport-3235-to-release-1.5
cd .worktree/backport-3235-to-release-1.5
git reset --hard HEAD^
git cherry-pick -x 747549168668376523e2548dff2709e027ef93df
git push --force-with-lease

Backport of #3235 onto release-1.5.

With gateway-enabled: "true" every Keycloak hostname answered 503 from
envoy: the keycloak-http Service exposes only port 8080, while the
HTTPRoute backendRef referenced port 80, and Gateway API resolves a
backendRef against the Service's declared ports, so nothing resolved.
The Ingress template was never affected because it references the port
by name.

release-1.5 has a single HTTPRoute, so the fix here is the one port.
main's version of this file carries the admin-hostname split (a separate
public/admin route pair added after v1.5.2 and not backported), which is
why the bot's cherry-pick collided: it tried to import that whole
structure, including two `$adminHost` variables this branch never
defines.

Assisted-By: Claude <[email protected]>
Signed-off-by: Myasnikov Daniil <[email protected]>
(cherry picked from commit a7e650e6e96addb274ffd5c18e502f00b3f3cb06)
@myasnikovdaniil
myasnikovdaniil force-pushed the backport-3235-to-release-1.5 branch from 758d210 to ecf9a3f Compare July 31, 2026 05:28
@github-actions github-actions Bot added size/XS This PR changes 0-9 lines, ignoring generated files area/keycloak Issues or PRs related to Keycloak (SSO / identity) area/release Issues or PRs related to release tooling (changelog, backport, release pipeline) kind/bug Categorizes issue or PR as related to a bug labels Jul 31, 2026
@myasnikovdaniil
myasnikovdaniil marked this pull request as ready for review August 4, 2026 09:07
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@dosubot dosubot Bot added area/networking Issues or PRs related to networking (ingress, gateway, vpn, metallb, kube-ovn) kind/backport Categorizes issue or PR as requiring a backport to the current release line labels Aug 4, 2026
@github-actions

Copy link
Copy Markdown
Author

This PR has had no activity for 60 days and was marked lifecycle/stale.
It will be closed in 14 days unless commented or labelled lifecycle/frozen.

@github-actions github-actions Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale label Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/keycloak Issues or PRs related to Keycloak (SSO / identity) area/networking Issues or PRs related to networking (ingress, gateway, vpn, metallb, kube-ovn) area/release Issues or PRs related to release tooling (changelog, backport, release pipeline) kind/backport Categorizes issue or PR as requiring a backport to the current release line kind/bug Categorizes issue or PR as related to a bug lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale size/XS This PR changes 0-9 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant