revert Update Keycloak image and version to 26.3.3
The Keycloak Docker image has been updated from
26.3.2-debian-12-r1 to 26.3.3-debian-12-r0 in both the Chart.yaml
and values.yaml files. This change was necessary to incorporate
the latest security patches and improvements provided in the
newer version.
Additionally, the appVersion and chart version in the Chart.yaml
file have been updated to 26.3.3 and 25.2.0 respectively to ensure
consistency with the image versioning. These updates help maintain
compatibility and ensure that users benefit from the latest enhancements.
The Keycloak Docker image has been updated from
26.3.2-debian-12-r1 to 26.3.3-debian-12-r0 in both the Chart.yaml
and values.yaml files. This change was necessary to incorporate
the latest security patches and improvements provided in the
newer version.
Additionally, the appVersion and chart version in the Chart.yaml
file have been updated to 26.3.3 and 25.2.0 respectively to ensure
consistency with the image versioning. These updates help maintain
compatibility and ensure that users benefit from the latest enhancements.
This commit introduces a complete Helm chart for deploying Keycloak on
Kubernetes. The chart includes a variety of configurations such as
service and ingress definitions, metrics exposure, resource limits, and
autoscaling options.
Key features include:
- Full support for PostgreSQL as a database, configurable through chart
values.
- Ingress resources for external access, including support for TLS and
admin interfaces.
- Options to use custom configurations and initialization scripts via
ConfigMaps.
- Metrics service for Prometheus integration, alongside ServiceMonitor
configurations for Kubernetes monitoring.
- Enhanced environment variables management, including secret handling
for sensitive data like passwords.
These changes provide a robust foundation for deploying Keycloak in
both development and production environments. Users should be aware
that this initial setup gives flexibility for customization, but care
should be taken when altering default configurations to ensure
compatibility with existing deployments.
