menu
arrow_back

Using Role-based Access Control in Kubernetes Engine

Using Role-based Access Control in Kubernetes Engine

1 jam 7 Kredit

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.

Bergabunglah dengan Qwiklabs untuk membaca tentang lab ini selengkapnya... beserta informasi lainnya!

  • Dapatkan akses sementara ke Google Cloud Console.
  • Lebih dari 200 lab mulai dari tingkat pemula hingga lanjutan.
  • Berdurasi singkat, jadi Anda dapat belajar dengan santai.
Bergabung untuk Memulai Lab Ini
Skor

—/100

Provisioning the Kubernetes Engine Cluster

Jalankan Langkah

/ 20

Creating the RBAC rules

Jalankan Langkah

/ 10

Create server in each namespace

Jalankan Langkah

/ 15

Deploying the sample application

Jalankan Langkah

/ 20

Fixing the service account name

Jalankan Langkah

/ 10

Identifying the application's role and permissions

Jalankan Langkah

/ 15

Teardown

Jalankan Langkah

/ 10