Kubernetes Authorization Resources are components that control access to the Kubernetes API and cluster resources, primarily using Role-Based Access Control (RBAC). These resources include Roles, ClusterRoles, RoleBindings, and ClusterRoleBindings, which work together to define and enforce fine-grained access policies for users, groups, and service accounts within a Kubernetes cluster.
Authorization Resources
Kubernetes Authorization Resources are components that regulate access to the Kubernetes API and cluster resources, primarily using Role-Based Access Control (RBAC).
This Knowledge store offers customizable configurations to help you generate your own setup. While Kubernetes has released multiple development versions, such as v1alpha1, v1beta1, and others, in mconnect.ai, the initial templates are derived from Kubernetes v1 release. Check templates section below to playaround with live examples.
Resources
| Resource | Description | Templates |
|---|---|---|
| ClusterRole | Defines permissions for actions on cluster-wide resources or all namespaces. | v0.0.1 |
| ClusterRoleBinding | Grants permissions defined in a ClusterRole to a user, group, or service account at the cluster level. | v0.0.1 |
| Role | Defines a set of permissions within a specific namespace, restricting access to namespaced resources. | v0.0.1 |
| RoleBinding | Assigns a Role’s permissions to a user, group, or service account within a specific namespace. | v0.0.1 |
Contributions
Permissions
Below are mconnect.ai Permissions overview and Kubernetes Organization structure.
Overview
A Knowledge store can be created under an Organization, Team, or User, with permissions inherited from the parent entity. An Admin role at the parent level grants admin privileges across all Knowledge stores and resources within it. In contrast, a Member role at the parent level, by default, has view access to private Knowledge stores and their resources but can be granted elevated permissions (such as Admin) for a specific Knowledge store. For more details, refer to the Authorization documentation.
Kubernetes Organization
| Team | Description |
|---|---|
| Maintainers | Kubernetes Maintainers team gets admin privileges all across Kubernetes organization. |
| Collaborators | Members of the Collaborators team receive Collaborator permissions, allowing them to edit resources in all Knowledge stores. |
If you'd like to contribute to the Authorization Resources Knowledge store, you can request Collaborator permission specific to this Knowledge store or join the Maintainers or Collaborators team.
Please reach out to us through our Discord community for permissions.
Releases
| Type | Description |
|---|---|
| Released | Versions in this state are finalized and cannot be modified by collaborators. They can be safely used as dependencies in other Knowledge stores, ensuring stability for associated resources such as data, collections, configurations, services, and endpoints. |
| Under Development | These versions are still being actively worked on and may change without prior notice. Using them as dependencies should be done with caution, as resources within them, including configurations and services, are subject to updates. |
| Archived | Archived versions are no longer supported, and resource modifications are disabled. They cannot be newly added as dependencies, but any previously included versions will continue to function as they were.. |