Upcoming workflow change for SOK development and release management

[rlieberman-splunk]

Hi all,

Hope you're having a great week so far!  We have a quick announcement to share around some internal changes to how Splunk will manage our code pipelines for Splunk Operator going forward.

While the Splunk Operator for Kubernetes (SOK) project will continue to be hosted on GitHub, Splunk will move to using our internal code repository and pipelines for development and release management. This is a key step that will enable us to:

1. Release new features faster for all SOK customers
2. Harden our testing and release processes
   This is a big part of our overall effort to make Kubernetes a first-class deployment model!! 😄

What changes for you
TL;DR: Very little!
Splunk Operator will continue to be hosted on GitHub, and act as a public mirror and intake surface. GitHub pull requests and issues will continue to be accepted as intake.

The only change will be that GitHub will no longer be the authoritative merge/release path.  We will share additional documentation shortly on the new workflow for contribution and issue-handling.  (If you have any recent / outstanding MRs and want to discuss next steps, please feel free to reach out to Venugopal Balasubramanian venubala@cisco.com!)

Please feel free to reach out if you have any questions!