Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

Repurpose this repository into hosting the official Ansible K8s collection #38

Open
5 tasks
geerlingguy opened this issue Nov 26, 2019 · 13 comments
Open
5 tasks

Comments

@geerlingguy
Copy link

geerlingguy commented Nov 26, 2019

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:
@geerlingguy
Copy link
Author

Related: ansible/ansible#65285

@geerlingguy
Copy link
Author

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
Copy link

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
Copy link
Author

@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
Copy link

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
Copy link

DanielFroehlich commented Jan 11, 2020 via email

@fabianvf
Copy link
Collaborator

@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
Copy link

gundalow commented Jan 21, 2020

@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 👍, otherwise 👎

@gundalow
Copy link

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

@gundalow
Copy link

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

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

@gundalow
Copy link

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
Copy link
Author

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
Copy link
Author

@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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants