Search Results for "packages"

Artifact Hub is a web-based application that enables finding, installing, and publishing packages and configurations for CNCF projects. Discovering artifacts to use with CNCF projects can be difficult. If every CNCF project that needs to share artifacts creates its own Hub this creates a fair amount of repeat work for each project and a fractured experience for those trying to find the artifacts to consume. The Artifact Hub attempts to solve that by providing a single experience for consumers that any CNCF project can leverage.

The Helm provider is used to deploy software packages in Kubernetes. The provider needs to be configured with the proper credentials before it can be used.

kpt is a package-centric toolchain that enables a WYSIWYG configuration authoring, automation, and delivery experience, which simplifies managing Kubernetes platforms and KRM-driven infrastructure (e.g., Config Connector, Crossplane) at scale by manipulating declarative Configuration as Data.

KubeClarity is a tool for detection and management of Software Bill Of Materials (SBOM) and vulnerabilities of container images and filesystems. It scans both runtime K8s clusters and CI/CD pipelines for enhanced software supply chain security. Effective vulnerability scanning requires an accurate Software Bill Of Materials (SBOM) detection. KubeClarity includes a CLI that can be run locally and especially useful for CI/CD pipelines. It allows to analyze images and directories to generate...

...Allowing to work with an environment reflecting production one, allowing to reduce any misconfiguration. This is a mono-repository of many services such as authentication or user domain. Each service has it own code base with the exception of shared packages to simplify things for this boilerplate. Services communicate with each other using gRPC. Each service might expose HTTP API for external communication or/and gRPC. This project setup should reduce the time spent on environment configuration for the whole Kubernetes cluster and/or each microservice. Extracting each of the services to its own repository or keeping it as mono-repo should be a matter of preference.