In our first post we went over setting up the Kubernetes Plugin. This described the basic setup of getting the plugin configured, and set with the proper perms to function. In this post we will go over how to leverage the plugin to generate agent pods. At Moogsoft most of our pipelines are scripted and are built inside of, or from parts of, Jenkins shared functions library we maintain.
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.
AWS CloudFormation provides an easy way to model and set up AWS resources to help you save time in deploying the stack you need to run your applications. Today, AWS announced the launch of AWS CloudFormation Public Registry. CloudFormation Public Registry is a searchable collection of extensions that allows you to easily discover, provision, and manage resource types and modules published and maintained by AWS Partner Network (APN) partners like Sysdig.
Thinking of migrating applications to cloud through a lift and shift approach? It could be a time to rethink your plan and take control of your migration journey, in a secure way. According to Markets and Markets, the global application modernization services market size is expected to grow from USD 11.4 billion in 2020 to USD 24.8 billion by 2025, at a Compound Annual Growth Rate (CAGR) of 16.8% during the forecast period. And the numbers are not stopping there!
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.
Three months ago, we launched VMWare Tanzu RabbitMQ for Kubernetes to automate high-performance messaging on demand with our cluster Operator.* Since then, customers have approached us with higher-level needs that inspired us to extend and improve Tanzu RabbitMQ. In other words, you’ve spoken, and we’ve listened. And so now, in version 1.1, we go well beyond automating cluster operations to orchestrating complex topologies, adding alerts, and previewing active-passive replication.
Microsoft recently reported two widespread cryptomining attacks targeting Kubeflow, a popular cloud-native platform for machine learning (ML) workloads on Kubernetes. Attackers targeted Kubeflow installations using either the Kubeflow central dashboard interface or Kubeflow Pipelines interface for scheduling crypto-mining workloads.
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.
In order to run Kubernetes in production, you need more than just the base Kubernetes, but a variety of other necessary add-on services, such as monitoring, security, disaster recovery, and more. However, navigating the cloud-native ecosystem is complex and rapidly changing, making it difficult to build a robust production platform required to run mission critical business services.
