Operations | Monitoring | ITSM | DevOps | Cloud

ChartCenter is a free Helm chart central repository that was built to help the Helm community find immutable, secure, and reliable charts for publicly available Kubernetes apps. With ChartCenter, you have a single source of truth to proxy all public charts from one, always available location. Without ChartCenter, you need to add each Helm chart’s repository to the Helm client for every Kubernetes app you want to install and update.

Logs in continuous delivery pipelines are often entirely ignored, right up until something goes wrong. We usually find ourselves wishing we’d put some thought into our logs, once we’re in the midst of trawling through thousands of lines. In order to try to prevent this, we can add DevOps metrics into our logs, which will provide us with greater observability, and give insight into anything going wrong in our pipelines.

Nowadays, software development teams utilize continuous delivery or some variation, to create better, faster, more accurate software releases. Continuous delivery is a DevOps practice that empowers software teams to continuously ship code directly to an environment once automated tests pass. Continuous delivery is facilitated through the deployment pipeline. You can read more about it in a previous post.

GitLab CI/CD is a tool that is built into GitLab. It allows you to create automated tasks that you can use to form a Continuous Integration and Continuous Delivery / Deployment process. You configure GitLab CI/CD by adding a yaml file (called `.gitlab-ci.yml`) to your source repository. This file creates a pipeline, which will then run when a code change is pushed to the repository. Pipelines are made up of a series of stages, and each stage can each contain a number of jobs or scripts.

Developers understand the importance of keeping their team up to date on work and use many of the integrations between Bitbucket Cloud and Jira like smart commits and automation triggers to do so automatically. However there may be times where there are nuances or uncommon situations when merging a pull request that aren't covered by existing automation rules – sometimes there are multiple pull requests, or sometimes merging means you're now in 'Done' and other times you're in 'Releasing'.

Bitbucket Pipelines provides teams with a one-stop solution to build, test, deploy and track their code, without ever leaving Bitbucket. Developers and release managers can easily track and visualize deployments, while non-technical teams can have visibility into what features are coming down the pipeline.

For the last four years, anyone wanting to deploy the Ingress NGINX Controller for Kubernetes would find its official Helm chart nginx-ingress in the stable repository maintained by the Helm project. Those days are over. And not just for NGINX, the most popular Ingress Controller used as a reverse proxy and load balancer, but for all open-source K8s apps. With the advent of Helm 3, the Helm project is deprecating the stable repositories.