menu
arrow_back

Using Role-based Access Control in Kubernetes Engine

Using Role-based Access Control in Kubernetes Engine

1 hora 7 créditos

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.

Únase a Qwiklabs para leer este lab completo… y mucho más.

  • Obtenga acceso temporal a Google Cloud Console.
  • Más de 200 labs para principiantes y niveles avanzados.
  • El contenido se presenta de a poco para que pueda aprender a su propio ritmo.
Únase para comenzar este lab
Puntuación

—/100

Provisioning the Kubernetes Engine Cluster

Ejecutar paso

/ 20

Creating the RBAC rules

Ejecutar paso

/ 10

Create server in each namespace

Ejecutar paso

/ 15

Deploying the sample application

Ejecutar paso

/ 20

Fixing the service account name

Ejecutar paso

/ 10

Identifying the application's role and permissions

Ejecutar paso

/ 15

Teardown

Ejecutar paso

/ 10