From d8b3ec4f63481951b8d443ad6b18171c85ac0cfa Mon Sep 17 00:00:00 2001
From: Bruno Gabriel da Silva <38823062+bgsilvait@users.noreply.github.com>
Date: Thu, 13 Aug 2020 11:06:12 +0100
Subject: [PATCH] Update manifests with the correct API version

Change the API from deployment  manifests  apps/v1beta1 ->  apps/v1

As per doc (https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/)

Deployment in the extensions/v1beta1, apps/v1beta1, and apps/v1beta2 API versions is no longer served
Migrate to use the apps/v1 API version, available since v1.9. Existing persisted data can be retrieved/updated via the new version.
---
 .../en/docs/tasks/configure-pod-container/configure-gmsa.md   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/en/docs/tasks/configure-pod-container/configure-gmsa.md b/content/en/docs/tasks/configure-pod-container/configure-gmsa.md
index a2b3f24628..7e4537adbb 100644
--- a/content/en/docs/tasks/configure-pod-container/configure-gmsa.md
+++ b/content/en/docs/tasks/configure-pod-container/configure-gmsa.md
@@ -130,7 +130,7 @@ roleRef:
 The Pod spec field `securityContext.windowsOptions.gmsaCredentialSpecName` is used to specify references to desired GMSA credential spec custom resources in Pod specs. This configures all containers in the Pod spec to use the specified GMSA. A sample Pod spec with the annotation populated to refer to `gmsa-WebApp1`:
 
 ```yaml
-apiVersion: apps/v1beta1
+apiVersion: apps/v1
 kind: Deployment
 metadata:
   labels:
@@ -161,7 +161,7 @@ spec:
 Individual containers in a Pod spec can also specify the desired GMSA credspec using a per-container `securityContext.windowsOptions.gmsaCredentialSpecName` field. For example:
 
 ```yaml
-apiVersion: apps/v1beta1
+apiVersion: apps/v1
 kind: Deployment
 metadata:
   labels: