richard
/
kubespray
mirror of https://github.com/kubernetes-sigs/kubespray.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
7671 Commits
29 Branches
81 Tags
150 MiB
Tree: 37ef2db81b
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '37ef2db81b'
${ noResults }
kubespray/tests/files/packet_fedora38-docker-weav...

12 lines
222 B
Raw Normal View History

Drop support for Fedora 28 and add Fedora 30 and 31 (#5969)
4 years ago
​
Use supported version of fedora in CI (#10108) * tests: replace fedora35 with fedora37 Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> * tests: replace fedora36 with fedora38 Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> * docs: update fedora version in docs Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> * molecule: upgrade fedora version Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> * tests: upgrade fedora images for vagrant and kubevirt Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> * vagrant: workaround to fix private network ip address in fedora Fedora stop supporting syconfig network script so we added a workaround here https://github.com/hashicorp/vagrant/issues/12762#issuecomment-1535957837 to fix it. * netowrkmanager: do not configure dns if using systemd-resolved We should not configure dns if we point to systemd-resolved. Systemd-resolved is using NetworkManager to infer the upstream DNS server so if we set NetworkManager to 127.0.0.53 it will prevent systemd-resolved to get the correct network DNS server. Thus if we are in this case we just don't set this setting. Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> * image-builder: update centos7 image Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> * gitlab-ci: mark fedora packet jobs as allow failure Fedora networking is still broken on Packet, let's mark it as allow failure for now. Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch> --------- Signed-off-by: Arthur Outhenin-Chalandre <arthur.outhenin-chalandre@proton.ch>
1 year ago
Drop support for Fedora 28 and add Fedora 30 and 31 (#5969)
4 years ago
​
​
​
Defaults: replace docker with containerd as our default container_manager (#8175) * Defaults: replace docker with containerd as our default container_manager * CI: Use docker for download_localhost test * Defaults: with container_manager=containerd we need etcd_deployment_type=host * CI: Run weave jobs with docker * CI: Vagrant don't download_force_cache * CI: Fix upgrade tests * should run compatible with old settings, this means docker * we need to run with a distro that has at least modern containerd, this means move from debian9 to debian10 to allow `containerd_version` to match between 2.17 and master
3 years ago
​
​
​
containerd: change default resolvconf_mode to host_resolvconf (#8247) * containerd: change default resolvconf_mode to host_resolvconf * Wait for kube-apiserver to come back after pod refresh * Handle resolv.conf gracefully * Retain currently configured DNS entries to ensure we don't break the resolvers * Suse uses wickedd for network management so no dhcp hooks * Molecule: increase ansible timeout * CI: Increase ansible timeout to 120s for Packet jobs
3 years ago
  1. ---
  2. # Instance settings
  3. cloud_image: fedora-38
  4. mode: default
  6. # Kubespray settings
  7. kube_network_plugin: weave
  9. # Docker specific settings:
  10. container_manager: docker
  11. etcd_deployment_type: docker
  12. resolvconf_mode: docker_dns