menu
arrow_back

Using Role-based Access Control in Kubernetes Engine

Using Role-based Access Control in Kubernetes Engine

1 heure 7 crédits

GKE-Engine.png

GSP493

Google Cloud Self-Paced Labs

Overview

This lab covers the usage and debugging of role-based access control (RBAC) in a Kubernetes Engine cluster.

While RBAC resource definitions are standard across all Kubernetes platforms, their interaction with underlying authentication and authorization providers needs to be understood when building on any cloud provider.

RBAC is a powerful security mechanism that provides great flexibility in how you restrict operations within a cluster. This lab will cover two use cases for RBAC:

  1. Assigning different permissions to user personas, namely owners and auditors.
  2. Granting limited API access to an application running within your cluster.

Since RBAC's flexibility can occasionally result in complex rules, common steps for troubleshooting RBAC are included as part of scenario 2.

Inscrivez-vous sur Qwiklabs pour consulter le reste de cet atelier, et bien plus encore.

  • Obtenez un accès temporaire à Google Cloud Console.
  • Plus de 200 ateliers, du niveau débutant jusqu'au niveau expert.
  • Fractionné pour vous permettre d'apprendre à votre rythme.
Inscrivez-vous pour démarrer cet atelier
Note

—/100

Provisioning the Kubernetes Engine Cluster

Réaliser l'étape

/ 20

Creating the RBAC rules

Réaliser l'étape

/ 10

Create server in each namespace

Réaliser l'étape

/ 15

Deploying the sample application

Réaliser l'étape

/ 20

Fixing the service account name

Réaliser l'étape

/ 10

Identifying the application's role and permissions

Réaliser l'étape

/ 15

Teardown

Réaliser l'étape

/ 10