Annotations in Kubernetes Operator Design

1. kubebuilder

   1 51 8,405 9.8 Go

   Kubebuilder - SDK for building Kubernetes APIs using CRDs

   

   The operator that I've been working on is designed to manage the full lifecycle of a QuestDB database instance, including version and hardware upgrades, config changes, backups, and (eventually) recovery from node failure. I used the Operator SDK and kubebuilder frameworks to provide scaffolding and API support.

2. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

3. operator-sdk

   2 26 7,405 8.4 Go

   SDK for building Kubernetes applications. Provides high level APIs, useful abstractions, and project scaffolding.

   

   The operator that I've been working on is designed to manage the full lifecycle of a QuestDB database instance, including version and hardware upgrades, config changes, backups, and (eventually) recovery from node failure. I used the Operator SDK and kubebuilder frameworks to provide scaffolding and API support.

4. kubernetes

   3 788 115,115 10.0 Go

   Production-Grade Container Scheduling and Management

   

   The first is that you are unable to use field selectors with CRDs, so this query is literally impossible in the current version of k8s!

5. QuestDB

   4 312 15,200 9.7 Java

   QuestDB is a high performance, open-source, time-series database

   

   In this post, I will detail a way in which I recently used annotations while writing an operator for my company's product, QuestDB. Hopefully this will give you an idea of how you can incorporate annotations into your own operators to harness their full potential.

Suggest a related project