libre.sh/keycloak-scim
4
0
Fork 0
Code Issues 15 Pull requests Releases 1 Activity Actions

removes direct operator installation for the product (#22828)

Browse source 
Closes #22829
This commit is contained in:
Steven Hawkins 2023-08-30 12:21:38 -04:00 committed by GitHub
parent 3c00286e6c
commit 5fc4dd03ad
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
docs/guides/operator/installation.adoc
View file

@ -2,6 +2,7 @@
<#import "/templates/kc.adoc" as kc> <#import "/templates/kc.adoc" as kc>
<#import "/templates/options.adoc" as opts> <#import "/templates/options.adoc" as opts>
<#import "/templates/links.adoc" as links> <#import "/templates/links.adoc" as links>
<#import "/templates/profile.adoc" as profile>
<@tmpl.guide <@tmpl.guide
title="Keycloak Operator Installation" title="Keycloak Operator Installation"
@ -41,6 +42,7 @@ Make sure you are installing from the *fast* channel:
+ +
image::configure-operator.jpeg["Configure Keycloak Operator"] image::configure-operator.jpeg["Configure Keycloak Operator"]
<@profile.ifCommunity>
=== Installing by using kubectl without Operator Lifecycle Manager === Installing by using kubectl without Operator Lifecycle Manager
You can install the Operator on a vanilla Kubernetes cluster by using `kubectl` commands: You can install the Operator on a vanilla Kubernetes cluster by using `kubectl` commands:
@ -61,5 +63,6 @@ kubectl apply -f https://raw.githubusercontent.com/keycloak/keycloak-k8s-resourc
---- ----
Currently the Operator watches only the namespace where the Operator is installed. Currently the Operator watches only the namespace where the Operator is installed.
</@profile.ifCommunity>
</@tmpl.guide> </@tmpl.guide>