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 manages the configuration for legacy Attribute-Based Access Control (ABAC) authorization in Kubernetes clusters."],["The latest version documented is 3.33.0, and the page lists a comprehensive range of versions down to 2.3.0 for reference."],["The documentation details the class's implementation, including its constructors, properties (like `Enabled`), inheritance from `Object`, and the interfaces it implements such as `IMessage`, `IEquatable`, `IDeepCloneable`, and `IBufferMessage`."],["The `Enabled` property determines whether the ABAC authorizer is active for a given cluster, granting additional permissions to system identities when enabled."]]],[]]
