-
Notifications
You must be signed in to change notification settings - Fork 70
Open
Description
On upgrades from 2.4.0 the issue was with keycloak not coming up with the right URL after the upgrade. That messed up the control plane.
But deploying 2.4.2 direct ended up with a cluster with keycloak working but 503's on all other API's.
We do need to test the deployments, upgrades and potentially downgrades.
Changes detected in configuration. Updating the server image.
The previous optimized build will be overridden with the following build options:
- db=dev-file > db=postgres
To avoid that, run the 'build' command again and then start the optimized server instance using the '--optimized' flag.
Updating the configuration and installing your custom providers, if any. Please wait.
2025-10-30 12:48:09,724 INFO [io.quarkus.deployment.QuarkusAugmentor] (main) Quarkus augmentation completed in 7223ms
Server configuration updated and persisted. Run the following command to review the configuration:
kc.sh show-config
Next time you run the server, just run:
kc.sh start --optimized --proxy=edge
ERROR: Unexpected error when starting the server in (production) mode
ERROR: Failed to start quarkus
ERROR: Invalid base URL for FrontEnd URLs: https://2a01:4f8:c014:3fe9::1.helix.cluster.world/auth/
ERROR: Error at index 1 in: "4f8:c014:3fe9::1.helix.cluster.world"
ERROR: Error at index 1 in: "4f8:c014:3fe9::1.helix.cluster.world"
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels