Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on Containers, Kubernetes, Docker and related technologies.

Shipa Cloud Operations and Practices

Shipa Cloud is how we run the Shipa control plane on behalf of users in order to give them the fastest path possible to implementing Application as Code within their clusters. You can try out Shipa Cloud for free today by going to shipa.io. Besides being the fastest way possible to get started with Shipa, it also takes away the responsibility of upgrades, maintenance, and uptime of the control plane for our users, but that responsibility doesn’t just disappear.

One Minute to Deployed on Kubernetes with Shipa

In this Shipa Shorts video, we deploy to Kubernetes in under a minute. All we had to produce is an image and Shipa takes care of the rest. No need to wire Networking Policies, Service Meshes, etc. With Shipa, you can deploy to Kubernetes without having to understand Kubernetes internals. Outside the UI, no matter your flavor of CI/CD, Shipa supports that.

Enabling simple, cost-effective Kubernetes on IBM Z with MicroK8s

Containerisation has transformed the enterprise IT landscape, driving faster, more secure, and more predictable software delivery than ever before. Thanks to technologies like Docker, building containerised applications is easy, and many businesses are working with hundreds or even thousands of containers. To effectively deploy and manage all of these microservices, a container orchestration tool is essential, and Kubernetes is the leading solution.

Automate Deployments to Amazon EKS with Skaffold and GitHub Actions

Creating a DevOps workflow to optimize application deployments to your Kubernetes cluster can be a complex journey. I recently demonstrated how to optimize your local K8s development workflow with Rancher Desktop and Skaffold. If you haven’t seen it yet, you can watch it by viewing the video below. You might be wondering, “What happens next?” How do you extend this solution beyond a local setup to a real-world pipeline with a remote cluster?

Five tools to increase Kubernetes developer productivity

This article was inspired by our recent "5 tools to increase Kubernetes developer productivity" video, hosted by Saiyam Pathak and Kunal Kushwaha. Over the years Kubernetes has become the de facto orchestration platform, as such it's crucial that developers have the right set of tools to increase their productivity for development and operations. In this article, we take a look at five such tools that can help developers inprove productivity while when Kubernetes. Let’s jump in.

Kubernetes for the JavaScript Developer - Part Two - Deploy to Kubernetes

Continuing on from Part One where we went through a brief history of containers and Kubernetes then Dockerized a NodeJS application, now we are ready to deploy to Kubernetes. If this is your first or nth time deploying to Kubernetes, Shipa makes this simple. You don’t have to worry about authoring multiple Kubernetes manifests and templates to deploy your application, all you need is an image.

Lightrun Releases KoolKits - Debugging Toolkits for Kubernetes

KoolKits (Kubernetes toolkits) are highly-opinionated, language-specific, batteries-included debug container images for Kubernetes. In practice, they’re what you would’ve installed on your production pods if you were stuck during a tough debug session in an unfamiliar shell. To briefly give some background, note that these container images are intended for use with the new kubectl debug feature, which spins up Ephemeral containers for interactive troubleshooting.

KoolKits - Highly-opinionated, batteries-included Kubernetes debugging toolkits

KoolKits (Kubernetes toolkits) are language-specific container images that contain a (highly-opinionated) set of tools for debugging applications running in Kubernetes pods. You can read more about the motivation behind this project here. Those images are intended for use with the new kubectl debug feature, which spins up Ephemeral containers for interactive troubleshooting. A KoolKit will be pulled by kubectl debug, spun up as a container in your pod, and have the ability to access the same process namespace as your original container.