Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/GoogleCloudPlatform/gke-rbac-best-practices below:

GitHub - GoogleCloudPlatform/gke-rbac-best-practices

This repository contains yaml files that can be used to implement access control in GKE. 2 Roles are defined, the first one is for the CICD pipeline and is intended to be granted to GCP services such as Cloud Build. Therefore, we specify the GPC service account in the role binding. If you want to implement the CICD pipeline by Jenkins or other services as Pods, please specify the Kubernetes service account. This role is created from "editor" of the cluster role. The other is the role for the security auditor. This is created based on the "view" of the cluster role, and the permissions of view roles and role bindings are added.

1. Clone it from GitHub.
2. Change to the directory which you have created with the git clone created. Note: the default directory will be gke-rbac-best-practices.
3. Modify the parts enclosed in <> to suit your environment in RoleBinding files.
4. Apply your yaml files to your gke cluster.

git clone https://github.com/GoogleCloudPlatform/gke-rbac-best-practices
cd gke-rbac-best-practices
vi cicd-rolebinding.yaml or security-auditor-rolebinding.yaml
kubectl apply -f your yaml file

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4