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

Deprecate podDisruptionBudget

Browse source
This commit is contained in:
Václav Muzikář 2022-05-26 17:06:12 +02:00 committed by Bruno Oliveira da Silva
parent 6094f2ad1a
commit a3be94c70b
4 changed files with 46 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
release_notes/index.adoc
View file

@ -14,6 +14,9 @@ include::topics/templates/document-attributes-community.adoc[]
include::topics/templates/release-header.adoc[] include::topics/templates/release-header.adoc[]
== {project_name_full} 19.0.0
include::topics/19_0_0.adoc[leveloffset=2]
== {project_name_full} 18.0.0 == {project_name_full} 18.0.0
include::topics/18_0_0.adoc[leveloffset=2] include::topics/18_0_0.adoc[leveloffset=2]

21
release_notes/topics/19_0_0.adoc
View file

@ -44,3 +44,24 @@ Specifically, the services will not be able to differentiate cached and non-cach
Hence, custom extensions that access objects in local storage or cache through `KeycloakSession` Hence, custom extensions that access objects in local storage or cache through `KeycloakSession`
methods must be reviewed. methods must be reviewed.
See link:{upgradingguide_link}[{upgradingguide_name}] for details. See link:{upgradingguide_link}[{upgradingguide_name}] for details.
= Deprecated `podDisruptionBudget` in the legacy {project_operator}
With this release, we have deprecated `podDisruptionBudget` field in the Keycloak CR of the https://github.com/keycloak/keycloak-operator[legacy {project_operator}].
This optional field will be ignored when the Operator is deployed on Kubernetes version 1.25 and higher.
As a workaround, you can manually create the Pod Disruption Budget in your cluster, for example:
```yaml
apiVersion: policy/v1
kind: PodDisruptionBudget
metadata:
labels:
app: keycloak
name: keycloak
spec:
maxUnavailable: 1
selector:
matchLabels:
component: keycloak
```
See also the https://kubernetes.io/docs/tasks/run-application/configure-pdb/[Kubernetes Documentation].

1
server_installation/topics/operator/installation.adoc
View file

@ -158,5 +158,6 @@ endif::[]
* The usage of embedded DB is not supported in a production environment. * The usage of embedded DB is not supported in a production environment.
* Backup CRD is deprecated and not supported in a production environment. * Backup CRD is deprecated and not supported in a production environment.
* The `podDisruptionBudget` field in the Keycloak CR is deprecated and will be ignored when the Operator is deployed on Kubernetes version 1.25 and higher.
* We fully support using the rest of the CRDs in production, despite the `v1alpha1` version. We do not plan to make any breaking changes in this CRDs version. * We fully support using the rest of the CRDs in production, despite the `v1alpha1` version. We do not plan to make any breaking changes in this CRDs version.

21
upgrading/topics/keycloak/changes-19_0_0.adoc
View file

@ -214,3 +214,24 @@ public class MyUserStorageProvider implements UserLookupProvider, ... {
} }
---- ----
= Deprecated `podDisruptionBudget` in the legacy {project_operator}
With this release, we have deprecated `podDisruptionBudget` field in the Keycloak CR of the https://github.com/keycloak/keycloak-operator[legacy {project_operator}].
This optional field will be ignored when the Operator is deployed on Kubernetes version 1.25 and higher.
As a workaround, you can manually create the Pod Disruption Budget in your cluster, for example:
```yaml
apiVersion: policy/v1
kind: PodDisruptionBudget
metadata:
labels:
app: keycloak
name: keycloak
spec:
maxUnavailable: 1
selector:
matchLabels:
component: keycloak
```
See also the https://kubernetes.io/docs/tasks/run-application/configure-pdb/[Kubernetes Documentation].