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."],[[["This page provides reference documentation for the `LegacyAbac` class within the Google Kubernetes Engine v1 API."],["The latest available version of the API is 3.33.0, and the documentation spans multiple versions, including 3.19.0, the main one associated with the `LegacyAbac` class."],["`LegacyAbac` is a configuration class for enabling the legacy Attribute Based Access Control (ABAC) authorization mode."],["The `LegacyAbac` class has a boolean property called `Enabled` which determines whether ABAC is active for a cluster, granting static permissions beyond those defined by RBAC or IAM."],["It implements several interfaces such as IMessage, IEquatable, IDeepCloneable, and IBufferMessage."]]],[]]
