databricks-kube-operator
spicedb
databricks-kube-operator | spicedb | |
---|---|---|
3 | 39 | |
16 | 5,195 | |
- | 1.9% | |
7.0 | 9.7 | |
3 months ago | about 17 hours ago | |
Rust | 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.
databricks-kube-operator
-
Writing a Kubernetes Operator
Here's another example of a custom rust operator, https://github.com/mach-kernel/databricks-kube-operator
Written by a co-worker to help manage our databricks projects across clusters. Works wonderfully!!
- Salut. Folosește cineva Kubernetes și Databricks? Am creat un Rust operator să ajute cu "easy CI/CD workflow".
-
What's everyone working on this week (45/2022)?
So I used kube-rs and came up with this: https://github.com/mach-kernel/databricks-kube-operator
spicedb
-
How I'm Learning SpiceDB
Good time to shout-out that SpiceDB is completely open-source, and we welcome community contributions! Whether you'd like to suggest improvements, fix documentation typos, or contribute to the community, please feel free to do so. Check out our Good First Issues and join our Discord community.
-
How do you manage transactions in Go? Do we really need to use one transaction for each request?
Have you taken a look at SpiceDB? The Authzed blog has a few posts that are useful to improving your understanding -- I can think of two: New Enemies and Writing relationships to SpiceDB.
-
How to start a Go project in 2023
Things I can't live without in a new Go project in no particular order:
- https://github.com/golangci/golangci-lint - meta-linter
- https://goreleaser.com - automate release workflows
- https://magefile.org - build tool that can version your tools
- https://github.com/ory/dockertest/v3 - run containers for e2e testing
- https://github.com/ecordell/optgen - generate functional options
- https://golang.org/x/tools/cmd/stringer - generate String()
- https://mvdan.cc/gofumpt - stricter gofmt
- https://github.com/stretchr/testify - test assertion library
- https://github.com/rs/zerolog - logging
- https://github.com/spf13/cobra - CLI framework
FWIW, I just lifted all the tools we use for https://github.com/authzed/spicedb
We've also written some custom linters that might be useful for other folks: https://github.com/authzed/spicedb/tree/main/tools/analyzers
-
Feature flags and authorization abstract the same concept
At AuthZed, we think about this topic regularly while developing SpiceDB[0], except we believe feature flags are a subset of authorization. I'd disagree with the author that permissions are always long-lived -- authorization can also be ephemeral (and often that's how it's most secure) or dependent on run-time context[1]. What's more, using SpiceDB, we can often collapse checking for authorization and feature-flags into a single round-trip by defining a permission that can additionally require a feature flag (e.g. permission = admin & has_feature_flag).
It's a little silly, but lots of folks ask for the moon when it comes to performance for authorization because it's critical to every request, but then go on and sprinkle a dozen feature flag RPCs each adding more and more latency. We think you should be able to have both.
What we're excited about is use cases beyond feature flags and authorization: we've also seen some folks use SpiceDB as an update graph or others as a dependency graph.
[0]: https://github.com/authzed/spicedb
[1]: https://authzed.com/blog/caveats/
-
Postgres: The Graph Database You Didn't Know You Had
It scaled well compared to a naive graph abstraction implemented outside the database, but when performance wasn't great, it REALLY wasn't great. We ended up throwing it out in later versions to try and get more consistent performance.
I've since worked on SpiceDB[1] which takes the traditional design approach for graph databases and simply treating Postgres as triple-store and that scales far better. IME, if you need a graph, you probably want to use a database optimized for graph access patterns. Most general-purpose graph databases are just bags of optimizations for common traversals.
[0]: https://github.com/quay/clair
[1]: https://github.com/authzed/spicedb
-
Writing a Kubernetes Operator
I get the sentiment. We held off on building an operator until we felt there was actually value in doing so (for the most part, Deployments cover the operational needs pretty well).
Migrations can be run in containers (and they are, even with the operator), but it's actually a lot of work to run them at the right time, only once, with the right flags, in the right order, waiting for SpiceDB to reach a specific spot in a phased migrations, etc.
Moving from v1.13.0 to v1.14.0 of SpiceDB requires a multi-phase migration to avoid downtime[0], as could any phased migration for any stateful workload. The operator will walk you through them correctly, without intervention. Users who aren't running on Kubernetes or aren't using the operator often have problems running these steps correctly.
The value is in this automation, but also in the API interface itself. RDS is just some automation and an API on top of EC2, and I think RDS has value over running postgres on EC2 myself directly.
As for helm charts, this is just my opinion, but I don't think they're a good way to distribute software to end users. The interface for a helm chart becomes polluted over time in the same way that most operator APIs become polluted over time, as more and more configuration is pulled up to the top. I think helm is better suited to managing configuration you write yourself to deploy on your own clusters (I realize I'm in the minority here).
[0]: https://github.com/authzed/spicedb/releases/tag/v1.14.0
- AWS Creates New Policy-Based Access Control Language Cedar
-
Solution for ReBAC authz using attributes?
To my understanding, the only ReBAC system that supports dynamic attributes is SpiceDB.
-
The Annotated Google Zanzibar Paper
If you're curious to see a Postgres-based implementation, SpiceDB has a Postgres driver: https://github.com/authzed/spicedb/tree/main/internal/datast...
- We built an open source authorization service based on Google Zanzibar
What are some alternatives?
smartcore - A comprehensive library for machine learning and numerical computing. The library provides a set of tools for linear algebra, numerical computing, optimization, and enables a generic, powerful yet still efficient approach to machine learning.
Ory Keto - The most scalable and customizable permission server on the market. Fix your slow or broken permission system with Google's proven "Zanzibar" approach. Supports ACL, RBAC, and more. Written in Go, cloud native, headless, API-first. Available as a service on Ory Network and for self-hosters.
heed - A fully typed LMDB wrapper with minimum overhead 🐦
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
kubectl-operator - Manage Kubernetes Operators from the command line
casbin - An authorization library that supports access control models like ACL, RBAC, ABAC in Golang: https://discord.gg/S5UjpzGZjN
controller-idioms - Generic libraries for building idiomatic Kubernetes controllers
openfga - A high performance and flexible authorization/permission engine built for developers and inspired by Google Zanzibar
spicedb-operator - Kubernetes controller for managing instances of SpiceDB
realworld - "The mother of all demo apps" — Exemplary fullstack Medium.com clone powered by React, Angular, Node, Django, and many more
konst - Const equivalents of std functions, compile-time comparison, and parsing.
zanzibar-pg - Pure PL/pgSQL implemenation of the Zanzibar API