Add additional descriptions

[josepalafox]

A lot of the description columns are somewhat redundant

"Redis operator for Kubernetes"
"Bulletproof MySQL on Kubernetes"
"KubeDB Operator"

I think what you'd want from the description column is something like: Operator for Redis an in-memory data structure store, used as a database, cache and message broker.

Else its incumbent on someone to figure out what all these tools do. For me I didn't know what Zeebe or Kong are. This may seem a little silly if you're steeped in this ecosystem but for people that might be new to these tools it presents a big learning curve to figure out what each tool does when they might just be trying to evaluate whether or not the K8s ecosystem has the bits and pieces they need to start a proof of concept with kubernetes.

Is it ok to add a "function" column or to clean up the description columns so they aren't self referential?

Also, some of these link to large sets of operators what aren't well referenced, like KubeDB supports a huge variety of databases but from this view you almost have to know what KubeDB is to expect more operators in their repository, since their Redis/PostgreSQL/etc. databases aren't on the top level. Same with the openstack components. If I land here searching for a PostgreSQL operator I'm bound to explore PostgreSQL #1 or #2 first rather than going to KubeDB and seeing that they have a whole suite of operators.

Also, People may benefit from some grouping of operators, eg.
Databases >
SQL
NoSQL
Amazon Services >
Openstack services >

Are you open to a few more layers of classification if I propose the changes? Is there a SIG that manages this at all?

[robszumski]

There is an Operators SIG, but it doesnt really cover this repo. Thank you for all of the PRs!