The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Your team is practicing DevOps and you’re delivering some flavor of Continuous Delivery. You’re deploying anywhere from three times a week to twenty times a day. You are moving fast! At that speed, how do you know if you are moving things in the right direction? Hopefully, your team has defined some key SLIs that define your application’s health.
It comes as no surprise that the demand for Kubernetes is skyrocketing across the industry. According to the CNCF’s 2019 survey, 78% of respondents are using Kubernetes in production today. This growth is contributing to a surge of demand for talent: there are over 100 thousand cloud native job postings across Dice and Indeed alone. The talent pool of people that have worked with Kubernetes and the adjacent technologies is limited and demand is growing.
The first HashiConf Digital event was held on June 22-24, online. The event was meant to be HashiConf Amsterdam, but the team pivoted and moved it online because of COVID-19. My employer FireHydrant was a sponsor, and I was happy to have a chance to attend. The event was very well organized, and that’s even more impressive given that the team had to shift it online.
Over the past few years, we’ve seen an almost obsession with developing and adopting CI/CD tools throughout the DevOps community. There are thousands of “how-to’s”, “top x tools”, and “tool x vs tool y” type articles, and it has gotten to the point where it’s quite difficult to figure out how and which one to pick as your own.
IT is advancing blazingly fast. To keep up with architectural changes and hybrid environments, it’s more important than ever to maintain efficient infrastructure monitoring and troubleshooting. Adding to the complexity is the increase of distributed systems, comprised of many components and services.
In Kubernetes, Ingress objects define rules for how to route a client’s request to a specific service running inside your cluster. These rules can take into account the unique aspects of an incoming HTTP message, including its Host header and the URL path, allowing you to send traffic to one service or another using data discovered in the request itself. That means you can use Ingress objects to define routing for many different applications.