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-03-21 UTC."],[[["The page provides documentation for the `LegacyAbac` class within the Google Kubernetes Engine v1 API, covering versions from 2.3.0 up to the latest, 3.33.0."],["`LegacyAbac` is a class used for configuring legacy Attribute Based Access Control (ABAC) authorization in Kubernetes clusters."],["The `LegacyAbac` class inherits from `object` and implements `IMessage`, `IEquatable\u003cLegacyAbac\u003e`, `IDeepCloneable\u003cLegacyAbac\u003e`, and `IBufferMessage` interfaces."],["The class has a property called `Enabled`, a boolean that dictates whether the ABAC authorizer is active, granting permissions beyond those set by RBAC or IAM."],["There are two constructors, one that is empty and the other taking a `LegacyAbac` parameter called `other` for creating a new instance."]]],[]]
