Lead Image © Sebastian Duda, 123RF.com
Safeguard your Kubernetes setup with Kanister
Blueprint for Success
Kanister, developed by Kasten and acquired by Veeam, has defined a number of objectives for its data management tool [1]. The focus is on application-centric backup, which, in concrete terms, means the target group is primarily users of specialist applications and not just those who deal with system-related infrastructure. The developers opted for an API-based approach to programming: All addressable tasks are abstracted by a well-defined API, which is also very easy to extend.
ActionSets and Blueprints
Like many other Kubernetes products, Kanister's implementation is based on the operator principle, which made it easy for Veeam to package, deploy, and manage Kanister, providing a range of Kubernetes resource definitions. In total, Kanister comprises three main components: one controller and two custom resources – ActionSets and Blueprints. The workflow is shown in Figure 1:
Figure 1: Interaction between the controller, ActionSets, and Blueprints in Kanister.
- First, an ActionSet is created. An ActionSet, which like most manifests is declarative, describes a set of
actionsto be executed on Kubernetes resources at runtime. Each action
Buy this article as PDF
(incl. VAT)
Buy ADMIN Magazine
US / Canada
UK / Australia
Related content
-
A GitOps continuous delivery tool for Kubernetes
Argo CD uses Git repositories as the source of truth for defining a desired application state and automates the deployment in target environments. -
Secure access to Kubernetes
Kubernetes comes with a sophisticated system for ensuring secure access by users and system components through an API. We look at the options for authentication, authorization, and access control. -
Serverless applications with OpenFaaS
Use advanced techniques for automation, optimization, and security to deploy serverless applications with the OpenFaaS framework in a Linux environment. -
Monitoring container clusters with Prometheus
In native cloud environments, classic monitoring tools reach their limits when monitoring transient objects such as containers. Prometheus closes this gap, which Kubernetes complements, thanks to its conceptual similarity, simple structure, and far-reaching automation. -
Secure microservices with centralized zero trust
SPIFFE and SPIRE put strong workload identities at the center of a zero-trust architecture. They improve reliability and security by taking the responsibility for identity creation and management away from individual services and workloads.