Config and Storage Resources in Kubernetes are essential components for managing application configurations and persistent data. They include ConfigMaps and Secrets for storing configuration data, and Persistent Volumes (PVs) and Persistent Volume Claims (PVCs) for handling durable storage needs of containerized applications. Configuration templates for these resources can be found in this Knowledge store.
Config and Storage Resources
The Knowledge store provides a comprehensive collection of templates for Kubernetes configuration and storage-related resources, including PersistentVolume, PersistentVolumeClaim, ConfigMap, Secret, and StorageClass. These templates enable efficient management of persistent storage and configuration data within clusters. Built on a flexible, facet-based design with dynamic variable population, they streamline the creation and customization of storage and configuration components while supporting diverse Kubernetes deployment scenarios.
Resources
| Resource | Description | Templates |
|---|---|---|
| PersistentVolume | Provides a cluster-wide storage resource, enabling persistent data storage across nodes. | v0.0.1 |
| PersistentVolumeClaim | Requests specific storage from available PersistentVolumes, allowing dynamic or static provisioning. | v0.0.1 |
| ConfigMap | Stores non-sensitive configuration data separately from application code for flexible management. | v0.0.1 |
| Secret | Manages sensitive data such as passwords and API keys securely within a Kubernetes cluster. | v0.0.1 |
| StorageClass | Defines storage provisioning policies, enabling dynamic allocation of persistent storage. | 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 Config and Storage 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.. |