For companies to survive until 2022, they’ll need to focus on two things: Binaries and Edges. We’ve just wrapped up swampUP 2020, where we showcased this bold idea. We heard from you firsthand how DevOps Fast Forward is a must, and how software must be able to be distributed anywhere to enable the continuity of any business. Your experience confirmed how the global crisis has accelerated the digital transformation in your companies.

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.

The previous two posts in this series walked through both the architecture of the Tanzu Kubernetes Grid (TKG) Service for vSphere and how to use it to deploy Tanzu Kubernetes clusters. In this post, we’ll walk through how to take a cluster and scale it on demand. The examples shown are consistent with the same tag-demo-cluster-01 cluster spec used previously.

Every day, application programming interfaces (APIs) are created to speed up the development of modern software applications—from globally-scaled public services to internal endpoints for your proprietary applications. For engineering leaders with teams that write and maintain APIs, however, it can be difficult to know how to prioritize API features, encourage adoption, and respond to feedback from developers. And as we at VMware Pivotal Labs well know, rapid iteration leads to product success.

TL;DR: Experts working with tech companies discuss a lot about security issues, both internally and with clients. Indeed, no software program or app is full-proof. While technological enhancements help companies and individuals to perform better, they enhance the capabilities of hackers too. Naturally, everybody has to take the necessary steps required to protect their interests, and the most common yet effective way to do it is to change passwords frequently.

Twitter’s SRE team is one of the most advanced in the industry, managing the services that capture the pulse of the world every single day and throughout the moments that connect us all. We had the privilege of interviewing Brian Brophy, Sr. Staff SRE, Carrie Fernandez, Head of Site Reliability Engineering, JP Doherty, Engineering Manager, and Zac Kiehl, Sr. Staff SRE to learn about how SRE is practiced at Twitter.

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.