Last October, I published a blog post describing the efforts we've committed to on the Bitbucket Cloud engineering team to achieve world-class reliability. A lot has happened in the past year (understatement of the year)! What the team has accomplished is tremendous, but we've also learned a thing or two that we can work further to improve.

Helm is an application package manager for Kubernetes. Using Kubernetes can often be overwhelming to maintain resources. Since Kubernetes is configured by YAML files, the more complex your application becomes, the more difficult it will be to navigate and make changes to the respective files; think about lots and lots of repetitive YAML files. A scenario that makes every developer cringe. Helm can help you solve this.

It takes a large team to manage enterprise DevOps, and it can take a large team of binary repository managers, too. It’s vital to get all team members going the same way, and quickly. A growing developer organization will have many instances of Artifactory to help them scale, on multiple nodes for high availability and multi-site repository replication. Configuring them all precisely, with the same set of repositories, users, and permissions, can’t be done effectively one at a time.

The GitHub Container Registry has just been announced by GitHub and is supported natively on Codefresh like any other Docker repository. Codefresh provides multiple options to connect to Docker Container Registries, one of which is GitHub Container Registries. Currently, GitHub plans to include the GitHub Container Registry within the pricing model of GitHub packages. In comparison, Docker Hub has added rate limits to free accounts.

You may have heard the latest Docker announcement about the new rate limits for container image pulls. Starting November 1st, Docker will start to limit Docker Hub usage based on your subscription level and block pull requests that exceed imposed limits. Not only that, Docker has also put in place a new retention policy, six months for free accounts, for inactive images (originally slated for November 1, this policy has been delayed to mid-2021 due to community feedback).

Thanks to Linus Torvalds, the creator of not only Linux, but also the most popular version control system - Git, multiple developers can simultaneously work on the development of the same application, ramping up the speed of production. Git was revolutionary - it enabled developers to keep track of code changes and collaborate seamlessly across different projects.

Hi, my name is Ayana Yokota and I’m a Developer Advocate at JFrog. I’m excited to introduce the first blog post in my JFrog customers interview series, highlighting unique use-cases and success stories. This fascinating first interview was held with Mr. Yan and Mr. Moriya, from the Infrastructure Engineering team, and Mr. Etourneau from the Arene Tools team, in the Toyota Research Institute – Advanced Development, Inc. (TRI-AD).

We are about to install and manage Argo CD through a CD pipeline. “Why would we do that? We can just as well accomplish that through a command like kubectl apply or helm upgrade --install.” I’m glad you asked. The primary objective of Argo CD is to help us apply GitOps processes when deploying applications. It is directing us towards the world in which everything is defined as code, and all code is stored in Git.

There are many articles and videos about practicing Continuous Delivery (CD) with applications, but not nearly as many for infrastructure. The same can be said for GitOps applied to infrastructure. That is a bit strange given that applications and infrastructure are almost the same today. Both are defined as code, and everyone stores code in Git repositories. Hence, GitOps is just as good of a fit for infrastructure as for anything else.

The concept of Continuous Delivery (CD) has been around for over a decade. Early adopters of CD have reaped the benefits of reduced cycle times coupled with greater stability and reliability. Yet CD is far from a “solved problem” with many organizations struggling to implement CD at scale (or at all!) due to organizational, process and technology challenges.