|
55 | 55 | "audit-webhook-truncate-max-batch-size", // Maximum size of the batch sent to the underlying backend. Actual serialized size can be several hundreds of bytes greater. If a batch exceeds this limit, it is split into several batches of smaller size. |
56 | 56 | "audit-webhook-truncate-max-event-size", // Maximum size of the audit event sent to the underlying backend. If the size of an event is greater than this number, first request and response are removed, and if this doesn't reduce the size enough, event is discarded. |
57 | 57 | "audit-webhook-version", // API group and version used for serializing audit events written to webhook. |
58 | | - |
59 | 58 | // authentication flags |
| 59 | + |
60 | 60 | "anonymous-auth", // Enables anonymous requests to the secure port of the API server. Requests that are not rejected by another authentication method are treated as anonymous requests. Anonymous requests have a username of system:anonymous, and a group name of system:unauthenticated. |
61 | 61 | "api-audiences", // Identifiers of the API. The service account token authenticator will validate that tokens used against the API are bound to at least one of these audiences. If the --service-account-issuer flag is configured and this flag is not, this field defaults to a single element list containing the issuer URL. |
62 | 62 | "authentication-token-webhook-cache-ttl", // The duration to cache responses from the webhook token authenticator. |
|
80 | 80 | "requestheader-username-headers", // List of request headers to inspect for usernames. X-Remote-User is common. |
81 | 81 | "token-auth-file", // If set, the file that will be used to secure the secure port of the API server via token authentication. |
82 | 82 |
|
| 83 | + // authorization |
| 84 | + "authorization-webhook-config-file", // File with webhook configuration in kubeconfig format, used with --authorization-mode=Webhook. The API server will query the remote service to determine access on the API server's secure port. |
| 85 | + "authorization-webhook-version", // The API version of the authorization.k8s.io SubjectAccessReview to send to and expect from the webhook. |
| 86 | + "authorization-webhook-cache-authorized-ttl", // The duration to cache 'authorized' responses from the webhook authorizer. |
| 87 | + "authorization-webhook-cache-unauthorized-ttl", // The duration to cache 'unauthorized' responses from the webhook authorizer. |
| 88 | + |
83 | 89 | // Kubernetes ServiceAccount Authentication flags |
84 | 90 | "service-account-extend-token-expiration", // Turns on projected service account expiration extension during token generation, which helps safe transition from legacy token to bound service account token feature. If this flag is enabled, admission injected tokens would be extended up to 1 year to prevent unexpected failure during transition, ignoring value of service-account-max-token-expiration. |
85 | 91 | "service-account-issuer", // Identifier of the service account token issuer. The issuer will assert this identifier in "iss" claim of issued tokens. This value is a string or URI. If this option is not a valid URI per the OpenID Discovery 1.0 spec, the ServiceAccountIssuerDiscovery feature will remain disabled, even if the feature gate is set to true. It is highly recommended that this value comply with the OpenID spec: https://openid.net/specs/openid-connect-discovery-1_0.html. In practice, this means that service-account-issuer must be an https URL. It is also highly recommended that this URL be capable of serving OpenID discovery documents at {service-account-issuer}/.well-known/openid-configuration. When this flag is specified multiple times, the first is used to generate tokens and all are used to determine which issuers are accepted. |
@@ -204,5 +210,10 @@ var ( |
204 | 210 | // authentication flags |
205 | 211 | // TODO(embik): look at enabling this feature. |
206 | 212 | "authentication-config", // File with Authentication Configuration to configure the JWT Token authenticator. Note: This feature is in Alpha since v1.29.--feature-gate=StructuredAuthenticationConfiguration=true needs to be set for enabling this feature.This feature is mutually exclusive with the oidc-* flags. |
| 213 | + |
| 214 | + // authorization flags |
| 215 | + "authorization-mode", // Ordered list of plug-ins to do authorization on secure port. Defaults to AlwaysAllow if --authorization-config is not used. Comma-delimited list of: Webhook |
| 216 | + "authorization-config", // File with Authorization Configuration to configure the authorizer chain. |
| 217 | + "authorization-policy-file", // File with authorization policy in json line by line format, used with --authorization-mode=ABAC, on the secure port. |
207 | 218 | ) |
208 | 219 | ) |
0 commit comments