update Azure AD AKS demo

Author: 0GiS0

04-cloud/00-aks/05-azure-active-directory/azure-ad-aks.sh

@@ -57,7 +57,7 @@ az aks get-credentials --resource-group $RESOURCE_GROUP --name $AKS_NAME --overw
 
 #Vamos a probar the north remembers creando un pod dentro de este namespace
 #Lanzar este comando te pedirá autenticación
-kubectl run --generator=run-pod/v1 nginx-north --image=nginx --namespace the-north-remembers
+kubectl run nginx-north --image=nginx --namespace the-north-remembers
 kubectl get po -n the-north-remembers
 
 #Si intentamos acceder al namespace de los Lanister o el default nos dará error
@@ -69,7 +69,7 @@ kubectl get po
 az aks get-credentials --resource-group $RESOURCE_GROUP --name $AKS_NAME --overwrite-existing
 
 #Intentamos la misma operación pero en el namespace de los Lanister
-kubectl run --generator=run-pod/v1 nginx-kings-landing --image=nginx --namespace kings-landing
+kubectl run nginx-kings-landing --image=nginx --namespace kings-landing
 #Si intentamos entrar en The North Remembers da un error
 kubectl get po -n the-north-remembers
 

04-cloud/00-aks/05-azure-active-directory/manifests/kings-landing.yaml

@@ -5,7 +5,7 @@ metadata:
 
 ---
 
-apiVersion: rbac.authorization.k8s.io/v1beta1
+apiVersion: rbac.authorization.k8s.io/v1
 kind: Role
 metadata:
   name: kings-landing-full-access
@@ -22,7 +22,7 @@ rules:
 
 ---
 
-apiVersion: rbac.authorization.k8s.io/v1beta1
+apiVersion: rbac.authorization.k8s.io/v1
 kind: RoleBinding
 metadata:
   name: lanister-access

04-cloud/00-aks/05-azure-active-directory/manifests/the-north-remembers.yaml

@@ -5,7 +5,7 @@ metadata:
 
 ---
 
-apiVersion: rbac.authorization.k8s.io/v1beta1
+apiVersion: rbac.authorization.k8s.io/v1
 kind: Role
 metadata:
   name: the-north-remembers-full-access
@@ -22,7 +22,7 @@ rules:
 
 ---
 
-apiVersion: rbac.authorization.k8s.io/v1beta1
+apiVersion: rbac.authorization.k8s.io/v1
 kind: RoleBinding
 metadata:
   name: stark-access