The latest News and Information on Containers, Kubernetes, Docker and related technologies.
At Moogsoft we use Jenkins to implement our CICD Pipelines. We run Jenkins where we run most everything else; Kubernetes, but you don’t need to have Jenkins running on Kubernetes to use this plugin. This is made possible by the community maintained Kubernetes plugin. Recently we had the need to not only run agents local to the same cluster that Jenkins runs in, but in other clusters across different regions.
Kubernetes workloads are highly dynamic, ephemeral, and are deployed on a distributed and agile infrastructure. Application developers, DevOps teams, and site reliability engineers (SREs) often require better visibility of their different microservices, what their dependencies are, how they are interconnected, and which other clients and applications access them. This makes Kubernetes observability challenges unique.
In a previous post, we described how we envision cloud-native initiatives reaching the 2.0 phase, where phase 1 was centered around providing clusters and running its underlying infrastructure effectively. Now that teams are starting to move some of their existing services to a microservices architecture, developers and platform engineers are being tasked with implementing the right policies and governance controls to ensure applications are running as securely as possible.
It has been 6 months since our engineering team started to work on what we decided to call Qovery v2. But what makes this next release so cool? Here are the top 4 features that make this release so appealing.
From zero to hero - here is a short video to show how to deploy an app from scratch on AWS with Qovery v2 - this video is linked to https://www.qovery.com/blog/one-week-before-the-launch-of-qovery-v2-beta-whats-new
We’re happy to debut our new website, highlighting our newest features! We’ve been busy updating our product UI and decided to showcase some of the work on the site. All of our case studies, whitepapers, and datasheets are now in the Resources page. We’ve also been featured on a variety of news sites, podcasts and blogs. We linked all of them in the “Speedscale in the Media” section.
Run your HAProxy Kubernetes Ingress Controller in External mode to reduce network hops and latency. Traditionally, you would run the HAProxy Kubernetes Ingress Controller as a pod inside your Kubernetes cluster. As a pod, it has access to other pods because they share the same pod-level network. That allows it to route and load balance traffic to applications running inside pods, but the challenge is how to connect traffic from outside the cluster to the ingress controller in the first place.
