I am using JFrog Container Registry ( /products/jfrog-container-registry-reviews ) for various projects that involve using different Docker ( /products/docker-37146-reviews ) setups for an enterprise-grade private container registry with JFrog Artifactory ( /products/jfrog-artifactory-reviews ). I have set up high availability JFrog instances on Kubernetes ( /products/kubernetes-reviews ), configured local and remote repositories for container images, and more. I have built an end-to-end CI/CD pipeline with JFrog and the registry on Kubernetes ( /products/kubernetes-reviews ), utilizing Jenkins ( /products/jenkins-reviews ), JFrog X-ray, and more.
We push our images and Helm charts to the JFrog Container Registry. Since we have a Kubernetes-based environment, these images and Helm charts are pulled from the Kubernetes cluster and deployed.
JFrog Container Registry acts as a single solution for storing and managing all of our software artifacts. This includes packages, files, and containers throughout our software supply chain. We have a central JFrog server, and we integrate various tools with it. The artifacts are stored there. It helps us manage the process from build to release.
We use the solution to compile the codes before publishing them. We utilize third-party containers and codes, downloading them to the JFrog Container Registry. Developers then access it from the JFrog Container Registry, and there's a specific job responsible for running and validating all security checks, ensuring compatibility. If there are any issues or if packages require updates, we manage those updates through this system.
The JFrog Container Registry is a repository manager, which supports Docker and Helm registries and Generic repositories, allowing you to build, deploy and manage your container images while providing powerful features with fine-grained permission control behind a sleek and easy-to-use UI.
I am using JFrog Container Registry ( /products/jfrog-container-registry-reviews ) for various projects that involve using different Docker ( /products/docker-37146-reviews ) setups for an enterprise-grade private container registry with JFrog Artifactory ( /products/jfrog-artifactory-reviews ). I have set up high availability JFrog instances on Kubernetes ( /products/kubernetes-reviews ), configured local and remote repositories for container images, and more. I have built an end-to-end CI/CD pipeline with JFrog and the registry on Kubernetes ( /products/kubernetes-reviews ), utilizing Jenkins ( /products/jenkins-reviews ), JFrog X-ray, and more.
We push our images and Helm charts to the JFrog Container Registry. Since we have a Kubernetes-based environment, these images and Helm charts are pulled from the Kubernetes cluster and deployed.
JFrog Container Registry acts as a single solution for storing and managing all of our software artifacts. This includes packages, files, and containers throughout our software supply chain. We have a central JFrog server, and we integrate various tools with it. The artifacts are stored there. It helps us manage the process from build to release.
We use the solution to compile the codes before publishing them. We utilize third-party containers and codes, downloading them to the JFrog Container Registry. Developers then access it from the JFrog Container Registry, and there's a specific job responsible for running and validating all security checks, ensuring compatibility. If there are any issues or if packages require updates, we manage those updates through this system.