Difference between revisions of "Helm install keycloak"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{lc}} | {{lc}} | ||
helm install my-keycloak oci://registry-1.docker.io/bitnamicharts/keycloak | helm install my-keycloak oci://registry-1.docker.io/bitnamicharts/keycloak | ||
| + | |||
| + | |||
| + | <pre> | ||
| + | keycloak | ||
| + | Pulled: registry-1.docker.io/bitnamicharts/keycloak:19.2.0 | ||
| + | Digest: sha256:9ff3338d09acd13dbafbaabbe3ea9481285ca5eb803203179b3274d0ba900b70 | ||
| + | NAME: my-keycloak | ||
| + | LAST DEPLOYED: Thu Mar 7 11:46:39 2024 | ||
| + | NAMESPACE: default | ||
| + | STATUS: deployed | ||
| + | REVISION: 1 | ||
| + | TEST SUITE: None | ||
| + | NOTES: | ||
| + | CHART NAME: keycloak | ||
| + | CHART VERSION: 19.2.0 | ||
| + | APP VERSION: 23.0.7 | ||
| + | |||
| + | ** Please be patient while the chart is being deployed ** | ||
| + | |||
| + | Keycloak can be accessed through the following DNS name from within your cluster: | ||
| + | |||
| + | my-keycloak.default.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: | ||
| + | |||
| + | export HTTP_SERVICE_PORT=$(kubectl get --namespace default -o jsonpath="{.spec.ports[?(@.name=='http')].port}" services my-keycloak) | ||
| + | kubectl port-forward --namespace default svc/my-keycloak ${HTTP_SERVICE_PORT}:${HTTP_SERVICE_PORT} & | ||
| + | |||
| + | echo "http://127.0.0.1:${HTTP_SERVICE_PORT}/" | ||
| + | |||
| + | 2. Access Keycloak using the obtained URL. | ||
| + | |||
| + | WARNING: There are "resources" sections in the chart not set. Using "resourcesPreset" is not recommended for production. For production installations, please set the following values according to your workload needs: | ||
| + | - resources | ||
| + | +info https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ | ||
| + | </pre> | ||
{{keycloak}} | {{keycloak}} | ||
Revision as of 10:47, 7 March 2024
helm install my-keycloak oci://registry-1.docker.io/bitnamicharts/keycloak
keycloak
Pulled: registry-1.docker.io/bitnamicharts/keycloak:19.2.0
Digest: sha256:9ff3338d09acd13dbafbaabbe3ea9481285ca5eb803203179b3274d0ba900b70
NAME: my-keycloak
LAST DEPLOYED: Thu Mar 7 11:46:39 2024
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
CHART NAME: keycloak
CHART VERSION: 19.2.0
APP VERSION: 23.0.7
** Please be patient while the chart is being deployed **
Keycloak can be accessed through the following DNS name from within your cluster:
my-keycloak.default.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:
export HTTP_SERVICE_PORT=$(kubectl get --namespace default -o jsonpath="{.spec.ports[?(@.name=='http')].port}" services my-keycloak)
kubectl port-forward --namespace default svc/my-keycloak ${HTTP_SERVICE_PORT}:${HTTP_SERVICE_PORT} &
echo "http://127.0.0.1:${HTTP_SERVICE_PORT}/"
2. Access Keycloak using the obtained URL.
WARNING: There are "resources" sections in the chart not set. Using "resourcesPreset" is not recommended for production. For production installations, please set the following values according to your workload needs:
- resources
+info https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
Advertising:
