Keep your clusters fighting fit with Palette’s advanced automation for key post-deployment operations tasks, from patching to backups.
The real work of running Kubernetes comes after deployment. How do you handle upgrades and patches, monitoring, role changes, backups, certificate rotations and all the other essential tasks — and do so consistently across multiple clusters? Palette can help.
Palette doesn’t just deploy Kubernetes clusters. It has a rich set of native features to help automate and simplify key tasks, drawing on the best of open source projects like Velero, Cluster API, KubeCost and Prometheus, preconfigured and supercharged by our declarative multicluster architecture.
Need to change your clusters? No problem. From Palette’s interface you can quickly edit the size and configuration of your node pools to adjust scaling, availability zones, disk and more. Just edit, type, and hit save, and Palette will do the rest.
Applying a patch or updating part of your Kubernetes stack to a new version from your repository is just a matter of editing your Cluster Profile, the declarative blueprint that Palette uses to build your clusters. It’s as easy as 1, 2, 3:
How much time could this save you, compared to logging in to each cluster individually, manually applying a patch, and verifying success?
With Palette you have a rich set of monitoring tools at your disposal, giving you the key insights you need to maintain Kubernetes availability and performance.
Need more? Through our Prometheus Monitoring Stack we make it straightforward to deploy a powerful set of additional monitoring capabilities on a dedicated monitoring cluster, particularly valuable for large-scale Kubernetes deployments where the volume of monitoring data is extreme.
We know that security matters to you. Palette has a native suite of scans to help you validate the integrity of your clusters. These include:
You can run all these scans on demand or schedule them.
Our native backup functionality is based on the best-of-breed open source tool Velero. We preconfigure it to make it easier to use as part of your enterprise Kubernetes workflow, across multiple clusters.
You have full control over which clusters you back up, where your backups are stored, which namespaces and other elements are backed up (including persistent volumes), and how your backups are scheduled.