Migrating Pods With Containerized Applications Between Nodes In The Same Kubernetes Cluster Using Cloudify
Kubernetes is decidedly the DevOps tool of 2018 for those companies already deep in the cloud-native game. More and more we’re hearing about companies moving to a container- and Kubernetes-driven architecture. We definitely see the draw for utilizing Kubernetes in a larger role – we recently updated our Kubernetes plugin and unleashed a new Kubernetes Provider –
Cloudify Kubernetes Plugin 2.0 Release – More K8s Awesomeness
If you’re not familiar yet with our Kubernetes integration, suffice it to say that we believe the platform is a really important part of the container and microservices ecosystem. In fact, we have written quite a bit about the Cloudify Kubernetes Provider integration as well as the Kubernetes Plugin. Just as a quick refresher, the Plugin
Driving Open Standards in a Fragmented Networking Landscape
This article originally appeared in SDxCentral on December 29, 2017. Once upon a time, standards were our friends. They provided industry accepted blueprints for building homogeneous infrastructures that were reliably interoperable. Company A could confidently build an application and—because of standards—know that it would perform as expected on infrastructure run by Company B. Standards have,
Why Do I Need TOSCA If I’m Using Kubernetes? Part II of II
In the first part of this series, titled ”Why Do I Need * If I’m Using Kubernetes?”, I discussed why I believe the general sentiment that everything should move to Kubernetes is shortsighted and misguided. Watch our upcoming Cloudify 4.2 webinar to see what’s in store for Kubernetes! REGISTER NOW I wanted to follow up that
Why Do I Need * If I’m Using Kubernetes? Part I of II
I’m just returning from the Kubecon Austin event and I must admit that the vibe, and the amount of innovation, around Kubernetes reminded me of the good old OpenStack events. Now that Docker Swarm seems to be dropping behind, it definitely feels like Google and Kubernetes are killing it. During the event we announced our
Introducing the Cloudify Kubernetes Multi-Cloud Provider
In my previous blog post about the Kubernetes Plugin for Cloudify, I broke down the reasoning behind the need to orchestrate Kubernetes – the main reason being the need to orchestrate across diverse workloads. It’s no easy feat to get multiple Kubernetes clusters on different public and private clouds to talk with each other in
Kubernetes Core Concepts and Tools for Monitoring K8s
Kubernetes, as we’ve mentioned in earlier posts, is definitely the fastest growing open source, container-specific orchestration tools today. We are hearing more and more large organizations moving over big chunks of their business to cloud-native workloads. Github was one of the latest to take the plunge into K8s in production for all of their workloads.
Introducing the Cloudify Kubernetes Plugin for Orchestrating the Deployment of Applications on K8s Clusters in a Multi-Cloud Environment
Kubernetes has already become a household name in the container management space since it dropped in 2014. When it comes to orchestration, most DevOps people come back to us with “Why orchestrate Kubernetes – it’s already an orchestrator of containers?” The answer is simple – diverse workloads! Yes, you want containers, but you also need
Orchestrating A Kubernetes Managed Virtual Network Function With Cloudify
This post explores the process of containerizing Quagga and deploying it using Kubernetes.
Hybrid VNF Container Orchestration With Kubernetes and Docker Swarm Using Cloudify
This post will show how Cloudify orchestrates a service chain that spans multiple container management engines such as Kubernetes and Docker Swarm.