Repurpose this repository into hosting the official Ansible K8s collection

[geerlingguy]

As the title says—this repository originally contained all the Kubernetes modules in a kubernetes role, but with Ansible 2.8, collections became the new fancy thing for distributing non-role content. We can now move all the Ansible Kubernetes modules into a collection, test them with ansible-test or molecule, and get some development velocity going again (since core has been slowing down on merging new community modules or features for existing community modules).

Some of the things we'll need to do:

• [ ] Close all existing issues in this repo (they are outdated)
• [ ] Create a new collection and replace the repo contents with that collection
• [ ] Begin moving k8s modules from Ansible core into this new collection
• [ ] Figure out how to communicate to users they should switch to using this collection for Kubernetes content
• [ ] Move select other k8s modules into this collection, for example:
  • k8s_exec
  • k8s_event
  • k8s_status
  • Etc.

[geerlingguy]

Related: https://github.com/ansible/ansible/issues/65285

[geerlingguy]

Another idea: Maybe we change the name of this repo to "ansible-kubernetes" or "ansible-kubernetes-content" (or collection) since it could (probably will) also include more content, like playbooks, roles, plugins, etc.

[gundalow]

If this will be a community collection, maybe it should be moved to github.com/ansible-collections/ I can help if people agree. Can get testing setup there as well.

[geerlingguy]

@gundalow - I think that would be a good idea (or we could just abandon this repo and create a new one with the same maintainers under github.com/ansible-collections/kubernetes maybe?).

[gundalow]

Can either move the repo or create a fresh one, I don't mind either way. Just let me know and I'll do the necessary.

[DanielFroehlich]

I vote for MOVE, because history is important. Just my two cents Dan

---

Sent from mobile, please excuse brevity. Daniel.Froehlich@redhat.com, +49 176 10 24 84 33

John R Barker notifications@github.com schrieb am Fr., 10. Jan. 2020, 21:40:

Can either move the repo or create a fresh one, I don't mind either way. Just let me know and I'll do the necessary.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ansible/ansible-kubernetes-modules/issues/38?email_source=notifications&email_token=AENMQWYXU5YS7FPC4KMZSHDQ5DML7A5CNFSM4JR4WWTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIVEVFI#issuecomment-573196949, or unsubscribe https://github.com/notifications/unsubscribe-auth/AENMQWYS5CPETY5HYKGD2PLQ5DML7ANCNFSM4JR4WWTA .

[fabianvf]

@DanielFroehlich The history of this repo isn't yet connected to the collection, we were just considering repurposing this repo for it. @gundalow let's go ahead and create a fresh one

[gundalow]

@DanielFroehlich The history of this repo isn't yet connected to the collection, we were just considering repurposing this repo for it. @gundalow let's go ahead and create a fresh one

That's correct I can create github.com/ansible-collections/kubernetes and you can move the existing files and keep the git history

If you'd like me to do this please "vote" on the issue with :+1:, otherwise :-1:

[gundalow]

Could I please get votes on the above issue? Then I'll create the repo as needed

[gundalow]

It lives https://github.com/ansible-collections/kubernetes

You can import the existing code and keep the git history if you wish..

[gundalow]

I've setup base GitHub actions which use ansible-test, though I've not looked into how you test kubernetes, feel free to poke me (gundalow) on IRC if that needs tweaking.

[geerlingguy]

I will work on moving the code/history, and then after things are working there, I believe we could archive this Git repository as its purpose has been fulfilled. I'll also be sure to update the Ansible Kubernetes community wiki entry.

[geerlingguy]

@gundalow - code was pushed to the new repo, and I'm working on restructuring it as a collection. How should we go about archiving this repo? I don't think any of the issues remain relevant anymore.