#267 Deploy Keycloak next to kubernetes#283
#267 Deploy Keycloak next to kubernetes#283sahithya23 wants to merge 3 commits intoGreenstand:masterfrom
Conversation
dadiorchen
left a comment
dadiorchen
left a comment
There was a problem hiding this comment.
@sahithya23 for those template folder and files under it, what are they about? Are they must-have files for us to download your code and run the helm command to install keycloak?
|
|
||
| ## Uninstall Keycloak | ||
| ```bash | ||
| helm uninstall keycloak --namespace keycloak |
There was a problem hiding this comment.
So @sahithya23 when we run this, it will use the current default kubectl context to deploy to the switched context env, right?
There was a problem hiding this comment.
About Template Folder
The templates/ folder is part of the Helm chart structure. It contains the Kubernetes manifest templates that Helm renders at install time.
They define the Keycloak Kubernetes resources such as Deployment, Service, Secrets, etc. Helm uses these templates along with the values.yaml file to generate the actual manifests deployed to the cluster.
Since we are using prepackaged helm chart, template folder has all the resources, we are controlling their behavior through values.yaml file using enabled: true/false
with this helm chart these resources are created: stateful set, service, secrets, pvc.
We can have separate values file for each environment so that we can use same chart across all environments.
About kube context when running Helm
Yes, that's correct — when running the Helm install command, it will deploy to the currently active Kubernetes context set in the user's kubeconfig.
|
@sahithya23 the sealed secret is part of the code, please commit to the repository. This service is doing the same: |
2 participants
• Purpose of the changes: Deploy keycloak next to Kubernetes
• Any relevant issue numbers: 267