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 documentation for the `LegacyAbac` class within the Google Kubernetes Engine v1 API, specifically for .NET development."],["The `LegacyAbac` class configures the legacy Attribute Based Access Control (ABAC) authorization mode for Kubernetes clusters."],["The most recent version of the API documented on the webpage is 3.33.0, while the page is viewed in the context of version 3.25.0, with a list of previous versions ranging down to 2.3.0."],["`LegacyAbac` implements several interfaces, including `IMessage`, `IEquatable`, `IDeepCloneable`, and `IBufferMessage`."],["The `LegacyAbac` class has a single configurable property, `Enabled`, which determines if the ABAC authorizer is active for the cluster, granting extra permissions to identities in the system."]]],[]]
