Next up in our "meet the team" blog series is Stefan Prodan, another one of our super talented Developer Experience Engineers. He spends most of his time here at Weaveworks integrating and testing different open source projects with Weave Cloud and blogging about it. He’s passionate about all things Cloud Native, programs in Golang and has a soft spot for Prometheus as well as OpenFaaS serverless technology -- where he is a core contributor.
Continuing with our "meet the team" blog series, we introduce Ilya Dmitrichenko. Ilya is one of our talented DX engineers at Weaveworks who spends a lot of his time seeking out new technology and coming up with innovative workflows that end up in our products. In addition to this, Ilya is also a CNCF ambassador and is a presenter and one of the creators of the Kubernetes Office Hours
This is the first post in our ‘Meet the Team’ blog series. We will be showcasing some of the Weaveworks’ team who are attending, speaking and teaching at the upcoming CNCF KubeCon held in Copenhagen. First up is Brice Fernandes - software engineer, entrepreneur and instructor.
In this blog we provide some context around why you need microservices and explain how the adoption of microservices was the catalyst that ultimately led to continuous delivery and continuous processes.
Sylvain Hellegouarch (ChaosIQ) demonstrates how to implement an accelerated learning and system-improvement loop. With ChaosIQ , built on top of the open source Chaos Toolkit, controlled and careful Chaos Engineering experiments were executed against a system running in Kubernetes and then observed, diagnosed and rolled out with Weave Cloud to make improvements based on the surfaced weaknesses.
Learn how an online financial advisory company secured their Kubernetes clusters and the benefits gained when using Weave Net to maintain security and compliance.
We’re counting down the days until we visit the Kubernetes community in Copenhagen, for the next KubeCon event (30 April - 4 May). Read our top 10 reasons for why you should attend!
In this Part 2 of our top 11 CICD tools for creating an automated pipeline to Kubernetes, we looked at tools designed for Continuous Delivery.
In this blog we look at the top 11 tools for continuous delivery to Kubernetes and discuss the pros and cons of each one.
Learn what the top 5 best practices are for building, deploying and managing services in Kubernetes from Sandeep Dinesh, Developer Advocate, Google Cloud Platform.
Not all systems can meet their SLAs by relying on CPU/memory usage metrics alone, most web and mobile backends require autoscaling based on requests per second to handle any traffic bursts. This step by step guide shows you how to set up Kubernetes Horizontal Pod Autoscaler with Prometheus defined custom metrics, to fine tune your application monitoring and ensure high availability.
Read our latest whitepaper which details the hurdles that DevOps teams must clear in order to move from Continuous Integration to Continuous Delivery. It is designed as a resource for DevOps practitioners who want to take full advantage of the efficiencies and operational advantages that CD enables, yet struggle to overcome the conceptual, cultural and technological challenges that complicate the transition from CI to CD.
Part 4 of the GitOps blog series explains how you can make your continuous delivery pipeline more secure using 3 best practices which enables auditing and compliance. This is aimed at Kubernetes users who have adopted Continuous Integration (CI) and who want to add Continuous Deployment (CD) to their pipeline.
While Helm helps with getting applications running, you need other tooling to keep them up to date when something changes. Check out our alpha release of our Helm integration in Weave Flux. It makes sure your Helm chart releases are kept up to date with what’s in Git. You can try it out using the published repository in Github.
Weave Cloud Deploy is a Continuous Deployment/Delivery operator for Kubernetes which makes it super easy to automate releases to a cluster - but what about multiple clusters? Weave Cloud Deploy can filter tags - by tagging each image with an environment specific prefix, it’s possible for the same image build to be automatically released to each environment in turn.
Looking at a CICD pipeline with security in mind, reveals some interesting concerns. Consider the credentials and access typically assigned to each step, and what’s actually required for each step - Read Write access, and Read Only access. The CI system can be a target, because it’s got credentials for the source code, the image repo and the cluster, and it crosses two logical security boundaries. Learn how you can mitigate this with a GitOps approach.