-
Notifications
You must be signed in to change notification settings - Fork 23.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Start Kubernetes Working Group #65285
Comments
Files identified in the description:
If these files are inaccurate, please update the |
+100, I think it's definitely past time we did this. I'm happy to sign on as a lead. I also wanted to point out that in addition to the members and use cases you listed, there's also a large community built around installing and managing Kubernetes with Ansible in the kubespray project |
@geerlingguy please add me to this proposal. |
Excellent stuff, thanks y'all All kubernetes things: k8s |
I'm in but, I'm wondering if it'd be helpful to spin up a similar effort in the kubernetes/community repo? Not sure where the best place to launch from? |
Chris, good question, perhaps where ever the most people are? I guess it should appear as an Ansible Working Group and a k8s SIG, and they should cross link. |
Yeah. The SIGs are aligned to functions not necessarily tooling. I can track down which SIG might work best. But, what will this group be managing, building, working on, etc.? |
I was thinking that it might be worth making a thing here: https://github.com/kubernetes/community/tree/master/sig-api-machinery#kubernetes-clients I had thought that @fabianvf was working on making the kubernetes collection to be apart of that IIRC form a conversation we had awhile ago. |
I think, for now, having the K8s WG on the Ansible side is most productive (since it's quite wide-ranging, from people using Ansible to manage cluster setup, to people managing apps inside clusters with Ansible, to people running operators with Ansible (and other use cases too). I've populated the Working Group wiki page (https://github.com/ansible/community/wiki/Kubernetes), and also set up a pinboard (ansible/community#515). There's a punchlist on the pinboard issue of initial thing we should figure out, especially where future module development work should go (that's probably most pressing as Ansible core is slower to adopt anything non-core right now, and there are some useful K8s modules that are lingering in the PRs). I've also put some of the TODOs from this issue into that Pinboard issue, and I figure we can continue the conversations on IRC. I think this issue's lived its course and was good to get the initial group kickstarted. See you in the issue queues! |
SUMMARY
I would like to kick off the Kubernetes Working Group for Ansible.
There is already something of an informal working group consisting of at least the following:
I hope to get a more comprehensive list, and also commitments for various roles through this issue.
Usage of Ansible with Kubernetes and OpenShift has become much more prevalent, and as such it's probably good to have a better handle on where things are, where things are going, and how to get to where we want to be—this requires a little more organization than the current informal Kubernetes community we have in Ansible-land.
For example, there are currently people using:
In many cases these groups of users are working independently, and have been developing Kubernetes-related content independently.
I believe we can make the 'use Ansible for Kubernetes' automation story more compelling if we formally get this working group going and to push things forward with a little more organization.
One short-term goal could be to get an official ansible-GitHub-namespaced repository set up to build an official
k8s
collection (so we can begin the process of moving the Kubernetes modules/plugins/etc. out of core and into a community-maintained collection). There are modules likek8s_exec
,k8s_event
, andk8s_status
which may be good candidates to get into a collection (since it seems like core is not really accepting new modules right now).ISSUE TYPE
COMPONENT NAME
k8s, k8s_info, k8s_scale, k8s_service (etc.)
ADDITIONAL INFORMATION
Community Wiki page: https://github.com/ansible/community/wiki/Kubernetes
cc @gundalow
The text was updated successfully, but these errors were encountered: