You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 7, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: content/onlineboutique/set-up-onlineboutique-git-repo.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,12 +79,12 @@ subjects:
79
79
namespace: config-management-system
80
80
roleRef:
81
81
kind: ClusterRole
82
-
name: cluster-admin
82
+
name: edit
83
83
apiGroup: rbac.authorization.k8s.io
84
84
EOF
85
85
```
86
-
{{% notice info %}}
87
-
We are using the `cluster-admin`role here, but in the future we will change this with a least privilege approach. It will be something with `edit` role and the the Istio resources like `VirtualService`, etc. leveraged in this workshop. See [more information about the user-facing roles here](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles).
86
+
{{% notice tip %}}
87
+
We are using the [`edit` user-facing role](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles) here, to follow the least privilege principle. Earlier in this workshop during the ASM installation, we extended the default `edit` role with more capabilities regarding to the Istio resources: `VirtualService`, `Sidecar` and `Authorization` wich will be leveraged in the OnlineBoutique's namespace.
Copy file name to clipboardExpand all lines: content/service-mesh/set-up-asm-configs.md
+45-17Lines changed: 45 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,6 +96,33 @@ spec: {}
96
96
EOF
97
97
```
98
98
99
+
## Define new ClusterRole with Istio capabilities for ConfigSync
100
+
101
+
Define the extended [`edit` user-facing role](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles) with more Istio resources capabilities:
Later in this workshop, for each app namespace, we will define a Config Sync's `RepoSync` which will be bound to the `edit``ClusterRole`. With that new extension, it will allow each namespace to deploy Istio resources such as `Sidecar`, `VirtualService` and `AuthorizationPolicy` while meeting with the least privilege principle requirement.
Copy file name to clipboardExpand all lines: content/whereami/set-up-whereami-git-repo.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,12 +79,12 @@ subjects:
79
79
namespace: config-management-system
80
80
roleRef:
81
81
kind: ClusterRole
82
-
name: cluster-admin
82
+
name: edit
83
83
apiGroup: rbac.authorization.k8s.io
84
84
EOF
85
85
```
86
-
{{% notice info %}}
87
-
We are using the `cluster-admin`role here, but in the future we will change this with a least privilege approach. It will be something with `edit` role and the the Istio resources like `VirtualService`, etc. leveraged in this workshop. See [more information about the user-facing roles here](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles).
86
+
{{% notice tip %}}
87
+
We are using the [`edit` user-facing role](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles) here, to follow the least privilege principle. Earlier in this workshop during the ASM installation, we extended the default `edit` role with more capabilities regarding to the Istio resources: `VirtualService`, `Sidecar` and `Authorization` wich will be leveraged in the Whereami's namespace.
0 commit comments