You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ?
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.
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 viakubectl
, but not theansible_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 theetc/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
The text was updated successfully, but these errors were encountered: