Kubernetes 1.24 is about to be released, and it comes packed with novelties! Where do we begin? Update: Kubernetes 1.24 release date has been moved to May 3rd(from April 19th). This release brings 46 enhancements, on par with the 45 in Kubernetes 1.23, and the 56 in Kubernetes 1.22. Of those 46 enhancements, 13 are graduating to Stable, 14 are existing features that keep improving, 13 are completely new, and 6 are deprecated features.

Another conversation that was recently had during our weekly field enablement office hours here at Shipa was “what exactly is a microservice?”. Certainly, a term that has been used to describe a paradigm and architectural practice. One can argue that the breaking down or decomposing of applications has been going on for decades and is not a monumental shift in computing. There are several definitions of microservices from a purist definition to a definition resembling a movement.

Today, there are growing pressures on operations and development teams to deploy software faster and into more environments, such as development, staging, or production. Organizations need self-service tools and operational efficiency, and VMware is meeting the challenge with solutions to help modernize operations and unburden their teams. VMware Tanzu Mission Control unifies cluster management to a single control plane and groups resources as a resource hierarchy.

This is the second part of our EKS with Terraform series. In Part 1, we talked about Infrastructure as Code and its benefits. We also mentioned the tools we will be using. This time we will actually start using Terraform to create a VPC and EC2 instance.

Many federal and public sector organizations seek to capitalize on the benefits of a production-grade Kubernetes distribution in their own private data centers, which are often highly restricted and air-gapped environments. However, deploying and operating Kubernetes and other technologies in air-gapped environments is incredibly complex. Teams maintaining Kubernetes in these environments contend with restrictive network access and software supply chain security concerns.

An important part of any Kubernetes cluster is the underlying containers. Containers are the workloads that your business relies on, what your customers engage with, and what shapes your networking infrastructure. Long story short, containers are arguably the soul of any containerized environment. One of the most popular open-source container orchestration systems, Kubernetes, has a modular architecture.

With our recent announcement regarding the general availability of Ocean for Azure Kubernetes Service (AKS), I decided to migrate one of our production services. The service was already running on AKS, but will now be managed by Spot’s Ocean for AKS. TL;DR: The results are pretty cool, as I was able to cut 82% out of the existing spending for this AKS cluster. You can see the results in the screen capture below.

If you are a vivid traveler of the tech universe, you’ve likely come across this term: Kubernetes. Scratching your head? Let me make it clear: In simple terms, we know Kubernetes — or K8s — as a portable and extensible platform for managing containerized workloads and services. It can facilitate both declarative configurations as well as automation.

Heroku and AWS are two of the common choices available for cloud hosting. Heroku is a Platform as Service (PaaS) provider that helps startups develop business applications with simplicity and without needing DevOps expertise in the team. Not only does it provide resources automatically, but you can deploy your applications with just a single click. Heroku has been a top choice for developers for years as it speeds up development cycles by providing fully managed infrastructure and application deployment.