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 available for the Google Cloud Container V1 API is 3.33.0, and the documentation provides access to various other versions, down to version 2.3.0.\u003c/p\u003e\n"],["\u003cp\u003eThe documentation covers the \u003ccode\u003eLegacyAbac\u003c/code\u003e class, which is used for configuring legacy Attribute Based Access Control (ABAC) authorization in Kubernetes clusters.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eLegacyAbac\u003c/code\u003e class implements several interfaces, including \u003ccode\u003eIMessage\u003c/code\u003e, \u003ccode\u003eIEquatable<LegacyAbac>\u003c/code\u003e, \u003ccode\u003eIDeepCloneable<LegacyAbac>\u003c/code\u003e, and \u003ccode\u003eIBufferMessage\u003c/code\u003e, and is part of the \u003ccode\u003eGoogle.Cloud.Container.V1\u003c/code\u003e namespace.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eLegacyAbac\u003c/code\u003e class includes a single configurable property named \u003ccode\u003eEnabled\u003c/code\u003e, which is a boolean that determines if the ABAC authorizer is enabled for a specific cluster.\u003c/p\u003e\n"]]],[],null,[]]
