Issues running Keycloak on Digital Ocean Kubernetes cluster about cloud-native-spring-in-action HOT 5 CLOSED

I have also been having the same issue with the keycloak deploy.sh script, and have thus far not managed to find a solution:

keycloak % ./deploy.sh

🗝️ Keycloak deployment started.

📦 Installing Keycloak...
namespace/keycloak-system created
configmap/keycloak-config created

📦 Configuring Helm chart...
"bitnami" already exists with the same configuration, skipping
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "bitnami" chart repository
Update Complete. ⎈Happy Helming!⎈
Release "polar-keycloak" does not exist. Installing it now.
NAME: polar-keycloak
LAST DEPLOYED: Tue Apr 25 12:47:22 2023
NAMESPACE: keycloak-system
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
CHART NAME: keycloak
CHART VERSION: 14.2.0
APP VERSION: 21.0.2

** Please be patient while the chart is being deployed **

Keycloak can be accessed through the following DNS name from within your cluster:

polar-keycloak.keycloak-system.svc.cluster.local (port 80)

To access Keycloak from outside the cluster execute the following commands:

1. Get the Keycloak URL by running these commands:

NOTE: It may take a few minutes for the LoadBalancer IP to be available.
You can watch its status by running 'kubectl get --namespace keycloak-system svc -w polar-keycloak'

export HTTP_SERVICE_PORT=$(kubectl get --namespace keycloak-system -o jsonpath="{.spec.ports[?(@.name=='http')].port}" services polar-keycloak)
export SERVICE_IP=$(kubectl get svc --namespace keycloak-system polar-keycloak -o jsonpath='{.status.loadBalancer.ingress[0].ip}')

echo "http://${SERVICE_IP}:${HTTP_SERVICE_PORT}/"

2. Access Keycloak using the obtained URL.

⌛ Waiting for Keycloak to be deployed...

⌛ Waiting for Keycloak to be ready...
error: timed out waiting for the condition on pods/polar-keycloak-0

As seen above, the script throws a timeout error whilst waiting for the polar-keycloak-0 pod to be ready and falls into a CrashLoopBackOff state.

The issue seems to be that the server within the polar-keycloak-0 pod does not start: is this a property defined in the keycloak-config.yml file or is it managed by Bitnami? Should the issue be raised within the Bitnami/keycloak repo?

Is there an alternative way to deploy a keycloak authentication service on Digital Ocean?

from cloud-native-spring-in-action.

i hope @ThomasVitale can come to the rescue at his most available time

from cloud-native-spring-in-action.

@sewah2012 @jempitman thank you both very much for reporting this issue. I should have blocked the Helm chart version in the scripts. The problem is that newer Chart versions from Bitnami don't work with Keycloak 19, which is the version used in the book. I have updated the scripts now and they should work correctly on DigitalOcean. It would be great if you could verify they work for you as well, thank you so much! You can find the necessary change in de5401d

from cloud-native-spring-in-action.

Hi @ThomasVitale, thank you for updating the script, it is now correctly for me.

from cloud-native-spring-in-action.

@jempitman thanks for confirming it works, I'll close the issue now. Feel free to register new issues should you encounter further problems with the scripts, thank you!

from cloud-native-spring-in-action.