xiaoanne
commented
1 year ago I have the same issue, the behaviour is that when following the installation guide in https://www.keycloak.org/keycloak-benchmark/kubernetes-guide/latest/installation, the installation gets stuck while executing task of running ./isup.sh file:
....
task: [keycloak] helm upgrade --install keycloak --set hostname=192.168.49.2.nip.io --set dbPoolInitialSize=5 --set dbPoolMinSize=5 --set dbPoolMaxSize=10 --set storage= --set database=postgres --set keycloakImage= keycloak
[keycloak] Release "keycloak" has been upgraded. Happy Helming!
[keycloak] NAME: keycloak
[keycloak] LAST DEPLOYED: Thu Jan 5 11:03:58 2023
[keycloak] NAMESPACE: default
[keycloak] STATUS: deployed
[keycloak] REVISION: 2
[keycloak] TEST SUITE: None
[keycloak] NOTES:
[keycloak] Keycloak will be available on https://keycloak.192.168.49.2.nip.io
[keycloak] user: admin
[keycloak] password: admin
[keycloak] sqlpad will be available on http://sqlpad.192.168.49.2.nip.io
[keycloak] user: admin
[keycloak] password: admin
[keycloak] Cryostat will be available on https://cryostat.192.168.49.2.nip.io
[keycloak] Connect to PostgreSQL on 192.168.49.2.nip.io:30009
[keycloak] user: keycloak
[keycloak] password: pass
[keycloak] JDBC URL: jdbc:postgresql://192.168.49.2.nip.io:30009/keycloak
task: [keycloak] bash -c ' if [ "postgres" == "cockroach-operator" ]; then kubectl -n keycloak -o yaml get crdbclusters.crdb.cockroachlabs.com/cockroach > .task/status-keycloak-db.json; elif [ "postgres" == "cockroach-single" ]; then kubectl get deployment/cockroach -n keycloak -o=jsonpath="{.spec}" > .task/status-keycloak-db.json; elif [ "postgres" != "none" ]; then kubectl get deployment/postgres -n keycloak -o=jsonpath="{.spec}" > .task/status-keycloak-db.json; else echo "none" > .task/status-keycloak-db.json; fi'
task: [keycloak] bash -c 'kubectl get pods -A | grep -E "(BackOff|Error)" | tr -s " " | cut -d" " -f1-2 | xargs -r -L 1 kubectl delete pod -n'
task: [keycloak] bash -c 'sleep 1'
task: [keycloak] ./init-database.sh postgres
task: [keycloak] ./isup.sh
^Ctask: Signal received: "interrupt"
[keycloak] .......................................................................................................................................
task: Failed to run task "keycloak": exit status 130
.....Therefore the installation couldn't be done with Mac M1.
ahus1
Describe the bug
When we start the minikube based provisioning on an M1 mac, with podman driver based VM, everything starts up but the cadvisor fails to start up properly.
Below is the messages I see when I query the cadvisor pod for logs
Version
keycloak-benchmark latest main
Expected behavior
would expect the cadvisor pod to come up with out issues
Actual behavior
All the other pods seems to be coming up without error. seems like this setup is facing an issue with ingress
How to Reproduce?
podman machine init --cpus 6 --memory 16000 --rootful && podman machine starttaskfrom within theprovision/minikubeAnything else?
M1 MacOS: Hardware Overview:
Model Name: MacBook Pro Model Identifier: MacBookPro18,3 Model Number: Z15G001X2LL/A Chip: Apple M1 Pro Total Number of Cores: 10 (8 performance and 2 efficiency) Memory: 32 GB System Firmware Version: 8419.60.31 OS Loader Version: 8419.60.31
System Software Overview:
System Version: macOS 13.1 (22C5033e) Kernel Version: Darwin 22.2.0 Boot Volume: Macintosh HD Boot Mode: Normal Secure Virtual Memory: Enabled System Integrity Protection: Enabled