Unfortunately I have a conflict and won't be able to attend. While I won't be there, I want to suggest some topics in an effort to get us closer to a code drop:
1. operator framework - operator-sdk vs kubebuilder vs kudo (vs something else) 2. build tool(s) 3. CI 4. e2e test framework, libraries, etc. I think most of the C* operator projects are built with operator-sdk. It would be nice to hear any thoughts on kubebuilder. It is perfect timing for Zain to talk about the Kudo project as well. I think it is safe to say that Make is the de facto build tool for Go projects in general. Cass Operator uses https://magefile.org/. I am not sure if CI needs to be sorted out now, but I think it makes sense to at least get the conversation started. Lastly, it would be great to get people's thoughts on test frameworks, libraries, etc. operator-sdk for example provides a test framework which provides options for running tests both out of cluster as well as in cluster. Cass Operator uses https://onsi.github.io/ginkgo/ and kubectl for integration tests out of cluster. CassKop uses https://github.com/aelsabbahy/goss/tree/master/extras/dgoss for image testing/validation. Thanks John On Wed, Jul 15, 2020 at 8:53 PM Patrick McFadin <pmcfa...@gmail.com> wrote: > Hi everyone, > > Just a reminder that our SIG will be meeting tomorrow at 11AM PST. We have > Zain Malik from the Kudo project coming to talk to us about operator > builder that has just just entered the sandbox at the CNCF. > > John Sanda will not be able to make it this week but will forward dome > notes on the community CRD for discussion. > > > https://cwiki.apache.org/confluence/display/CASSANDRA/2020-07-16+Cassandra+Kubernetes+Operator+SIG > > See you there, > > Patrick > -- - John
