Skip to content
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

Populate the 'ansible_connection' so a role can interact with the container itself #1

Open
DanSibbernsen opened this issue Apr 11, 2022 · 2 comments · May be fixed by #4
Open

Populate the 'ansible_connection' so a role can interact with the container itself #1

DanSibbernsen opened this issue Apr 11, 2022 · 2 comments · May be fixed by #4

Comments

@DanSibbernsen
Copy link

DanSibbernsen commented Apr 11, 2022

Hi! I was reading the ansible-for-kubernetes book, and part of my role interacts with the container that is created by kind, and it can't connect to the docker container itself to make modifications. It seems setup to test via kubectl, but not the ansible_connection used by molecule.

For reference, my role is designed to renew the kubernetes certificates. It calls kubeadm certs renew all and then refresh the static pods of [kube-apiserver, kube-controller-manager, kube-scheduler, etcd] by moving the files out of the etc/kuberntes/manifests and then back once the pods have come down.

Can we enhance this driver so Molecule can connect to the docker container spun up by kind ?

Ansible-for-kubernetes-97

@github-actions
Copy link

Thank you for your first issue! 😊🕹️

@retr0h
Copy link
Owner

retr0h commented Jan 21, 2024

You could do that by simply writing playbooks which use the ansible kubernetes ecosystem. I'm not too familiar with the ansible_connection stuff as it relates to kubernetes.

@mnaser mnaser linked a pull request Jan 24, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants