Hi Daniel, The reason I had removed `kubernetes` component is that the component attracted two different kinds of issues. I would like to be able to differentiate issues related to kubernetes executor, and kubernetes-related operators and hooks. I have been thinking that prefixes may be helpful in this case.
- For operators/hooks, we can have a: `contrib-kubernetes` component. - For the Kubernetes executor, we can have a `executor-kubernetes` component. I think this prefix structure would be really helpful, as it sets a precedent for other components for executors (e.g. `executor-celery`, `executors` (for any without a particular component)); and for operators/hook (e.g. `contrib-gcp`, `contrib-aws`, ...). This allows users/contributors to file issues, and see the appropriate components as they type the prefix. Thoughts?
