lyft / flinkk8soperator vs GoogleCloudPlatform / flink-on-k8s-operator
- Dominant language
- Go
- Stars
- 581
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
I'm having a hard time picking a Flink Kubernetes operator between this one and https://github.com/GoogleCloudPlatform/flink-on-k8s-operator
They are pretty similar but they also have some differences. It would be nice to have a comparison between those solutions so people can make the right choice for their use case.
E.g.:
The Lyft Flink K8S operator supports Blue/Green deployments and rollbacks.
The GCP Flink K8S operator supports Sessions clusters and taking savepoints automatically.
Thanks!
Contributor guide
No contributing guide indexed for this repository
Research direction
Compare this repository with GoogleCloudPlatform/flink-on-k8s-operator, starting with the capabilities named in the issue: Blue/Green deployments, rollbacks, Sessions clusters, and automatic savepoints. Document the meaningful differences and indicate which use cases each operator suits, so readers can make an informed choice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100