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"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThe latest version of the Google Cloud Container V1 API is 3.33.0, as shown in the provided list of available versions.\u003c/p\u003e\n"],["\u003cp\u003eThis document provides reference material for the \u003ccode\u003eLegacyAbac\u003c/code\u003e class within the Google Kubernetes Engine v1 API, and it outlines configurations for legacy Attribute Based Access Control authorization mode.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eLegacyAbac\u003c/code\u003e class implements interfaces like \u003ccode\u003eIMessage\u003c/code\u003e, \u003ccode\u003eIEquatable\u003c/code\u003e, \u003ccode\u003eIDeepCloneable\u003c/code\u003e, and \u003ccode\u003eIBufferMessage\u003c/code\u003e and inherits from the \u003ccode\u003eobject\u003c/code\u003e class.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eEnabled\u003c/code\u003e property within the \u003ccode\u003eLegacyAbac\u003c/code\u003e class determines if the ABAC authorizer is active for a cluster, and when enabled it grants permissions beyond what RBAC or IAM would typically provide.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eLegacyAbac\u003c/code\u003e class has two constructors, one that is parameterless and another that accepts another \u003ccode\u003eLegacyAbac\u003c/code\u003e object as a parameter.\u003c/p\u003e\n"]]],[],null,[]]