There are companies that are building proprietary operators not hosted on github, but other places like the Red Hat container registry. Are they in scope for this awesome list?

Hello!
Thanks for creating this list :D

I was wanting to ask about updating the notes on the Kong Operator - it does what it says, however it has not been updated in 2 years and is not compatible with kubectl v1.7+ - it still uses the ThirdPartyResource API, instead of CRDs and so I have not been able to use it / check if it actually works.

I had planned on updating the Operator, but that would take time + learning Go, so wont happen this weekend ;)

Thanks!

https://github.com/solo-io/envoy-operator

If this can go here https://github.com/practo/k8s-worker-pod-autoscaler

It is an autoscaler for workers.

It's been two months since the last commit (i.e. 98c3541) and Pull requests that want to include new operators are piling up.

Is the project still maintained?

Here is a list of moved and removed repos.

The following repos have moved:

aerogear/android-sdk-operator => aerogear-attic/android-sdk-operator
application-runtimes/operator => application-stacks/runtime-component-operator
aws/aws-controllers-k8s => aws-controllers-k8s/community
Orange-OpenSource/cassandra-k8s-operator => Orange-OpenSource/casskop
eclipse/che-operator => eclipse-che/che-operator
kubic-project/dex-operator => SUSE/dex-operator
appscode/searchlight => searchlight/icinga-operator
gianarb/influxdb-operator => influxdata/influxdb-operator
jenkinsci/jenkins-operator => jenkinsci/kubernetes-operator
absaoss/k8gb => k8gb-io/k8gb
strimzi/strimzi => strimzi/strimzi-kafka-operator
Percona-Lab/percona-xtradb-cluster-operator => percona/percona-xtradb-cluster-operator
openfaas-incubator/openfaas-operator => openfaas/faas-netes
zalando-incubator/postgres-operator => zalando/postgres-operator
coreos/prometheus-operator => prometheus-operator/prometheus-operator
reactiveops/rbac-manager => FairwindsOps/rbac-manager
kubic-project/registries-operator => SUSE/registries-operator
jmckind/rethinkdb-operator => jomkz/rethinkdb-operator
jvm-operators/spark-operator => radanalyticsio/spark-operator
heptio/velero => vmware-tanzu/velero
zeebe-io/zeebe-operator => camunda-community-hub/zeebe-operator
Nuance-Mobility/zookeeper-operator => Nuance-XINFRA/zookeeper-operator

The following repos have been removed:

kudobuilder/operators/cassandra
containership/cerebral
cloudfoundry/cf-operator
couchbase/operator
ibm/couchdb-operator
kudobuilder/operators/elastic
ContainerSolutions/externalsecrets-operator
banzaicloud/infinispan-operator
kudobuilder/operators/kafka
kopf/operator
banzaicloud/mysql-operator
andyxning/nsq-operator
nuodb/nuodb-operator
Quobyte/Quobyte
MYOB-Technology/ops-kube-db-operator
fintechstuiods/ververica-platform-k8s-operator
banzaicloud/wildfly-operator
kudobuilder/operators/zookeeper

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?

When selecting a good Redis Cluster operator I found KubeDB elsewhere, but in this table it is not clear that it provides operators for:

• elasticsearch,
• memcached,
• mongodb,
• mysql,
• postgresql,
• redis

Multiple paths to go:

• add tags and host this page as something interactive with some tag-filtering on Github Pages?
• add these db's to comment column
• add kubedb also at "#3 Redis Cluster" etc

See issue #18

Hi

We have built some operators based on the new SDK - see below:

• https://github.com/banzaicloud/prometheus-jmx-exporter-operator - seamlessly (and non intrusively) monitor any Java app by injecting a Prometheus JMX agent into the pod (more details here: https://banzaicloud.com/blog/operator-sdk/)
• https://github.com/banzaicloud/infinispan-operator - create/operate Infinispan clusters
• https://github.com/banzaicloud/wildfly-operator - operate a WildFly cluster
• https://github.com/banzaicloud/pvc-operator - dynamically/programatically trigger PV by creating the accounts, class, etc

Let me know if you'd like to list them as they are all based on the new SDK.

Hello, we've been internally collecting a list of resources (Talks, presentations, docs) to learn about operators. I was wondering if, like other awesome-* lists, we could add a 'learning resources' section here for people looking for curated videos etc.

Not sure if that fits in the scope of this list, but would love to see a place where we find all of this :)

CC @surajnarwade