@@ -165,41 +165,14 @@ to the built-in `cluster-admin` ClusterRole.
165
165
### Authorization mode configuration {#choice-of-authz-config}
166
166
167
167
You can configure the Kubernetes API server's authorizer chain using either
168
- [ command line arguments ] ( #using-flags- for-your- authorization-module ) only or, as a beta feature,
169
- using a [ configuration file ] ( #using-configuration-file- for-authorization ) .
168
+ a [ configuration file ] ( #using-configuration-file- for-authorization ) only or
169
+ [ command line arguments ] ( #using-flags- for-your- authorization-module ) .
170
170
171
171
You have to pick one of the two configuration approaches; setting both ` --authorization-config `
172
172
path and configuring an authorization webhook using the ` --authorization-mode ` and
173
173
` --authorization-webhook-* ` command line arguments is not allowed.
174
174
If you try this, the API server reports an error message during startup, then exits immediately.
175
175
176
- ### Command line authorization mode configuration {#using-flags-for-your-authorization-module}
177
-
178
- {{< feature-state state="stable" for_k8s_version="v1.8" >}}
179
-
180
- You can use the following modes:
181
-
182
- * ` --authorization-mode=ABAC ` (Attribute-based access control mode)
183
- * ` --authorization-mode=RBAC ` (Role-based access control mode)
184
- * ` --authorization-mode=Node ` (Node authorizer)
185
- * ` --authorization-mode=Webhook ` (Webhook authorization mode)
186
- * ` --authorization-mode=AlwaysAllow ` (always allows requests; carries [ security risks] ( #warning-always-allow ) )
187
- * ` --authorization-mode=AlwaysDeny ` (always denies requests)
188
-
189
- You can choose more than one authorization mode; for example:
190
- ` --authorization-mode=Node,RBAC,Webhook `
191
-
192
- Kubernetes checks authorization modules based on the order that you specify them
193
- on the API server's command line, so an earlier module has higher priority to allow
194
- or deny a request.
195
-
196
- You cannot combine the ` --authorization-mode ` command line argument with the
197
- ` --authorization-config ` command line argument used for
198
- [ configuring authorization using a local file] ( #using-configuration-file-for-authorization-mode ) .
199
-
200
- For more information on command line arguments to the API server, read the
201
- [ ` kube-apiserver ` reference] ( /docs/reference/command-line-tools-reference/kube-apiserver/ ) .
202
-
203
176
<!-- keep legacy hyperlinks working -->
204
177
<a id =" configuring-the-api-server-using-an-authorization-config-file " />
205
178
@@ -347,6 +320,31 @@ A reload **must not** add or remove Node or RBAC authorizers (they can be reorde
347
320
but cannot be added or removed).
348
321
{{< /note >}}
349
322
323
+ ### Command line authorization mode configuration {#using-flags-for-your-authorization-module}
324
+
325
+ You can use the following modes:
326
+
327
+ * ` --authorization-mode=ABAC ` (Attribute-based access control mode)
328
+ * ` --authorization-mode=RBAC ` (Role-based access control mode)
329
+ * ` --authorization-mode=Node ` (Node authorizer)
330
+ * ` --authorization-mode=Webhook ` (Webhook authorization mode)
331
+ * ` --authorization-mode=AlwaysAllow ` (always allows requests; carries [ security risks] ( #warning-always-allow ) )
332
+ * ` --authorization-mode=AlwaysDeny ` (always denies requests)
333
+
334
+ You can choose more than one authorization mode; for example:
335
+ ` --authorization-mode=Node,RBAC,Webhook `
336
+
337
+ Kubernetes checks authorization modules based on the order that you specify them
338
+ on the API server's command line, so an earlier module has higher priority to allow
339
+ or deny a request.
340
+
341
+ You cannot combine the ` --authorization-mode ` command line argument with the
342
+ ` --authorization-config ` command line argument used for
343
+ [ configuring authorization using a local file] ( #using-configuration-file-for-authorization-mode ) .
344
+
345
+ For more information on command line arguments to the API server, read the
346
+ [ ` kube-apiserver ` reference] ( /docs/reference/command-line-tools-reference/kube-apiserver/ ) .
347
+
350
348
## Privilege escalation via workload creation or edits {#privilege-escalation-via-pod-creation}
351
349
352
350
Users who can create/edit pods in a namespace, either directly or through an object that
0 commit comments