Carlos Camacho Gonzalez

@haidaraM the include_role is an incredibly common case when including tasks from roles, is there a way to workaround this in order to not append the tasks of the role...

Hi @rsshilli by any chance, do you have an example for rendering the network like you have in https://github.com/visjs/vis-network/issues/203#issuecomment-571164712 ? Thanks!

This `https://github.com/Kubeinit/kubeinit/blob/main/kubeinit/roles/kubeinit_prepare/tasks/prepare_podman.yml#L39` needs to run in the hypervisors. Called from `roles/kubeinit_services/tasks/00_create_service_pod.yml` Maybe we need to do the login first.

Right, the deployment is as it was since the beginning, services pod in the first hypervisor, (the single-node deployment) and running the playbook also from the hypervisor (no container yet)....

Hi, would you mind running the de[ployment like this? ``` ansible-playbook -v --user root -e kubeinit_spec=k8s-libvirt-1-1-1 -e hypervisor_hosts_spec='[[ansible_host=nyctea],[ansible_host=tyto]]' ./kubeinit/playbook.yml ``` I bet you are using the default inventory file, there...

Hi, So far adding additional interfaces to the compute nodes is not supported, maybe if you could share your use case we could add it in the future.

Maybe there are some IPtables rules not persisted after rebooting and I dont have a way to test this on Rocky.

I didnt see this again @jeffabailey I built all the packages for aarch64 but there are some changes needed in the guest vm images to have it running in ARM....