Adding docs for artifact storage

docs/artifact-storage/container-registry.md

@@ -1,11 +1,44 @@
 ---
-sidebar_position: 1
+sidebar_position: 2
 ---
 
 # Container Registry
 
-A container registry is a repository for storing, managing, and distributing container images. It is a critical component of modern software development and Platform Engineering, providing a centralized location for storing and sharing containerized applications. Container registries are essential for DevOps practices, as they facilitate the deployment of containerized applications across various environments, from development through to production.
+A Container Registry is a critical component of the container ecosystem, providing a centralized storage and distribution system for container images. These images contain the code, runtime, libraries, environment variables, and configuration files needed to run software applications in isolated environments, known as containers. Container Registries play a pivotal role in the DevOps and Continuous Integration/Continuous Deployment (CI/CD) pipelines, enabling teams to efficiently manage and deploy containerized applications.
 
-:::warning
-🚧 Work in progress 🚧
-:::
+## Key Features of a Container Registry
+
+- **Image Storage**: Centralized repository for storing container images.
+- **Version Control**: Tracks different versions of images, facilitating rollback if necessary.
+- **Access Control**: Manages who can push to or pull from the registry, enhancing security.
+- **Automation Support**: Integrates with CI/CD pipelines for automated image updates and deployment.
+- **Vulnerability Scanning**: Some registries offer scanning services to detect security vulnerabilities within images.
+- **Replication**: Supports replicating images across multiple locations for redundancy and quicker access.
+
+## Container Registry Providers
+
+Several cloud providers offer managed container registries as part of their cloud services. Some of the popular container registry providers include:
+
+- **Amazon Elastic Container Registry (ECR)**: A fully managed container registry service provided by AWS.
+- **Google Container Registry (GCR)**: A private container registry for Google Cloud Platform users.
+- **Azure Container Registry (ACR)**: A managed, private Docker registry service provided by Microsoft Azure.
+- **Docker Hub**: A public container registry that also offers private repositories for Docker users.
+- **Harbor**: An open-source registry that provides a rich set of container management features, including security scanning and image signing.
+
+## OCI Specification and Its Significance
+
+The Open Container Initiative (OCI) Specification is a set of open standards designed to define container formats and runtime. The OCI aims to create a standardized ecosystem for container technologies, ensuring interoperability and consistency across different environments and platforms. The specification is divided into two main components:
+
+1. **OCI Runtime Specification**: Defines how to run a "filesystem bundle" that is unpacked on disk. This ensures that containers based on OCI-compliant images can run in any OCI-compliant system.
+2. **OCI Image Specification**: Describes the container image format, including the container filesystem, configuration, and manifest. This standardizes how images are built, shared, and deployed.
+
+## Differences Between Regular Container Registries and OCI-Spec Registries
+
+- **Compatibility**: OCI-spec registries adhere to the OCI Image Specification, ensuring that images stored in these registries are compatible with any OCI-compliant runtime environment. Regular container registries might not adhere to these standards, potentially leading to compatibility issues.
+- **Interoperability**: OCI-spec registries offer greater interoperability between different container orchestration platforms (like Kubernetes, Docker Swarm, and Mesos) since they follow a standardized image format.
+- **Innovation and Vendor Neutrality**: By following the OCI specifications, registries encourage innovation and prevent vendor lock-in, allowing developers to choose their tools and platforms freely.
+- **Feature Set**: While both types of registries provide similar basic functionalities (like image storage and version control), OCI-spec registries are more likely to offer advanced features aligned with the evolving standards, such as enhanced security scanning and image signing based on the OCI distribution specification.
+
+## Conclusion
+
+A container registry is an essential tool for managing and deploying container images in a secure and efficient manner. The adoption of OCI specifications by a registry ensures broader compatibility, interoperability, and innovation across the container ecosystem. When selecting a container registry, consider whether adherence to OCI standards is critical for your organization's operational and development workflows.

docs/artifact-storage/open-container-initiative.md

@@ -0,0 +1,41 @@
+---
+sidebar_position: 3
+---
+
+# Open Container Initiative (OCI)
+
+The Open Container Initiative (OCI) specifications, particularly the OCI Image Specification, have paved the way for OCI registries to store a variety of artifacts beyond traditional container images. This flexibility is critical for supporting a wide range of use cases in modern software development and deployment processes. Here are several notable types of artifacts that can be stored in OCI-compliant registries apart from container images.
+
+## 1. Helm Charts
+
+Helm, the package manager for Kubernetes, uses charts to describe a set of Kubernetes resources. OCI registries can store Helm charts as artifacts, enabling versioning, sharing, and management of Kubernetes applications alongside container images.
+
+## 2. Singularity Images
+
+Singularity is a container solution created for scientific and high-performance computing environments. Singularity images (SIF files) can be stored in OCI registries, allowing for versioned storage and distribution within scientific and research communities.
+
+## 3. WASM Modules
+
+WebAssembly (WASM) modules, which enable high-performance applications to run in web browsers and other environments, can be stored in OCI registries. This storage solution facilitates versioning, sharing, and deploying WASM modules in a manner similar to container images.
+
+## 4. OPA Policies
+
+Open Policy Agent (OPA) policies, which provide a high-level declarative language to specify policies as code, can be distributed through OCI registries. This capability allows for centralized management and distribution of policies across different environments.
+
+## 5. Machine Learning Models
+
+Machine learning models can be packaged and distributed as OCI artifacts. This approach offers a standardized way to version, share, and deploy models across various stages of the machine learning lifecycle, from development to production.
+
+## 6. Configuration Files
+
+Configuration files, such as those used for infrastructure as code (IaC) or application configurations, can be versioned and stored in OCI registries. This enables consistent deployment and management of configurations alongside the applications they support.
+
+## 7. Serverless Functions
+
+Artifacts related to serverless computing, such as function code and dependencies, can be stored in OCI registries. This facilitates the versioning, sharing, and deployment of serverless functions in a cloud-native environment.
+
+## 8. Custom Application Artifacts
+
+Developers can leverage OCI registries to store custom application artifacts that adhere to the OCI Image Specification. This flexibility allows for innovative uses of OCI registries beyond their initial intent, supporting a broad range of applications and workflows.
+
+The ability to store these diverse artifacts in OCI registries highlights the flexibility and potential of the OCI specifications to support a wide array of cloud-native technologies and workflows. This versatility is instrumental in fostering a unified, standardized approach to artifact storage and distribution in the software development lifecycle.