This document defines a high level roadmap for the rss operator development.
The dates below should not be considered authoritative, but rather indicative of the projected timeline of the project.
- Need user facing documentation. Much of the current documentation in doc/user was carried over from the etcd-operator and is in need of revision.
-
Remove lingering traces of etcd and galera references and terminology
-
Check conformance with the controller pattern
-
Check conformance with logging conventions
-
Incorporate Subresources for CustomResources
-
Incorporate User Aggregated API Servers to improve reliability, validation and versioning.
The use of Aggregated API should be minimally disruptive to existing users but may change what Kubernetes objects are created or how users deploy the operator.
-
Metrics and logging?
- Expose operator metrics
- How many clusters it manages
- How many actions it does
- Expose the running status of the cluster
- cluster size, version
- Expose errors
- bad version, bad cluster size, dead cluster
- Expose operator metrics
-
Security
-
Create a Rabbit MQ sample app
-
Decide on an upgrade story
-
Implement backup/restore (Great for demos where there is no shared storage)
-
Review TLS code/docs for relevance
-
Create a demo
-
Additional unit tests
-
e2e testing