spicedb-operator
operator-sdk
spicedb-operator | operator-sdk | |
---|---|---|
2 | 23 | |
57 | 7,005 | |
- | 0.5% | |
7.8 | 8.0 | |
7 days ago | 7 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
spicedb-operator
-
Writing a Kubernetes Operator
This is a common frustration of mine as well!
In the latest release of the spicedb-operator[0], I added a feature that allows users to specify arbitrary patches over operator-managed resources directly in the API (examples in the link).
There are some other projects like Kyverno and Gatekeeper that try to do this generically with mutating webhooks, but embedding a `patches` API into the operator itself gives the operator a chance to ensure the changes are within some reasonable guardrails.
[0]: https://github.com/authzed/spicedb-operator/releases/tag/v1....
operator-sdk
-
Building a Kubernetes Operator with the Operator Framework
operator-sdk: brew install operator-sdk
-
Annotations in Kubernetes Operator Design
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.
-
Hacking in kind (Kubernetes in Docker)
I've recently been working on an operator (built using the operator-sdk) that manages cluster node lifecycles. Kind allows you to spin up clusters with multiple nodes, using a Docker container per-node and joining them using a common Docker network. However, the kind executable does not allow you to modify an existing cluster by adding or removing a node.
-
Creating Kubernetes Operators with operator-sdk
To illustrate what we can do with an operator, I will create a proof of concept using operator-sdk. According to the official website::
- What Is A Kubernetes Operator?
-
Writing a Kubernetes Operator
Besides the frameworks TFA lists, you can also build Operators in Ansible or Helm.
https://sdk.operatorframework.io/
- Question: Resources to learn K8s operator programming
-
Using k8s-apiserver as AAA server for microservices?
Operator SDK is basically just a thin wrapper for kube-builder
-
What topics should I cover as DevOps in Golang after practice and learning syntax
You mean the Operator SDK? https://sdk.operatorframework.io
-
Dont understand how I can watch external resources modification/deletion with my custom operator
yes I agree with youu, an issue has been opened on the operator-sdk github page regarding this topic https://github.com/operator-framework/operator-sdk/issues/6117
What are some alternatives?
examples - A collection of examples for SpiceDB users
kubebuilder - Kubebuilder - SDK for building Kubernetes APIs using CRDs
prometheus-operator - Prometheus Operator creates/configures/manages Prometheus clusters atop Kubernetes
terraform-provider-kubernetes-alpha - A Terraform provider for Kubernetes that uses dynamic resource types and server-side apply. Supports all Kubernetes resources.
sample-controller-kubebuilder - This is Sample Controller(Foo Controller) developed by Kubebuilder
rbacsync - Automatically sync groups into Kubernetes RBAC
postgres-operator - Postgres operator creates and manages PostgreSQL clusters running in Kubernetes
kubeplus - Kubernetes Operator to create multi-instance SaaS from Helm charts using Kubernetes-native APIs
controller-runtime - Repo for the controller-runtime subproject of kubebuilder (sig-apimachinery)
databricks-kube-operator - A Kubernetes operator to enable GitOps style deploys for Databricks resources
sandbox-operator - A Kubernetes operator for creating isolated environments