From c7ca50426c83c8d059138b94eefbd31119e03e5b Mon Sep 17 00:00:00 2001 From: sebdevaux Date: Thu, 16 Mar 2023 14:18:22 +0100 Subject: [PATCH] chore: fix typo --- pages/am/3.x/breaking-changes/breaking-changes-3.21.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pages/am/3.x/breaking-changes/breaking-changes-3.21.adoc b/pages/am/3.x/breaking-changes/breaking-changes-3.21.adoc index e26ef1db8..663bb5349 100644 --- a/pages/am/3.x/breaking-changes/breaking-changes-3.21.adoc +++ b/pages/am/3.x/breaking-changes/breaking-changes-3.21.adoc @@ -8,10 +8,10 @@ NOTE: To take advantage of these new features and incorporate these breaking cha == Docker images -From this version, to be complient with https://www.tenable.com/audits/items/CIS_Docker_v1.3.1_L1_Docker_Linux.audit:bdcea17ac365110218526796ae3095b1[CIS_Docker_v1.3.1_L1] the docker images are now using the user `graviteeio` -This means that if you use the official images and deploy them to Kubernetes, nothing changes. -If you build your own Dockerfile from Gravitee images, you must give the right rights to the modifications you add. -If you deploy in `openshift`, you have to add the following configure: +From this version, to be compliant with https://www.tenable.com/audits/items/CIS_Docker_v1.3.1_L1_Docker_Linux.audit:bdcea17ac365110218526796ae3095b1[CIS_Docker_v1.3.1_L1] the docker images are now use the `graviteeio` user +This means that if you use the official images and deploy them on your k8s installation, nothing changes. +If you build your own Dockerfile from Gravitee images, you must give the correct rights according to your modifications. +If you deploy on `openshift`, you have to add the following configuration: ```yaml securityContext: