fix: adding the ability to set the ingress tlsSecret (#41426)

* fix: adding the ability to set the ingress tlsSecret

closes: #34777

Signed-off-by: Steve Hawkins <shawkins@redhat.com>

* Apply suggestions from code review

Co-authored-by: Martin Bartoš <mabartos@redhat.com>
Signed-off-by: Steven Hawkins <shawkins@redhat.com>

---------

Signed-off-by: Steve Hawkins <shawkins@redhat.com>
Signed-off-by: Steven Hawkins <shawkins@redhat.com>
Co-authored-by: Martin Bartoš <mabartos@redhat.com>
This commit is contained in:
Steven Hawkins
2025-08-04 08:28:46 -04:00
committed by GitHub
parent db01ff742b
commit f5f93ef6e1
6 changed files with 102 additions and 6 deletions
@@ -21,6 +21,10 @@ This helps you to track down a warning or error message in the log to a specific
For more details on this opt-in feature, see the https://www.keycloak.org/server/logging[Logging guide].
= Ability to specify a `tlsSecret` on the Keycloak CR `ingress` spec
In order to support basic TLS termination (edge) deployments via the operator, you may now set the Keycloak CR `spec.ingress.tlsSecret` field to a TLS Secret name in the namespace.
= HTTP Access logging
{project_name} supports HTTP access logging to record details of incoming HTTP requests.