fix: adding doc note about admin ingress (#33392)
* fix: adding doc note about admin ingress closes: #33203 Signed-off-by: Steve Hawkins <shawkins@redhat.com> * Update docs/guides/operator/basic-deployment.adoc 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:
parent
b4a200d333
commit
8d314a69a0
2 changed files with 5 additions and 1 deletions
|
@ -100,6 +100,10 @@ When running on OpenShift, with ingress enabled, and with the spec.ingress.class
|
|||
The operator will assign a default hostname to the stored version of the CR similar to what would be created by an OpenShift Route without an explicit host - that is ingress-namespace.appsDomain
|
||||
If the appsDomain changes, or should you need a different hostname for any reason, then update the Keycloak CR.
|
||||
|
||||
NOTE: If you set the `hostname-admin`, or the deprecated `hostname-admin-url`, even if you enable ingress, no ingress will be created specifically for admin access.
|
||||
Admin access via a separate hostname is generally expected to have access restrictions, which are not currently expressible via the Keycloak CR.
|
||||
Also the default ingress does not prevent accessing admin endpoints, so you may not want to enable ingress handling via the Keycloak CR at all when you have a separate hostname for admin endpoints.
|
||||
|
||||
==== TLS Certificate and key
|
||||
|
||||
See your Certification Authority to obtain the certificate and the key.
|
||||
|
|
|
@ -11,7 +11,7 @@ When build from the project root directory, this module is only enabled if the i
|
|||
|
||||
## Building
|
||||
|
||||
Ensure you have JDK 11 (or newer) installed.
|
||||
Ensure you have JDK 17 (or newer) installed.
|
||||
|
||||
Build the Docker image with:
|
||||
|
||||
|
|
Loading…
Reference in a new issue