whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update manifests with the correct API version

Browse Source 
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.
This commit is contained in:
Bruno Gabriel da Silva
2020-08-13 11:06:12 +01:00
committed by GitHub
parent 8cb0b199ae
commit d8b3ec4f63
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/configure-pod-container/configure-gmsa.md
+2 -2
View File
@@ -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: