Whether the ABAC authorizer is enabled for this cluster. When enabled,
identities in the system, including service accounts, nodes, and
controllers, will have statically granted permissions beyond those
provided by the RBAC configuration or IAM.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-17 UTC."],[[["The documentation covers the `LegacyAbac` class within the Google Kubernetes Engine v1 API, with the latest version being 3.33.0."],["`LegacyAbac` is a class used for configuring the legacy Attribute Based Access Control (ABAC) authorization mode in Kubernetes clusters."],["The documentation includes reference material for `LegacyAbac` class implementations such as IMessage, IEquatable, IDeepCloneable, and IBufferMessage."],["The `Enabled` property within the `LegacyAbac` class determines if the ABAC authorizer is active for a given cluster."],["There are many versions of the `LegacyAbac` class in the provided content, ranging from 3.33.0 down to 2.3.0, with each version being a separate documented entity."]]],[]]
