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."],[[["This webpage provides reference documentation for the `LegacyAbac` class within the Google Kubernetes Engine v1 API."],["The `LegacyAbac` class is used for configuring the legacy Attribute Based Access Control (ABAC) authorization mode in a Kubernetes cluster."],["The latest version available is 3.33.0, and the webpage lists versions from 3.33.0 down to 2.3.0 with the ability to drill into the documentation for each version."],["The class implements several interfaces, including `IMessage`, `IEquatable`, `IDeepCloneable`, and `IBufferMessage`, and inherits from the `object` class."],["The `Enabled` property within `LegacyAbac` determines whether the ABAC authorizer is activated for the cluster, granting permissions beyond RBAC or IAM when turned on."]]],[]]
