Summary

To go fast you need a reliable way to configure and deploy clusters whenever and wherever you need one; be that in development, testing, staging or production. Spending time configuring bespoke clusters everytime doesn’t work in this era of multiple daily deployments often cited as a measure of success in today’s cloud native world.

Kubernetes helps you innovate more quickly provided that you can manage the complexity of configuring platforms for it. But one of the biggest challenges with adopting a cloud native way of software development is maintaining Kubernetes developer platforms used by multiple teams who need to operate across multiple environments and clouds. 

No matter where the clusters are run, fleets will not only require an identical configuration, but the configuration must also be quickly and easily upgraded with security patches and other required maintenance with minimal to no down time.

What it Does

In Weave Kubernetes Platform (WKP), declarative configuration is extended with the concept of models that can handle any variants. A model consists of a cluster definition, a set of components and team workspaces. Users can deploy a model and specialize the configuration at build time to deal with their particular needs. Common cluster components make use of overrides so that configuration data is provided at runtime, and if that's not enough, you can build your own component models and keep them in Git.

models-diagram.png

Manage the entire lifecycle of the cluster from a single pane of glass. Apply Kubernetes upgrades and security patches, as well as any version upgrades and fixes for components and add-ons managed and controlled from within Git. 

  • Automate the cluster configuration management.
  • Control who can apply upgrades, and security patches.
  • Control which components get upgraded.

Why should I care?

Almost every element of Kubernetes uses declarative configuration: the cluster, and each component within it as well as the applications running on it. This allows for the platform configuration to be stored together in Git as a cluster definition. In GitOps, an agent running inside the cluster ensures that the cluster configuration and the apps that run on it are always up to date. In the case of a drift in configuration, an alert is triggered and the cluster can be automatically reconciled with a known state stored in Git:

  • Git-backed security guarantees provenance with a built-in audit trail of who did what. 
  • Increased reliability with secure built-in GitOps to automate the upgrade process across fleets.
  • Scalable cluster management across fleets of clusters and applications.
  • Save time and costs with complete platform configurations pushed to Git.
  • Proactive monitoring with alerts on cluster configuration drift.

history_of_changes_v2.png

Find Out More

The Weave Kubernetes Platform (WKP) is a production ready platform with GitOps as the underlying architecture and developer experience. It simplifies cluster configuration and management across your organization by bringing together all the tools, services, and components that your team needs to run into a single platform. WKP also provides policy and Git-based rules to specify, audit, and control who can change what in the cluster configuration.

Solving Cloud Native App Delivery with the Weave Kubernetes Platform

GitOps is both the underlying architecture and developer experience of WKP which simplifies the configuration and management of Kubernetes platforms.

Schedule a demo