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.

Participe do Qwiklabs para ler o restante deste laboratório e muito mais!

  • Receber acesso temporário a Console do Google Cloud.
  • Mais de 200 laboratórios, do nível iniciante ao avançado.
  • Tamanho compacto para que você possa aprender no seu próprio ritmo.
Participe para iniciar este laboratório
Pontuação

—/100

Provisioning the Kubernetes Engine Cluster

Executar etapa

/ 20

Creating the RBAC rules

Executar etapa

/ 10

Create server in each namespace

Executar etapa

/ 15

Deploying the sample application

Executar etapa

/ 20

Fixing the service account name

Executar etapa

/ 10

Identifying the application's role and permissions

Executar etapa

/ 15

Teardown

Executar etapa

/ 10