<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Karim on Medium]]></title>
        <description><![CDATA[Stories by Karim on Medium]]></description>
        <link>https://medium.com/@deep75?source=rss-9f1ca3c659fa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*TyBOdqjBKGix1ncmkqL8Xw.png</url>
            <title>Stories by Karim on Medium</title>
            <link>https://medium.com/@deep75?source=rss-9f1ca3c659fa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:17:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@deep75/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[AIOps : Investigation par l’IA dans Kubernetes avec HolmesGPT, Ollama et RunPod …]]></title>
            <link>https://deep75.medium.com/aiops-investigation-par-lia-dans-kubernetes-avec-holmesgpt-ollama-et-runpod-15846adcb2ee?source=rss-9f1ca3c659fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/15846adcb2ee</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[ollama]]></category>
            <dc:creator><![CDATA[Karim]]></dc:creator>
            <pubDate>Wed, 15 Jan 2025 00:52:40 GMT</pubDate>
            <atom:updated>2025-01-15T00:52:40.952Z</atom:updated>
            <content:encoded><![CDATA[<h3>AIOps : Investigation par l’IA dans Kubernetes avec HolmesGPT, Ollama et RunPod …</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rxIc_87saLNujjnQyHkE_g.png" /></figure><p>Dans le monde de l’orchestration de conteneurs, Kubernetes est devenu une norme pour gérer les workloads conteneurisés. Cependant, la gestion et le dépannage des clusters Kubernetes peuvent être complexes et chronophages. Cet article explore comment l’intelligence artificielle (IA) peut être intégrée dans Kubernetes pour améliorer l’investigation et la gestion des incidents. J’avais d’ailleurs évoqué le sujet dans un article précédent :</p><p><a href="https://deep75.medium.com/aiops-d%C3%A9boguer-son-cluster-kubernetes-en-utilisant-lintelligence-artificielle-g%C3%A9n%C3%A9rative-via-3924474de984">AIOps : Déboguer son cluster Kubernetes en utilisant l’intelligence artificielle générative via…</a></p><p>Ici je vais m’intéresser à HolmesGPT. HolmesGPT, développé par Robusta, est un agent de dépannage open source qui utilise l’IA pour investiguer les incidents dans les clusters Kubernetes avec ces caractéristiques :</p><ul><li><strong>Intégration avec les outils de gestion d’incidents</strong> : HolmesGPT se connecte à des outils comme PagerDuty, OpsGenie et Prometheus pour collecter des données et analyser les alertes.</li><li><strong>Investigation automatisée</strong> : Grâce à l’IA, HolmesGPT peut identifier et résoudre des problèmes tels que l’expiration des certificats SSL, les problèmes de ressources insuffisantes et les problèmes d’affinité des nœuds. Cela réduit significativement le temps et l’effort nécessaires pour le dépannage.</li><li><strong>Personnalisation</strong> : HolmesGPT permet de créer des livres de recettes (runbooks) personnalisés pour gérer des problèmes spécifiques, en utilisant des API et des outils personnalisés si nécessaire.</li></ul><p><a href="https://github.com/robusta-dev/holmesgpt">GitHub - robusta-dev/holmesgpt: On-Call Assistant for Prometheus Alerts - Get a head start on fixing alerts with AI investigation</a></p><p>Pour cet exercice, je vais d’abord lancer une instance Ubuntu 24.04 LTS de nouveau chez le fournisseur Cloud DigitalOcean :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3SRS1gKDiCuwMygt6M_hyg.png" /></figure><p>Je vais y installer Incus, un fork de LXD qui va me servir de base pour la formation d’un cluster Kubernetes avec plusieurs containers :</p><p><a href="https://linuxcontainers.org/incus/">Linux Containers - Incus - Introduction</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/524/0*brmP2ztMGlQFlgZP.jpg" /></figure><p>Comme pour LXD, je vais procéder à la création de plusieurs profiles. Mais dans un premier temps, installation d’Incus sur l’instance :</p><pre>root@k0s-incus:~# curl -fsSL https://pkgs.zabbly.com/key.asc | gpg --show-keys --fingerprint<br>gpg: directory &#39;/root/.gnupg&#39; created<br>gpg: keybox &#39;/root/.gnupg/pubring.kbx&#39; created<br>pub   rsa3072 2023-08-23 [SC] [expires: 2025-08-22]<br>      4EFC 5906 96CB 15B8 7C73  A3AD 82CC 8797 C838 DCFD<br>uid                      Zabbly Kernel Builds &lt;info@zabbly.com&gt;<br>sub   rsa3072 2023-08-23 [E] [expires: 2025-08-22]<br><br>root@k0s-incus:~# mkdir -p /etc/apt/keyrings/<br><br>root@k0s-incus:~# curl -fsSL https://pkgs.zabbly.com/key.asc -o /etc/apt/keyrings/zabbly.asc<br><br>root@k0s-incus:~# sh -c &#39;cat &lt;&lt;EOF &gt; /etc/apt/sources.list.d/zabbly-incus-stable.sources<br>Enabled: yes<br>Types: deb<br>URIs: https://pkgs.zabbly.com/incus/stable<br>Suites: $(. /etc/os-release &amp;&amp; echo ${VERSION_CODENAME})<br>Components: main<br>Architectures: $(dpkg --print-architecture)<br>Signed-By: /etc/apt/keyrings/zabbly.asc<br><br>EOF&#39;</pre><pre>root@k0s-incus:~# apt-get update<br><br>Hit:1 http://security.ubuntu.com/ubuntu noble-security InRelease<br>Hit:2 http://mirrors.digitalocean.com/ubuntu noble InRelease<br>Hit:3 https://repos-droplet.digitalocean.com/apt/droplet-agent main InRelease<br>Hit:4 http://mirrors.digitalocean.com/ubuntu noble-updates InRelease<br>Hit:5 http://mirrors.digitalocean.com/ubuntu noble-backports InRelease<br>Get:6 https://pkgs.zabbly.com/incus/stable noble InRelease [7358 B]   <br>Get:7 https://pkgs.zabbly.com/incus/stable noble/main amd64 Packages [3542 B]<br>Fetched 10.9 kB in 1s (13.3 kB/s)   <br>Reading package lists... Done</pre><pre>root@k0s-incus:~# apt-get install incus incus-client incus-ui-canonical -y<br>Reading package lists... Done<br>Building dependency tree... Done<br>Reading state information... Done<br>The following additional packages will be installed:<br>  attr dconf-gsettings-backend dconf-service dns-root-data dnsmasq-base fontconfig genisoimage glib-networking glib-networking-common glib-networking-services gsettings-desktop-schemas<br>  gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-x incus-base iw libaa1 libasyncns0 libavc1394-0 libboost-iostreams1.83.0 libboost-thread1.83.0 libbtrfs0t64 libcaca0<br>  libcairo-gobject2 libcairo2 libcdparanoia0 libdatrie1 libdaxctl1 libdconf1 libdv4t64 libflac12t64 libgdk-pixbuf-2.0-0 libgdk-pixbuf2.0-bin libgdk-pixbuf2.0-common libgraphite2-3<br>  libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libharfbuzz0b libiec61883-0 libmp3lame0 libmpg123-0t64 libndctl6 libnet1 libogg0 libopus0 liborc-0.4-0t64 libpango-1.0-0<br>  libpangocairo-1.0-0 libpangoft2-1.0-0 libpixman-1-0 libpmem1 libpmemobj1 libproxy1v5 libpulse0 librados2 libraw1394-11 librbd1 librdmacm1t64 libshout3 libsndfile1 libsoup-3.0-0<br>  libsoup-3.0-common libspeex1 libspice-server1 libtag1v5 libtag1v5-vanilla libthai-data libthai0 libtheora0 libtwolame0 libusbredirparser1t64 libv4l-0t64 libv4lconvert0t64 libvisual-0.4-0<br>  libvorbis0a libvorbisenc2 libvpx9 libwavpack1 libx11-xcb1 libxcb-render0 libxcb-shm0 libxdamage1 libxfixes3 libxi6 libxrender1 libxtst6 libxv1 session-migration sshfs wireless-regdb<br>  x11-common xdelta3</pre><pre>root@k0s-incus:~# incus<br>Description:<br>  Command line client for Incus<br><br>  All of Incus&#39;s features can be driven through the various commands below.<br>  For help with any of those, simply call them with --help.<br><br>  Custom commands can be defined through aliases, use &quot;incus alias&quot; to control those.<br><br>Usage:<br>  incus [command]<br><br>Available Commands:<br>  admin       Manage incus daemon<br>  cluster     Manage cluster members<br>  config      Manage instance and server configuration options<br>  console     Attach to instance consoles<br>  copy        Copy instances within or in between servers<br>  create      Create instances from images<br>  delete      Delete instances<br>  exec        Execute commands in instances<br>  export      Export instance backups<br>  file        Manage files in instances<br>  help        Help about any command<br>  image       Manage images<br>  import      Import instance backups<br>  info        Show instance or server information<br>  launch      Create and start instances from images<br>  list        List instances<br>  move        Move instances within or in between servers<br>  network     Manage and attach instances to networks<br>  pause       Pause instances<br>  profile     Manage profiles<br>  project     Manage projects<br>  publish     Publish instances as images<br>  rebuild     Rebuild instances<br>  remote      Manage the list of remote servers<br>  rename      Rename instances<br>  restart     Restart instances<br>  resume      Resume instances<br>  snapshot    Manage instance snapshots<br>  start       Start instances<br>  stop        Stop instances<br>  storage     Manage storage pools and volumes<br>  top         Display resource usage info per instance<br>  version     Show local and remote versions<br>  webui       Open the web interface<br><br>Flags:<br>      --all            Show less common commands<br>      --debug          Show all debug messages<br>      --force-local    Force using the local unix socket<br>  -h, --help           Print help<br>      --project        Override the source project<br>  -q, --quiet          Don&#39;t show progress information<br>      --sub-commands   Use with help or --help to view sub-commands<br>  -v, --verbose        Show all information messages<br>      --version        Print version number<br><br>Use &quot;incus [command] --help&quot; for more information about a command.</pre><p>Initialisation d’Incus en version minimaliste :</p><pre>root@k0s-incus:~# incus admin init<br>Would you like to use clustering? (yes/no) [default=no]: <br>Do you want to configure a new storage pool? (yes/no) [default=yes]: <br>Name of the new storage pool [default=default]: <br>Name of the storage backend to use (btrfs, dir, lvm) [default=btrfs]: dir<br>Where should this storage pool store its data? [default=/var/lib/incus/storage-pools/default]: <br>Would you like to create a new local network bridge? (yes/no) [default=yes]: <br>What should the new bridge be called? [default=incusbr0]: <br>What IPv4 address should be used? (CIDR subnet notation, “auto” or “none”) [default=auto]: <br>What IPv6 address should be used? (CIDR subnet notation, “auto” or “none”) [default=auto]: <br>Would you like the server to be available over the network? (yes/no) [default=no]:    <br>Would you like stale cached images to be updated automatically? (yes/no) [default=yes]: <br>Would you like a YAML &quot;init&quot; preseed to be printed? (yes/no) [default=no]: <br><br>root@k0s-incus:~# incus list<br>+------+-------+------+------+------+-----------+<br>| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |<br>+------+-------+------+------+------+-----------+<br><br>root@k0s-incus:~# incus profile list<br>+---------+-----------------------+---------+<br>|  NAME   |      DESCRIPTION      | USED BY |<br>+---------+-----------------------+---------+<br>| default | Default Incus profile | 0       |<br>+---------+-----------------------+---------+<br><br>root@k0s-incus:~# incus profile show default<br>config: {}<br>description: Default Incus profile<br>devices:<br>  eth0:<br>    name: eth0<br>    network: incusbr0<br>    type: nic<br>  root:<br>    path: /<br>    pool: default<br>    type: disk<br>name: default<br>used_by: []<br>project: default<br><br>root@k0s-incus:~# incus profile create k8s</pre><p>Incus dispose d’un tableau de bord de contrôle qui peut être actionné temporairement par incus webui.</p><p><a href="https://linuxcontainers.org/incus/docs/main/reference/manpages/incus/webui/">incus webui</a></p><p>Activation de ce dernier :</p><pre>root@k0s-incus:~# nohup incus webui &amp;<br>[1] 4104<br>root@k0s-incus:~# nohup: ignoring input and appending output to &#39;nohup.out&#39;<br><br>root@k0s-incus:~# cat nohup.out <br>Web server running at: http://127.0.0.1:34363/ui?auth_token=3c5f5d4b-f9ed-4bf9-a174-d5ea2366cfbf<br><br></pre><p>Utilisation de <strong>pinggy.io</strong> pour y accéder :</p><p><a href="https://pinggy.io/">Pinggy - Simple Localhost Tunnels</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xwPRqOfTGupcieNHf8emEQ.png" /></figure><pre>root@k0s-incus:~# ssh -p 443 -R0:127.0.0.1:34363 a.pinggy.io<br></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J4VDtZUCZq95uKLwcfCR4w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ETQjT9QQsn9XI0lGq0c5kA.png" /></figure><p>Je récupère le même profile qu’utilise LXD pour MicroK8s :</p><p><a href="https://microk8s.io/docs/install-lxd">MicroK8s - MicroK8s in LXD | MicroK8s</a></p><pre>roothttps://microk8s.io/docs/install-lxd@k0s-incus:~# wget https://raw.githubusercontent.com/ubuntu/microk8s/master/tests/lxc/microk8s.profile -O k8s.profile<br>--2025-01-14 20:58:42--  https://raw.githubusercontent.com/ubuntu/microk8s/master/tests/lxc/microk8s.profile<br>Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.108.133, 185.199.110.133, 185.199.109.133, ...<br>Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.108.133|:443... connected.<br>HTTP request sent, awaiting response... 200 OK<br>Length: 816 [text/plain]<br>Saving to: ‘k8s.profile’<br><br>k8s.profile                                     100%[=====================================================================================================&gt;]     816  --.-KB/s    in 0s      <br><br>2025-01-14 20:58:42 (33.4 MB/s) - ‘k8s.profile’ saved [816/816]<br><br>root@k0s-incus:~# cat k8s.profile | incus profile edit k8s<br>root@k0s-incus:~# rm k8s.profile</pre><pre>root@k0s-incus:~# incus profile show k8s<br>config:<br>  boot.autostart: &quot;true&quot;<br>  linux.kernel_modules: ip_vs,ip_vs_rr,ip_vs_wrr,ip_vs_sh,ip_tables,ip6_tables,netlink_diag,nf_nat,overlay,br_netfilter<br>  raw.lxc: |<br>    lxc.apparmor.profile=unconfined<br>    lxc.mount.auto=proc:rw sys:rw cgroup:rw<br>    lxc.cgroup.devices.allow=a<br>    lxc.cap.drop=<br>  security.nesting: &quot;true&quot;<br>  security.privileged: &quot;true&quot;<br>description: &quot;&quot;<br>devices:<br>  aadisable:<br>    path: /sys/module/nf_conntrack/parameters/hashsize<br>    source: /sys/module/nf_conntrack/parameters/hashsize<br>    type: disk<br>  aadisable2:<br>    path: /dev/kmsg<br>    source: /dev/kmsg<br>    type: unix-char<br>  aadisable3:<br>    path: /sys/fs/bpf<br>    source: /sys/fs/bpf<br>    type: disk<br>  aadisable4:<br>    path: /proc/sys/net/netfilter/nf_conntrack_max<br>    source: /proc/sys/net/netfilter/nf_conntrack_max<br>    type: disk<br>name: k8s<br>used_by: []<br>project: default</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HZxlCo3Khla7sUsQuU89_g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6FFl2wumZy1MjCxY69A5eg.png" /></figure><p>Comme Incus a la faculté d’utiliser cloud-init, je crée un nouveau profile destiné à cet usage :</p><pre>root@k0s-incus:~# incus profile show cloud<br>config:<br>  cloud-init.user-data: |<br>    #cloud-config<br>    package_update: true<br>    package_upgrade: true<br>    package_reboot_if_required: true<br>    packages:<br>      - vim<br>      - wget<br>      - git<br>      - curl<br>      - htop<br>      - openssh-server<br>    bootcmd:<br>      - systemctl enable ssh<br>      - systemctl start ssh<br>    ssh_authorized_keys:<br>      - ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQCpbsaaVUMa2TM9q8VkeBmbKvJpbreXTcqI5F5N3riGsoZ7Z/IIN7eR6J47UP2bj3IBTdgHmij1uOexm60QBO2PY4abIhsN+xnVS4a0LSyI8v6nYECWbEehL/gFn6uDmSLA4m0hZCF5BSpLxQYzKS28dHIdXsLC4CDd67nAXIhOiVpM0q/AUCuSy+mA0VwFa/JAkFCk8TpQBorgwJIq635imrgxYIpEUA2wHXOhw23mO3zTUlay13LSlA2a1xyTkP8hSDWdRYVxr2DEB/MtmTX2BdWlA5rDRmzXE7R2/csE245WAxG+XfSu4zNqhHzm8Df3zmZn3/UyKLcx4eJF//mVZyrM7RQHRteA/im8I4IavrReGyCUKY+OsSfygYVFyO87rYQ+IOauOnB4LxBohBjSBN3Skk4X7krYFIi8D9R1lmL+VvBfpvy0YMurOahY1VJFzD0dUeK2bDUdeWzfFkcX039d9/RRXRxieNpxwp1BLPi5/DXG8FihzgwVTf6h60J9/fkYzY+BO8CKG2kYTUsy1ykuXLzLY5sTCREiEoEKcJ9IGz8OimZ1AmkgJJCrQnI6mT/KiNDU6YCc75ONKTKX5HKVPhZWT255Aw4f5LBbBrj06cJX3GuunV0I30+BYyHwLbPBoqgd4GUk3YJlr8wS3qre/YUSc2iKNDTOzFCC8Q== root@k0s-incus<br>description: incus with cloud-init<br>devices: {}<br>name: cloud<br>used_by: []<br>project: default</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JuKSFnSV_VR5t4Jsn2lJJA.png" /></figure><p>Je suis prêt pour la création de trois containers qui me serviront de pivot à la création d’un cluster Kubernetes :</p><pre>root@k0s-incus:~# for i in {1..3}; do incus launch -p default -p k8s -p cloud images:ubuntu/24.04/cloud k0s-$i; done<br>Launching k0s-1<br>Launching k0s-2                                    <br>Launching k0s-3<br><br>root@k0s-incus:~# incus list                       <br>+-------+---------+-----------------------+-----------------------------------------------+-----------+-----------+<br>| NAME  |  STATE  |         IPV4          |                     IPV6                      |   TYPE    | SNAPSHOTS |<br>+-------+---------+-----------------------+-----------------------------------------------+-----------+-----------+<br>| k0s-1 | RUNNING | 10.224.160.99 (eth0)  | fd42:4641:b619:c782:216:3eff:fea4:53d3 (eth0) | CONTAINER | 0         |<br>+-------+---------+-----------------------+-----------------------------------------------+-----------+-----------+<br>| k0s-2 | RUNNING | 10.224.160.54 (eth0)  | fd42:4641:b619:c782:216:3eff:feee:7af8 (eth0) | CONTAINER | 0         |<br>+-------+---------+-----------------------+-----------------------------------------------+-----------+-----------+<br>| k0s-3 | RUNNING | 10.224.160.215 (eth0) | fd42:4641:b619:c782:216:3eff:fef3:709b (eth0) | CONTAINER | 0         |<br>+-------+---------+-----------------------+-----------------------------------------------+-----------+-----------+<br><br>root@k0s-incus:~# cat .ssh/config <br>Host *<br>   StrictHostKeyChecking no<br>   UserKnownHostsFile=/dev/null<br>   <br>root@k0s-incus:~# ssh ubuntu@10.224.160.99<br><br>Welcome to Ubuntu 24.04.1 LTS (GNU/Linux 6.8.0-51-generic x86_64)<br><br> * Documentation:  https://help.ubuntu.com<br> * Management:     https://landscape.canonical.com<br> * Support:        https://ubuntu.com/pro<br><br>The programs included with the Ubuntu system are free software;<br>the exact distribution terms for each program are described in the<br>individual files in /usr/share/doc/*/copyright.<br><br>Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by<br>applicable law.<br><br>To run a command as administrator (user &quot;root&quot;), use &quot;sudo &lt;command&gt;&quot;.<br>See &quot;man sudo_root&quot; for details.<br><br>ubuntu@k0s-1:~$</pre><p>Récupération de k0sctl pour la création d’un cluster Kubernetes avec k0s :</p><p><a href="https://docs.k0sproject.io/head/k0sctl-install/">Using k0sctl - Documentation</a></p><pre>root@k0s-incus:~# wget -c https://github.com/k0sproject/k0sctl/releases/download/v0.21.0/k0sctl-linux-amd64 &amp;&amp; chmod +x k0sctl-linux-amd64 &amp;&amp; mv k0sctl-linux-amd64 /usr/local/bin/k0sctl<br><br>Saving to: ‘k0sctl-linux-amd64’<br><br>k0sctl-linux-amd64                              100%[=====================================================================================================&gt;]  18.21M  --.-KB/s    in 0.1s    <br><br>2025-01-14 21:22:23 (122 MB/s) - ‘k0sctl-linux-amd64’ saved [19091608/19091608]<br><br>root@k0s-incus:~# k0sctl <br>NAME:<br>   k0sctl - k0s cluster management tool<br><br>USAGE:<br>   k0sctl [global options] command [command options]<br><br>COMMANDS:<br>   version     Output k0sctl version<br>   apply       Apply a k0sctl configuration<br>   kubeconfig  Output the admin kubeconfig of the cluster<br>   init        Create a configuration template<br>   reset       Remove traces of k0s from all of the hosts<br>   backup      Take backup of existing clusters state<br>   config      Configuration related sub-commands<br>   completion  <br>   help, h     Shows a list of commands or help for one command<br><br>GLOBAL OPTIONS:<br>   --debug, -d  Enable debug logging (default: false) [$DEBUG]<br>   --trace      Enable trace logging (default: false) [$TRACE]<br>   --no-redact  Do not hide sensitive information in the output (default: false)<br>   --help, -h   show help</pre><pre>root@k0s-incus:~# k0sctl init --k0s &gt; k0sctl.yaml</pre><pre>root@k0s-incus:~# cat k0sctl.yaml <br>apiVersion: k0sctl.k0sproject.io/v1beta1<br>kind: Cluster<br>metadata:<br>  name: k0s-cluster<br>  user: admin<br>spec:<br>  hosts:<br>  - ssh:<br>      address: 10.224.160.99 <br>      user: ubuntu<br>      port: 22<br>      keyPath: /root/.ssh/id_rsa<br>    role: controller<br>  - ssh:<br>      address: 10.224.160.54<br>      user: ubuntu<br>      port: 22<br>      keyPath: /root/.ssh/id_rsa<br>    role: worker<br>  - ssh:<br>      address: 10.224.160.215<br>      user: ubuntu<br>      port: 22<br>      keyPath: /root/.ssh/id_rsa<br>    role: worker<br>  k0s:<br>    config:<br>      apiVersion: k0s.k0sproject.io/v1beta1<br>      kind: Cluster<br>      metadata:<br>        name: k0s<br>      spec:<br>        api:<br>          k0sApiPort: 9443<br>          port: 6443<br>        installConfig:<br>          users:<br>            etcdUser: etcd<br>            kineUser: kube-apiserver<br>            konnectivityUser: konnectivity-server<br>            kubeAPIserverUser: kube-apiserver<br>            kubeSchedulerUser: kube-scheduler<br>        konnectivity:<br>          adminPort: 8133<br>          agentPort: 8132<br>        network:<br>          kubeProxy:<br>            disabled: false<br>            mode: iptables<br>          kuberouter:<br>            autoMTU: true<br>            mtu: 0<br>            peerRouterASNs: &quot;&quot;<br>            peerRouterIPs: &quot;&quot;<br>          podCIDR: 10.244.0.0/16<br>          provider: kuberouter<br>          serviceCIDR: 10.96.0.0/12<br>        podSecurityPolicy:<br>          defaultPolicy: 00-k0s-privileged<br>        storage:<br>          type: etcd<br>        telemetry:<br>          enabled: true </pre><p>Lancement de la création :</p><pre>                                                      <br>root@k0s-incus:~# k0sctl apply --config k0sctl.yaml <br><br>⠀⣿⣿⡇⠀⠀⢀⣴⣾⣿⠟⠁⢸⣿⣿⣿⣿⣿⣿⣿⡿⠛⠁⠀⢸⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠀█████████ █████████ ███<br>⠀⣿⣿⡇⣠⣶⣿⡿⠋⠀⠀⠀⢸⣿⡇⠀⠀⠀⣠⠀⠀⢀⣠⡆⢸⣿⣿⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀███          ███    ███<br>⠀⣿⣿⣿⣿⣟⠋⠀⠀⠀⠀⠀⢸⣿⡇⠀⢰⣾⣿⠀⠀⣿⣿⡇⢸⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠀███          ███    ███<br>⠀⣿⣿⡏⠻⣿⣷⣤⡀⠀⠀⠀⠸⠛⠁⠀⠸⠋⠁⠀⠀⣿⣿⡇⠈⠉⠉⠉⠉⠉⠉⠉⠉⢹⣿⣿⠀███          ███    ███<br>⠀⣿⣿⡇⠀⠀⠙⢿⣿⣦⣀⠀⠀⠀⣠⣶⣶⣶⣶⣶⣶⣿⣿⡇⢰⣶⣶⣶⣶⣶⣶⣶⣶⣾⣿⣿⠀█████████    ███    ██████████<br>k0sctl v0.21.0 Copyright 2023, k0sctl authors.<br>By continuing to use k0sctl you agree to these terms:<br>https://k0sproject.io/licenses/eula<br>INFO ==&gt; Running phase: Set k0s version  <br>INFO Looking up latest stable k0s version         <br>INFO Using k0s version v1.31.3+k0s.0              <br>INFO ==&gt; Running phase: Connect to hosts <br>INFO [ssh] 10.224.160.215:22: connected           <br>INFO [ssh] 10.224.160.99:22: connected            <br>INFO [ssh] 10.224.160.54:22: connected            <br>INFO ==&gt; Running phase: Detect host operating systems <br>INFO [ssh] 10.224.160.215:22: is running Ubuntu 24.04.1 LTS <br>INFO [ssh] 10.224.160.99:22: is running Ubuntu 24.04.1 LTS <br>INFO [ssh] 10.224.160.54:22: is running Ubuntu 24.04.1 LTS <br>INFO ==&gt; Running phase: Acquire exclusive host lock <br>INFO ==&gt; Running phase: Prepare hosts    <br>INFO ==&gt; Running phase: Gather host facts <br>INFO [ssh] 10.224.160.215:22: using k0s-3 as hostname <br>INFO [ssh] 10.224.160.54:22: using k0s-2 as hostname <br>INFO [ssh] 10.224.160.99:22: using k0s-1 as hostname <br>INFO [ssh] 10.224.160.215:22: discovered eth0 as private interface <br>INFO [ssh] 10.224.160.54:22: discovered eth0 as private interface <br>INFO [ssh] 10.224.160.99:22: discovered eth0 as private interface <br>INFO ==&gt; Running phase: Validate hosts   <br>INFO ==&gt; Running phase: Validate facts   <br>INFO ==&gt; Running phase: Download k0s on hosts <br>INFO [ssh] 10.224.160.215:22: downloading k0s v1.31.3+k0s.0 <br>INFO [ssh] 10.224.160.54:22: downloading k0s v1.31.3+k0s.0 <br>INFO [ssh] 10.224.160.99:22: downloading k0s v1.31.3+k0s.0 <br>INFO ==&gt; Running phase: Install k0s binaries on hosts <br>INFO [ssh] 10.224.160.99:22: validating configuration <br>INFO ==&gt; Running phase: Configure k0s    <br>INFO [ssh] 10.224.160.99:22: installing new configuration <br>INFO ==&gt; Running phase: Initialize the k0s cluster <br>INFO [ssh] 10.224.160.99:22: installing k0s controller <br>INFO [ssh] 10.224.160.99:22: waiting for the k0s service to start <br>INFO [ssh] 10.224.160.99:22: wait for kubernetes to reach ready state <br>INFO ==&gt; Running phase: Install workers  <br>INFO [ssh] 10.224.160.99:22: generating a join token for worker 1 <br>INFO [ssh] 10.224.160.99:22: generating a join token for worker 2 <br>INFO [ssh] 10.224.160.215:22: validating api connection to https://10.224.160.99:6443 using join token <br>INFO [ssh] 10.224.160.54:22: validating api connection to https://10.224.160.99:6443 using join token <br>INFO [ssh] 10.224.160.215:22: writing join token to /etc/k0s/k0stoken <br>INFO [ssh] 10.224.160.54:22: writing join token to /etc/k0s/k0stoken <br>INFO [ssh] 10.224.160.54:22: installing k0s worker <br>INFO [ssh] 10.224.160.215:22: installing k0s worker <br>INFO [ssh] 10.224.160.215:22: starting service    <br>INFO [ssh] 10.224.160.215:22: waiting for node to become ready <br>INFO [ssh] 10.224.160.54:22: starting service     <br>INFO [ssh] 10.224.160.54:22: waiting for node to become ready <br>INFO ==&gt; Running phase: Release exclusive host lock <br>INFO ==&gt; Running phase: Disconnect from hosts <br>INFO ==&gt; Finished in 42s                 <br>INFO k0s cluster version v1.31.3+k0s.0 is now installed <br>INFO Tip: To access the cluster you can now fetch the admin kubeconfig using: <br>INFO      k0sctl kubeconfig</pre><p>Le cluster est actif :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yDw7ARCCjOPPLe8NDBvOkw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*toITqmXZlgBgRsUjCAaOlA.png" /></figure><pre>root@k0s-incus:~# curl -LO https://dl.k8s.io/release/v1.31.3/bin/linux/amd64/kubectl &amp;&amp; chmod +x kubectl &amp;&amp; mv kubectl /usr/local/bin/<br>  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current<br>                                 Dload  Upload   Total   Spent    Left  Speed<br>100   138  100   138    0     0    923      0 --:--:-- --:--:-- --:--:--   926<br>100 53.7M  100 53.7M    0     0   476k      0  0:01:55  0:01:55 --:--:-- 1023k<br><br>root@k0s-incus:~# mkdir .kube<br>root@k0s-incus:~# k0sctl kubeconfig --config k0sctl.yaml &gt; .kube/config</pre><pre>root@k0s-incus:~# kubectl cluster-info<br>Kubernetes control plane is running at https://10.224.160.99:6443<br>CoreDNS is running at https://10.224.160.99:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy<br><br>To further debug and diagnose cluster problems, use &#39;kubectl cluster-info dump&#39;.<br><br>root@k0s-incus:~# kubectl get nodes -o wide<br>NAME    STATUS   ROLES    AGE    VERSION       INTERNAL-IP      EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION     CONTAINER-RUNTIME<br>k0s-2   Ready    &lt;none&gt;   5m1s   v1.31.3+k0s   10.224.160.54    &lt;none&gt;        Ubuntu 24.04.1 LTS   6.8.0-51-generic   containerd://1.7.24<br>k0s-3   Ready    &lt;none&gt;   5m1s   v1.31.3+k0s   10.224.160.215   &lt;none&gt;        Ubuntu 24.04.1 LTS   6.8.0-51-generic   containerd://1.7.24<br><br>root@k0s-incus:~# kubectl get po,svc -A<br>NAMESPACE     NAME                                  READY   STATUS    RESTARTS   AGE<br>kube-system   pod/coredns-645c5d6f5b-kgnsf          1/1     Running   0          5m2s<br>kube-system   pod/coredns-645c5d6f5b-n2rbk          1/1     Running   0          5m2s<br>kube-system   pod/konnectivity-agent-2dg8l          1/1     Running   0          5m4s<br>kube-system   pod/konnectivity-agent-5l5dl          1/1     Running   0          5m4s<br>kube-system   pod/kube-proxy-cx47n                  1/1     Running   0          5m7s<br>kube-system   pod/kube-proxy-sp5fd                  1/1     Running   0          5m7s<br>kube-system   pod/kube-router-6l4qv                 1/1     Running   0          5m7s<br>kube-system   pod/kube-router-b9t89                 1/1     Running   0          5m7s<br>kube-system   pod/metrics-server-78c4ccbc7f-jxpzz   1/1     Running   0          5m1s<br><br>NAMESPACE     NAME                     TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)                  AGE<br>default       service/kubernetes       ClusterIP   10.96.0.1      &lt;none&gt;        443/TCP                  5m17s<br>kube-system   service/kube-dns         ClusterIP   10.96.0.10     &lt;none&gt;        53/UDP,53/TCP,9153/TCP   5m7s<br>kube-system   service/metrics-server   ClusterIP   10.109.44.51   &lt;none&gt;        443/TCP                  5m1s</pre><p>Il est alors possible de procéder à l’installation d’HolmesGPT via Pipx :</p><p><a href="https://github.com/robusta-dev/holmesgpt?tab=readme-ov-file#installation">GitHub - robusta-dev/holmesgpt: On-Call Assistant for Prometheus Alerts - Get a head start on fixing alerts with AI investigation</a></p><pre>root@k0s-incus:~# apt install pipx -y<br><br>root@k0s-incus:~# pipx ensurepath<br><br>Success! Added /root/.local/bin to the PATH environment variable.<br><br>Consider adding shell completions for pipx. Run &#39;pipx completions&#39; for instructions.<br><br>You will need to open a new terminal or re-login for the PATH changes to take effect.<br><br>Otherwise pipx is ready to go! ✨ 🌟 ✨<br><br>root@k0s-incus:~# pipx install &quot;https://github.com/robusta-dev/holmesgpt/archive/refs/heads/master.zip&quot;<br>  installed package holmesgpt 0.1.0, installed using Python 3.12.3<br>  These apps are now globally available<br>    - holmes<br>done! ✨ 🌟 ✨<br>root@k0s-incus:~# holmes version<br>/root/.local/share/pipx/venvs/holmesgpt/lib/python3.12/site-packages/pydantic/_internal/_config.py:345: UserWarning: Valid config keys have changed in V2:<br>* &#39;fields&#39; has been removed<br>  warnings.warn(message, UserWarning)<br>HEAD -&gt; master-bfafbde3</pre><p>Pour l’accompagner, je récupère K9s qui fournit une interface utilisateur de terminal pour interagir avec vos clusters Kubernetes. L’objectif de ce projet est de faciliter la navigation, l’observation et la gestion de vos applications dans la nature. K9s surveille continuellement Kubernetes pour les changements et offre des commandes ultérieures pour interagir avec vos ressources observées.</p><p><a href="https://github.com/derailed/k9s">GitHub - derailed/k9s: 🐶 Kubernetes CLI To Manage Your Clusters In Style!</a></p><pre>root@k0s-incus:~# wget -c https://github.com/derailed/k9s/releases/download/v0.32.7/k9s_linux_amd64.deb<br>HTTP request sent, awaiting response... 200 OK<br>Length: 31832132 (30M) [application/octet-stream]<br>Saving to: ‘k9s_linux_amd64.deb’<br><br>k9s_linux_amd64.deb                             100%[=====================================================================================================&gt;]  30.36M  --.-KB/s    in 0.1s    <br><br>2025-01-14 21:40:07 (291 MB/s) - ‘k9s_linux_amd64.deb’ saved [31832132/31832132]<br><br>root@k0s-incus:~# apt install -f ./k9s_linux_amd64.deb <br>root@k0s-incus:~# k9s --help<br>K9s is a CLI to view and manage your Kubernetes clusters.<br><br>Usage:<br>  k9s [flags]<br>  k9s [command]<br><br>Available Commands:<br>  completion  Generate the autocompletion script for the specified shell<br>  help        Help about any command<br>  info        List K9s configurations info<br>  version     Print version/build info<br><br>Flags:<br>  -A, --all-namespaces                 Launch K9s in all namespaces<br>      --as string                      Username to impersonate for the operation<br>      --as-group stringArray           Group to impersonate for the operation<br>      --certificate-authority string   Path to a cert file for the certificate authority<br>      --client-certificate string      Path to a client certificate file for TLS<br>      --client-key string              Path to a client key file for TLS<br>      --cluster string                 The name of the kubeconfig cluster to use<br>  -c, --command string                 Overrides the default resource to load when the application launches<br>      --context string                 The name of the kubeconfig context to use<br>      --crumbsless                     Turn K9s crumbs off<br>      --headless                       Turn K9s header off<br>  -h, --help                           help for k9s<br>      --insecure-skip-tls-verify       If true, the server&#39;s caCertFile will not be checked for validity<br>      --kubeconfig string              Path to the kubeconfig file to use for CLI requests<br>      --logFile string                 Specify the log file (default &quot;/root/.local/state/k9s/k9s.log&quot;)<br>  -l, --logLevel string                Specify a log level (error, warn, info, debug, trace) (default &quot;info&quot;)<br>      --logoless                       Turn K9s logo off<br>  -n, --namespace string               If present, the namespace scope for this CLI request<br>      --readonly                       Sets readOnly mode by overriding readOnly configuration setting<br>  -r, --refresh int                    Specify the default refresh rate as an integer (sec) (default 2)<br>      --request-timeout string         The length of time to wait before giving up on a single server request<br>      --screen-dump-dir string         Sets a path to a dir for a screen dumps<br>      --token string                   Bearer token for authentication to the API server<br>      --user string                    The name of the kubeconfig user to use<br>      --write                          Sets write mode by overriding the readOnly configuration setting<br><br>Use &quot;k9s [command] --help&quot; for more information about a command.</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Nxor0qNSlA_tKTaYN8I8Q.png" /></figure><p>Ollama, une alternative à ChatGPT, peut être déployée pour fournir des capacités de traitement du langage naturel directement dans votre environnement. Cela permet de bénéficier des capacités de traitement du langage naturel de Ollama sans dépendre de services cloud externes.</p><p><a href="https://ollama.com/">Ollama · Run AI models locally and in the cloud</a></p><blockquote>En intégrant Ollama à vos outils de dépannage, vous pouvez générer des réponses et des solutions basées sur l’analyse des logs et des données de votre cluster Kubernetes.</blockquote><p>Pour son exécution, je suis amené à utiliser RunPod, une plateforme qui permet d’exécuter des tâches de traitement du langage naturel et d’autres tâches IA. RunPod vous permet en effet de créer des environnements de pod personnalisés pour exécuter des modèles de langage comme Ollama ou d’autres applications IA :</p><p><a href="https://www.runpod.io/">RunPod - The Cloud Built for AI</a></p><p>Création d’un Pod GPU qui me permet donc d’utiliser Ollama …</p><p><a href="https://docs.runpod.io/tutorials/pods/run-ollama">Set up Ollama on your GPU Pod | RunPod Documentation</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vvuQq2ijzUQ2-fjdmaRZgw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N-2voUHnWHe1j2N4dEIe3w.png" /></figure><p>Je peux m’y connecter via SSH :</p><pre>Welcome to Ubuntu 22.04.3 LTS (GNU/Linux 6.5.0-44-generic x86_64)<br><br> * Documentation:  https://help.ubuntu.com<br> * Management:     https://landscape.canonical.com<br> * Support:        https://ubuntu.com/advantage<br><br>This system has been minimized by removing packages and content that are<br>not required on a system that users do not log into.<br><br>To restore this content, you can run the &#39;unminimize&#39; command.<br><br>The programs included with the Ubuntu system are free software;<br>the exact distribution terms for each program are described in the<br>individual files in /usr/share/doc/*/copyright.<br><br>Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by<br>applicable law.<br><br> ______                 ______            _<br>(_____ \               (_____ \          | |<br> _____) ) _   _  ____   _____) )___    __| |<br>|  __  / | | | ||  _ \ |  ____// _ \  / _  |<br>| |  \ \ | |_| || | | || |    | |_| |( (_| |<br>|_|   |_||____/ |_| |_||_|     \___/  \____|<br><br>For detailed documentation and guides, please visit:<br>https://docs.runpod.io/ and https://blog.runpod.io/<br><br><br>root@5ed8df208cf4:~# nvidia-smi<br>Tue Jan 14 22:03:15 2025       <br>+-----------------------------------------------------------------------------------------+<br>| NVIDIA-SMI 550.90.07              Driver Version: 550.90.07      CUDA Version: 12.4     |<br>|-----------------------------------------+------------------------+----------------------+<br>| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |<br>| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |<br>|                                         |                        |               MIG M. |<br>|=========================================+========================+======================|<br>|   0  NVIDIA GeForce RTX 4070 Ti     On  |   00000000:81:00.0 Off |                  N/A |<br>|  0%   28C    P8             11W /  285W |       2MiB /  12282MiB |      0%      Default |<br>|                                         |                        |                  N/A |<br>+-----------------------------------------+------------------------+----------------------+<br>                                                                                         <br>+-----------------------------------------------------------------------------------------+<br>| Processes:                                                                              |<br>|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |<br>|        ID   ID                                                               Usage      |<br>|=========================================================================================|<br>|  No running processes found                                                             |<br>+-----------------------------------------------------------------------------------------+</pre><p>Exécution d’Ollama :</p><pre>root@5ed8df208cf4:~# apt update 2&gt; /dev/null &amp;&amp; apt install -qq lshw -y 2&gt; /dev/null<br><br>root@5ed8df208cf4:~# export OLLAMA_HOST=0.0.0.0:11434<br>root@5ed8df208cf4:~# (curl -fsSL https://ollama.com/install.sh | sh &amp;&amp; ollama serve &gt; ollama.log 2&gt;&amp;1) &amp;<br>[1] 950<br>root@5ed8df208cf4:~# &gt;&gt;&gt; Installing ollama to /usr/local<br>&gt;&gt;&gt; Downloading Linux amd64 bundle<br>######################################################################## 100.0%<br>&gt;&gt;&gt; Creating ollama user...<br>&gt;&gt;&gt; Adding ollama user to video group...<br>&gt;&gt;&gt; Adding current user to ollama group...<br>&gt;&gt;&gt; Creating ollama systemd service...<br>WARNING: systemd is not running<br>&gt;&gt;&gt; NVIDIA GPU installed.<br>&gt;&gt;&gt; The Ollama API is now available at 127.0.0.1:11434.<br>&gt;&gt;&gt; Install complete. Run &quot;ollama&quot; from the command line.<br><br>root@5ed8df208cf4:~# netstat -tunlp<br>Active Internet connections (only servers)<br>Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    <br>tcp        0      0 0.0.0.0:7861            0.0.0.0:*               LISTEN      52/nginx: master pr <br>tcp        0      0 0.0.0.0:8081            0.0.0.0:*               LISTEN      52/nginx: master pr <br>tcp        0      0 0.0.0.0:8001            0.0.0.0:*               LISTEN      52/nginx: master pr <br>tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      70/sshd: /usr/sbin/ <br>tcp        0      0 0.0.0.0:3001            0.0.0.0:*               LISTEN      52/nginx: master pr <br>tcp        0      0 0.0.0.0:9091            0.0.0.0:*               LISTEN      52/nginx: master pr <br>tcp        0      0 127.0.0.11:39145        0.0.0.0:*               LISTEN      -                   <br>tcp6       0      0 :::22                   :::*                    LISTEN      70/sshd: /usr/sbin/ <br>tcp6       0      0 :::11434                :::*                    LISTEN      1006/ollama         <br>udp        0      0 127.0.0.11:33663        0.0.0.0:*                           -</pre><p>Récupération d’un LLM avec Llama3.2 :</p><ul><li><a href="https://ollama.com/library/llama3.2">llama3.2</a></li><li><a href="https://ai.meta.com/blog/llama-3-2-connect-2024-vision-edge-mobile-devices/">Llama 3.2: Revolutionizing edge AI and vision with open, customizable models</a></li></ul><pre>root@5ed8df208cf4:~# ollama pull llama3.2:3b-instruct-q4_K_S<br>pulling manifest <br>pulling d5e517daeee4... 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 1.9 GB                         <br>pulling 966de95ca8a6... 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 1.4 KB                         <br>pulling fcc5a6bec9da... 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 7.7 KB                         <br>pulling a70ff7e570d9... 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 6.0 KB                         <br>pulling 56bb8bd477a5... 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏   96 B                         <br>pulling 9c65e8607c0c... 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  561 B                         <br>verifying sha256 digest <br>writing manifest <br>success <br><br>root@5ed8df208cf4:~# ollama list       <br>NAME                           ID              SIZE      MODIFIED       <br>llama3.2:3b-instruct-q4_K_S    80f2089878c9    1.9 GB    31 seconds ago</pre><p>L’endpoint d’Ollama est disponible publiquement via le proxy offert par RunPod :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*arLF1LeAM5IApSRSQ5xZUw.png" /></figure><p>Modification de K9s pour y intégrer cet endpoint et HolmesGPT sous forme d’un plug-in :</p><pre>root@k0s-incus:~# cat ~/.config/k9s/plugins.yaml<br>plugins:<br>  holmesgpt:<br>    shortCut: Shift-H<br>    description: Ask HolmesGPT<br>    scopes:<br>      - all<br>    command: bash<br>    background: false<br>    confirm: false<br>    args:<br>      - -c<br>      - |<br>        holmes ask &quot;why is $NAME of $RESOURCE_NAME in -n $NAMESPACE not working as expected&quot; --model=&quot;openai/llama3.2:3b-instruct-q4_K_S&quot;<br>        echo &quot;Press &#39;q&#39; to exit&quot;<br>        while : ; do<br>        read -n 1 k &lt;&amp;1<br>        if [[ $k = q ]] ; then<br>        break<br>        fi<br>        done<br><br>root@k0s-incus:~# export OPENAI_API_BASE=&quot;https://vsr6spvysc6jly-11434.proxy.runpod.net/v1&quot;<br>root@k0s-incus:~# export OPENAI_API_KEY=123</pre><p>Déploiement d’un exemple de Pod problématique dans le cluster Kubernetes via les exemples fournis par Robusta :</p><pre>root@k0s-incus:~# kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/crashpod/broken.yaml<br>deployment.apps/payment-processing-worker created<br><br>root@k0s-incus:~# kubectl get po<br>NAME                                         READY   STATUS             RESTARTS     AGE<br>payment-processing-worker-747ccfb9db-njgmw   0/1     CrashLoopBackOff   1 (4s ago)   9s</pre><p>Je peux lancer la requête relative au plug-in avec HolmesGPT et la combinaison CTRL+H pour obtenir cette première réponse :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-jjVfLa_NaSQ_N1-DOuppQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mgI3TLWhwgTFUla1irZSAg.png" /></figure><pre>The payment-processing-container container has crashed and is being restarted for the 6th time due to a CrashLoopBackOff. The last state indicates that the container was terminated with an  <br>exit code of 0, which suggests that the command executed successfully but did not complete as expected.                                                                                       <br><br>To investigate further, you can check the logs of the payment-processing-container container to see if there are any error messages or clues about what is causing the issue. You can also    <br>check the Kubernetes events for any other errors or warnings that may be related to this issue.                                                                                               <br><br>Additionally, you can try to debug the command executed by the payment-processing-container container to see if it&#39;s correct and working as expected. The command is:                         <br><br>                                                                                                                                                                                              <br> if [[ -z &quot;${DEPLOY_ENV}&quot; ]]; then echo Environment variable DEPLOY_ENV is undefined ; else while true; do echo hello; sleep 10;done; fi<br><br>This command checks if the DEPLOY_ENV environment variable is set, and if it&#39;s not, it prints a message. If it is set, it enters an infinite loop that prints &quot;hello&quot; every 10 seconds.       <br><br>If you&#39;re running this container in a Kubernetes pod, you can try to debug the issue by checking the pod&#39;s logs or using a tool like kubectl to inspect the container&#39;s state and logs.       <br>Press &#39;q&#39; to exit<br><br></pre><p>Modification de la requête et autre réponse :</p><pre>root@k0s-incus:~# cat ~/.config/k9s/plugins.yaml<br>plugins:<br>  holmesgpt:<br>    shortCut: Shift-H<br>    description: Ask HolmesGPT<br>    scopes:<br>      - all<br>    command: bash<br>    background: false<br>    confirm: false<br>    args:<br>      - -c<br>      - |<br>        holmes ask &quot;why is $NAME of $RESOURCE_NAME in -n $NAMESPACE not working and why $NAME is crashed?&quot; --model=&quot;openai/llama3.2:3b-instruct-q4_K_S&quot;<br>        echo &quot;Press &#39;q&#39; to exit&quot;<br>        while : ; do<br>        read -n 1 k &lt;&amp;1<br>        if [[ $k = q ]] ; then<br>        break<br>        fi<br>        done</pre><pre>The payment-processing-container container has crashed and is being restarted for the 6th time due to a CrashLoopBackOff. The last state indicates that the container was terminated with an  <br>exit code of 0, which suggests that the command executed successfully but did not produce any output.                                                                                         <br><br>To investigate further, you can check the logs of the payment-processing-container container to see if there are any error messages or clues about what is causing the crash:                 <br><br>                                                                                                                                                                                              <br> kubectl logs payment-processing-worker-747ccfb9db-njgmw -c payment-processing-container<br><br>Additionally, you can check the configuration of the payment-processing-container container to ensure that it is running with the correct environment variables and settings.                 <br><br>                                                                                                                                                                                              <br> kubectl describe pod payment-processing-worker-747ccfb9db-njgmw -c payment-processing-container<br><br>This will provide more detailed information about the container&#39;s configuration and any errors that may be occurring. </pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/582/0*s_KFhG_IB2F68pD6.jpg" /></figure><p>HolmesGPT peut s’intégrer plus globalement à la plateforme Robusta via une installation dans le cluster Kubernetes et Helm …</p><p><a href="https://docs.robusta.dev/master/configuration/ai-analysis.html#ai-analysis">AI Analysis - Robusta documentation</a></p><p>Pour cela génération du fichier YAML de ce type en configuration :</p><pre>root@k0s-incus:~# cat generated_values.yaml <br>globalConfig:<br>  signing_key: 568927d5-6e65-4c13-b3fe-fdc50e616fde<br>  account_id: a4d7cea6-fba3-4ce6-ba3d-941b55ec83db<br>sinksConfig:<br>  - robusta_sink:<br>      name: robusta_ui_sink<br>      token: &lt;TOKEN&gt;<br>enablePrometheusStack: true<br>kube-prometheus-stack:<br>  grafana:<br>    persistence:<br>      enabled: true<br>enablePlatformPlaybooks: true<br>runner:<br>  sendAdditionalTelemetry: true<br>enableHolmesGPT: true<br>holmes:<br>  additionalEnvVars:<br>    - name: ROBUSTA_AI<br>      value: &quot;true&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4EX7XXSD-dmaq020qN56bw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vmBqq1nHbZaa0utT8glQtg.png" /></figure><p>Utilisation des commandes et du fichier de configuration YAML fournis par la plateforme Robusta :</p><pre>root@k0s-incus:~# helm repo add robusta https://robusta-charts.storage.googleapis.com &amp;&amp; helm repo update<br>&quot;robusta&quot; has been added to your repositories<br>Hang tight while we grab the latest from your chart repositories...<br>...Successfully got an update from the &quot;robusta&quot; chart repository<br>Update Complete. ⎈Happy Helming!⎈<br>root@k0s-incus:~# helm install robusta robusta/robusta -f ./generated_values.yaml --set clusterName=&quot;k0s-cluster&quot; \<br>--set isSmallCluster=true \<br>--set holmes.resources.requests.memory=512Mi \<br>--set kube-prometheus-stack.prometheus.prometheusSpec.retentionSize=9GB \<br>--set kube-prometheus-stack.prometheus.prometheusSpec.storageSpec.volumeClaimTemplate.spec.resources.requests.storage=10Gi \<br>--set kube-prometheus-stack.prometheus.prometheusSpec.resources.requests.memory=512Mi<br>NAME: robusta<br>LAST DEPLOYED: Tue Jan 14 22:59:09 2025<br>NAMESPACE: default<br>STATUS: deployed<br>REVISION: 1<br>NOTES:<br>Thank you for installing Robusta 0.20.0<br><br>As an open source project, we collect general usage statistics.<br>This data is extremely limited and contains only general metadata to help us understand usage patterns.<br>If you are willing to share additional data, please do so! It really help us improve Robusta.<br><br>You can set sendAdditionalTelemetry: true as a Helm value to send exception reports and additional data.<br>This is disabled by default.<br><br>To opt-out of telemetry entirely, set a ENABLE_TELEMETRY=false environment variable on the robusta-runner deployment.<br>Note that if the Robusta UI is enabled, telemetry cannot be disabled even if ENABLE_TELEMETRY=false is set.<br><br>Visit the web UI at: https://platform.robusta.dev/<br><br>root@k0s-incus:~# helm ls -A<br>NAME    NAMESPACE       REVISION        UPDATED                                 STATUS          CHART           APP VERSION<br>robusta default         2               2025-01-14 23:10:13.935906491 +0000 UTC deployed        robusta-0.20.0  0.20.0</pre><pre>root@k0s-incus:~# kubectl get po,svc<br>NAME                                                         READY   STATUS             RESTARTS         AGE<br>pod/alertmanager-robusta-kube-prometheus-st-alertmanager-0   0/2     Pending            0                2m<br>pod/payment-processing-worker-747ccfb9db-njgmw               0/1     CrashLoopBackOff   10 (2m33s ago)   28m<br>pod/prometheus-robusta-kube-prometheus-st-prometheus-0       0/2     Pending            0                2m<br>pod/robusta-forwarder-cd847ccc-wxc6d                         1/1     Running            0                2m5s<br>pod/robusta-grafana-8588b8fb85-fv5vj                         3/3     Running            0                2m5s<br>pod/robusta-holmes-55dd58ff6d-m4zth                          1/1     Running            0                2m5s<br>pod/robusta-kube-prometheus-st-operator-6885c8f675-szncg     1/1     Running            0                2m5s<br>pod/robusta-kube-state-metrics-8667fd9775-s49z4              1/1     Running            0                2m5s<br>pod/robusta-prometheus-node-exporter-c6jvb                   1/1     Running            0                2m5s<br>pod/robusta-prometheus-node-exporter-j6zp5                   1/1     Running            0                2m5s<br>pod/robusta-runner-5d667b7d9c-dm2z7                          1/1     Running            0                2m5s<br><br>NAME                                              TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                      AGE<br>service/alertmanager-operated                     ClusterIP   None             &lt;none&gt;        9093/TCP,9094/TCP,9094/UDP   2m1s<br>service/kubernetes                                ClusterIP   10.96.0.1        &lt;none&gt;        443/TCP                      94m<br>service/prometheus-operated                       ClusterIP   None             &lt;none&gt;        9090/TCP                     2m1s<br>service/robusta-forwarder                         ClusterIP   10.102.7.41      &lt;none&gt;        80/TCP                       2m5s<br>service/robusta-grafana                           ClusterIP   10.106.69.72     &lt;none&gt;        80/TCP                       2m5s<br>service/robusta-holmes                            ClusterIP   10.110.124.241   &lt;none&gt;        80/TCP                       2m5s<br>service/robusta-kube-prometheus-st-alertmanager   ClusterIP   10.105.101.210   &lt;none&gt;        9093/TCP,8080/TCP            2m5s<br>service/robusta-kube-prometheus-st-operator       ClusterIP   10.103.213.208   &lt;none&gt;        443/TCP                      2m5s<br>service/robusta-kube-prometheus-st-prometheus     ClusterIP   10.107.13.104    &lt;none&gt;        9090/TCP,8080/TCP            2m5s<br>service/robusta-kube-state-metrics                ClusterIP   10.103.53.30     &lt;none&gt;        8080/TCP                     2m5s<br>service/robusta-prometheus-node-exporter          ClusterIP   10.102.243.65    &lt;none&gt;        9104/TCP                     2m5s<br>service/robusta-runner                            ClusterIP   10.97.82.15      &lt;none&gt;        80/TCP                       2m5s</pre><p>Je peux procéder à l’installation complête via cette formule :</p><pre>root@k0s-incus:~# helm upgrade robusta robusta/robusta -f ./generated_values.yaml --set clusterName=&quot;k0s-cluster&quot;<br>Release &quot;robusta&quot; has been upgraded. Happy Helming!<br>NAME: robusta<br>LAST DEPLOYED: Tue Jan 14 23:14:02 2025<br>NAMESPACE: default<br>STATUS: deployed<br>REVISION: 5<br>NOTES:<br>Thank you for installing Robusta 0.20.0<br><br>As an open source project, we collect general usage statistics.<br>This data is extremely limited and contains only general metadata to help us understand usage patterns.<br>If you are willing to share additional data, please do so! It really help us improve Robusta.<br><br>You can set sendAdditionalTelemetry: true as a Helm value to send exception reports and additional data.<br>This is disabled by default.<br><br>To opt-out of telemetry entirely, set a ENABLE_TELEMETRY=false environment variable on the robusta-runner deployment.<br>Note that if the Robusta UI is enabled, telemetry cannot be disabled even if ENABLE_TELEMETRY=false is set.<br><br>Visit the web UI at: https://platform.robusta.dev/</pre><p>Le cluster apparaît sur Robusta :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*adLYxxTFb_QZ1vYbsEvGAA.png" /></figure><p>Et là également via HolmesGPT, intterogation de la plateforme sur les éventuelles problématiques rencontrées dans le cluster Kubernetes :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CAGjuo9MP3W5wG5_ewzxlg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QC2xc3W9pABAmjxWAOR_YQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VT0kssD7BseUWtSLs8XS8g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t4iLiaFTdC-ptn_XkC4RUw.png" /></figure><p>Le tout avec une consommation moindre dans le cluster …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*seiGKpBTX4iogmdnWelPBQ.png" /></figure><p>L’utilisation de l’IA pour le dépannage et l’analyse des incidents réduit le temps et l’effort humain nécessaire, permettant aux équipes de se concentrer sur des tâches plus stratégiques.</p><blockquote>Les outils comme HolmesGPT et Ollama peuvent être mis à l’échelle en fonction de la demande, ce qui est particulièrement utile dans les environnements de production où la charge de travail peut varier significativement.</blockquote><p>On peut donc en conclure que l’intégration de l’IA dans les clusters Kubernetes à l’aide d’outils comme HolmesGPT, Ollama et de fournisseur d’instances GPU comme RunPod, offre des avantages significatifs en termes d’efficiacité, de scalabilité et de tolérance aux pannes.</p><blockquote>Ces technologies permettent de rationaliser le cycle de vie des applications, de simplifier le dépannage et d’améliorer la gestion des ressources, rendant ainsi les opérations Kubernetes plus robustes et plus performantes …</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*dF2YNSbOM9r4TOoe.jpg" /></figure><p><strong>À suivre !</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15846adcb2ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implémenter le Retrieval Augmented Generation (RAG) de manière privée sur Kubernetes avec KubeAI et…]]></title>
            <link>https://deep75.medium.com/impl%C3%A9menter-le-retrieval-augmented-generation-rag-de-mani%C3%A8re-priv%C3%A9e-sur-kubernetes-avec-kubeai-et-fd23b1cae930?source=rss-9f1ca3c659fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd23b1cae930</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[Karim]]></dc:creator>
            <pubDate>Mon, 30 Dec 2024 18:01:16 GMT</pubDate>
            <atom:updated>2024-12-30T18:01:16.444Z</atom:updated>
            <content:encoded><![CDATA[<h3>Implémenter le Retrieval Augmented Generation (RAG) de manière privée sur Kubernetes avec KubeAI et Weaviate …</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZzDsLE--BXBtCd11ZS_f5Q.png" /></figure><p>L’utilisation combinée de KubeAI et Weaviate offre une solution puissante pour implémenter le Retrieval Augmented Generation (RAG) de manière privée et évolutive sur Kubernetes. Dans cet article, nous allons explorer comment mettre en place cette architecture pour créer des applications d’IA avancées.</p><blockquote>KubeAI est une plateforme qui permet de déployer des modèles d’IA open source sur Kubernetes, offrant une alternative privée aux services d’IA dans le cloud</blockquote><p><a href="https://www.kubeai.org/">KubeAI</a></p><p>KubeAI utilise une API HTTP compatible avec OpenAI et peut être considéré comme un opérateur de modèlequi gère les serveurs vLLM et Ollama.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/0*E-ZlxH73NTYCQQlR.png" /></figure><p>Pour commencer, il faut déployer KubeAI sur un cluster Kubernetes. Voici les étapes principales : je pars d’une instance Ubuntu 24.04 LTS sur DigitalOcean mettant en oeuvre des processeurs CPU dédiés premium d’Intel …</p><p><a href="https://www.digitalocean.com/blog/introducing-premium-cpu-optimized-droplets">Introducing Premium CPU-Optimized Droplets | DigitalOcean</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*beoXP5BGdHzNfjhEBzMsEg.png" /></figure><p>Et j’y installe de nouveau k3s pour former mon cluster Kubernetes local avec les clients nécessaires (kubectl et helm) :</p><p><a href="https://k3s.io/">K3s</a></p><pre>root@kubeai:~# snap install kubectl --classic<br>2024-12-30T13:37:55Z INFO Waiting for automatic snapd restart...<br>kubectl 1.31.4 from Canonical✓ installed<br>root@kubeai:~# snap install helm --classic<br>helm 3.16.4 from Snapcrafters✪ installed<br>root@kubeai:~# type kubectl &amp;&amp; type helm<br>kubectl is /snap/bin/kubectl<br>helm is /snap/bin/helm</pre><pre>root@kubeai:~# curl -sfL https://get.k3s.io | sh -<br>[INFO]  Finding release for channel stable<br>[INFO]  Using v1.31.4+k3s1 as release<br>[INFO]  Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.31.4+k3s1/sha256sum-amd64.txt<br>[INFO]  Downloading binary https://github.com/k3s-io/k3s/releases/download/v1.31.4+k3s1/k3s<br>[INFO]  Verifying binary download<br>[INFO]  Installing k3s to /usr/local/bin/k3s<br>[INFO]  Skipping installation of SELinux RPM<br>[INFO]  Skipping /usr/local/bin/kubectl symlink to k3s, command exists in PATH at /snap/bin/kubectl<br>[INFO]  Creating /usr/local/bin/crictl symlink to k3s<br>[INFO]  Creating /usr/local/bin/ctr symlink to k3s<br>[INFO]  Creating killall script /usr/local/bin/k3s-killall.sh<br>[INFO]  Creating uninstall script /usr/local/bin/k3s-uninstall.sh<br>[INFO]  env: Creating environment file /etc/systemd/system/k3s.service.env<br>[INFO]  systemd: Creating service file /etc/systemd/system/k3s.service<br>[INFO]  systemd: Enabling k3s unit<br>Created symlink /etc/systemd/system/multi-user.target.wants/k3s.service → /etc/systemd/system/k3s.service.<br>[INFO]  systemd: Starting k3s</pre><pre>root@kubeai:~# mkdir .kube &amp;&amp; cp /etc/rancher/k3s/k3s.yaml ~/.kube/config &amp;&amp; chmod 600 ~/.kube/config<br>root@kubeai:~# helm ls<br>NAME    NAMESPACE       REVISION        UPDATED STATUS  CHART   APP VERSION<br>root@kubeai:~# kubectl cluster-info<br>Kubernetes control plane is running at https://127.0.0.1:6443<br>CoreDNS is running at https://127.0.0.1:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy<br>Metrics-server is running at https://127.0.0.1:6443/api/v1/namespaces/kube-system/services/https:metrics-server:https/proxy<br><br>To further debug and diagnose cluster problems, use &#39;kubectl cluster-info dump&#39;.<br>root@kubeai:~# kubectl get po,svc -A<br>NAMESPACE     NAME                                          READY   STATUS      RESTARTS   AGE<br>kube-system   pod/coredns-ccb96694c-l6mzp                   1/1     Running     0          3m51s<br>kube-system   pod/helm-install-traefik-crd-462cg            0/1     Completed   0          3m51s<br>kube-system   pod/helm-install-traefik-jbx28                0/1     Completed   1          3m51s<br>kube-system   pod/local-path-provisioner-5cf85fd84d-hkdkl   1/1     Running     0          3m51s<br>kube-system   pod/metrics-server-5985cbc9d7-vjmrj           1/1     Running     0          3m51s<br>kube-system   pod/svclb-traefik-75ae73e0-5s2fq              2/2     Running     0          3m43s<br>kube-system   pod/traefik-57b79cf995-b662r                  1/1     Running     0          3m43s<br><br>NAMESPACE     NAME                     TYPE           CLUSTER-IP      EXTERNAL-IP      PORT(S)                      AGE<br>default       service/kubernetes       ClusterIP      10.43.0.1       &lt;none&gt;           443/TCP                      3m58s<br>kube-system   service/kube-dns         ClusterIP      10.43.0.10      &lt;none&gt;           53/UDP,53/TCP,9153/TCP       3m53s<br>kube-system   service/metrics-server   ClusterIP      10.43.49.80     &lt;none&gt;           443/TCP                      3m53s<br>kube-system   service/traefik          LoadBalancer   10.43.140.130   164.92.248.129   80:32667/TCP,443:32508/TCP   3m43s</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/535/0*Pa77V-4GDiOsRbyg.jpg" /></figure><p>KubeAI offre une compatibilité avec certains API d’OpenAI :</p><pre># Implemented #<br>/v1/chat/completions<br>/v1/completions<br>/v1/embeddings<br>/v1/models<br>/v1/audio/transcriptions<br><br># Planned #<br># /v1/assistants/*<br># /v1/batches/*<br># /v1/fine_tuning/*<br># /v1/images/*<br># /v1/vector_stores/*</pre><p>Je procède au déploiement de KubeAI via Helm en définissant les modèles nécessaires, notamment un modèle d’embedding et un modèle génératif (Le modèle d’intégration nomique est utilisé à la place de text-embedding-ada-002 et Google Gemma 2-2B est utilisé à la place de GPT-3.5-turbo) :</p><ul><li><a href="https://huggingface.co/google/gemma-2-2b">google/gemma-2-2b · Hugging Face</a></li><li><a href="https://ollama.com/library/gemma2:2b">gemma2:2b</a></li></ul><pre>root@kubeai:~# cat kubeai-model-values.yaml <br>catalog:<br>  text-embedding-ada-002:<br>    enabled: true<br>    minReplicas: 1<br>    features: [&quot;TextEmbedding&quot;]<br>    owner: nomic<br>    url: &quot;ollama://nomic-embed-text&quot;<br>    engine: OLlama<br>    resourceProfile: cpu:1<br>  gpt-3.5-turbo:<br>    enabled: true<br>    minReplicas: 1<br>    features: [&quot;TextGeneration&quot;]<br>    owner: google<br>    url: &quot;ollama://gemma2:2b&quot;<br>    engine: OLlama<br>    resourceProfile: cpu:4</pre><pre>root@kubeai:~# helm repo add kubeai https://www.kubeai.org &amp;&amp; helm repo update<br>&quot;kubeai&quot; has been added to your repositories<br>Hang tight while we grab the latest from your chart repositories...<br>...Successfully got an update from the &quot;kubeai&quot; chart repository<br>Update Complete. ⎈Happy Helming!⎈<br>root@kubeai:~# helm install kubeai kubeai/kubeai<br>NAME: kubeai<br>LAST DEPLOYED: Mon Dec 30 13:47:00 2024<br>NAMESPACE: default<br>STATUS: deployed<br>REVISION: 1<br>TEST SUITE: None<br><br><br>root@kubeai:~# helm install kubeai-models kubeai/models \<br>    -f ./kubeai-model-values.yaml<br>NAME: kubeai-models<br>LAST DEPLOYED: Mon Dec 30 13:47:11 2024<br>NAMESPACE: default<br>STATUS: deployed<br>REVISION: 1<br>TEST SUITE: None</pre><pre>root@kubeai:~# kubectl get po,svc<br>NAME                                                READY   STATUS    RESTARTS   AGE<br>pod/kubeai-6b7b6866fb-26qwq                         1/1     Running   0          3m1s<br>pod/model-gpt-3.5-turbo-545cf68d8d-v97gs            1/1     Running   0          27s<br>pod/model-text-embedding-ada-002-64dc467cf4-8m64j   1/1     Running   0          30s<br>pod/openwebui-55d54bd69-k4ttm                       1/1     Running   0          3m1s<br><br>NAME                 TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)           AGE<br>service/kubeai       ClusterIP   10.43.24.35    &lt;none&gt;        80/TCP,8080/TCP   3m1s<br>service/kubernetes   ClusterIP   10.43.0.1      &lt;none&gt;        443/TCP           9m12s<br>service/openwebui    ClusterIP   10.43.107.76   &lt;none&gt;        80/TCP            3m1s</pre><p>Ollama est bien présent avec KubeAI :</p><pre>(weaviate) root@kubeai:~# kubectl logs pod/model-gpt-3.5-turbo-545cf68d8d-v97gs<br>Couldn&#39;t find &#39;/root/.ollama/id_ed25519&#39;. Generating new private key.<br>Your new public key is: <br><br>ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAGHk39koguimeZFYBSjv9LDxjj5vZRjFmwznLdXSWUV<br><br>2024/12/30 13:49:36 routes.go:1259: INFO server config env=&quot;map[CUDA_VISIBLE_DEVICES: GPU_DEVICE_ORDINAL: HIP_VISIBLE_DEVICES: HSA_OVERRIDE_GFX_VERSION: HTTPS_PROXY: HTTP_PROXY: NO_PROXY: OLLAMA_DEBUG:false OLLAMA_FLASH_ATTENTION:false OLLAMA_GPU_OVERHEAD:0 OLLAMA_HOST:http://0.0.0.0:8000 OLLAMA_INTEL_GPU:false OLLAMA_KEEP_ALIVE:999999h0m0s OLLAMA_KV_CACHE_TYPE: OLLAMA_LLM_LIBRARY: OLLAMA_LOAD_TIMEOUT:5m0s OLLAMA_MAX_LOADED_MODELS:0 OLLAMA_MAX_QUEUE:512 OLLAMA_MODELS:/root/.ollama/models OLLAMA_MULTIUSER_CACHE:false OLLAMA_NOHISTORY:false OLLAMA_NOPRUNE:false OLLAMA_NUM_PARALLEL:0 OLLAMA_ORIGINS:[http://localhost https://localhost http://localhost:* https://localhost:* http://127.0.0.1 https://127.0.0.1 http://127.0.0.1:* https://127.0.0.1:* http://0.0.0.0 https://0.0.0.0 http://0.0.0.0:* https://0.0.0.0:* app://* file://* tauri://* vscode-webview://*] OLLAMA_SCHED_SPREAD:false ROCR_VISIBLE_DEVICES: http_proxy: https_proxy: no_proxy:]&quot;<br>time=2024-12-30T13:49:36.768Z level=INFO source=images.go:757 msg=&quot;total blobs: 0&quot;<br>time=2024-12-30T13:49:36.768Z level=INFO source=images.go:764 msg=&quot;total unused blobs removed: 0&quot;<br>[GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached.<br><br>[GIN-debug] [WARNING] Running in &quot;debug&quot; mode. Switch to &quot;release&quot; mode in production.<br> - using env:   export GIN_MODE=release<br> - using code:  gin.SetMode(gin.ReleaseMode)<br><br>[GIN-debug] POST   /api/pull                 --&gt; github.com/ollama/ollama/server.(*Server).PullHandler-fm (5 handlers)<br>[GIN-debug] POST   /api/generate             --&gt; github.com/ollama/ollama/server.(*Server).GenerateHandler-fm (5 handlers)<br>[GIN-debug] POST   /api/chat                 --&gt; github.com/ollama/ollama/server.(*Server).ChatHandler-fm (5 handlers)<br>[GIN-debug] POST   /api/embed                --&gt; github.com/ollama/ollama/server.(*Server).EmbedHandler-fm (5 handlers)<br>[GIN-debug] POST   /api/embeddings           --&gt; github.com/ollama/ollama/server.(*Server).EmbeddingsHandler-fm (5 handlers)<br>[GIN-debug] POST   /api/create               --&gt; github.com/ollama/ollama/server.(*Server).CreateHandler-fm (5 handlers)<br>[GIN-debug] POST   /api/push                 --&gt; github.com/ollama/ollama/server.(*Server).PushHandler-fm (5 handlers)<br>[GIN-debug] POST   /api/copy                 --&gt; github.com/ollama/ollama/server.(*Server).CopyHandler-fm (5 handlers)<br>[GIN-debug] DELETE /api/delete               --&gt; github.com/ollama/ollama/server.(*Server).DeleteHandler-fm (5 handlers)<br>[GIN-debug] POST   /api/show                 --&gt; github.com/ollama/ollama/server.(*Server).ShowHandler-fm (5 handlers)<br>[GIN-debug] POST   /api/blobs/:digest        --&gt; github.com/ollama/ollama/server.(*Server).CreateBlobHandler-fm (5 handlers)<br>[GIN-debug] HEAD   /api/blobs/:digest        --&gt; github.com/ollama/ollama/server.(*Server).HeadBlobHandler-fm (5 handlers)<br>[GIN-debug] GET    /api/ps                   --&gt; github.com/ollama/ollama/server.(*Server).PsHandler-fm (5 handlers)<br>[GIN-debug] POST   /v1/chat/completions      --&gt; github.com/ollama/ollama/server.(*Server).ChatHandler-fm (6 handlers)</pre><p>Weaviate est un moteur de recherche vectoriel qui peut s’intégrer de manière transparente aux modèles d’intégration et de génération de KubeAI. Je vais utiliser KubeAI comme point de terminaison OpenAI pour Weaviate :</p><p><a href="https://weaviate.io/developers/weaviate/model-providers/kubeai">KubeAI + Weaviate | Weaviate</a></p><p>Création d’un fichier nommé <strong><em>weaviate-values.yaml</em></strong> avec le contenu suivant pour l’installation de Weaviate via Helm (et activer les modules <em>text2vec-openai</em> et <em>generative-openai ; </em>apiKeyest ignoré dans ce cas car on utilise ici KubeAI comme point de terminaison OpenAI) :</p><pre>root@kubeai:~# cat weaviate-values.yaml <br>modules:<br>  text2vec-openai:<br>    enabled: true<br>    apiKey: thisIsIgnored<br>  generative-openai:<br>    enabled: true<br>    apiKey: thisIsIgnored<br>  default_vectorizer_module: text2vec-openai<br>service:<br>  # To prevent Weaviate being exposed publicly<br>  type: ClusterIP</pre><pre>root@kubeai:~# helm repo add weaviate https://weaviate.github.io/weaviate-helm &amp;&amp; helm repo update<br>&quot;weaviate&quot; has been added to your repositories<br>Hang tight while we grab the latest from your chart repositories...<br>...Successfully got an update from the &quot;weaviate&quot; chart repository<br>...Successfully got an update from the &quot;kubeai&quot; chart repository<br>Update Complete. ⎈Happy Helming!⎈<br><br><br>root@kubeai:~# helm install \<br>  &quot;weaviate&quot; \<br>  weaviate/weaviate \<br>  -f weaviate-values.yaml<br>NAME: weaviate<br>LAST DEPLOYED: Mon Dec 30 13:51:48 2024<br>NAMESPACE: default<br>STATUS: deployed<br>REVISION: 1<br>TEST SUITE: None</pre><pre>root@kubeai:~# kubectl get po,svc<br>NAME                                                READY   STATUS    RESTARTS   AGE<br>pod/kubeai-6b7b6866fb-26qwq                         1/1     Running   0          5m18s<br>pod/model-gpt-3.5-turbo-545cf68d8d-v97gs            1/1     Running   0          2m44s<br>pod/model-text-embedding-ada-002-64dc467cf4-8m64j   1/1     Running   0          2m47s<br>pod/openwebui-55d54bd69-k4ttm                       1/1     Running   0          5m18s<br>pod/weaviate-0                                      1/1     Running   0          31s<br><br>NAME                        TYPE           CLUSTER-IP     EXTERNAL-IP      PORT(S)           AGE<br>service/kubeai              ClusterIP      10.43.24.35    &lt;none&gt;           80/TCP,8080/TCP   5m18s<br>service/kubernetes          ClusterIP      10.43.0.1      &lt;none&gt;           443/TCP           11m<br>service/openwebui           ClusterIP      10.43.107.76   &lt;none&gt;           80/TCP            5m18s<br>service/weaviate            ClusterIP      10.43.211.85   &lt;none&gt;           80/TCP            31s<br>service/weaviate-grpc       LoadBalancer   10.43.37.63    164.92.248.129   50051:31360/TCP   31s<br>service/weaviate-headless   ClusterIP      None           &lt;none&gt;           80/TCP            31s</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iRyqh9S_zvGgCwI5YTqWGg.png" /></figure><p>Je vais exécuter des requêtes en Python pour interagir avec Weaviate. Installation de l’environnement nécessaire via <strong>uv</strong> (gestionnaire de paquets et de projets pour Python extrêmement rapide et écrit en Rust) :</p><ul><li><a href="https://github.com/astral-sh/uv">GitHub - astral-sh/uv: An extremely fast Python package and project manager, written in Rust.</a></li><li><a href="https://docs.astral.sh/uv/">uv</a></li></ul><pre>root@kubeai:~# curl -LsSf https://astral.sh/uv/install.sh | sh<br>downloading uv 0.5.13 x86_64-unknown-linux-gnu<br>no checksums to verify<br>installing to /root/.local/bin<br>  uv<br>  uvx<br>everything&#39;s installed!<br><br>To add $HOME/.local/bin to your PATH, either restart your shell or run:<br><br>    source $HOME/.local/bin/env (sh, bash, zsh)<br>    source $HOME/.local/bin/env.fish (fish)<br>    <br>root@kubeai:~# source $HOME/.local/bin/env<br><br>root@kubeai:~# uv<br>An extremely fast Python package manager.<br><br>Usage: uv [OPTIONS] &lt;COMMAND&gt;<br><br>Commands:<br>  run      Run a command or script<br>  init     Create a new project<br>  add      Add dependencies to the project<br>  remove   Remove dependencies from the project<br>  sync     Update the project&#39;s environment<br>  lock     Update the project&#39;s lockfile<br>  export   Export the project&#39;s lockfile to an alternate format<br>  tree     Display the project&#39;s dependency tree<br>  tool     Run and install commands provided by Python packages<br>  python   Manage Python versions and installations<br>  pip      Manage Python packages with a pip-compatible interface<br>  venv     Create a virtual environment<br>  build    Build Python packages into source distributions and wheels<br>  publish  Upload distributions to an index<br>  cache    Manage uv&#39;s cache<br>  self     Manage the uv executable<br>  version  Display uv&#39;s version<br>  help     Display documentation for a command<br><br>Cache options:<br>  -n, --no-cache               Avoid reading from or writing to the cache, instead using a temporary directory for the duration of the operation [env: UV_NO_CACHE=]<br>      --cache-dir &lt;CACHE_DIR&gt;  Path to the cache directory [env: UV_CACHE_DIR=]<br><br>Python options:<br>      --python-preference &lt;PYTHON_PREFERENCE&gt;  Whether to prefer uv-managed or system Python installations [env: UV_PYTHON_PREFERENCE=] [possible values: only-managed, managed, system,<br>                                               only-system]<br>      --no-python-downloads                    Disable automatic downloads of Python. [env: &quot;UV_PYTHON_DOWNLOADS=never&quot;]<br><br>Global options:<br>  -q, --quiet                                      Do not print any output<br>  -v, --verbose...                                 Use verbose output<br>      --color &lt;COLOR_CHOICE&gt;                       Control colors in output [default: auto] [possible values: auto, always, never]<br>      --native-tls                                 Whether to load TLS certificates from the platform&#39;s native certificate store [env: UV_NATIVE_TLS=]<br>      --offline                                    Disable network access [env: UV_OFFLINE=]<br>      --allow-insecure-host &lt;ALLOW_INSECURE_HOST&gt;  Allow insecure connections to a host [env: UV_INSECURE_HOST=]<br>      --no-progress                                Hide all progress outputs [env: UV_NO_PROGRESS=]<br>      --directory &lt;DIRECTORY&gt;                      Change to the given directory prior to running the command<br>      --project &lt;PROJECT&gt;                          Run the command within the given project directory<br>      --config-file &lt;CONFIG_FILE&gt;                  The path to a `uv.toml` file to use for configuration [env: UV_CONFIG_FILE=]<br>      --no-config                                  Avoid discovering configuration files (`pyproject.toml`, `uv.toml`) [env: UV_NO_CONFIG=]<br>  -h, --help                                       Display the concise help for this command<br>  -V, --version                                    Display the uv version<br><br>Use `uv help` for more details.</pre><pre>root@kubeai:~# uv self update<br>info: Checking for updates...<br>success: You&#39;re on the latest version of uv (v0.5.13)<br>root@kubeai:~# uv venv weaviate<br>Using CPython 3.12.3 interpreter at: /usr/bin/python3<br>Creating virtual environment at: weaviate<br>Activate with: source weaviate/bin/activate<br><br>root@kubeai:~# source weaviate/bin/activate</pre><p>Installation du client Python pour Weaviate à cette étape :</p><pre>(weaviate) root@kubeai:~# uv pip install -U weaviate-client requests<br>Using Python 3.12.3 environment at: weaviate<br>Resolved 25 packages in 382ms<br>Prepared 25 packages in 252ms<br>Installed 25 packages in 11ms<br> + annotated-types==0.7.0<br> + anyio==4.7.0<br> + authlib==1.3.1<br> + certifi==2024.12.14<br> + cffi==1.17.1<br> + charset-normalizer==3.4.1<br> + cryptography==44.0.0<br> + grpcio==1.68.1<br> + grpcio-health-checking==1.68.1<br> + grpcio-tools==1.68.1<br> + h11==0.14.0<br> + httpcore==1.0.7<br> + httpx==0.28.1<br> + idna==3.10<br> + protobuf==5.29.2<br> + pycparser==2.22<br> + pydantic==2.10.4<br> + pydantic-core==2.27.2<br> + requests==2.32.3<br> + setuptools==75.6.0<br> + sniffio==1.3.1<br> + typing-extensions==4.12.2<br> + urllib3==2.3.0<br> + validators==0.34.0<br> + weaviate-client==4.10.2</pre><p>Weaviate n’est pas exposé publiquement dans cette configuration. Je configure des redirections de port locales pour accéder aux services Weaviate :</p><pre>(weaviate) root@kubeai:~# screen -L -S weaviate-http<br>[detached from 11693.weaviate-http]<br>(weaviate) root@kubeai:~# screen -L -S weaviate-grpc<br>[detached from 11996.weaviate-grpc]<br>(weaviate) root@kubeai:~# tail -f screenlog.0<br>root@kubeai:~# kubectl port-forward svc/weaviate 8080:80 &amp;&amp; kubectl port-forward svc/weaviate-grpc 50051:50051<br>Forwarding from 127.0.0.1:8080 -&gt; 8080<br>Forwarding from [::1]:8080 -&gt; 8080<br>root@kubeai:~# kubectl port-forward svc/weaviate-grpc 50051:50051<br>Forwarding from 127.0.0.1:50051 -&gt; 50051<br>Forwarding from [::1]:50051 -&gt; 50051<br><br>(weaviate) root@kubeai:~# netstat -tunlp | grep kubectl<br>tcp        0      0 127.0.0.1:8080          0.0.0.0:*               LISTEN      11710/kubectl       <br>tcp        0      0 127.0.0.1:50051         0.0.0.0:*               LISTEN      12018/kubectl       <br>tcp6       0      0 ::1:8080                :::*                    LISTEN      11710/kubectl       <br>tcp6       0      0 ::1:50051               :::*                    LISTEN      12018/kubectl  </pre><p>J’aborde le cas d’une recherche sémantique à l’aide d’un modèle d’intégration avec collecte et importation de données. Pour cela création et exécution du fichier Python suivant :</p><pre>(weaviate) root@kubeai:~# cat create-collection.py <br><br>import json<br>import weaviate<br>import requests<br>from weaviate.classes.config import Configure<br><br># This works due to port forward in previous step<br>with weaviate.connect_to_local(port=8080, grpc_port=50051) as client:<br><br>    client.collections.create(<br>        &quot;Question&quot;,<br>        vectorizer_config=Configure.Vectorizer.text2vec_openai(<br>                model=&quot;text-embedding-ada-002&quot;,<br>                base_url=&quot;http://kubeai/openai&quot;,<br>        ),<br>        generative_config=Configure.Generative.openai(<br>            model=&quot;gpt-3.5-turbo&quot;,<br>            base_url=&quot;http://kubeai/openai&quot;,<br>        ),<br>    )<br><br>    # import data<br>    resp = requests.get(&#39;https://raw.githubusercontent.com/weaviate-tutorials/quickstart/main/data/jeopardy_tiny.json&#39;)<br>    data = json.loads(resp.text)  # Load data<br><br>    question_objs = list()<br>    for i, d in enumerate(data):<br>        question_objs.append({<br>            &quot;answer&quot;: d[&quot;Answer&quot;],<br>            &quot;question&quot;: d[&quot;Question&quot;],<br>            &quot;category&quot;: d[&quot;Category&quot;],<br>        })<br><br>    questions = client.collections.get(&quot;Question&quot;)<br>    questions.data.insert_many(question_objs)<br>    print(&quot;Data imported successfully&quot;)</pre><pre>(weaviate) root@kubeai:~# python create-collection.py<br>&quot;Data imported successfully&quot;</pre><p>On se base sur le petit fichier JSON (questions/réponses sur le jeu Jeopardy).</p><pre>[{&quot;Category&quot;:&quot;SCIENCE&quot;,&quot;Question&quot;:&quot;This organ removes excess glucose from the blood &amp; stores it as glycogen&quot;,&quot;Answer&quot;:&quot;Liver&quot;},{&quot;Category&quot;:&quot;ANIMALS&quot;,&quot;Question&quot;:&quot;It&#39;s the only living mammal in the order Proboseidea&quot;,&quot;Answer&quot;:&quot;Elephant&quot;},{&quot;Category&quot;:&quot;ANIMALS&quot;,&quot;Question&quot;:&quot;The gavial looks very much like a crocodile except for this bodily feature&quot;,&quot;Answer&quot;:&quot;the nose or snout&quot;},{&quot;Category&quot;:&quot;ANIMALS&quot;,&quot;Question&quot;:&quot;Weighing around a ton, the eland is the largest species of this animal in Africa&quot;,&quot;Answer&quot;:&quot;Antelope&quot;},{&quot;Category&quot;:&quot;ANIMALS&quot;,&quot;Question&quot;:&quot;Heaviest of all poisonous snakes is this North American rattlesnake&quot;,&quot;Answer&quot;:&quot;the diamondback rattler&quot;},{&quot;Category&quot;:&quot;SCIENCE&quot;,&quot;Question&quot;:&quot;2000 news: the Gunnison sage grouse isn&#39;t just another northern sage grouse, but a new one of this classification&quot;,&quot;Answer&quot;:&quot;species&quot;},{&quot;Category&quot;:&quot;SCIENCE&quot;,&quot;Question&quot;:&quot;A metal that is ductile can be pulled into this while cold &amp; under pressure&quot;,&quot;Answer&quot;:&quot;wire&quot;},{&quot;Category&quot;:&quot;SCIENCE&quot;,&quot;Question&quot;:&quot;In 1953 Watson &amp; Crick built a model of the molecular structure of this, the gene-carrying substance&quot;,&quot;Answer&quot;:&quot;DNA&quot;},{&quot;Category&quot;:&quot;SCIENCE&quot;,&quot;Question&quot;:&quot;Changes in the tropospheric layer of this are what gives us weather&quot;,&quot;Answer&quot;:&quot;the atmosphere&quot;},{&quot;Category&quot;:&quot;SCIENCE&quot;,&quot;Question&quot;:&quot;In 70-degree air, a plane traveling at about 1,130 feet per second breaks it&quot;,&quot;Answer&quot;:&quot;Sound barrier&quot;}]</pre><p>La collection est maintenant créée et les données sont importées. Les vecteurs sont générés par KubeAI et stockés dans Weaviate. Je peux effectuer une recherche sémantique en lien avec le terme “biology” qui utilise les intégrations via la création de ce fichier Python :</p><pre>(weaviate) root@kubeai:~# cat search.py <br>import weaviate<br>from weaviate.classes.config import Configure<br><br># This works due to port forward in previous step<br>with weaviate.connect_to_local(port=8080, grpc_port=50051) as client:<br>    questions = client.collections.get(&quot;Question&quot;)<br>    response = questions.query.near_text(<br>        query=&quot;biology&quot;,<br>        limit=2<br>    )<br>    print(response.objects[0].properties)  # Inspect the first object</pre><p>avec la réponse suivante :</p><pre>(weaviate) root@kubeai:~# python search.py<br>{&#39;answer&#39;: &#39;DNA&#39;, &#39;question&#39;: &#39;In 1953 Watson &amp; Crick built a model of the molecular structure of this, the gene-carrying substance&#39;, &#39;category&#39;: &#39;SCIENCE&#39;}</pre><p>Je peux modifier ma recherche sémantique avec le terme “poison” par exemple :</p><pre>(weaviate) root@kubeai:~# cat search.py <br>import weaviate<br>from weaviate.classes.config import Configure<br><br># This works due to port forward in previous step<br>with weaviate.connect_to_local(port=8080, grpc_port=50051) as client:<br>    questions = client.collections.get(&quot;Question&quot;)<br>    response = questions.query.near_text(<br>        query=&quot;poison&quot;,<br>        limit=2<br>    )<br>    print(response.objects[0].properties)  # Inspect the first object</pre><pre>(weaviate) root@kubeai:~# python search.py<br>{&#39;answer&#39;: &#39;the diamondback rattler&#39;, &#39;question&#39;: &#39;Heaviest of all poisonous snakes is this North American rattlesnake&#39;, &#39;category&#39;: &#39;ANIMALS&#39;}</pre><p>Passons maintenant à la recherche générative, qui utilise le modèle génératif (Génération de texte LLM). Le modèle génératif est exécuté localement et géré par KubeAI. Création d’un fichier nommé generate.pyavec le contenu suivant pour genérer un tweet avec des emojis en lien avec la recherche sémantique précédente (et en utilisant les redirections de port locales) :</p><pre><br>(weaviate) root@kubeai:~# cat generate.py <br>import weaviate<br>from weaviate.classes.config import Configure<br><br># This works due to port forward in previous step<br>with weaviate.connect_to_local(port=8080, grpc_port=50051) as client:<br>    questions = client.collections.get(&quot;Question&quot;)<br><br>    response = questions.generate.near_text(<br>        query=&quot;biology&quot;,<br>        limit=2,<br>        grouped_task=&quot;Write a tweet with emojis about these facts.&quot;<br>    )<br><br>    print(response.generated)  # Inspect the generated text</pre><p>avec cette réponse …</p><pre>(weaviate) root@kubeai:~# python generate.py<br>🧬 **Watson &amp; Crick** cracked the code in 1953!  🤯 They built a model of DNA, the blueprint of life. 🧬<br><br>🧠 **Liver power!** 💪 This organ keeps your blood sugar balanced by storing glucose as glycogen. 🩸 #ScienceFacts #Biology<br><br></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/0*-9rfBuJSz0pn-C2F.jpg" /></figure><p>L’importation de données a permis d’effectuer des recherches et à générer du contenu à l’aide de modèles gérés par KubeAI. Il est possible de l’utiliser avec LangChain qui facilite la création d’applications basées sur des LLM :</p><p><a href="https://python.langchain.com/docs/introduction/">Introduction | 🦜️🔗 LangChain</a></p><p>LangChain peut en effet interagir avec l’API compatible OpenAI de KubeAI. Installation du client Python pour LangChain avec <strong>uv</strong> :</p><pre>(weaviate) root@kubeai:~# uv pip install -U langchain_openai<br>Using Python 3.12.3 environment at: weaviate<br>Resolved 30 packages in 1.32s<br>Prepared 16 packages in 93ms<br>Installed 16 packages in 7ms<br> + distro==1.9.0<br> + jiter==0.8.2<br> + jsonpatch==1.33<br> + jsonpointer==3.0.0<br> + langchain-core==0.3.28<br> + langchain-openai==0.2.14<br> + langsmith==0.2.6<br> + openai==1.58.1<br> + orjson==3.10.13<br> + packaging==24.2<br> + pyyaml==6.0.2<br> + regex==2024.11.6<br> + requests-toolbelt==1.0.0<br> + tenacity==9.0.0<br> + tiktoken==0.8.0<br> + tqdm==4.67.1</pre><p>Accession locale à l’API compatible KubeAI OpenAI pour faciliter la tâche via un transfert de port vers le service KubeAI :</p><pre>(weaviate) root@kubeai:~# screen -L -S kubeai<br>[detached from 15501.kubeai]<br>(weaviate) root@kubeai:~# cat screenlog.0 <br>root@kubeai:~# kubectl port-forward svc/kubeai 8000:80<br>Forwarding from 127.0.0.1:8000 -&gt; 8000<br>Forwarding from [::1]:8000 -&gt; 8000<br>(weaviate) root@kubeai:~# netstat -tunlp | grep kubectl<br>tcp        0      0 127.0.0.1:8000          0.0.0.0:*               LISTEN      15511/kubectl       <br>tcp6       0      0 ::1:8000                :::*                    LISTEN      15511/kubectl</pre><p>Création d’un fichier Python simple qui utilise LangChain et connecté à KubeAI (c’est cette interface compatible avec OpenAI qui est consommée au lieu de l’API publique OpenAI par défaut) :</p><pre>(weaviate) root@kubeai:~# cat test-langchain.py <br><br>from langchain_openai import ChatOpenAI<br><br>llm = ChatOpenAI(<br>    model=&quot;gpt-3.5-turbo&quot;,<br>    temperature=0,<br>    max_tokens=None,<br>    timeout=None,<br>    max_retries=2,<br>    api_key=&quot;thisIsIgnored&quot;,<br>    base_url=&quot;http://localhost:8000/openai/v1&quot;,<br>)<br><br>messages = [<br>    (<br>        &quot;system&quot;,<br>        &quot;You are a helpful assistant in cloud native technologies&quot;,<br>    ),<br>    (&quot;How can i create a kubernetes cluster with k3s ?&quot;),<br>]<br>ai_msg = llm.invoke(messages)<br>print(ai_msg.content)</pre><p>Je pose une question au LLM embarqué via Ollama sur la création d’un cluster k3s avec cette réponse :</p><pre>(weaviate) root@kubeai:~# python test-langchain.py<br><br>Let&#39;s get you started with creating a Kubernetes cluster using K3s! <br><br>**What is K3s?**<br><br>K3s is a lightweight, production-ready distribution of Kubernetes designed for simplicity and efficiency. It&#39;s ideal for:<br><br>* **Small to medium-sized deployments:**  It excels in environments where resource constraints are a factor.<br>* **Edge computing:** Deploying applications on devices with limited resources.<br>* **DevOps teams:** Its ease of use makes it perfect for rapid prototyping and deployment. <br><br>**Steps to Create a K3s Cluster**<br><br>Here&#39;s a breakdown of the process, along with explanations:<br><br>1. **Prerequisites:**<br>   * **Hardware:** You&#39;ll need a machine (physical or virtual) capable of running Kubernetes.  K3s is designed for low-resource environments. <br>   * **Networking:** Ensure your machine has network connectivity and can reach the internet.<br>   * **Basic Linux knowledge:** Familiarity with command-line tools like `curl`, `wget`, and basic terminal navigation will be helpful.<br><br>2. **Installation:**<br>   * **Download K3s:**  Visit the official K3s website ([https://k3s.io/](https://k3s.io/)) to download the latest version of K3s for your operating system (e.g., Linux, macOS). <br>   * **Installation:** Follow the instructions provided in the K3s documentation to install K3s on your machine. You&#39;ll likely need to use a terminal or command-line interface.<br><br>3. **Cluster Configuration:**<br>   * **Networking:**  Configure your network settings for your K3s cluster (e.g., IP addresses, subnet masks). <br>   * **Storage:** Decide how you want to store data within your cluster (e.g., local disk, persistent volumes).<br>   * **Security:** Implement security measures like TLS certificates and firewall rules if needed.<br><br>4. **Initialization:**<br>   * **Start the K3s Cluster:**  Use the `k3s` command-line tool to start the cluster. <br>   * **Access the Dashboard (Optional):** If you&#39;re using a dashboard, follow the instructions provided by your chosen dashboard provider.<br><br>5. **Deploying Applications:**<br>   * **kubectl:** Use the `kubectl` command-line tool to interact with your K3s cluster and deploy applications. <br>   * **YAML Configuration:**  Create Kubernetes YAML files (configuration files) for your desired application deployments. <br><br><br>**Example Commands:**<br><br>```bash<br># Install K3s on Ubuntu<br>curl -LO https://get.k3s.io/install.sh<br>chmod +x install.sh<br>./install.sh<br><br># Start the cluster<br>k3s start<br>```<br><br>**Key Advantages of K3s:**<br><br>* **Simplicity:**  K3s is designed for ease of use, making it a great choice for beginners and experienced users alike. <br>* **Lightweight:** It&#39;s incredibly efficient, requiring minimal resources to run. This makes it ideal for edge deployments or environments with limited hardware.<br>* **Fast Deployment:** K3s offers quick cluster setup times, allowing you to get your applications running faster.<br><br>**Additional Resources:**<br><br>* **K3s Website:** [https://k3s.io/](https://k3s.io/) <br>* **K3s Documentation:** [https://docs.k3s.io/](https://docs.k3s.io/)<br><br><br>Let me know if you have any specific questions or want to dive deeper into a particular aspect of K3s!</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q7O6WotwWGgipEJWG2cy8g.png" /></figure><p>Pour plus de visibiliter, j’insère Rancher Server sur ce cluster k3s avec les commandes suivantes :</p><pre>helm repo add rancher-latest https://releases.rancher.com/server-charts/latest<br><br>kubectl create namespace cattle-system<br><br>kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.16.2/cert-manager.crds.yaml<br><br>helm repo add jetstack https://charts.jetstack.io<br><br>helm repo update<br><br>helm install cert-manager jetstack/cert-manager \<br>  --namespace cert-manager \<br>  --create-namespace<br><br>&quot;rancher-latest&quot; has been added to your repositories<br>namespace/cattle-system created<br>customresourcedefinition.apiextensions.k8s.io/certificaterequests.cert-manager.io created<br>customresourcedefinition.apiextensions.k8s.io/certificates.cert-manager.io created<br>customresourcedefinition.apiextensions.k8s.io/challenges.acme.cert-manager.io created<br>customresourcedefinition.apiextensions.k8s.io/clusterissuers.cert-manager.io created<br>customresourcedefinition.apiextensions.k8s.io/issuers.cert-manager.io created<br>customresourcedefinition.apiextensions.k8s.io/orders.acme.cert-manager.io created<br>&quot;jetstack&quot; has been added to your repositories<br>Hang tight while we grab the latest from your chart repositories...<br>...Successfully got an update from the &quot;weaviate&quot; chart repository<br>...Successfully got an update from the &quot;kubeai&quot; chart repository<br>...Successfully got an update from the &quot;jetstack&quot; chart repository<br>...Successfully got an update from the &quot;rancher-latest&quot; chart repository<br>Update Complete. ⎈Happy Helming!⎈<br>NAME: cert-manager<br>LAST DEPLOYED: Mon Dec 30 15:00:45 2024<br>NAMESPACE: cert-manager<br>STATUS: deployed<br>REVISION: 1<br>TEST SUITE: None<br>NOTES:<br>cert-manager v1.16.2 has been deployed successfully!<br><br>In order to begin issuing certificates, you will need to set up a ClusterIssuer<br>or Issuer resource (for example, by creating a &#39;letsencrypt-staging&#39; issuer).<br><br>More information on the different types of issuers and how to configure them<br>can be found in our documentation:<br><br>https://cert-manager.io/docs/configuration/<br><br>For information on how to configure cert-manager to automatically provision<br>Certificates for Ingress resources, take a look at the `ingress-shim`<br>documentation:<br><br>https://cert-manager.io/docs/usage/ingress/</pre><pre><br>(weaviate) root@kubeai:~# helm install rancher rancher-latest/rancher \<br>  --namespace cattle-system \<br>  --set hostname=rancher.164.92.248.129.sslip.io \<br>  --set replicas=1 \<br>  --set bootstrapPassword=nochangeme<br>NAME: rancher<br>LAST DEPLOYED: Mon Dec 30 15:01:59 2024<br>NAMESPACE: cattle-system<br>STATUS: deployed<br>REVISION: 1<br>TEST SUITE: None<br>NOTES:<br>Rancher Server has been installed.<br><br>NOTE: Rancher may take several minutes to fully initialize. Please standby while Certificates are being issued, Containers are started and the Ingress rule comes up.<br><br>Check out our docs at https://rancher.com/docs/<br><br>If you provided your own bootstrap password during installation, browse to https://rancher.164.92.248.129.sslip.io to get started.<br><br>If this is the first time you installed Rancher, get started by running this command and clicking the URL it generates:<br><br>```<br>echo https://rancher.164.92.248.129.sslip.io/dashboard/?setup=$(kubectl get secret --namespace cattle-system bootstrap-secret -o go-template=&#39;{{.data.bootstrapPassword|base64decode}}&#39;)<br>```<br><br>To get just the bootstrap password on its own, run:<br><br>```<br>kubectl get secret --namespace cattle-system bootstrap-secret -o go-template=&#39;{{.data.bootstrapPassword|base64decode}}{{ &quot;\n&quot; }}&#39;<br>```<br><br><br>Happy Containering!</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b_zQ_obAaZZoQIj7TQzJjg.png" /></figure><p>Je modifie le fichier YAML pour KubeAI pour bénéficier d’un accès à Ollama :</p><pre>root@kubeai:~# cat &lt;&lt;EOF &gt; models-helm-values.yaml<br>catalog:<br>  gemma2-2b-cpu:<br>    enabled: true<br>    minReplicas: 1<br>EOF</pre><pre>root@kubeai:~# helm upgrade kubeai-models kubeai/models \<br>    -f ./models-helm-values.yaml<br><br>Release &quot;kubeai-models&quot; has been upgraded. Happy Helming!<br>NAME: kubeai-models<br>LAST DEPLOYED: Mon Dec 30 15:14:49 2024<br>NAMESPACE: default<br>STATUS: deployed<br>REVISION: 2<br>TEST SUITE: None<br>root@kubeai:~# helm ls<br>NAME            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART           APP VERSION<br>kubeai          default         1               2024-12-30 13:47:00.713372779 +0000 UTC deployed        kubeai-0.10.0   v0.12.0    <br>kubeai-models   default         2               2024-12-30 15:14:49.154697606 +0000 UTC deployed        models-0.10.0   1.16.0     <br>weaviate        default         1               2024-12-30 13:51:48.357464607 +0000 UTC deployed        weaviate-17.3.3 1.27.8</pre><p>Avec de nouveau une redirection locale de port pour accéder à Open WebUI (intégré à KubeAI), une interface utilisateur extensible, riche en fonctionnalités et conviviale, conçue pour fonctionner entièrement hors ligne. Elle prend en charge différents runners LLM, y compris Ollama et les API compatibles avec OpenAI :</p><pre>(weaviate) root@kubeai:~# kubectl port-forward service/openwebui 10000:80 --address=&#39;0.0.0.0&#39;<br>Forwarding from 0.0.0.0:10000 -&gt; 8080<br>Handling connection for 10000<br>Handling connection for 10000<br>Handling connection for 10000</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T8RfOIC_rf342xth5hetqQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8R9xCF9XWb--CjwmfWVjyA.png" /></figure><p>Accession à l’interface utilisateur d’Open WebUI :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zEugXKeda6RRDJqRTKdMwQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HsAp73EHoJlnGwQ0u0zPIg.png" /></figure><p>C’est ce petit LLM utilisé précedemment qui est encore mis en oeuvre ici :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HWxj4EZYGcEjv6O7iLloHQ.png" /></figure><p>J’effectue alors une recherche sur la base d’un document PDF extrait de la documentation officielle de k3s via cette interface …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RL152KObkerODoEiIOLVbg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hu0Wt9mBik0uVymHIHTt4A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u2yeZAnGStGffp6VqfPRfg.png" /></figure><p>Dans cet article, j’ai utiliser uniquement des modèles CPU (il devrait donc fonctionner même sur votre ordinateur portable) qui fait que KubeAI peut fonctionner sur votre matériel existant, réduisant ainsi le besoin de payer pour des intégrations et des modèles génératifs.</p><blockquote>KubeAI s’exécute localement dans votre cluster Kubernetes, de sorte que vos données ne quittent jamais votre infrastructure. Vous pouvez facilement changer ou mettre à jour les modèles utilisés sans modifier votre code applicatif et KubeAI permet une mise à l’échelle automatique des modèles en fonction de la charge.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*aavP9LRNAXqe_g5N.jpg" /></figure><p>En conclusion, on a vu que l’utilisation combinée de KubeAI et Weaviate offre une solution robuste et flexible pour implémenter le RAG de manière privée et évolutive. Cette approche permet aux entreprises de bénéficier des avancées de l’IA tout en gardant le contrôle sur leurs données et leur infrastructure …</p><p>À suivre !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd23b1cae930" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AIOps : Déboguer son cluster Kubernetes en utilisant l’intelligence artificielle générative via…]]></title>
            <link>https://deep75.medium.com/aiops-d%C3%A9boguer-son-cluster-kubernetes-en-utilisant-lintelligence-artificielle-g%C3%A9n%C3%A9rative-via-3924474de984?source=rss-9f1ca3c659fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/3924474de984</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[digitalocean]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Karim]]></dc:creator>
            <pubDate>Sat, 28 Dec 2024 14:57:15 GMT</pubDate>
            <atom:updated>2024-12-28T15:21:58.246Z</atom:updated>
            <content:encoded><![CDATA[<h3>AIOps : Déboguer son cluster Kubernetes en utilisant l’intelligence artificielle générative via K8sGPT et Ollama …</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OuCGvnBYusNcO42tyEnOgw.png" /></figure><p>Les avancées dans l’Intelligence Artificielle Générative et sa mise en oeuvre simplifiée via certains outils, transforment profondément la gestion des clusters Kubernetes via ce concept d’<strong>AIOps</strong> (acronyme anglais de <em>Artificial Intelligence for IT Operations</em>) énoncé par Gartner, un processus dans lequel vous utilisez des techniques d’intelligence artificielle (IA) pour maintenir par exemple une infrastructure. L’un des domaines dans lesquels les ingénieurs DevOps et les opérateurs de cluster débutants sont souvent confrontés, est relatif aux défis de l’identification, de la compréhension et de la résolution de problèmes au sein d’un cluster Kubernetes …</p><ul><li><a href="https://fr.wikipedia.org/wiki/AIOps">AIOps - Wikipédia</a></li><li><a href="https://aws.amazon.com/fr/what-is/aiops/">Qu&#39;est-ce que l&#39;intelligence artificielle pour les opérations informatiques (AIOps) ? - Explication de l&#39;intelligence artificielle pour les opérations informatiques - AWS</a></li><li><a href="https://fr.wikipedia.org/wiki/Intelligence_artificielle_g%C3%A9n%C3%A9rative">Intelligence artificielle générative - Wikipédia</a></li></ul><p>Dans cet article, nous allons donc explorer comment configurer et utiliser K8sGPT, un outil open source basé sur l’IA générative, en combinaison avec Ollama et le modèle Falcon3, pour identifier et résoudre les problèmes dans un cluster Kubernetes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/0*Tpd8dKAYwDyr_NZa.jpg" /></figure><p>Pour cela, je pars ici d’une instance Ubuntu 24.04 LTS dans DigitalOcean :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*inAiTX6J7aQFAEve9X7hhA.png" /></figure><p>En y installant localement le moteur Docker …</p><pre>(base) root@k8sgpt:~# curl -fsSL https://get.docker.com | sh -<br># Executing docker install script, commit: 4c94a56999e10efcf48c5b8e3f6afea464f9108e<br>+ sh -c apt-get -qq update &gt;/dev/null<br>+ sh -c DEBIAN_FRONTEND=noninteractive apt-get -y -qq install ca-certificates curl &gt;/dev/null<br>Scanning processes...                                                                                                                                                                         <br>Scanning candidates...                                                                                                                                                                        <br>Scanning linux images...                                                                                                                                                                      <br>+ sh -c install -m 0755 -d /etc/apt/keyrings<br>+ sh -c curl -fsSL &quot;https://download.docker.com/linux/ubuntu/gpg&quot; -o /etc/apt/keyrings/docker.asc<br>+ sh -c chmod a+r /etc/apt/keyrings/docker.asc<br>+ sh -c echo &quot;deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu noble stable&quot; &gt; /etc/apt/sources.list.d/docker.list<br>+ sh -c apt-get -qq update &gt;/dev/null<br>+ sh -c DEBIAN_FRONTEND=noninteractive apt-get -y -qq install docker-ce docker-ce-cli containerd.io docker-compose-plugin docker-ce-rootless-extras docker-buildx-plugin &gt;/dev/null<br>Scanning processes...                                                                                                                                                                         <br>Scanning candidates...                                                                                                                                                                        <br>Scanning linux images...                                                                                                                                                                      <br>+ sh -c docker version<br>Client: Docker Engine - Community<br> Version:           27.4.1<br> API version:       1.47<br> Go version:        go1.22.10<br> Git commit:        b9d17ea<br> Built:             Tue Dec 17 15:45:46 2024<br> OS/Arch:           linux/amd64<br> Context:           default<br><br>Server: Docker Engine - Community<br> Engine:<br>  Version:          27.4.1<br>  API version:      1.47 (minimum version 1.24)<br>  Go version:       go1.22.10<br>  Git commit:       c710b88<br>  Built:            Tue Dec 17 15:45:46 2024<br>  OS/Arch:          linux/amd64<br>  Experimental:     false<br> containerd:<br>  Version:          1.7.24<br>  GitCommit:        88bf19b2105c8b17560993bee28a01ddc2f97182<br> runc:<br>  Version:          1.2.2<br>  GitCommit:        v1.2.2-0-g7cb3632<br> docker-init:<br>  Version:          0.19.0<br>  GitCommit:        de40ad0<br><br>================================================================================<br><br>To run Docker as a non-privileged user, consider setting up the<br>Docker daemon in rootless mode for your user:<br><br>    dockerd-rootless-setuptool.sh install<br><br>Visit https://docs.docker.com/go/rootless/ to learn about rootless mode.<br><br><br>To run the Docker daemon as a fully privileged service, but granting non-root<br>users access, refer to https://docs.docker.com/go/daemon-access/<br><br>WARNING: Access to the remote API on a privileged Docker daemon is equivalent<br>         to root access on the host. Refer to the &#39;Docker daemon attack surface&#39;<br>         documentation for details: https://docs.docker.com/go/attack-surface/<br><br>================================================================================</pre><p>Et je suis capable d’y lancer directmeent Ollama via son image officiellle pour exécuter des modèles de langage de grande taille (LLM) localement en y utilisant les CPU premium d’Intel présents dans l’instance Ubuntu :</p><p><a href="https://ollama.com/blog/ollama-is-now-available-as-an-official-docker-image">Ollama is now available as an official Docker image · Ollama Blog</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nUhRlxxO7BfGZr1jewh6fQ.png" /></figure><pre>(base) root@k8sgpt:~# docker run -d -v ollama:/root/.ollama -p 11434:11434 --name ollama ollama/ollama:latest<br>Unable to find image &#39;ollama/ollama:latest&#39; locally<br>latest: Pulling from ollama/ollama<br>6414378b6477: Pull complete <br>9423a26b200c: Pull complete <br>629da9618c4f: Pull complete <br>00b71e3f044c: Pull complete <br>Digest: sha256:18bfb1d605604fd53dcad20d0556df4c781e560ebebcd923454d627c994a0e37<br>Status: Downloaded newer image for ollama/ollama:latest<br>7b09d9fcdacff4319e553c41f741a15266eb5a5ec745959363e7754c53a203ef<br><br><br>(base) root@k8sgpt:~# docker ps -a<br>CONTAINER ID   IMAGE                  COMMAND               CREATED              STATUS              PORTS                                           NAMES<br>7b09d9fcdacf   ollama/ollama:latest   &quot;/bin/ollama serve&quot;   About a minute ago   Up About a minute   0.0.0.0:11434-&gt;11434/tcp, :::11434-&gt;11434/tcp   ollama<br></pre><pre>(base) root@k8sgpt:~# netstat -tunlp<br>Active Internet connections (only servers)<br>Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    <br>tcp        0      0 0.0.0.0:11434           0.0.0.0:*               LISTEN      46227/docker-proxy  <br>tcp        0      0 127.0.0.54:53           0.0.0.0:*               LISTEN      744/systemd-resolve <br>tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      744/systemd-resolve <br>tcp6       0      0 :::22                   :::*                    LISTEN      1/init              <br>tcp6       0      0 :::11434                :::*                    LISTEN      46235/docker-proxy  <br>udp        0      0 127.0.0.54:53           0.0.0.0:*                           744/systemd-resolve <br>udp        0      0 127.0.0.53:53           0.0.0.0:*                           744/systemd-resolve</pre><p>Et en y chargeant le grand modèle <strong>Falcon 3</strong> développé par le Technology Innovation Institute (TII) d’Abu Dhab et présent dans la bibliothèque de grands modèles d’Ollama :</p><ul><li><a href="https://huggingface.co/blog/falcon3">Welcome to the Falcon 3 Family of Open Models!</a></li><li><a href="https://ollama.com/library/falcon3">falcon3</a></li></ul><pre>(base) root@k8sgpt:~# docker exec -it ollama ollama pull falcon3<br>pulling manifest <br>pulling 3717a52b7aea... 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 4.6 GB                         <br>pulling 803b5adc3448... 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  218 B                         <br>pulling 58f83c52a4e3... 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  13 KB                         <br>pulling 35e31ed4c388... 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  101 B                         <br>pulling acb75345e14b... 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  487 B                         <br>verifying sha256 digest <br>writing manifest <br>success <br>(base) root@k8sgpt:~# docker exec -it ollama ollama list<br>NAME              ID              SIZE      MODIFIED       <br>falcon3:latest    472ea1c89f64    4.6 GB    11 seconds ago</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/0*EOpSifDpZbra9th8.jpg" /></figure><p>Je peux à cette étape y charger K8sGPT, un outil pour scanner vos clusters kubernetes, diagnostiquer et trier les problèmes en anglais simple. Il dispose d’une expérience SRE codifiée dans ses analyseurs et aide à extraire les informations les plus pertinentes pour les enrichir avec de l’IA générative.</p><p><strong>K8sGPT fonctionne en trois étapes</strong> :</p><ul><li>Extraction : Récupération des détails de configuration de toutes les charges de travail déployées dans le cluster.</li><li>Filtration : Un composant appelé « analyzer » filtre les données nécessaires.</li><li>Génération : Les données filtrées sont traitées pour générer des insights et des rapports en anglais simple.</li></ul><p><a href="https://k8sgpt.ai/">K8sGPT</a></p><pre>(base) root@k8sgpt:~# curl -LO https://github.com/k8sgpt-ai/k8sgpt/releases/download/v0.3.48/k8sgpt_amd64.deb<br>  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current<br>                                 Dload  Upload   Total   Spent    Left  Speed<br>  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0<br>100 34.5M  100 34.5M    0     0  30.5M      0  0:00:01  0:00:01 --:--:-- 30.5M<br>(base) root@k8sgpt:~# dpkg -i k8sgpt_amd64.deb <br>(Reading database ... 74447 files and directories currently installed.)<br>Preparing to unpack k8sgpt_amd64.deb ...<br>Unpacking k8sgpt (0.3.48) over (0.3.48) ...<br>Setting up k8sgpt (0.3.48) ...<br><br><br>(base) root@k8sgpt:~# k8sgpt<br>Kubernetes debugging powered by AI<br><br>Usage:<br>  k8sgpt [command]<br><br>Available Commands:<br>  analyze         This command will find problems within your Kubernetes cluster<br>  auth            Authenticate with your chosen backend<br>  cache           For working with the cache the results of an analysis<br>  completion      Generate the autocompletion script for the specified shell<br>  custom-analyzer Manage a custom analyzer<br>  dump            Creates a dumpfile for debugging issues with K8sGPT<br>  filters         Manage filters for analyzing Kubernetes resources<br>  generate        Generate Key for your chosen backend (opens browser)<br>  help            Help about any command<br>  integration     Integrate another tool into K8sGPT<br>  serve           Runs k8sgpt as a server<br>  version         Print the version number of k8sgpt<br><br>Flags:<br>      --config string        Default config file (/root/.config/k8sgpt/k8sgpt.yaml)<br>  -h, --help                 help for k8sgpt<br>      --kubeconfig string    Path to a kubeconfig. Only required if out-of-cluster.<br>      --kubecontext string   Kubernetes context to use. Only required if out-of-cluster.<br><br>Use &quot;k8sgpt [command] --help&quot; for more information about a command.</pre><p>La ligne de commande est alors disponible pour y vérifier les fournisseurs disponibles localement dans cette instance :</p><p><a href="https://docs.k8sgpt.ai/getting-started/installation/">Installation</a></p><pre><br>(base) root@k8sgpt:~# k8sgpt auth list<br>Default: <br>&gt; openai<br>Active: <br>Unused: <br>&gt; openai<br>&gt; localai<br>&gt; ollama<br>&gt; azureopenai<br>&gt; cohere<br>&gt; amazonbedrock<br>&gt; amazonsagemaker<br>&gt; google<br>&gt; noopai<br>&gt; huggingface<br>&gt; googlevertexai<br>&gt; oci<br>&gt; ibmwatsonxai</pre><p>Ollama sera utilisé comme fournisseur de backend IA pour K8sGPT au travers de LocalAI (qui agit comme l’API REST de remplacement compatible avec les spécifications de l’API OpenAI pour une inférence locale).</p><ul><li><a href="https://docs.k8sgpt.ai/reference/providers/backend/">Overview - k8sgpt</a></li><li><a href="https://localai.io/">Overview</a></li></ul><p>Voici la commande pour configurer K8sGPT avec Ollama et le modèle Falcon3 :</p><pre>(base) root@k8sgpt:~# k8sgpt auth add --backend localai --model falcon3 --baseurl http://localhost:11434/v1<br>localai added to the AI backend provider list</pre><p>Je lance un cluster Kubernetes managé sur DigitalOcean via DigitalOcean Kubernetes (DOKS) :</p><p><a href="https://www.digitalocean.com/products/kubernetes">DigitalOcean Managed Kubernetes | Starting at $12/mo.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zPQZV_ngoK5yePNmpOF_Zg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P6Q-MnVn3fhiW5ME9cVO7A.png" /></figure><p>Récupération du fichier <strong><em>Kubeconfig </em></strong>depuis ce cluster pour l’insérer localement sur l’instance Ubuntu pour l’utiliser avec le client <strong><em>Kubectl</em></strong> :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*k6_26ZWMfITa1l4FipwpPQ.png" /></figure><pre>(base) root@k8sgpt:~# curl -LO https://dl.k8s.io/release/v1.32.0/bin/linux/amd64/kubectl &amp;&amp; chmod +x ./kubectl &amp;&amp; mv kubectl /usr/local/bin/ &amp;&amp; kubectl<br>  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current<br>                                 Dload  Upload   Total   Spent    Left  Speed<br>100   138  100   138    0     0   1000      0 --:--:-- --:--:-- --:--:--  1007<br>100 54.6M  100 54.6M    0     0   120M      0 --:--:-- --:--:-- --:--:--  120M<br>kubectl controls the Kubernetes cluster manager.<br><br> Find more information at: https://kubernetes.io/docs/reference/kubectl/<br><br>Basic Commands (Beginner):<br>  create          Create a resource from a file or from stdin<br>  expose          Take a replication controller, service, deployment or pod and expose it as a new Kubernetes service<br>  run             Run a particular image on the cluster<br>  set             Set specific features on objects<br><br>Basic Commands (Intermediate):<br>  explain         Get documentation for a resource<br>  get             Display one or many resources<br>  edit            Edit a resource on the server<br>  delete          Delete resources by file names, stdin, resources and names, or by resources and label selector<br><br>Deploy Commands:<br>  rollout         Manage the rollout of a resource<br>  scale           Set a new size for a deployment, replica set, or replication controller<br>  autoscale       Auto-scale a deployment, replica set, stateful set, or replication controller<br><br>Cluster Management Commands:<br>  certificate     Modify certificate resources<br>  cluster-info    Display cluster information<br>  top             Display resource (CPU/memory) usage<br>  cordon          Mark node as unschedulable<br>  uncordon        Mark node as schedulable<br>  drain           Drain node in preparation for maintenance<br>  taint           Update the taints on one or more nodes<br><br>Troubleshooting and Debugging Commands:<br>  describe        Show details of a specific resource or group of resources<br>  logs            Print the logs for a container in a pod<br>  attach          Attach to a running container<br>  exec            Execute a command in a container<br>  port-forward    Forward one or more local ports to a pod<br>  proxy           Run a proxy to the Kubernetes API server<br>  cp              Copy files and directories to and from containers<br>  auth            Inspect authorization<br>  debug           Create debugging sessions for troubleshooting workloads and nodes<br>  events          List events<br><br>Advanced Commands:<br>  diff            Diff the live version against a would-be applied version<br>  apply           Apply a configuration to a resource by file name or stdin<br>  patch           Update fields of a resource<br>  replace         Replace a resource by file name or stdin<br>  wait            Experimental: Wait for a specific condition on one or many resources<br>  kustomize       Build a kustomization target from a directory or URL<br><br>Settings Commands:<br>  label           Update the labels on a resource<br>  annotate        Update the annotations on a resource<br>  completion      Output shell completion code for the specified shell (bash, zsh, fish, or powershell)<br><br>Subcommands provided by plugins:<br><br>Other Commands:<br>  api-resources   Print the supported API resources on the server<br>  api-versions    Print the supported API versions on the server, in the form of &quot;group/version&quot;<br>  config          Modify kubeconfig files<br>  plugin          Provides utilities for interacting with plugins<br>  version         Print the client and server version information<br><br>Usage:<br>  kubectl [flags] [options]<br><br>Use &quot;kubectl &lt;command&gt; --help&quot; for more information about a given command.<br>Use &quot;kubectl options&quot; for a list of global command-line options (applies to all commands).</pre><pre>(base) root@k8sgpt:~# kubectl cluster-info<br>Kubernetes control plane is running at https://738af175-32d4-43e9-9e31-b7ae3058be3e.k8s.ondigitalocean.com<br>CoreDNS is running at https://738af175-32d4-43e9-9e31-b7ae3058be3e.k8s.ondigitalocean.com/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy<br><br>To further debug and diagnose cluster problems, use &#39;kubectl cluster-info dump&#39;.<br>(base) root@k8sgpt:~# kubectl get nodes -o wide<br>NAME                   STATUS   ROLES    AGE     VERSION   INTERNAL-IP   EXTERNAL-IP      OS-IMAGE                         KERNEL-VERSION   CONTAINER-RUNTIME<br>pool-kuaxj3k47-ejvl3   Ready    &lt;none&gt;   6m40s   v1.31.1   10.110.0.3    159.65.200.52    Debian GNU/Linux 12 (bookworm)   6.1.0-27-amd64   containerd://1.6.31<br>pool-kuaxj3k47-ejvl8   Ready    &lt;none&gt;   6m38s   v1.31.1   10.110.0.2    164.92.147.176   Debian GNU/Linux 12 (bookworm)   6.1.0-27-amd64   containerd://1.6.31<br>(base) root@k8sgpt:~# kubectl get po,svc -A<br>NAMESPACE     NAME                              READY   STATUS    RESTARTS      AGE<br>kube-system   pod/cilium-4gxht                  1/1     Running   0             6m46s<br>kube-system   pod/cilium-lw8gd                  1/1     Running   0             6m48s<br>kube-system   pod/coredns-c5c6457c-bnzfc        0/1     Running   0             36s<br>kube-system   pod/coredns-c5c6457c-nz6gr        0/1     Running   0             36s<br>kube-system   pod/cpc-bridge-proxy-ebpf-7ncbq   1/1     Running   0             55s<br>kube-system   pod/cpc-bridge-proxy-ebpf-qth8w   1/1     Running   0             55s<br>kube-system   pod/hubble-relay-67597fb8-kmlw5   1/1     Running   1 (51s ago)   8m40s<br>kube-system   pod/hubble-ui-79957d9f7b-4n9kj    2/2     Running   0             74s<br>kube-system   pod/konnectivity-agent-7ml7p      1/1     Running   0             61s<br>kube-system   pod/konnectivity-agent-tnf8j      1/1     Running   0             61s<br>kube-system   pod/kube-proxy-ebpf-4gt2z         1/1     Running   0             6m48s<br>kube-system   pod/kube-proxy-ebpf-ztjql         1/1     Running   0             6m46s<br><br>NAMESPACE     NAME                   TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                  AGE<br>default       service/kubernetes     ClusterIP   10.108.32.1     &lt;none&gt;        443/TCP                  9m54s<br>kube-system   service/hubble-peer    ClusterIP   10.108.54.62    &lt;none&gt;        443/TCP                  8m40s<br>kube-system   service/hubble-relay   ClusterIP   10.108.41.20    &lt;none&gt;        80/TCP                   8m40s<br>kube-system   service/hubble-ui      ClusterIP   10.108.52.164   &lt;none&gt;        80/TCP                   8m40s<br>kube-system   service/kube-dns       ClusterIP   10.108.32.10    &lt;none&gt;        53/UDP,53/TCP,9153/TCP   36s</pre><p>Installation d’Headlamp, une interface web qui remplace le dashboard traditionnel de Kubernetes, facile à utiliser et extensible.</p><ul><li><a href="https://headlamp.dev/">Headlamp</a></li><li><a href="https://github.com/headlamp-k8s/headlamp">GitHub - headlamp-k8s/headlamp: A Kubernetes web UI that is fully-featured, user-friendly and extensible</a></li></ul><blockquote>Headlamp a été créé pour combiner les fonctionnalités traditionnelles des autres interfaces web et tableaux de bord (c’est-à-dire pour lister et visualiser les ressources) avec des fonctionnalités supplémentaires.</blockquote><pre>(base) root@k8sgpt:~# kubectl apply -f https://raw.githubusercontent.com/kinvolk/headlamp/main/kubernetes-headlamp.yaml<br>service/headlamp created<br>deployment.apps/headlamp created<br>secret/headlamp-admin created<br>(base) root@k8sgpt:~# kubectl get po,svc -n kube-system<br>NAME                              READY   STATUS    RESTARTS        AGE<br>pod/cilium-4gxht                  1/1     Running   0               11m<br>pod/cilium-lw8gd                  1/1     Running   0               11m<br>pod/coredns-c5c6457c-bnzfc        1/1     Running   0               5m7s<br>pod/coredns-c5c6457c-nz6gr        1/1     Running   0               5m7s<br>pod/cpc-bridge-proxy-ebpf-7ncbq   1/1     Running   0               5m26s<br>pod/cpc-bridge-proxy-ebpf-qth8w   1/1     Running   0               5m26s<br>pod/csi-do-node-gxlmb             2/2     Running   0               4m24s<br>pod/csi-do-node-swqfv             2/2     Running   0               4m24s<br>pod/do-node-agent-7bgsh           1/1     Running   0               4m11s<br>pod/do-node-agent-hwt6l           1/1     Running   0               4m11s<br>pod/headlamp-7dfd97b98b-wmn66     1/1     Running   0               48s<br>pod/hubble-relay-67597fb8-kmlw5   1/1     Running   1 (5m22s ago)   13m<br>pod/hubble-ui-79957d9f7b-4n9kj    2/2     Running   0               5m45s<br>pod/konnectivity-agent-7ml7p      1/1     Running   0               5m32s<br>pod/konnectivity-agent-tnf8j      1/1     Running   0               5m32s<br>pod/kube-proxy-ebpf-4gt2z         1/1     Running   0               11m<br>pod/kube-proxy-ebpf-ztjql         1/1     Running   0               11m<br><br>NAME                   TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                  AGE<br>service/headlamp       ClusterIP   10.108.38.247   &lt;none&gt;        80/TCP                   48s<br>service/hubble-peer    ClusterIP   10.108.54.62    &lt;none&gt;        443/TCP                  13m<br>service/hubble-relay   ClusterIP   10.108.41.20    &lt;none&gt;        80/TCP                   13m<br>service/hubble-ui      ClusterIP   10.108.52.164   &lt;none&gt;        80/TCP                   13m<br>service/kube-dns       ClusterIP   10.108.32.10    &lt;none&gt;        53/UDP,53/TCP,9153/TCP   5m7s</pre><p>en l’exposant localement et récupérant la clé nécessaire à l’accès à son interface web :</p><pre>(base) root@k8sgpt:~# nohup kubectl port-forward -n kube-system service/headlamp 8080:80 &amp;<br>(base) root@k8sgpt:~# cat nohup.out <br>Forwarding from 127.0.0.1:8080 -&gt; 4466<br>Forwarding from [::1]:8080 -&gt; 4466</pre><pre>(base) root@k8sgpt:~# kubectl -n kube-system create serviceaccount headlamp-admin<br>serviceaccount/headlamp-admin created<br><br>(base) root@k8sgpt:~# kubectl create clusterrolebinding headlamp-admin --serviceaccount=kube-system:headlamp-admin --clusterrole=cluster-admin<br>clusterrolebinding.rbac.authorization.k8s.io/headlamp-admin created<br><br>(base) root@k8sgpt:~# kubectl create token headlamp-admin -n kube-system<br>eyJhbGciOiJSUzI1NiIsImtpZCI6Ikd0UHltNHV6c1liSkY0VkhNRWFZMXJKYklqY1R6ckZrMDZQS281dEg3dUUifQ.eyJhdWQiOlsic3lzdGVtOmtvbm5lY3Rpdml0eS1zZXJ2ZXIiXSwiZXhwIjoxNzM1MzkyNDEwLCJpYXQiOjE3MzUzODg4MTAsImlzcyI6Imh0dHBzOi8va3ViZXJuZXRlcy5kZWZhdWx0LnN2Yy5jbHVzdGVyLmxvY2FsIiwianRpIjoiNTVkNjI1ZTItNjA2Yi00MTNhLTk2OTgtODFmYjdjZDU4MWY4Iiwia3ViZXJuZXRlcy5pbyI6eyJuYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsInNlcnZpY2VhY2NvdW50Ijp7Im5hbWUiOiJoZWFkbGFtcC1hZG1pbiIsInVpZCI6IjdmOGQwMTU0LWRiYWQtNGU2MS04NTUzLWU1NWI3ZWU0ZjhlOSJ9fSwibmJmIjoxNzM1Mzg4ODEwLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6a3ViZS1zeXN0ZW06aGVhZGxhbXAtYWRtaW4ifQ.jbrtuXS7uMP6HfwR3CbIbnpRTq4CDaacq0okwm_4tvmJNNcExi9-Dti3cGj1J3tteszpxVzurWPhrWgFlL4UkEacY9fD1TRH4GAZDCFldJ_jvyeaclzGeymrjEGAZ9TbBdoyuXtLeIVhApdICF1KNM-s8mfr1oOREDwlR9HzzrhoECozYxVS9uM1WIEZpum4FwMEl6cKPqOyNx1Rn5MtKPcc87JyK0FxuXzg9WC-cPSNOxu_rUFrZYHyrVapCDpl_XLymD3pFUUuB8XPVidVXcVOthH1Djwm8TRE6aAD4XlkHTcyTYchvN_CpOI2JQ6DVY60unSU8nq2pxfqLC6G2Q</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*91Ss8G6p5QuVLz4MDOy4hw.png" /></figure><p>Avant de lancer une analyse via K8sGPT, introduction d’un problème dans le cluster Kubernetes pour simuler une situation réelle. Vous pouvez utiliser des exemples de déploiements défectueux disponibles sur des répositories comme celui de Robusta :</p><p><a href="https://github.com/robusta-dev/kubernetes-demos">GitHub - robusta-dev/kubernetes-demos: YAMLs for creating Kubernetes errors and other scenarios</a></p><p>Exemple avec ce déploiement d’un Pod cassé via :</p><pre>apiVersion: apps/v1<br>kind: Deployment<br>metadata:<br>  name: payment-processing-worker<br>spec:<br>  replicas: 1<br>  selector:<br>    matchLabels:<br>      app: payment-processing-worker<br>  template:<br>    metadata:<br>      labels:<br>        app: payment-processing-worker<br>    spec:<br>      containers:<br>      - name: payment-processing-container<br>        image: bash<br>        command: [&quot;/bin/sh&quot;]<br>        args: [&quot;-c&quot;, &quot;if [[ -z \&quot;${DEPLOY_ENV}\&quot; ]]; then echo Environment variable DEPLOY_ENV is undefined ; else while true; do echo hello; sleep 10;done; fi&quot;]</pre><pre>base) root@k8sgpt:~# kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/crashpod/broken.yaml<br>deployment.apps/payment-processing-worker created<br><br>(base) root@k8sgpt:~# kubectl get po<br>NAME                                         READY   STATUS             RESTARTS      AGE<br>payment-processing-worker-747ccfb9db-dzjqx   0/1     CrashLoopBackOff   1 (11s ago)   17s<br><br>(base) root@k8sgpt:~# kubectl logs po/payment-processing-worker-747ccfb9db-dzjqx<br>Environment variable DEPLOY_ENV is undefined</pre><p>Il s’est en effet crashé …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IVhkm9V2T8uJcpOOx8Gnkw.png" /></figure><p>Lancement de l’analyse avec une sortie en JSON :</p><pre>(base) root@k8sgpt:~# k8sgpt analyze -o json --explain --filter=Pod --backend localai |  jq .<br><br>{<br>  &quot;provider&quot;: &quot;localai&quot;,<br>  &quot;errors&quot;: null,<br>  &quot;status&quot;: &quot;ProblemDetected&quot;,<br>  &quot;problems&quot;: 1,<br>  &quot;results&quot;: [<br>    {<br>      &quot;kind&quot;: &quot;Pod&quot;,<br>      &quot;name&quot;: &quot;default/payment-processing-worker-747ccfb9db-dzjqx&quot;,<br>      &quot;error&quot;: [<br>        {<br>          &quot;Text&quot;: &quot;the last termination reason is Completed container=payment-processing-container pod=payment-processing-worker-747ccfb9db-dzjqx&quot;,<br>          &quot;KubernetesDoc&quot;: &quot;&quot;,<br>          &quot;Sensitive&quot;: []<br>        }<br>      ],<br>      &quot;details&quot;: &quot;Error: The pod \&quot;payment-processing-worker-747ccfb9db-dzjqx\&quot; has completed its execution with a \&quot;Completed\&quot; termination reason, indicating the container \&quot;payment-processing-container\&quot; has finished successfully.\n\nSolution: Verify the logs for the container to ensure data integrity, then check related services for expected outcomes; if successful, mark the pod as ready in the cluster.&quot;,<br>      &quot;parentObject&quot;: &quot;Deployment/payment-processing-worker&quot;<br>    }<br>  ]<br>}</pre><p>ou en mode texte :</p><pre>(base) root@k8sgpt:~# k8sgpt analyze --explain --backend localai --with-doc<br> 100% |████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| (1/1, 7960 it/s)        <br>AI Provider: localai<br><br>0: Pod default/payment-processing-worker-747ccfb9db-dzjqx(Deployment/payment-processing-worker)<br>- Error: the last termination reason is Completed container=payment-processing-container pod=payment-processing-worker-747ccfb9db-dzjqx<br>Error: The pod &quot;payment-processing-worker-747ccfb9db-dzjqx&quot; has completed its execution with a &quot;Completed&quot; termination reason, indicating the container &quot;payment-processing-container&quot; has finished successfully.<br><br>Solution: Verify the logs for the container to ensure data integrity, then check related services for expected outcomes; if successful, mark the pod as ready in the cluster.</pre><p>Comme le montre cette sortie, K8sGPT a identifié et signalé le pod problématique et a également fourni des conseils sur les mesures potentielles à prendre pour comprendre et résoudre le problème.</p><p>Autre exemple avec ce Pod Nginx problématique :</p><pre>apiVersion: v1<br>kind: Pod<br>metadata:<br>  name: inventory-management-api<br>spec:<br>  containers:<br>  - name: nginx<br>    image: nginx<br>    ports:<br>    - containerPort: 80<br>    command:<br>      - wge<br>      - &quot;-O&quot;<br>      - &quot;/work-dir/index.html&quot;<br>      - https://home.robusta.dev</pre><pre>(base) root@k8sgpt:~# kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/refs/heads/main/crashloop_backoff/create_crashloop_backoff.yaml<br>pod/inventory-management-api created<br><br>(base) root@k8sgpt:~# kubectl get po<br>NAME                       READY   STATUS              RESTARTS   AGE<br>inventory-management-api   0/1     ContainerCreating   0          5s<br><br>(base) root@k8sgpt:~# kubectl get po<br>NAME                       READY   STATUS              RESTARTS     AGE<br>inventory-management-api   0/1     RunContainerError   1 (1s ago)   10s</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TWFdmL8eE_tPJ-cZ9cY4qw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a8PmuDf8LY3NrGAwJZ0viQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*npkAOOzjBUaBTl2a-l3MNQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zphI-iUg4XAz5YtO45eQ_A.png" /></figure><p>Et une nouvelle analyse met le doigt sur le Pod problématique …</p><pre>(base) root@k8sgpt:~# k8sgpt analyze --explain --backend localai --with-doc<br> 100% |████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| (1/1, 2 it/min)         <br>AI Provider: localai<br><br>0: Pod default/inventory-management-api()<br>- Error: the last termination reason is StartError container=nginx pod=inventory-management-api<br>Error: The Kubernetes error indicates that there was a StartError issue with the nginx container for the pod named inventory-management-api.<br><br>Solution: <br>1. Check the nginx configuration file for syntax errors.<br>2. Ensure all required resources and permissions are correctly set.<br>3. Verify network accessibility within the pod.<br>4. Confirm proper image pull secrets if using Docker images.<br>5. Review any recent changes to the deployment or service configurations.</pre><p>Dans cet autre exemple il peut ne pas détecter de problématique avec cette simulation de faux positif via busybox :</p><pre>apiVersion: batch/v1<br>kind: Job<br>metadata:<br>  name: java-api-checker<br>spec:<br>  template:<br>    spec:<br>      containers:<br>      - name: java-beans<br>        image: busybox<br>        command: [&quot;/bin/sh&quot;, &quot;-c&quot;]<br>        args: [&quot;echo &#39;Java Network Exception: \nAll host(s) tried for db query failed (tried: prod-db:3333) - no available connection and the queue has reached its max size 256 \nAll host(s) tried for db query failed (tried: prod-db:3333) - no available connection and the queue has reached its max size 256 \nAll host(s) tried for db query failed (tried: prod-db:3333) - no available connection and the queue has reached its max size 256 \nAll host(s) tried for db query failed (tried: prod-db:3333) - no available connection and the queue has reached its max size 256&#39;; sleep 60; exit 1&quot;]<br>      restartPolicy: Never<br>  backoffLimit: 1</pre><pre>(base) root@k8sgpt:~# kubectl delete -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/refs/heads/main/crashloop_backoff/create_crashloop_backoff.yaml<br>pod &quot;inventory-management-api&quot; deleted<br>(base) root@k8sgpt:~# kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/refs/heads/main/job_failure/job_crash.yaml<br>job.batch/java-api-checker created<br><br>(base) root@k8sgpt:~# kubectl get po<br>NAME                     READY   STATUS    RESTARTS   AGE<br>java-api-checker-5s6dc   1/1     Running   0          7s<br>(base) root@k8sgpt:~# kubectl logs po/java-api-checker-5s6dc<br>Java Network Exception: <br>All host(s) tried for db query failed (tried: prod-db:3333) - no available connection and the queue has reached its max size 256 <br>All host(s) tried for db query failed (tried: prod-db:3333) - no available connection and the queue has reached its max size 256 <br>All host(s) tried for db query failed (tried: prod-db:3333) - no available connection and the queue has reached its max size 256 <br>All host(s) tried for db query failed (tried: prod-db:3333) - no available connection and the queue has reached its max size 256</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7GVW2FVudO9MAgI8uKiPuA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fH2TzOWaXea4dCBsv9RcZw.png" /></figure><pre>(base) root@k8sgpt:~# k8sgpt analyze --explain --backend localai --with-doc<br>AI Provider: localai<br><br>No problems detected</pre><blockquote>Pour une intégration plus complète, vous pouvez installer l’opérateur K8sGPT dans votre cluster Kubernetes. Cet opérateur surveille en continu les problèmes dans le cluster et génère des insights que vous pouvez consulter en interrogeant la ressource personnalisée (CR) de l&#39;opérateur.</blockquote><p><a href="https://github.com/k8sgpt-ai/k8sgpt-operator">GitHub - k8sgpt-ai/k8sgpt-operator: Automatic SRE Superpowers within your Kubernetes cluster</a></p><pre>$ helm repo add k8sgpt https://charts.k8sgpt.ai/<br>$ helm repo update<br>$ helm install release k8sgpt/k8sgpt-operator -n k8sgpt-operator-system --create-namespace</pre><pre># Installer l&#39;opérateur k8sGPT<br>$ kubectl apply -n k8sgpt-operator-system -f - &lt;&lt; EOF<br>apiVersion: core.k8sgpt.ai/v1alpha1<br>kind: K8sGPT<br>metadata:<br>  name: k8sgpt-ollama<br>spec:<br>  ai:<br>    enabled: true<br>    model: falcon3<br>    backend: localai<br>    baseUrl: http://localhost:11434/v1<br>  noCache: false<br>  filters: [&quot;Pod&quot;]<br>  repository: ghcr.io/k8sgpt-ai/k8sgpt<br>  version: v0.3.48<br>EOF</pre><p><a href="https://www.suse.com/c/rancher_blog/debugging-your-rancher-kubernetes-cluster-the-genai-way-with-k8sgpt-ollama-rancher-desktop/">Debugging your Rancher Kubernetes Cluster the GenAI Way w...</a></p><p>Il est également possible d’analyser plusieurs clusters Kubernetes en spécifiant le chemin vers le fichier Kubeconfig concerné :</p><pre>$ k8sgpt analyze --explain --backend localai --with-doc --kubeconfig &lt;chemin vers le fichier Kubeconfig&gt;</pre><blockquote>L’opérateur recherchera les problèmes dans le cluster et générera des résultats d’analyse.</blockquote><p>En fonction de la puissance de votre machine (pour accélerer les temps de réponse d’Ollama, des ressources GPU sont nécessaires), il faut un certain temps à l’opérateur pour appeler le LLM et générer les informations …</p><p>Pour conclure, K8sGPT en combinaison avec Ollama offre une solution puissante pour déboguer et gérer les clusters Kubernetes de manière efficace. Cette intégration utilise l&#39;intelligence artificielle pour fournir des insights clairs et des recommandations pour résoudre les problèmes, simplifiant ainsi la vie des opérateurs de cluster. En suivant ces étapes, vous pouvez mettre en place une solution de diagnostic automatisée et basée sur l&#39;IA pour votre environnement Kubernetes …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*GK4ioQHW8Gb3Bq3c.jpg" /></figure><p>À suivre !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3924474de984" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OpenStack sur Kubernetes en toute simplicité avec Canonical MicroStack et Pulumi …]]></title>
            <link>https://deep75.medium.com/openstack-sur-kubernetes-en-toute-simplicit%C3%A9-avec-canonical-microstack-et-pulumi-abdbcf41b127?source=rss-9f1ca3c659fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/abdbcf41b127</guid>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[openstack]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[digitalocean]]></category>
            <dc:creator><![CDATA[Karim]]></dc:creator>
            <pubDate>Tue, 24 Dec 2024 12:48:32 GMT</pubDate>
            <atom:updated>2024-12-24T13:02:31.292Z</atom:updated>
            <content:encoded><![CDATA[<h3>OpenStack sur Kubernetes en toute simplicité avec Canonical MicroStack et Pulumi …</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*orTxPiajre8BVs_BJFuJVg.png" /></figure><p>MicroStack est une solution développée par Canonical, utilisant Snap, Juju et Kubernetes pour déployer et gérer OpenStack. Cette solution simplifie considérablement la complexité traditionnellement associée à la gestion des clouds OpenStack. Elle a évolué comme je le relatais auparavant dans différents articles en y insérant Canonical Kubernetes :</p><ul><li><a href="https://deep75.medium.com/k8s-snap-canonical-kubernetes-pour-un-d%C3%A9ploiement-simple-et-rapide-dun-cluster-k8s-3a60f52838b4">k8s-snap (Canonical Kubernetes) pour un déploiement simple et rapide d’un cluster k8s …</a></li><li><a href="https://deep75.medium.com/un-cluster-openstack-sur-sa-station-en-une-minute-avec-microstack-8da478196299">Un cluster OpenStack sur sa station en une minute avec Microstack …</a></li><li><a href="https://deep75.medium.com/mise-en-oeuvre-dun-service-mesh-avec-microstack-linkerd-2-x-et-k3s-23242310246c">Mise en oeuvre d’un Service Mesh avec MicroStack, Linkerd 2.x et K3S …</a></li></ul><h3>Avantages de MicroStack</h3><p><a href="https://canonical.com/microstack">OpenStack on Kubernetes | Ubuntu | Canonical</a></p><ul><li><strong>Déploiement Simplifié</strong> : MicroStack offre un processus d’installation rationalisé, capable de démarrer un déploiement cloud en moins de 6 commandes, avec un temps de déploiement moyen de 40 minutes. Cela le rend particulièrement adapté aux organisations qui cherchent à établir ou à étendre rapidement un environnement Cloud sans disposer d’une expertise technique approfondie.</li><li><strong>Flexibilité et Customisation</strong> : MicroStack permet une grande flexibilité, incluant l’intégration d’un large éventail de plug-ins et d’extensions, ce qui permet aux entreprises de construire un environnement Cloud qui s’aligne précisément sur leurs objectifs opérationnels.</li></ul><p>Mise en oeuvre concrète de Microstack sur un noeud unique selon ces préconisations techniques :</p><p><a href="https://canonical.com/microstack/docs/enterprise-reqs">Enterprise requirements | Canonical</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JyVM_hxDvQxxhrhbKrVE4g.png" /></figure><p>Je pars donc d’une instance dédiée sur DigitalOcean autorisant la virtualisation imbriquée :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SOAaKwRYf9UGfHkCGF4FVA.png" /></figure><p>Pour installer MicroStack sur un nœud unique, vous pouvez suivre ces étapes. Pour commencer, création d’un utilisateur non root avec sudo activé :</p><pre>root@microstack:~# useradd -s /bin/bash -d /home/ubuntu -m ubuntu<br>root@microstack:~# echo &quot;ubuntu ALL=(ALL) NOPASSWD: ALL&quot; | tee /etc/sudoers.d/ubuntu<br>ubuntu ALL=(ALL) NOPASSWD: ALL<br>root@microstack:~# cp -r .ssh/ /home/ubuntu/<br>root@microstack:~# chown -R ubuntu:ubuntu /home/ubuntu/.ssh/</pre><p>Puis installation de snapd :</p><pre>ubuntu@microstack:~$ sudo apt install snapd<br>Reading package lists... Done<br>Building dependency tree... Done<br>Reading state information... Done<br>Suggested packages:<br>  zenity | kdialog<br>The following packages will be upgraded:<br>  snapd<br>1 upgraded, 0 newly installed, 0 to remove and 195 not upgraded.<br>Need to get 30.0 MB of archives.<br>After this operation, 5513 kB of additional disk space will be used.<br>Get:1 http://mirrors.digitalocean.com/ubuntu noble-updates/main amd64 snapd amd64 2.66.1+24.04 [30.0 MB]<br>Fetched 30.0 MB in 0s (93.2 MB/s)<br>(Reading database ... 71895 files and directories currently installed.)<br>Preparing to unpack .../snapd_2.66.1+24.04_amd64.deb ...<br>Unpacking snapd (2.66.1+24.04) over (2.63+24.04) ...<br>Setting up snapd (2.66.1+24.04) ...<br>Installing new version of config file /etc/apparmor.d/usr.lib.snapd.snap-confine.real ...<br>snapd.failure.service is a disabled or a static unit not running, not starting it.<br>snapd.snap-repair.service is a disabled or a static unit not running, not starting it.<br>Processing triggers for dbus (1.14.10-4ubuntu4) ...<br>Processing triggers for man-db (2.12.0-4build2) ...<br>Scanning processes...                                                                                                                                                                         <br>Scanning linux images...                                                                                                                                                                      <br><br>Running kernel seems to be up-to-date.<br><br>No services need to be restarted.<br><br>No containers need to be restarted.<br><br>No user sessions are running outdated binaries.<br><br>No VM guests are running outdated hypervisor (qemu) binaries on this host.<br>ubuntu@microstack:~$ sudo systemctl enable --now snapd</pre><p>Installation de MicroStack via la dernière version avec snapd :</p><p><a href="https://snapcraft.io/openstack">Install Canonical MicroStack on Linux | Snap Store</a></p><pre>ubuntu@microstack:~$ sudo snap install openstack --channel 2024.1/beta<br>2024-12-24T08:58:22Z INFO Waiting for automatic snapd restart...<br>openstack (2024.1/beta) 2024.1 from Canonical✓ installed<br>ubuntu@microstack:~$ sudo snap list<br>Name       Version   Rev    Tracking       Publisher   Notes<br>core24     20240920  609    latest/stable  canonical✓  base<br>openstack  2024.1    637    2024.1/beta    canonical✓  -<br>snapd      2.66.1    23258  latest/stable  canonical✓  snapd</pre><p>MicroStack utilise Sunbeam pour générer un script qui s’assure que la machine dispose de toutes les dépendances nécessaires et qu’elle est configurée correctement pour être utilisée dans OpenStack. Lancement de ce dernier de manière directe :</p><pre>ubuntu@microstack:~$ sunbeam prepare-node-script | bash -x &amp;&amp; newgrp snap_daemon<br>++ lsb_release -sc<br>+ &#39;[&#39; noble &#39;!=&#39; noble &#39;]&#39;<br>++ whoami<br>+ USER=ubuntu<br>++ id -u<br>+ &#39;[&#39; 1000 -eq 0 -o ubuntu = root &#39;]&#39;<br>+ SUDO_ASKPASS=/bin/false<br>+ sudo -A whoami<br>+ sudo grep -r ubuntu /etc/sudoers /etc/sudoers.d<br>+ grep NOPASSWD:ALL<br>+ echo &#39;ubuntu ALL=(ALL) NOPASSWD:ALL&#39;<br>+ sudo install -m 440 /tmp/90-ubuntu-sudo-access /etc/sudoers.d/90-ubuntu-sudo-access<br>+ rm -f /tmp/90-ubuntu-sudo-access<br>+ dpkg -s openssh-server<br>+ dpkg -s curl<br>+ sudo usermod --append --groups snap_daemon ubuntu<br>+ &#39;[&#39; -f /home/ubuntu/.ssh/id_rsa &#39;]&#39;<br>+ ssh-keygen -b 4096 -f /home/ubuntu/.ssh/id_rsa -t rsa -N &#39;&#39;<br>Generating public/private rsa key pair.<br>Your identification has been saved in /home/ubuntu/.ssh/id_rsa<br>Your public key has been saved in /home/ubuntu/.ssh/id_rsa.pub<br>The key fingerprint is:<br>SHA256:NTnupee3yat23zAuoYy5U6VoXqK+JaU5R3L36nwrauM ubuntu@microstack<br>The key&#39;s randomart image is:<br>+---[RSA 4096]----+<br>|                 |<br>|           .     |<br>|          =      |<br>|         o o.    |<br>|      . S.oo.    |<br>|       B+o++.    |<br>|      =+oBo.o.o  |<br>|      .=B.+++oo+.|<br>|     .o+E*+++**+o|<br>+----[SHA256]-----+<br>+ cat /home/ubuntu/.ssh/id_rsa.pub<br>++ hostname --all-ip-addresses<br>+ ssh-keyscan -H 134.209.225.128 10.19.0.5 10.114.0.2<br># 134.209.225.128:22 SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.4<br># 134.209.225.128:22 SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.4<br># 134.209.225.128:22 SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.4<br># 134.209.225.128:22 SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.4<br># 134.209.225.128:22 SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.4<br># 10.19.0.5:22 SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.4<br># 10.19.0.5:22 SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.4<br># 10.19.0.5:22 SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.4<br># 10.19.0.5:22 SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.4<br># 10.19.0.5:22 SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.4<br># 10.114.0.2:22 SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.4<br># 10.114.0.2:22 SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.4<br># 10.114.0.2:22 SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.4<br># 10.114.0.2:22 SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.4<br>10.114.0.2: Connection closed by remote host<br>+ grep -E &#39;HTTPS?_PROXY&#39; /etc/environment<br>+ curl -s -m 10 -x &#39;&#39; api.charmhub.io<br>+ sudo snap connect openstack:ssh-keys<br>+ sudo snap install --channel 3.6/stable juju<br>juju (3.6/stable) 3.6.1 from Canonical✓ installed<br>+ mkdir -p /home/ubuntu/.local/share<br>+ mkdir -p /home/ubuntu/.config/openstack<br>++ snap list openstack --unicode=never --color=never<br>++ grep openstack<br>+ snap_output=&#39;openstack  2024.1   637  2024.1/beta  canonical**  -&#39;<br>++ awk -v col=4 &#39;{print $col}&#39;<br>+ track=2024.1/beta<br>+ [[ 2024.1/beta =~ edge ]]<br>+ [[ 2024.1/beta == \- ]]<br>+ [[ 2024.1/beta =~ beta ]]<br>+ risk=beta<br>+ [[ beta != \s\t\a\b\l\e ]]<br>+ sudo snap set openstack deployment.risk=beta<br>+ echo &#39;Snap has been automatically configured to deploy from&#39; &#39;beta channel.&#39;<br>Snap has been automatically configured to deploy from beta channel.<br>+ echo &#39;Override by passing a custom manifest with -m/--manifest.&#39;<br>Override by passing a custom manifest with -m/--manifest.</pre><p>Possibilité à cette étape de déployer le cloud OpenStack à l’aide de cette commande en acceptant les valeurs par défaut (cela prend environ 30 minutes en fonction de la vitesse de connexion) :</p><pre>ubuntu@microstack:~$ sunbeam cluster bootstrap --accept-defaults<br>Node has been bootstrapped with roles: compute, control</pre><pre>ubuntu@microstack:~$ sunbeam cluster list<br>                           controller                           <br>┏━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━┓<br>┃ Node       ┃ Cluster ┃ Machine ┃ Compute ┃ Control ┃ Storage ┃<br>┡━━━━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━━┩<br>│ microstack │ ONLINE  │ running │ active  │ active  │         │<br>└────────────┴─────────┴─────────┴─────────┴─────────┴─────────┘<br><br>ubuntu@microstack:~$ sudo systemctl status snap.openstack.clusterd.service<br>● snap.openstack.clusterd.service - Service for snap application openstack.clusterd<br>     Loaded: loaded (/etc/systemd/system/snap.openstack.clusterd.service; enabled; preset: enabled)<br>     Active: active (running) since Tue 2024-12-24 08:58:36 UTC; 1h 10min ago<br>   Main PID: 4497 (sunbeamd)<br>      Tasks: 18 (limit: 77123)<br>     Memory: 34.6M (peak: 39.2M)<br>        CPU: 11.947s<br>     CGroup: /system.slice/snap.openstack.clusterd.service<br>             └─4497 sunbeamd --state-dir /var/snap/openstack/common/state --socket-group snap_daemon --verbose</pre><p>MicroStack est alors déployé et on peut lancer l’environnement de démo qui crée un tenant préconfiguré (avec les accès au dashboard) :</p><pre>ubuntu@microstack:~$ sunbeam configure --accept-defaults --openrc demo-openrc<br>⠋ Generating openrc for cloud admin usage ... Writing openrc to demo-openrc ... done<br>The cloud has been configured for sample usage.<br>You can start using the OpenStack client or access the OpenStack dashboard at http://172.16.1.204:80/openstack-horizon </pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/622/0*nGSCmci55y41yJZ2.jpg" /></figure><p>Je dispose des identifiants pour ce dernier :</p><pre>ubuntu@microstack:~$ cat demo-openrc <br># openrc for demo<br>export OS_AUTH_URL=http://172.16.1.204/openstack-keystone/v3<br>export OS_USERNAME=demo<br>export OS_PASSWORD=C0jg0mAgdvD5<br>export OS_USER_DOMAIN_NAME=users<br>export OS_PROJECT_DOMAIN_NAME=users<br>export OS_PROJECT_NAME=demo<br>export OS_AUTH_VERSION=3<br>export OS_IDENTITY_API_VERSION=3</pre><p>Ou pour le compte admin :</p><pre>ubuntu@microstack:~$ sunbeam openrc &gt; admin-openrc<br>ubuntu@microstack:~$ cat admin-openrc <br># openrc for access to OpenStack<br>export OS_USERNAME=admin<br>export OS_PASSWORD=f7M1ey2dqpHo<br>export OS_AUTH_URL=http://172.16.1.204/openstack-keystone/v3<br>export OS_USER_DOMAIN_NAME=admin_domain<br>export OS_PROJECT_DOMAIN_NAME=admin_domain<br>export OS_PROJECT_NAME=admin<br>export OS_AUTH_VERSION=3<br>export OS_IDENTITY_API_VERSION=3</pre><p>Lancement rapide d’une instance de test :</p><pre>ubuntu@microstack:~$ sunbeam launch ubuntu --name instance1 <br>Launching an OpenStack instance ... <br>Access the instance by running the following command:<br>`ssh -i /home/ubuntu/snap/openstack/637/sunbeam ubuntu@172.16.2.31`<br><br>ubuntu@microstack:~$ source demo-openrc <br>ubuntu@microstack:~$ openstack server list<br>+--------------------------------------+-----------+--------+-----------------------------------------+--------+---------+<br>| ID                                   | Name      | Status | Networks                                | Image  | Flavor  |<br>+--------------------------------------+-----------+--------+-----------------------------------------+--------+---------+<br>| efe46971-56f4-4da4-9c6e-eebee2795b72 | instance1 | ACTIVE | demo-network=172.16.2.31, 192.168.0.166 | ubuntu | m1.tiny |<br>+--------------------------------------+-----------+--------+-----------------------------------------+--------+---------+</pre><p>J’accède ici au dashboard via une redirection ssh :</p><pre>$ ssh -L 0.0.0.0:8888:172.16.1.204:80 ubuntu@134.209.225.128</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CciOFlPoKcX2iyPDiP3F0A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1zD1YwoZMTImCfdAVhnbtQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1hpa71atYPPDLfrJJ4eavw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*odaRXmQ0Dsc-f6ad7dyKLw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SwaUlIAJI1_SzWm3rGA63Q.png" /></figure><p>Dans MicroStack, Sunbeam permet l’activation de plusieurs extensions intéressantes :</p><pre>ubuntu@microstack:~$ sunbeam enable --help<br>Usage: sunbeam enable [OPTIONS] COMMAND [ARGS]...<br><br>  Enable features.<br><br>Options:<br>  -m, --manifest FILE  Manifest file.<br>  -h, --help           Show this message and exit.<br><br>Commands:<br>  caas                   Enable Container as a Service feature.<br>  dns                    Enable dns service.<br>  images-sync            Enable images-sync service.<br>  ldap                   Enable ldap service.<br>  loadbalancer           Enable Loadbalancer service.<br>  observability          Enable Observability service.<br>  orchestration          Enable Orchestration service.<br>  pro                    Enable Ubuntu Pro across deployment.<br>  resource-optimization  Enable Resource Optimization service (watcher).<br>  secrets                Enable OpenStack Secrets service.<br>  telemetry              Enable OpenStack Telemetry applications.<br>  tls                    Enable tls group.<br>  validation             Enable OpenStack Integration Test Suite (tempest).<br>  vault                  Enable Vault.</pre><p>Activation de plusieures d’entre elles …</p><pre>ubuntu@microstack:~$ sunbeam enable orchestration<br>OpenStack orchestration application enabled.<br>ubuntu@microstack:~$ sunbeam enable telemetry<br>OpenStack telemetry application enabled.<br>ubuntu@microstack:~$ sunbeam enable observability embedded<br>Observability enabled.</pre><p>Dont celle relative à la stack d’observabilité mettant en oeuvre Grafana dont on obtient ici le lien et les identifiants :</p><p><a href="https://canonical.com/microstack/docs/observability">Observability | Canonical</a></p><pre><br>(base) ubuntu@microstack:~$ sunbeam observability dashboard-url<br>http://172.16.1.205/observability-grafana<br><br>(base) ubuntu@microstack:~$ juju run --model observability grafana/leader get-admin-password<br>Running operation 5 with 1 task<br>  - task 6 on unit-grafana-0<br><br>Waiting for task 6...<br>admin-password: 0EAJrXNIt3jd<br>url: http://172.16.1.205/observability-grafana</pre><p>Sunbeam utilise une série de manifestes dont on retrouve la liste à la suite de tous ces déploiements :</p><pre>ubuntu@microstack:~$ sunbeam manifest list<br>┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━┓<br>┃ ID                               ┃ Applied Date        ┃<br>┡━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━┩<br>│ ecd1a516be9a244376923e9f7b8217ce │ 2024-12-24 09:00:10 │<br>└──────────────────────────────────┴─────────────────────┘<br><br>ubuntu@microstack:~$ sunbeam manifest show ecd1a516be9a244376923e9f7b8217ce<br>core:<br>  software:<br>    charms:<br>      cinder-ceph-k8s:<br>        channel: 2024.1/beta<br>      cinder-k8s:<br>        channel: 2024.1/beta<br>      glance-k8s:<br>        channel: 2024.1/beta<br>      horizon-k8s:<br>        channel: 2024.1/beta<br>      keystone-k8s:<br>        channel: 2024.1/beta<br>      microceph:<br>        channel: squid/beta<br>        config:<br>          snap-channel: squid/beta<br>      neutron-k8s:<br>        channel: 2024.1/beta<br>      nova-k8s:<br>        channel: 2024.1/beta<br>      openstack-hypervisor:<br>        channel: 2024.1/beta<br>        config:<br>          snap-channel: 2024.1/beta<br>      ovn-central-k8s:<br>        channel: 24.03/beta<br>      ovn-relay-k8s:<br>        channel: 24.03/beta<br>      placement-k8s:<br>        channel: 2024.1/beta<br>      sunbeam-clusterd:<br>        channel: 2024.1/beta<br>        config:<br>          snap-channel: 2024.1/beta<br>      sunbeam-machine:<br>        channel: 2024.1/beta<br>features:<br>  caas:<br>    software:<br>      charms:<br>        magnum-k8s:<br>          channel: 2024.1/beta<br>  dns:<br>    software:<br>      charms:<br>        designate-bind-k8s:<br>          channel: 9/beta<br>        designate-k8s:<br>          channel: 2024.1/beta<br>  images-sync:<br>    software:<br>      charms:<br>        openstack-images-sync-k8s:<br>          channel: 2024.1/beta<br>  instance-recovery:<br>    software:<br>      charms:<br>        consul-client:<br>          channel: 1.19/beta<br>        consul-k8s:<br>          channel: 1.19/beta<br>        masakari-k8s:<br>          channel: 2024.1/beta<br>  ldap:<br>    software:<br>      charms:<br>        keystone-ldap-k8s:<br>          channel: 2024.1/beta<br>  loadbalancer:<br>    software:<br>      charms:<br>        octavia-k8s:<br>          channel: 2024.1/beta<br>  orchestration:<br>    software:<br>      charms:<br>        heat-k8s:<br>          channel: 2024.1/beta<br>  resource-optimization:<br>    software:<br>      charms:<br>        watcher-k8s:<br>          channel: 2024.1/beta<br>  secrets:<br>    software:<br>      charms:<br>        barbican-k8s:<br>          channel: 2024.1/beta<br>  telemetry:<br>    software:<br>      charms:<br>        aodh-k8s:<br>          channel: 2024.1/beta<br>        ceilometer-k8s:<br>          channel: 2024.1/beta<br>        gnocchi-k8s:<br>          channel: 2024.1/beta<br>        openstack-exporter-k8s:<br>          channel: 2024.1/beta<br>  validation:<br>    software:<br>      charms:<br>        tempest-k8s:<br>          channel: 2024.1/beta</pre><p>Dont on peut aussi vérifier la présence via Juju :</p><pre><br>ubuntu@microstack:~$ juju status -m admin/controller<br>Model       Controller          Cloud/Region      Version  SLA          Timestamp<br>controller  sunbeam-controller  one-deer/default  3.6.1    unsupported  10:04:08Z<br><br>SAAS                             Status   Store  URL<br>ceilometer                       waiting  local  microstack/openstack.ceilometer<br>cert-distributor                 active   local  microstack/openstack.cert-distributor<br>certificate-authority            active   local  microstack/openstack.certificate-authority<br>cinder-ceph                      blocked  local  microstack/openstack.cinder-ceph<br>grafana-dashboards               active   local  microstack/observability.grafana-dashboards<br>keystone-credentials             active   local  microstack/openstack.keystone-credentials<br>keystone-endpoints               active   local  microstack/openstack.keystone-endpoints<br>loki-logging                     active   local  microstack/observability.loki-logging<br>nova                             active   local  microstack/openstack.nova<br>ovn-relay                        active   local  microstack/openstack.ovn-relay<br>prometheus-receive-remote-write  active   local  microstack/observability.prometheus-receive-remote-write<br>rabbitmq                         active   local  microstack/openstack.rabbitmq<br><br>App                   Version  Status   Scale  Charm                 Channel         Rev  Exposed  Message<br>controller                     active       1  juju-controller       3.6/stable      116  no       <br>grafana-agent                  active       1  grafana-agent         latest/stable   260  no       tracing: off<br>k8s                   1.31.3   active       1  k8s                   1.31/candidate  141  no       Ready<br>microceph                      unknown      0  microceph             squid/beta       84  no       <br>openstack-hypervisor           waiting      1  openstack-hypervisor  2024.1/beta     221  no       (ceph-access) integration incomplete<br>sunbeam-machine                active       1  sunbeam-machine       2024.1/beta      49  no       <br><br>Unit                     Workload  Agent  Machine  Public address   Ports     Message<br>controller/0*            active    idle   0        134.209.225.128            <br>k8s/0*                   active    idle   0        134.209.225.128  6443/tcp  Ready<br>openstack-hypervisor/0*  waiting   idle   0        134.209.225.128            (ceph-access) integration incomplete<br>  grafana-agent/0*       active    idle            134.209.225.128            tracing: off<br>sunbeam-machine/0*       active    idle   0        134.209.225.128            <br><br>Machine  State    Address          Inst id  Base          AZ  Message<br>0        started  134.209.225.128  manual:  ubuntu@24.04      Manually provisioned machine<br><br>Offer      Application  Charm      Rev  Connected  Endpoint  Interface    Role<br>microceph  microceph    microceph  84   0/0        ceph      ceph-client  provider<br><br><br>ubuntu@microstack:~$ juju status -m openstack<br>Model      Controller          Cloud/Region            Version  SLA          Timestamp<br>openstack  sunbeam-controller  one-deer-k8s/localhost  3.6.1    unsupported  10:04:48Z<br><br>SAAS                             Status  Store  URL<br>grafana-dashboards               active  local  microstack/observability.grafana-dashboards<br>loki-logging                     active  local  microstack/observability.loki-logging<br>prometheus-receive-remote-write  active  local  microstack/observability.prometheus-receive-remote-write<br><br>App                       Version                  Status   Scale  Charm                     Channel        Rev  Address         Exposed  Message<br>aodh                                               active       1  aodh-k8s                  2024.1/beta     62  10.152.183.238  no       <br>aodh-mysql                8.0.37-0ubuntu0.22.04.3  active       1  mysql-k8s                 8.0/stable     180  10.152.183.134  no       <br>aodh-mysql-router         8.0.37-0ubuntu0.22.04.3  active       1  mysql-router-k8s          8.0/stable     155  10.152.183.200  no       <br>ceilometer                                         waiting      1  ceilometer-k8s            2024.1/beta     62  10.152.183.88   no       (workload) Not all relations are ready<br>certificate-authority                              active       1  self-signed-certificates  latest/beta    228  10.152.183.220  no       <br>cinder                                             active       1  cinder-k8s                2024.1/beta     99  10.152.183.160  no       <br>cinder-ceph                                        blocked      1  cinder-ceph-k8s           2024.1/beta     97  10.152.183.202  no       (ceph) integration missing<br>cinder-ceph-mysql-router  8.0.37-0ubuntu0.22.04.3  active       1  mysql-router-k8s          8.0/stable     155  10.152.183.244  no       <br>cinder-mysql              8.0.37-0ubuntu0.22.04.3  active       1  mysql-k8s                 8.0/stable     180  10.152.183.77   no       <br>cinder-mysql-router       8.0.37-0ubuntu0.22.04.3  active       1  mysql-router-k8s          8.0/stable     155  10.152.183.92   no       <br>glance                                             active       1  glance-k8s                2024.1/beta    120  10.152.183.187  no       <br>glance-mysql              8.0.37-0ubuntu0.22.04.3  active       1  mysql-k8s                 8.0/stable     180  10.152.183.163  no       <br>glance-mysql-router       8.0.37-0ubuntu0.22.04.3  active       1  mysql-router-k8s          8.0/stable     155  10.152.183.116  no       <br>gnocchi                                            blocked      1  gnocchi-k8s               2024.1/beta     61  10.152.183.81   no       (ceph) integration missing<br>gnocchi-mysql             8.0.37-0ubuntu0.22.04.3  active       1  mysql-k8s                 8.0/stable     180  10.152.183.35   no       <br>gnocchi-mysql-router      8.0.37-0ubuntu0.22.04.3  active       1  mysql-router-k8s          8.0/stable     155  10.152.183.72   no       <br>grafana-agent             0.40.4                   active       1  grafana-agent-k8s         latest/stable   80  10.152.183.169  no       <br>heat                                               active       1  heat-k8s                  2024.1/beta     79  10.152.183.151  no       <br>heat-mysql                8.0.37-0ubuntu0.22.04.3  active       1  mysql-k8s                 8.0/stable     180  10.152.183.222  no       <br>heat-mysql-router         8.0.37-0ubuntu0.22.04.3  active       1  mysql-router-k8s          8.0/stable     155  10.152.183.249  no       <br>horizon                                            active       1  horizon-k8s               2024.1/beta    111  10.152.183.234  no       http://172.16.1.204/openstack-horizon<br>horizon-mysql             8.0.37-0ubuntu0.22.04.3  active       1  mysql-k8s                 8.0/stable     180  10.152.183.131  no       <br>horizon-mysql-router      8.0.37-0ubuntu0.22.04.3  active       1  mysql-router-k8s          8.0/stable     155  10.152.183.140  no       <br>keystone                                           active       1  keystone-k8s              2024.1/beta    213  10.152.183.63   no       <br>keystone-mysql            8.0.37-0ubuntu0.22.04.3  active       1  mysql-k8s                 8.0/stable     180  10.152.183.48   no       <br>keystone-mysql-router     8.0.37-0ubuntu0.22.04.3  active       1  mysql-router-k8s          8.0/stable     155  10.152.183.108  no       <br>neutron                                            active       1  neutron-k8s               2024.1/beta    119  10.152.183.212  no       <br>neutron-mysql             8.0.37-0ubuntu0.22.04.3  active       1  mysql-k8s                 8.0/stable     180  10.152.183.75   no       <br>neutron-mysql-router      8.0.37-0ubuntu0.22.04.3  active       1  mysql-router-k8s          8.0/stable     155  10.152.183.197  no       <br>nova                                               active       1  nova-k8s                  2024.1/beta    109  10.152.183.104  no       <br>nova-api-mysql-router     8.0.37-0ubuntu0.22.04.3  active       1  mysql-router-k8s          8.0/stable     155  10.152.183.189  no       <br>nova-cell-mysql-router    8.0.37-0ubuntu0.22.04.3  active       1  mysql-router-k8s          8.0/stable     155  10.152.183.178  no       <br>nova-mysql                8.0.37-0ubuntu0.22.04.3  active       1  mysql-k8s                 8.0/stable     180  10.152.183.24   no       <br>nova-mysql-router         8.0.37-0ubuntu0.22.04.3  active       1  mysql-router-k8s          8.0/stable     155  10.152.183.152  no       <br>openstack-exporter                                 active       1  openstack-exporter-k8s    2024.1/beta     72  10.152.183.100  no       <br>ovn-central                                        active       1  ovn-central-k8s           24.03/beta     110  10.152.183.194  no       <br>ovn-relay                                          active       1  ovn-relay-k8s             24.03/beta      97  172.16.1.201    no       <br>placement                                          active       1  placement-k8s             2024.1/beta     92  10.152.183.199  no       <br>placement-mysql           8.0.37-0ubuntu0.22.04.3  active       1  mysql-k8s                 8.0/stable     180  10.152.183.83   no       <br>placement-mysql-router    8.0.37-0ubuntu0.22.04.3  active       1  mysql-router-k8s          8.0/stable     155  10.152.183.248  no       <br>rabbitmq                  3.12.1                   active       1  rabbitmq-k8s              3.12/stable     34  172.16.1.202    no       <br>traefik                   2.11.0                   active       1  traefik-k8s               latest/beta    223  10.152.183.125  no       Serving at 172.16.1.203<br>traefik-public            2.11.0                   active       1  traefik-k8s               latest/beta    223  10.152.183.54   no       Serving at 172.16.1.204<br>vault                                              blocked      1  vault-k8s                 1.16/stable    280  10.152.183.78   no       Please initialize Vault or integrate with an auto-unseal provider<br><br>Unit                         Workload  Agent  Address     Ports  Message<br>aodh-mysql-router/0*         active    idle   10.1.0.57          <br>aodh-mysql/0*                active    idle   10.1.0.6           Primary<br>aodh/0*                      active    idle   10.1.0.90          <br>ceilometer/0*                waiting   idle   10.1.0.149         (workload) Not all relations are ready<br>certificate-authority/0*     active    idle   10.1.0.5           <br>cinder-ceph-mysql-router/0*  active    idle   10.1.0.167         <br>cinder-ceph/0*               blocked   idle   10.1.0.108         (ceph) integration missing<br>cinder-mysql-router/0*       active    idle   10.1.0.253         <br>cinder-mysql/0*              active    idle   10.1.0.145         Primary<br>cinder/0*                    active    idle   10.1.0.56          <br>glance-mysql-router/0*       active    idle   10.1.0.85          <br>glance-mysql/0*              active    idle   10.1.0.183         Primary<br>glance/0*                    active    idle   10.1.0.251         <br>gnocchi-mysql-router/0*      active    idle   10.1.0.196         <br>gnocchi-mysql/0*             active    idle   10.1.0.213         Primary<br>gnocchi/0*                   blocked   idle   10.1.0.55          (ceph) integration missing<br>grafana-agent/0*             active    idle   10.1.0.2           <br>heat-mysql-router/0*         active    idle   10.1.0.54          <br>heat-mysql/0*                active    idle   10.1.0.9           Primary<br>heat/0*                      active    idle   10.1.0.138         <br>horizon-mysql-router/0*      active    idle   10.1.0.248         <br>horizon-mysql/0*             active    idle   10.1.0.185         Primary<br>horizon/0*                   active    idle   10.1.0.35          <br>keystone-mysql-router/0*     active    idle   10.1.0.243         <br>keystone-mysql/0*            active    idle   10.1.0.104         Primary<br>keystone/0*                  active    idle   10.1.0.223         <br>neutron-mysql-router/0*      active    idle   10.1.0.135         <br>neutron-mysql/0*             active    idle   10.1.0.79          Primary<br>neutron/0*                   active    idle   10.1.0.23          <br>nova-api-mysql-router/0*     active    idle   10.1.0.93          <br>nova-cell-mysql-router/0*    active    idle   10.1.0.165         <br>nova-mysql-router/0*         active    idle   10.1.0.143         <br>nova-mysql/0*                active    idle   10.1.0.226         Primary<br>nova/0*                      active    idle   10.1.0.147         <br>openstack-exporter/0*        active    idle   10.1.0.100         <br>ovn-central/0*               active    idle   10.1.0.222         <br>ovn-relay/0*                 active    idle   10.1.0.82          <br>placement-mysql-router/0*    active    idle   10.1.0.224         <br>placement-mysql/0*           active    idle   10.1.0.148         Primary<br>placement/0*                 active    idle   10.1.0.78          <br>rabbitmq/0*                  active    idle   10.1.0.238         <br>traefik-public/0*            active    idle   10.1.0.96          Serving at 172.16.1.204<br>traefik/0*                   active    idle   10.1.0.151         Serving at 172.16.1.203<br>vault/0*                     blocked   idle   10.1.0.178         Please initialize Vault or integrate with an auto-unseal provider<br><br>Offer                  Application            Charm                     Rev  Connected  Endpoint              Interface             Role<br>ceilometer             ceilometer             ceilometer-k8s            62   1/1        ceilometer-service    ceilometer            provider<br>cert-distributor       keystone               keystone-k8s              213  2/2        send-ca-cert          certificate_transfer  provider<br>certificate-authority  certificate-authority  self-signed-certificates  228  1/1        certificates          tls-certificates      provider<br>cinder-ceph            cinder-ceph            cinder-ceph-k8s           97   1/1        ceph-access           cinder-ceph-key       provider<br>keystone-credentials   keystone               keystone-k8s              213  1/1        identity-credentials  keystone-credentials  provider<br>keystone-endpoints     keystone               keystone-k8s              213  1/1        identity-service      keystone              provider<br>nova                   nova                   nova-k8s                  109  1/1        nova-service          nova                  provider<br>ovn-relay              ovn-relay              ovn-relay-k8s             97   1/1        ovsdb-cms-relay       ovsdb-cms             provider<br>rabbitmq               rabbitmq               rabbitmq-k8s              34   1/1        amqp                  rabbitmq              provider</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0_NDfSxsaTm_MT1J9P3T-A.png" /></figure><p>Ou via Canonical Kubernetes (qui supporte OpenStack) :</p><pre>ubuntu@microstack:~$ sudo k8s kubectl cluster-info<br>Kubernetes control plane is running at https://127.0.0.1:6443<br>CoreDNS is running at https://127.0.0.1:6443/api/v1/namespaces/kube-system/services/coredns:udp-53/proxy<br><br>To further debug and diagnose cluster problems, use &#39;kubectl cluster-info dump&#39;.<br>ubuntu@microstack:~$ sudo k8s kubectl get po,svc -A<br>NAMESPACE        NAME                                      READY   STATUS    RESTARTS   AGE<br>kube-system      pod/cilium-87pxh                          1/1     Running   0          62m<br>kube-system      pod/cilium-operator-6f7f8cf67-5vfsx       1/1     Running   0          63m<br>kube-system      pod/ck-storage-rawfile-csi-controller-0   2/2     Running   0          63m<br>kube-system      pod/ck-storage-rawfile-csi-node-5vbjd     4/4     Running   0          63m<br>kube-system      pod/coredns-598bfdf87d-qt2j4              1/1     Running   0          63m<br>kube-system      pod/metrics-server-7ff9f4d4c9-jqb9x       1/1     Running   0          63m<br>metallb-system   pod/metallb-controller-7bb5f6c9b4-pbzdb   1/1     Running   0          63m<br>metallb-system   pod/metallb-speaker-dxg5x                 1/1     Running   0          62m<br>observability    pod/alertmanager-0                        2/2     Running   0          13m<br>observability    pod/catalogue-0                           2/2     Running   0          13m<br>observability    pod/grafana-0                             3/3     Running   0          13m<br>observability    pod/loki-0                                3/3     Running   0          12m<br>observability    pod/modeloperator-88fc49d74-tjcnm         1/1     Running   0          14m<br>observability    pod/prometheus-0                          2/2     Running   0          13m<br>observability    pod/traefik-0                             2/2     Running   0          13m<br>openstack        pod/aodh-0                                6/6     Running   0          18m<br>openstack        pod/aodh-mysql-0                          2/2     Running   0          22m<br>openstack        pod/aodh-mysql-router-0                   2/2     Running   0          19m<br>openstack        pod/ceilometer-0                          3/3     Running   0          22m<br>openstack        pod/certificate-authority-0               1/1     Running   0          61m<br>openstack        pod/cinder-0                              3/3     Running   0          56m<br>openstack        pod/cinder-ceph-0                         2/2     Running   0          56m<br>openstack        pod/cinder-ceph-mysql-router-0            2/2     Running   0          56m<br>openstack        pod/cinder-mysql-0                        2/2     Running   0          60m<br>openstack        pod/cinder-mysql-router-0                 2/2     Running   0          56m<br>openstack        pod/glance-0                              2/2     Running   0          56m<br>openstack        pod/glance-mysql-0                        2/2     Running   0          61m<br>openstack        pod/glance-mysql-router-0                 2/2     Running   0          56m<br>openstack        pod/gnocchi-0                             3/3     Running   0          19m<br>openstack        pod/gnocchi-mysql-0                       2/2     Running   0          22m<br>openstack        pod/gnocchi-mysql-router-0                2/2     Running   0          19m<br>openstack        pod/grafana-agent-0                       2/2     Running   0          10m<br>openstack        pod/heat-0                                4/4     Running   0          29m<br>openstack        pod/heat-mysql-0                          2/2     Running   0          30m<br>openstack        pod/heat-mysql-router-0                   2/2     Running   0          29m<br>openstack        pod/horizon-0                             2/2     Running   0          55m<br>openstack        pod/horizon-mysql-0                       2/2     Running   0          61m<br>openstack        pod/horizon-mysql-router-0                2/2     Running   0          55m<br>openstack        pod/keystone-0                            2/2     Running   0          55m<br>openstack        pod/keystone-mysql-0                      2/2     Running   0          61m<br>openstack        pod/keystone-mysql-router-0               2/2     Running   0          55m<br>openstack        pod/modeloperator-56b4d68fb7-tznnv        1/1     Running   0          62m<br>openstack        pod/neutron-0                             2/2     Running   0          55m<br>openstack        pod/neutron-mysql-0                       2/2     Running   0          60m<br>openstack        pod/neutron-mysql-router-0                2/2     Running   0          55m<br>openstack        pod/nova-0                                5/5     Running   0          56m<br>openstack        pod/nova-api-mysql-router-0               2/2     Running   0          56m<br>openstack        pod/nova-cell-mysql-router-0              2/2     Running   0          56m<br>openstack        pod/nova-mysql-0                          2/2     Running   0          60m<br>openstack        pod/nova-mysql-router-0                   2/2     Running   0          56m<br>openstack        pod/openstack-exporter-0                  2/2     Running   0          22m<br>openstack        pod/ovn-central-0                         4/4     Running   0          61m<br>openstack        pod/ovn-relay-0                           2/2     Running   0          61m<br>openstack        pod/placement-0                           2/2     Running   0          55m<br>openstack        pod/placement-mysql-0                     2/2     Running   0          61m<br>openstack        pod/placement-mysql-router-0              2/2     Running   0          55m<br>openstack        pod/rabbitmq-0                            2/2     Running   0          61m<br>openstack        pod/traefik-0                             2/2     Running   0          61m<br>openstack        pod/traefik-public-0                      2/2     Running   0          60m<br>openstack        pod/vault-0                               2/2     Running   0          27m<br><br>NAMESPACE        NAME                                         TYPE           CLUSTER-IP       EXTERNAL-IP    PORT(S)                          AGE<br>default          service/kubernetes                           ClusterIP      10.152.183.1     &lt;none&gt;         443/TCP                          63m<br>kube-system      service/ck-storage-rawfile-csi-controller    ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           63m<br>kube-system      service/ck-storage-rawfile-csi-node          ClusterIP      10.152.183.237   &lt;none&gt;         9100/TCP                         63m<br>kube-system      service/coredns                              ClusterIP      10.152.183.37    &lt;none&gt;         53/UDP,53/TCP                    63m<br>kube-system      service/hubble-peer                          ClusterIP      10.152.183.23    &lt;none&gt;         443/TCP                          63m<br>kube-system      service/metrics-server                       ClusterIP      10.152.183.119   &lt;none&gt;         443/TCP                          63m<br>metallb-system   service/metallb-webhook-service              ClusterIP      10.152.183.110   &lt;none&gt;         443/TCP                          63m<br>observability    service/alertmanager                         ClusterIP      10.152.183.36    &lt;none&gt;         9093/TCP,9094/TCP                13m<br>observability    service/alertmanager-endpoints               ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           13m<br>observability    service/catalogue                            ClusterIP      10.152.183.190   &lt;none&gt;         80/TCP                           14m<br>observability    service/catalogue-endpoints                  ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           14m<br>observability    service/grafana                              ClusterIP      10.152.183.170   &lt;none&gt;         3000/TCP                         13m<br>observability    service/grafana-endpoints                    ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           13m<br>observability    service/loki                                 ClusterIP      10.152.183.201   &lt;none&gt;         3100/TCP                         13m<br>observability    service/loki-endpoints                       ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           13m<br>observability    service/modeloperator                        ClusterIP      10.152.183.59    &lt;none&gt;         17071/TCP                        14m<br>observability    service/prometheus                           ClusterIP      10.152.183.147   &lt;none&gt;         9090/TCP                         13m<br>observability    service/prometheus-endpoints                 ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           13m<br>observability    service/traefik                              ClusterIP      10.152.183.198   &lt;none&gt;         65535/TCP                        13m<br>observability    service/traefik-endpoints                    ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           13m<br>observability    service/traefik-lb                           LoadBalancer   10.152.183.60    172.16.1.205   80:30845/TCP,443:31176/TCP       13m<br>openstack        service/aodh                                 ClusterIP      10.152.183.238   &lt;none&gt;         8042/TCP                         20m<br>openstack        service/aodh-endpoints                       ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           20m<br>openstack        service/aodh-mysql                           ClusterIP      10.152.183.134   &lt;none&gt;         3306/TCP,33060/TCP               23m<br>openstack        service/aodh-mysql-endpoints                 ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           22m<br>openstack        service/aodh-mysql-primary                   ClusterIP      10.152.183.176   &lt;none&gt;         3306/TCP                         19m<br>openstack        service/aodh-mysql-replicas                  ClusterIP      10.152.183.74    &lt;none&gt;         3306/TCP                         19m<br>openstack        service/aodh-mysql-router                    ClusterIP      10.152.183.200   &lt;none&gt;         6446/TCP,6447/TCP,65535/TCP      20m<br>openstack        service/aodh-mysql-router-endpoints          ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           20m<br>openstack        service/ceilometer                           ClusterIP      10.152.183.88    &lt;none&gt;         65535/TCP                        23m<br>openstack        service/ceilometer-endpoints                 ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           22m<br>openstack        service/certificate-authority                ClusterIP      10.152.183.220   &lt;none&gt;         65535/TCP                        61m<br>openstack        service/certificate-authority-endpoints      ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           61m<br>openstack        service/cinder                               ClusterIP      10.152.183.160   &lt;none&gt;         8776/TCP                         58m<br>openstack        service/cinder-ceph                          ClusterIP      10.152.183.202   &lt;none&gt;         65535/TCP                        58m<br>openstack        service/cinder-ceph-endpoints                ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/cinder-ceph-mysql-router             ClusterIP      10.152.183.244   &lt;none&gt;         6446/TCP,6447/TCP,65535/TCP      57m<br>openstack        service/cinder-ceph-mysql-router-endpoints   ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/cinder-endpoints                     ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/cinder-mysql                         ClusterIP      10.152.183.77    &lt;none&gt;         3306/TCP,33060/TCP               61m<br>openstack        service/cinder-mysql-endpoints               ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           61m<br>openstack        service/cinder-mysql-primary                 ClusterIP      10.152.183.113   &lt;none&gt;         3306/TCP                         55m<br>openstack        service/cinder-mysql-replicas                ClusterIP      10.152.183.127   &lt;none&gt;         3306/TCP                         55m<br>openstack        service/cinder-mysql-router                  ClusterIP      10.152.183.92    &lt;none&gt;         6446/TCP,6447/TCP,65535/TCP      57m<br>openstack        service/cinder-mysql-router-endpoints        ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/glance                               ClusterIP      10.152.183.187   &lt;none&gt;         9292/TCP                         58m<br>openstack        service/glance-endpoints                     ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/glance-mysql                         ClusterIP      10.152.183.163   &lt;none&gt;         3306/TCP,33060/TCP               61m<br>openstack        service/glance-mysql-endpoints               ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           61m<br>openstack        service/glance-mysql-primary                 ClusterIP      10.152.183.245   &lt;none&gt;         3306/TCP                         55m<br>openstack        service/glance-mysql-replicas                ClusterIP      10.152.183.246   &lt;none&gt;         3306/TCP                         55m<br>openstack        service/glance-mysql-router                  ClusterIP      10.152.183.116   &lt;none&gt;         6446/TCP,6447/TCP,65535/TCP      58m<br>openstack        service/glance-mysql-router-endpoints        ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/gnocchi                              ClusterIP      10.152.183.81    &lt;none&gt;         65535/TCP                        20m<br>openstack        service/gnocchi-endpoints                    ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           20m<br>openstack        service/gnocchi-mysql                        ClusterIP      10.152.183.35    &lt;none&gt;         3306/TCP,33060/TCP               23m<br>openstack        service/gnocchi-mysql-endpoints              ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           22m<br>openstack        service/gnocchi-mysql-primary                ClusterIP      10.152.183.146   &lt;none&gt;         3306/TCP                         19m<br>openstack        service/gnocchi-mysql-replicas               ClusterIP      10.152.183.153   &lt;none&gt;         3306/TCP                         19m<br>openstack        service/gnocchi-mysql-router                 ClusterIP      10.152.183.72    &lt;none&gt;         6446/TCP,6447/TCP,65535/TCP      20m<br>openstack        service/gnocchi-mysql-router-endpoints       ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           20m<br>openstack        service/grafana-agent                        ClusterIP      10.152.183.169   &lt;none&gt;         3500/TCP,3600/TCP                10m<br>openstack        service/grafana-agent-endpoints              ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           10m<br>openstack        service/heat                                 ClusterIP      10.152.183.151   &lt;none&gt;         8004/TCP                         30m<br>openstack        service/heat-endpoints                       ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           29m<br>openstack        service/heat-mysql                           ClusterIP      10.152.183.222   &lt;none&gt;         3306/TCP,33060/TCP               30m<br>openstack        service/heat-mysql-endpoints                 ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           30m<br>openstack        service/heat-mysql-primary                   ClusterIP      10.152.183.98    &lt;none&gt;         3306/TCP                         29m<br>openstack        service/heat-mysql-replicas                  ClusterIP      10.152.183.80    &lt;none&gt;         3306/TCP                         29m<br>openstack        service/heat-mysql-router                    ClusterIP      10.152.183.249   &lt;none&gt;         6446/TCP,6447/TCP,65535/TCP      30m<br>openstack        service/heat-mysql-router-endpoints          ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           29m<br>openstack        service/horizon                              ClusterIP      10.152.183.234   &lt;none&gt;         65535/TCP                        57m<br>openstack        service/horizon-endpoints                    ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/horizon-mysql                        ClusterIP      10.152.183.131   &lt;none&gt;         3306/TCP,33060/TCP               61m<br>openstack        service/horizon-mysql-endpoints              ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           61m<br>openstack        service/horizon-mysql-primary                ClusterIP      10.152.183.126   &lt;none&gt;         3306/TCP                         55m<br>openstack        service/horizon-mysql-replicas               ClusterIP      10.152.183.145   &lt;none&gt;         3306/TCP                         55m<br>openstack        service/horizon-mysql-router                 ClusterIP      10.152.183.140   &lt;none&gt;         6446/TCP,6447/TCP,65535/TCP      57m<br>openstack        service/horizon-mysql-router-endpoints       ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/keystone                             ClusterIP      10.152.183.63    &lt;none&gt;         5000/TCP                         57m<br>openstack        service/keystone-endpoints                   ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/keystone-mysql                       ClusterIP      10.152.183.48    &lt;none&gt;         3306/TCP,33060/TCP               61m<br>openstack        service/keystone-mysql-endpoints             ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           61m<br>openstack        service/keystone-mysql-primary               ClusterIP      10.152.183.159   &lt;none&gt;         3306/TCP                         55m<br>openstack        service/keystone-mysql-replicas              ClusterIP      10.152.183.114   &lt;none&gt;         3306/TCP                         55m<br>openstack        service/keystone-mysql-router                ClusterIP      10.152.183.108   &lt;none&gt;         6446/TCP,6447/TCP,65535/TCP      57m<br>openstack        service/keystone-mysql-router-endpoints      ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/modeloperator                        ClusterIP      10.152.183.26    &lt;none&gt;         17071/TCP                        62m<br>openstack        service/neutron                              ClusterIP      10.152.183.212   &lt;none&gt;         9696/TCP                         57m<br>openstack        service/neutron-endpoints                    ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/neutron-mysql                        ClusterIP      10.152.183.75    &lt;none&gt;         3306/TCP,33060/TCP               60m<br>openstack        service/neutron-mysql-endpoints              ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           60m<br>openstack        service/neutron-mysql-primary                ClusterIP      10.152.183.55    &lt;none&gt;         3306/TCP                         55m<br>openstack        service/neutron-mysql-replicas               ClusterIP      10.152.183.34    &lt;none&gt;         3306/TCP                         55m<br>openstack        service/neutron-mysql-router                 ClusterIP      10.152.183.197   &lt;none&gt;         6446/TCP,6447/TCP,65535/TCP      57m<br>openstack        service/neutron-mysql-router-endpoints       ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/nova                                 ClusterIP      10.152.183.104   &lt;none&gt;         8774/TCP                         58m<br>openstack        service/nova-api-mysql-router                ClusterIP      10.152.183.189   &lt;none&gt;         6446/TCP,6447/TCP,65535/TCP      57m<br>openstack        service/nova-api-mysql-router-endpoints      ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/nova-cell-mysql-router               ClusterIP      10.152.183.178   &lt;none&gt;         6446/TCP,6447/TCP,65535/TCP      58m<br>openstack        service/nova-cell-mysql-router-endpoints     ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/nova-endpoints                       ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/nova-mysql                           ClusterIP      10.152.183.24    &lt;none&gt;         3306/TCP,33060/TCP               61m<br>openstack        service/nova-mysql-endpoints                 ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           61m<br>openstack        service/nova-mysql-primary                   ClusterIP      10.152.183.130   &lt;none&gt;         3306/TCP                         56m<br>openstack        service/nova-mysql-replicas                  ClusterIP      10.152.183.186   &lt;none&gt;         3306/TCP                         56m<br>openstack        service/nova-mysql-router                    ClusterIP      10.152.183.152   &lt;none&gt;         6446/TCP,6447/TCP,65535/TCP      58m<br>openstack        service/nova-mysql-router-endpoints          ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/openstack-exporter                   ClusterIP      10.152.183.100   &lt;none&gt;         9180/TCP                         23m<br>openstack        service/openstack-exporter-endpoints         ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           22m<br>openstack        service/ovn-central                          ClusterIP      10.152.183.194   &lt;none&gt;         6641/TCP,6642/TCP                62m<br>openstack        service/ovn-central-endpoints                ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           61m<br>openstack        service/ovn-relay                            LoadBalancer   10.152.183.149   172.16.1.201   6642:32293/TCP                   62m<br>openstack        service/ovn-relay-endpoints                  ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           62m<br>openstack        service/placement                            ClusterIP      10.152.183.199   &lt;none&gt;         8778/TCP                         57m<br>openstack        service/placement-endpoints                  ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/placement-mysql                      ClusterIP      10.152.183.83    &lt;none&gt;         3306/TCP,33060/TCP               61m<br>openstack        service/placement-mysql-endpoints            ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           61m<br>openstack        service/placement-mysql-primary              ClusterIP      10.152.183.188   &lt;none&gt;         3306/TCP                         55m<br>openstack        service/placement-mysql-replicas             ClusterIP      10.152.183.165   &lt;none&gt;         3306/TCP                         55m<br>openstack        service/placement-mysql-router               ClusterIP      10.152.183.248   &lt;none&gt;         6446/TCP,6447/TCP,65535/TCP      57m<br>openstack        service/placement-mysql-router-endpoints     ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           57m<br>openstack        service/rabbitmq                             LoadBalancer   10.152.183.150   172.16.1.202   5672:31615/TCP,15672:31040/TCP   61m<br>openstack        service/rabbitmq-endpoints                   ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           61m<br>openstack        service/traefik                              ClusterIP      10.152.183.125   &lt;none&gt;         65535/TCP                        61m<br>openstack        service/traefik-endpoints                    ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           61m<br>openstack        service/traefik-lb                           LoadBalancer   10.152.183.221   172.16.1.203   80:32485/TCP,443:31534/TCP       61m<br>openstack        service/traefik-public                       ClusterIP      10.152.183.54    &lt;none&gt;         65535/TCP                        61m<br>openstack        service/traefik-public-endpoints             ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           61m<br>openstack        service/traefik-public-lb                    LoadBalancer   10.152.183.115   172.16.1.204   80:30599/TCP,443:30927/TCP       60m<br>openstack        service/vault                                ClusterIP      10.152.183.78    &lt;none&gt;         8200/TCP                         27m<br>openstack        service/vault-endpoints                      ClusterIP      None             &lt;none&gt;         &lt;none&gt;                           27m</pre><p>Une fois que MicroStack a été déployé, vous avez la possibilité de gérer les charges de travail manuellement (c’est-à-dire via la CLI d’openstack) ou avec Juju :</p><p><a href="https://canonical.com/microstack/docs/juju-workloads">Manage workloads with Juju | Canonical</a></p><p>Mais je vais utiliser Pulumi. Pulumi est une plateforme moderne d’infrastructure en tant que code (IaC) qui permet aux utilisateurs de gérer et de fournir une infrastructure en nuage à l’aide de langages de programmation (notamment TypeScript, JavaScript, Python, Go, .NET, Java et YAML).</p><p><a href="https://www.pulumi.com/">Pulumi - Infrastructure as Code, Secrets Management, and AI</a></p><blockquote>Pulumi adopte une approche déclarative pour définir l’infrastructure. Les utilisateurs spécifient l’état souhaité de leur infrastructure, et Pulumi gère la création, la mise à jour et la suppression des ressources pour atteindre cet état. Cette approche est plus intuitive que la programmation impérative, où chaque étape pour atteindre l’état souhaité doit être explicitement décrite.</blockquote><p>L’interface de ligne de commande de Pulumi est le principal outil de gestion et de déploiement de l’infrastructure et je l’installe à cette étape :</p><pre>(base) ubuntu@microstack:~$ curl -fsSL https://get.pulumi.com | sh<br>=== Installing Pulumi 3.144.1 ===<br>+ Downloading https://github.com/pulumi/pulumi/releases/download/v3.144.1/pulumi-v3.144.1-linux-x64.tar.gz...<br>  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current<br>                                 Dload  Upload   Total   Spent    Left  Speed<br>  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0<br>100 80.1M  100 80.1M    0     0   103M      0 --:--:-- --:--:-- --:--:--  433M<br>+ Extracting to /home/ubuntu/.pulumi/bin<br>+ Adding /home/ubuntu/.pulumi/bin to $PATH in /home/ubuntu/.bashrc<br><br>=== Pulumi is now installed! 🍹 ===<br>+ Please restart your shell or add /home/ubuntu/.pulumi/bin to your $PATH<br>+ Get started with Pulumi: https://www.pulumi.com/docs/quickstart<br>(base) ubuntu@microstack:~$ source .bashrc<br>(base) ubuntu@microstack:~$ pulumi<br>Pulumi - Modern Infrastructure as Code<br><br>To begin working with Pulumi, run the `pulumi new` command:<br><br>    $ pulumi new<br><br>This will prompt you to create a new project for your cloud and language of choice.<br><br>The most common commands from there are:<br><br>    - pulumi up       : Deploy code and/or resource changes<br>    - pulumi stack    : Manage instances of your project<br>    - pulumi config   : Alter your stack&#39;s configuration or secrets<br>    - pulumi destroy  : Tear down your stack&#39;s resources entirely<br><br>For more information, please visit the project page: https://www.pulumi.com/docs/<br><br>Usage:<br>  pulumi [command]<br><br>Stack Management Commands:<br>  new                   Create a new Pulumi project<br>  config                Manage configuration<br>  stack                 Manage stacks and view stack state<br>  console               Opens the current stack in the Pulumi Console<br>  import                Import resources into an existing stack<br>  refresh               Refresh the resources in a stack<br>  state                 Edit the current stack&#39;s state<br>  install               Install packages and plugins for the current program or policy pack.<br><br>Deployment Commands:<br>  up                    Create or update the resources in a stack<br>  destroy               Destroy all existing resources in the stack<br>  preview               Show a preview of updates to a stack&#39;s resources<br>  cancel                Cancel a stack&#39;s currently running update, if any<br><br>Environment Commands:<br>  env                   Manage environments<br><br>Pulumi Cloud Commands:<br>  login                 Log in to the Pulumi Cloud<br>  logout                Log out of the Pulumi Cloud<br>  whoami                Display the current logged-in user<br>  org                   Manage Organization configuration<br><br>Policy Management Commands:<br>  policy                Manage resource policies<br><br>Plugin Commands:<br>  plugin                Manage language and resource provider plugins<br>  schema                Analyze package schemas<br>  package               Work with Pulumi packages<br><br>Other Commands:<br>  version               Print Pulumi&#39;s version number<br>  about                 Print information about the Pulumi environment.<br>  gen-completion        Generate completion scripts for the Pulumi CLI<br><br>Experimental Commands:<br>  convert               Convert Pulumi programs from a supported source program into other supported languages<br>  watch                 Continuously update the resources in a stack<br>  logs                  Show aggregated resource logs for a stack<br><br>Flags:<br>      --color string                 Colorize output. Choices are: always, never, raw, auto (default &quot;auto&quot;)<br>  -C, --cwd string                   Run pulumi as if it had been started in another directory<br>      --disable-integrity-checking   Disable integrity checking of checkpoint files<br>  -e, --emoji                        Enable emojis in the output<br>  -Q, --fully-qualify-stack-names    Show fully-qualified stack names<br>  -h, --help                         help for pulumi<br>      --logflow                      Flow log settings to child processes (like plugins)<br>      --logtostderr                  Log to stderr instead of to files<br>      --memprofilerate int           Enable more precise (and expensive) memory allocation profiles by setting runtime.MemProfileRate<br>      --non-interactive              Disable interactive mode for all commands<br>      --profiling string             Emit CPU and memory profiles and an execution trace to &#39;[filename].[pid].{cpu,mem,trace}&#39;, respectively<br>      --tracing file:                Emit tracing to the specified endpoint. Use the file: scheme to write tracing data to a local file<br>  -v, --verbose int                  Enable verbose logging (e.g., v=3); anything &gt;3 is very verbose<br><br>Use `pulumi [command] --help` for more information about a command.</pre><p>J’utilise le système de fichiers de la machine afin de stocker les fichiers d’état localement :</p><pre>(base) ubuntu@microstack:~$ pulumi login --local<br>Logged in to microstack as ubuntu (file://~)</pre><p>J’utilise Miniconda pour rapidement disposer d’un environnement Python prêt à l’emploi :</p><p><a href="https://docs.anaconda.com/miniconda/">Miniconda - Anaconda documentation</a></p><pre>ubuntu@microstack:~$ mkdir -p ~/miniconda3<br>ubuntu@microstack:~$ wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh -O ~/miniconda3/miniconda.sh<br>ubuntu@microstack:~$ bash ~/miniconda3/miniconda.sh -b -u -p ~/miniconda3<br>ubuntu@microstack:~$ rm ~/miniconda3/miniconda.sh<br><br><br>PREFIX=/home/ubuntu/miniconda3<br>Unpacking payload ...<br><br>Installing base environment...<br><br>Preparing transaction: ...working... done<br>Executing transaction: ...working... done<br>installation finished.<br>ubuntu@microstack:~$ source ~/miniconda3/bin/activate<br>(base) ubuntu@microstack:~$ conda init --all<br>no change     /home/ubuntu/miniconda3/condabin/conda<br>no change     /home/ubuntu/miniconda3/bin/conda<br>no change     /home/ubuntu/miniconda3/bin/conda-env<br>no change     /home/ubuntu/miniconda3/bin/activate<br>no change     /home/ubuntu/miniconda3/bin/deactivate<br>no change     /home/ubuntu/miniconda3/etc/profile.d/conda.sh<br>no change     /home/ubuntu/miniconda3/etc/fish/conf.d/conda.fish<br>no change     /home/ubuntu/miniconda3/shell/condabin/Conda.psm1<br>no change     /home/ubuntu/miniconda3/shell/condabin/conda-hook.ps1<br>no change     /home/ubuntu/miniconda3/lib/python3.12/site-packages/xontrib/conda.xsh<br>no change     /home/ubuntu/miniconda3/etc/profile.d/conda.csh<br>modified      /home/ubuntu/.bashrc<br>modified      /home/ubuntu/.zshrc<br>modified      /home/ubuntu/.config/fish/config.fish<br>modified      /home/ubuntu/.xonshrc<br>modified      /home/ubuntu/.tcshrc<br><br>==&gt; For changes to take effect, close and re-open your current shell. &lt;==<br><br>(base) ubuntu@microstack:~$ source .bashrc<br>(base) ubuntu@microstack:~$ type pip<br>pip is /home/ubuntu/miniconda3/bin/pip</pre><p>Création d’un environnement avec le fournisseur OpenStack et son template en Python pour Pulumi :</p><pre>(base) ubuntu@microstack:~$ mkdir test<br>(base) ubuntu@microstack:~$ cd test<br>(base) ubuntu@microstack:~/test$ pulumi new openstack-python<br>This command will walk you through creating a new Pulumi project.<br><br>Enter a value or leave blank to accept the (default), and press &lt;ENTER&gt;.<br>Press ^C at any time to quit.<br><br>Project name (test):  <br>Project description (A minimal OpenStack Python Pulumi program):  <br>Created project &#39;test&#39;<br><br>Stack name (dev):  <br>Enter your passphrase to protect config/secrets:  <br>Re-enter your passphrase to confirm:  <br>Created stack &#39;dev&#39;<br><br>The toolchain to use for installing dependencies and running the program pip<br>Installing dependencies...<br><br>Creating virtual environment...<br>Finished creating virtual environment<br>Updating pip, setuptools, and wheel in virtual environment...<br>Requirement already satisfied: pip in ./venv/lib/python3.12/site-packages (24.3.1)<br>Collecting setuptools<br>  Downloading setuptools-75.6.0-py3-none-any.whl.metadata (6.7 kB)<br>Collecting wheel<br>  Downloading wheel-0.45.1-py3-none-any.whl.metadata (2.3 kB)<br>Downloading setuptools-75.6.0-py3-none-any.whl (1.2 MB)<br>   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.2/1.2 MB 29.2 MB/s eta 0:00:00<br>Downloading wheel-0.45.1-py3-none-any.whl (72 kB)<br>Installing collected packages: wheel, setuptools<br>Successfully installed setuptools-75.6.0 wheel-0.45.1<br>Finished updating<br>Installing dependencies in virtual environment...<br>Collecting pulumi&lt;4.0.0,&gt;=3.0.0 (from -r requirements.txt (line 1))<br>  Downloading pulumi-3.144.1-py3-none-any.whl.metadata (12 kB)<br>Collecting pulumi-openstack&lt;4.0.0,&gt;=3.0.0 (from -r requirements.txt (line 2))<br>  Downloading pulumi_openstack-3.15.2-py3-none-any.whl.metadata (9.2 kB)<br>Collecting protobuf~=4.21 (from pulumi&lt;4.0.0,&gt;=3.0.0-&gt;-r requirements.txt (line 1))<br>  Downloading protobuf-4.25.5-cp37-abi3-manylinux2014_x86_64.whl.metadata (541 bytes)<br>Collecting grpcio~=1.66.2 (from pulumi&lt;4.0.0,&gt;=3.0.0-&gt;-r requirements.txt (line 1))<br>  Downloading grpcio-1.66.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (3.9 kB)<br>Collecting dill~=0.3 (from pulumi&lt;4.0.0,&gt;=3.0.0-&gt;-r requirements.txt (line 1))<br>  Downloading dill-0.3.9-py3-none-any.whl.metadata (10 kB)<br>Collecting six~=1.12 (from pulumi&lt;4.0.0,&gt;=3.0.0-&gt;-r requirements.txt (line 1))<br>  Downloading six-1.17.0-py2.py3-none-any.whl.metadata (1.7 kB)<br>Collecting semver~=2.13 (from pulumi&lt;4.0.0,&gt;=3.0.0-&gt;-r requirements.txt (line 1))<br>  Downloading semver-2.13.0-py2.py3-none-any.whl.metadata (5.0 kB)<br>Collecting pyyaml~=6.0 (from pulumi&lt;4.0.0,&gt;=3.0.0-&gt;-r requirements.txt (line 1))<br>  Downloading PyYAML-6.0.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.1 kB)<br>Collecting debugpy~=1.8.7 (from pulumi&lt;4.0.0,&gt;=3.0.0-&gt;-r requirements.txt (line 1))<br>  Downloading debugpy-1.8.11-cp312-cp312-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (1.1 kB)<br>Collecting parver&gt;=0.2.1 (from pulumi-openstack&lt;4.0.0,&gt;=3.0.0-&gt;-r requirements.txt (line 2))<br>  Downloading parver-0.5-py3-none-any.whl.metadata (2.7 kB)<br>Collecting arpeggio&gt;=1.7 (from parver&gt;=0.2.1-&gt;pulumi-openstack&lt;4.0.0,&gt;=3.0.0-&gt;-r requirements.txt (line 2))<br>  Downloading Arpeggio-2.0.2-py2.py3-none-any.whl.metadata (2.4 kB)<br>Collecting attrs&gt;=19.2 (from parver&gt;=0.2.1-&gt;pulumi-openstack&lt;4.0.0,&gt;=3.0.0-&gt;-r requirements.txt (line 2))<br>  Downloading attrs-24.3.0-py3-none-any.whl.metadata (11 kB)<br>Downloading pulumi-3.144.1-py3-none-any.whl (294 kB)<br>Downloading pulumi_openstack-3.15.2-py3-none-any.whl (551 kB)<br>   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 551.5/551.5 kB 19.0 MB/s eta 0:00:00<br>Downloading debugpy-1.8.11-cp312-cp312-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (4.2 MB)<br>   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4.2/4.2 MB 99.4 MB/s eta 0:00:00<br>Downloading dill-0.3.9-py3-none-any.whl (119 kB)<br>Downloading grpcio-1.66.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (5.8 MB)<br>   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 5.8/5.8 MB 10.8 MB/s eta 0:00:00<br>Downloading parver-0.5-py3-none-any.whl (15 kB)<br>Downloading protobuf-4.25.5-cp37-abi3-manylinux2014_x86_64.whl (294 kB)<br>Downloading PyYAML-6.0.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (767 kB)<br>   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 767.5/767.5 kB 120.7 MB/s eta 0:00:00<br>Downloading semver-2.13.0-py2.py3-none-any.whl (12 kB)<br>Downloading six-1.17.0-py2.py3-none-any.whl (11 kB)<br>Downloading Arpeggio-2.0.2-py2.py3-none-any.whl (55 kB)<br>Downloading attrs-24.3.0-py3-none-any.whl (63 kB)<br>Installing collected packages: arpeggio, six, semver, pyyaml, protobuf, grpcio, dill, debugpy, attrs, pulumi, parver, pulumi-openstack<br>Successfully installed arpeggio-2.0.2 attrs-24.3.0 debugpy-1.8.11 dill-0.3.9 grpcio-1.66.2 parver-0.5 protobuf-4.25.5 pulumi-3.144.1 pulumi-openstack-3.15.2 pyyaml-6.0.2 semver-2.13.0 six-1.17.0<br>Finished installing dependencies<br>Finished installing dependencies<br><br>Your new project is ready to go! <br><br>To perform an initial deployment, run `pulumi up`<br><br></pre><pre>(base) ubuntu@microstack:~/test$ ls<br>Pulumi.dev.yaml  Pulumi.yaml  __main__.py  requirements.txt  venv<br>(base) ubuntu@microstack:~/test$ cat Pulumi.yaml <br>name: test<br>description: A minimal OpenStack Python Pulumi program<br>runtime:<br>  name: python<br>  options:<br>    toolchain: pip<br>    virtualenv: venv<br>config:<br>  pulumi:tags:<br>    value:<br>      pulumi:template: openstack-python</pre><p>Je modifie le principal fichier Python pour déployer une stack avec une nouvelle instance Ubuntu de test :</p><pre>(base) ubuntu@microstack:~/test$ cat __main__.py <br>&quot;&quot;&quot;An OpenStack Python Pulumi program&quot;&quot;&quot;<br><br>import pulumi<br>from pulumi_openstack import compute<br><br># Create an OpenStack resource (Compute Instance)<br>instance = compute.Instance(&#39;test-pulumi&#39;,<br>        flavor_name=&#39;m1.small&#39;,<br>    key_pair=&quot;sunbeam&quot;,                        <br>        image_name=&#39;ubuntu&#39;)<br><br># Export the IP of the instance<br>pulumi.export(&#39;instance_ip&#39;, instance.access_ip_v4)</pre><p>Et je déploie ma stack avec Pulumi en utilisant les variables d’environnement du tenant de démonstration :</p><pre>(base) ubuntu@microstack:~/test$ source ../demo-openrc <br>(base) ubuntu@microstack:~/test$ pulumi up<br>Enter your passphrase to unlock config/secrets<br>    (set PULUMI_CONFIG_PASSPHRASE or PULUMI_CONFIG_PASSPHRASE_FILE to remember):  <br>Enter your passphrase to unlock config/secrets<br>Previewing update (dev):<br>     Type                           Name         Plan       Info<br> +   pulumi:pulumi:Stack            test-dev     create     1 warning<br> +   └─ openstack:compute:Instance  test-pulumi  create     <br><br>Diagnostics:<br>  pulumi:pulumi:Stack (test-dev):<br>    warning: provider config warning: Users not using loadbalancer resources can ignore this message. Support for neutron-lbaas will be removed on next major release. Octavia will be the only supported method for loadbalancer resources. Users using octavia will have to remove &#39;use_octavia&#39; option from the provider configuration block. Users using neutron-lbaas will have to migrate/upgrade to octavia.<br><br>Outputs:<br>    instance_ip: output&lt;string&gt;<br><br>Resources:<br>    + 2 to create<br><br>Do you want to perform this update? yes<br>Updating (dev):<br>     Type                           Name         Status            Info<br> +   pulumi:pulumi:Stack            test-dev     created (15s)     1 warning<br> +   └─ openstack:compute:Instance  test-pulumi  created (15s)     <br><br>Diagnostics:<br>  pulumi:pulumi:Stack (test-dev):<br>    warning: provider config warning: Users not using loadbalancer resources can ignore this message. Support for neutron-lbaas will be removed on next major release. Octavia will be the only supported method for loadbalancer resources. Users using octavia will have to remove &#39;use_octavia&#39; option from the provider configuration block. Users using neutron-lbaas will have to migrate/upgrade to octavia.<br><br>Outputs:<br>    instance_ip: &quot;192.168.0.227&quot;<br><br>Resources:<br>    + 2 created<br><br>Duration: 16s</pre><p>L’instance est créée …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I9sgsYiz-qrSoSMlRvXcKQ.png" /></figure><pre>(base) ubuntu@microstack:~/test$ openstack server list<br>+--------------------------------------+---------------------+--------+-----------------------------------------+--------+----------+<br>| ID                                   | Name                | Status | Networks                                | Image  | Flavor   |<br>+--------------------------------------+---------------------+--------+-----------------------------------------+--------+----------+<br>| 6ec4c753-92c5-4221-a76d-8045638efd32 | test-pulumi-54bdcae | ACTIVE | demo-network=192.168.0.227              | ubuntu | m1.small |<br>| efe46971-56f4-4da4-9c6e-eebee2795b72 | instance1           | ACTIVE | demo-network=172.16.2.31, 192.168.0.166 | ubuntu | m1.tiny  |<br>+--------------------------------------+---------------------+--------+-----------------------------------------+--------+----------+<br>(base) ubuntu@microstack:~/test$ openstack server show test-pulumi-54bdcae --fit<br>+-------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+<br>| Field                               | Value                                                                                                                                                |<br>+-------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+<br>| OS-DCF:diskConfig                   | MANUAL                                                                                                                                               |<br>| OS-EXT-AZ:availability_zone         | nova                                                                                                                                                 |<br>| OS-EXT-SRV-ATTR:host                | None                                                                                                                                                 |<br>| OS-EXT-SRV-ATTR:hostname            | test-pulumi-54bdcae                                                                                                                                  |<br>| OS-EXT-SRV-ATTR:hypervisor_hostname | None                                                                                                                                                 |<br>| OS-EXT-SRV-ATTR:instance_name       | None                                                                                                                                                 |<br>| OS-EXT-SRV-ATTR:kernel_id           | None                                                                                                                                                 |<br>| OS-EXT-SRV-ATTR:launch_index        | None                                                                                                                                                 |<br>| OS-EXT-SRV-ATTR:ramdisk_id          | None                                                                                                                                                 |<br>| OS-EXT-SRV-ATTR:reservation_id      | None                                                                                                                                                 |<br>| OS-EXT-SRV-ATTR:root_device_name    | None                                                                                                                                                 |<br>| OS-EXT-SRV-ATTR:user_data           | None                                                                                                                                                 |<br>| OS-EXT-STS:power_state              | Running                                                                                                                                              |<br>| OS-EXT-STS:task_state               | None                                                                                                                                                 |<br>| OS-EXT-STS:vm_state                 | active                                                                                                                                               |<br>| OS-SRV-USG:launched_at              | 2024-12-24T10:36:58.000000                                                                                                                           |<br>| OS-SRV-USG:terminated_at            | None                                                                                                                                                 |<br>| accessIPv4                          |                                                                                                                                                      |<br>| accessIPv6                          |                                                                                                                                                      |<br>| addresses                           | demo-network=192.168.0.227                                                                                                                           |<br>| config_drive                        |                                                                                                                                                      |<br>| created                             | 2024-12-24T10:36:53Z                                                                                                                                 |<br>| description                         | test-pulumi-54bdcae                                                                                                                                  |<br>| flavor                              | description=, disk=&#39;30&#39;, ephemeral=&#39;0&#39;, , id=&#39;m1.small&#39;, is_disabled=, is_public=&#39;True&#39;, location=, name=&#39;m1.small&#39;, original_name=&#39;m1.small&#39;,       |<br>|                                     | ram=&#39;2048&#39;, rxtx_factor=, swap=&#39;0&#39;, vcpus=&#39;1&#39;                                                                                                        |<br>| hostId                              | 021ebc639163d77a5eb8018996d0b8aad50066a8552682313f3f293f                                                                                             |<br>| host_status                         | None                                                                                                                                                 |<br>| id                                  | 6ec4c753-92c5-4221-a76d-8045638efd32                                                                                                                 |<br>| image                               | ubuntu (ff3ccb3b-f44f-4b50-a030-20267c302d75)                                                                                                        |<br>| key_name                            | sunbeam                                                                                                                                              |<br>| locked                              | False                                                                                                                                                |<br>| locked_reason                       | None                                                                                                                                                 |<br>| name                                | test-pulumi-54bdcae                                                                                                                                  |<br>| progress                            | 0                                                                                                                                                    |<br>| project_id                          | 8b373f844efd47c8b38c4f1bcdcfba2a                                                                                                                     |<br>| properties                          |                                                                                                                                                      |<br>| security_groups                     | name=&#39;default&#39;                                                                                                                                       |<br>| server_groups                       | []                                                                                                                                                   |<br>| status                              | ACTIVE                                                                                                                                               |<br>| tags                                |                                                                                                                                                      |<br>| trusted_image_certificates          | None                                                                                                                                                 |<br>| updated                             | 2024-12-24T10:36:59Z                                                                                                                                 |<br>| user_id                             | 114709b3342c45f295d116c63c51884a                                                                                                                     |<br>| volumes_attached                    |                                                                                                                                                      |<br>+-------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+</pre><p>Et on s’y connecte en y adjoignant une adresse IP flottante :</p><pre>(base) ubuntu@microstack:~$ ssh -i snap/openstack/637/sunbeam ubuntu@172.16.2.124<br>Welcome to Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-127-generic x86_64)<br><br> * Documentation:  https://help.ubuntu.com<br> * Management:     https://landscape.canonical.com<br> * Support:        https://ubuntu.com/pro<br><br> System information as of Tue Dec 24 10:42:48 UTC 2024<br><br>  System load:  0.0               Processes:             89<br>  Usage of /:   5.0% of 28.89GB   Users logged in:       0<br>  Memory usage: 9%                IPv4 address for ens3: 192.168.0.227<br>  Swap usage:   0%<br><br><br>Expanded Security Maintenance for Applications is not enabled.<br><br>0 updates can be applied immediately.<br><br>Enable ESM Apps to receive additional future security updates.<br>See https://ubuntu.com/esm or run: sudo pro status<br><br><br>The list of available updates is more than a week old.<br>To check for new updates run: sudo apt update<br>New release &#39;24.04.1 LTS&#39; available.<br>Run &#39;do-release-upgrade&#39; to upgrade to it.<br><br><br>Last login: Tue Dec 24 10:42:48 2024 from 172.16.2.1<br>To run a command as administrator (user &quot;root&quot;), use &quot;sudo &lt;command&gt;&quot;.<br>See &quot;man sudo_root&quot; for details.</pre><p>Une instance facilement supprimée via la stack déployée par Pulumi :</p><pre>(base) ubuntu@microstack:~/test$ pulumi destroy<br>Enter your passphrase to unlock config/secrets<br>    (set PULUMI_CONFIG_PASSPHRASE or PULUMI_CONFIG_PASSPHRASE_FILE to remember):  <br>Enter your passphrase to unlock config/secrets<br>Previewing destroy (dev):<br>     Type                           Name         Plan       <br> -   pulumi:pulumi:Stack            test-dev     delete     <br> -   └─ openstack:compute:Instance  test-pulumi  delete     <br><br>Outputs:<br>  - instance_ip: &quot;192.168.0.227&quot;<br><br>Resources:<br>    - 2 to delete<br><br>Do you want to perform this destroy? yes<br>Destroying (dev):<br>     Type                           Name         Status              <br> -   pulumi:pulumi:Stack            test-dev     deleted (0.00s)     <br> -   └─ openstack:compute:Instance  test-pulumi  deleted (10s)       <br><br>Outputs:<br>  - instance_ip: &quot;192.168.0.227&quot;<br><br>Resources:<br>    - 2 deleted<br><br>Duration: 11s<br><br>The resources in the stack have been deleted, but the history and configuration associated with the stack are still maintained. <br>If you want to remove the stack completely, run `pulumi stack rm dev`.<br><br>(base) ubuntu@microstack:~/test$ openstack server list<br>+--------------------------------------+-----------+--------+-----------------------------------------+--------+---------+<br>| ID                                   | Name      | Status | Networks                                | Image  | Flavor  |<br>+--------------------------------------+-----------+--------+-----------------------------------------+--------+---------+<br>| efe46971-56f4-4da4-9c6e-eebee2795b72 | instance1 | ACTIVE | demo-network=172.16.2.31, 192.168.0.166 | ubuntu | m1.tiny |<br>+--------------------------------------+-----------+--------+-----------------------------------------+--------+---------+<br><br>(base) ubuntu@microstack:~/test$ pulumi stack rm dev<br>This will permanently remove the &#39;dev&#39; stack!<br>Please confirm that this is what you&#39;d like to do by typing `dev`: dev<br>Stack &#39;dev&#39; has been removed!<br>(base) ubuntu@microstack:~/test$ pulumi stack ls<br>NAME  LAST UPDATE  RESOURCE COUNT</pre><p>La pile d’observabilité Canonical (COS) a été déployée précedemment. MicroStack propagera automatiquement les métriques et les tableaux de bord par défaut, vous permettant de surveiller sans effort l’état de votre déploiement de Sunbeam à un ou plusieurs nœuds sans avoir besoin d’une configuration supplémentaire via Grafana (dont on a obtenu les identifiants via Juju et avec une redirection ssh locale) :</p><pre>$ ssh -L 0.0.0.0:8080:172.16.1.205:80 ubuntu@134.209.225.128</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6PzopXSc5JYIpp3lyJND1w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qV_XTlqbAgS3egyOaYfVYw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EfncwzuW4vXbUQFFjyKh4w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CJzN2IDU0w1j_btQwvfoPg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sy7XmcLzk3YAB_zMgPY7Ng.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B9QiLsmDgDOoRrZlTYVqQw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4LgAOBAEKLqc4IRzXs7GvA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gv0tL6JSTQDXuQg5xj00bQ.png" /></figure><p>Et le tout (dans ce cas précis) pour une consommation conséquente …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x9_lzTmXlWynr4u082eJ-Q.png" /></figure><p>Pour des déploiements plus avancés, MicroStack supporte également les clusters multi-nœuds. Vous pouvez suivre le tutoriel détaillé sur la documentation officielle de Canonical pour déployer un cluster OpenStack multi-nœuds via Sunbeam et MAAS :</p><ul><li><a href="https://canonical.com/microstack/docs/multi-node">Multi-node | Canonical</a></li><li><a href="https://canonical.com/microstack/docs/multi-node-maas">Multi-node with MAAS | Canonical</a></li></ul><p>Comme on a pule voir, MicroStack est conçu pour être hautemement personnalisable , permettant l’intégration de divers backends de stockage tels que Cinder (stockage en bloc) et Swift (stockage d’objets).</p><p><a href="https://canonical.com/microstack/docs/object-storage">Object Storage | Canonical</a></p><p>Les entreprises peuvent adapter la plateforme à leurs besoins uniques en intégrant des plug-ins et des extensions spécifiques. MicroStack offre une solution de cloud privée légère, facile à installer et à utiliser, ce qui en fait un choix idéal pour les organisations cherchant à déployer rapidement un environnement cloud sans la complexité traditionnelle associée à OpenStack. Avec sa flexibilité et sa capacité de customisation, MicroStack est une solution robuste et adaptable pour une variété de besoins en infrastructure cloud y compris pour le contexte de l’Edge Computing …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/534/0*VqkvAvwdsA0lwTse.jpg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abdbcf41b127" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Une autre manière de faire fonctionner OpenStack au-dessus de Kubernetes avec Atmosphere …]]></title>
            <link>https://deep75.medium.com/une-autre-mani%C3%A8re-de-faire-fonctionner-openstack-au-dessus-de-kubernetes-avec-atmosphere-9ac8c46b4232?source=rss-9f1ca3c659fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ac8c46b4232</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[openstack]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[phoenixnap]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Karim]]></dc:creator>
            <pubDate>Mon, 03 Jun 2024 15:53:30 GMT</pubDate>
            <atom:updated>2024-06-03T15:58:34.342Z</atom:updated>
            <content:encoded><![CDATA[<h3>Une autre manière de faire fonctionner OpenStack au-dessus de Kubernetes avec Atmosphere …</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u_-0fC4skAZuh9AVXmpT7Q.png" /></figure><p>Plusieurs projets de déploiement d’OpenStack qui reposent sur un cluster Kubernetes existent à commencer par OpenStack Helm :</p><ul><li><a href="https://wiki.openstack.org/wiki/Openstack-helm">Openstack-helm</a></li><li><a href="https://github.com/openstack/openstack-helm">GitHub - openstack/openstack-helm: Helm charts for deploying OpenStack on Kubernetes. Mirror of code maintained at opendev.org.</a></li></ul><blockquote>Mais c’est aussi le cas du projet open source Atmosphere du fournisseur Cloud Vexxhost qui fournit un large éventail de fonctionnalités d’infrastructure, notamment des machines virtuelles, Kubernetes, du bare metal, du stockage en bloc et en objet, des équilibreurs de charge en tant que service, et plus encore …</blockquote><p><a href="https://vexxhost.com/platform/">Atmosphere deployment tool | VEXXHOST</a></p><p>Atmosphere fait tourner OpenStack au-dessus de Kubernetes. Cette configuration permet des déploiements, des mises à niveau et des contrôles de santé simples et facile.</p><p><a href="https://vexxhost.com/company/newsroom/vexxhost-launches-atmosphere-a-new-open-source-openstack-deployment-tool/">VEXXHOST Launches Atmosphere, a New Open Source, OpenStack Deployment Tool</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FwHrTGBdqmmI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DwHrTGBdqmmI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FwHrTGBdqmmI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4bed38c2a2363fbc3187f49f6ab2dc05/href">https://medium.com/media/4bed38c2a2363fbc3187f49f6ab2dc05/href</a></iframe><p><a href="https://github.com/vexxhost/atmosphere">GitHub - vexxhost/atmosphere: Simple &amp; easy private cloud platform featuring VMs, Kubernetes &amp; bare-metal</a></p><p>Je vais simplement suivre le modus operandi proposé par Vexxhost pour un serveur Bare Metal :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/583/0*TR5ELWDZxFDXLarG.jpg" /></figure><ul><li><a href="https://vexxhost.github.io/atmosphere/quick-start.html">Quick Start - Atmosphere 1.10.4.post231.dev0+f2e3b279 documentation</a></li><li><a href="https://deep75.medium.com/openstack-sur-lxd-avec-juju-et-k3sup-dans-phoenixnap-e5867a487497">OpenStack sur LXD avec Juju  et k3sup dans phoenixNAP …</a></li><li><a href="https://deep75.medium.com/openstack-on-lxd-et-k0s-dans-un-serveur-bare-metal-arm-64-bits-daws-176d1ce32ac3">“OpenStack on LXD” et “k0s” dans un serveur Bare Metal ARM 64 Bits d’AWS …</a></li><li><a href="https://dev.to/deep75/creer-simplement-un-cluster-k8s-dans-phoenixnap-avec-rancher-en-quelques-clics--3d6i">Créer simplement un cluster k8s dans PhoenixNAP avec Rancher en quelques clics ...</a></li></ul><p>Pour cela je pars d’un serveur dans PhoenixNAP sous Ubuntu 22.04 LTS :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UlAO_YM2O1eRwsUv6BYwoQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rN5mS70yck-ErBC_Yp8isg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zk3XoBUwg29VNcuNrXW0yQ.png" /></figure><p>Mise à jour de ce dernier et installation des paquets nécessaires au lancement du déploiement d’Atmosphere :</p><pre>ubuntu@atmosphere:~$ sudo apt-get update &amp;&amp; sudo apt-get install git python3-pip -y &amp;&amp; sudo pip install poetry<br><br>ubuntu@atmosphere:~$ git clone https://github.com/vexxhost/atmosphere.git<br>Cloning into &#39;atmosphere&#39;...<br>remote: Enumerating objects: 25111, done.<br>remote: Counting objects: 100% (825/825), done.<br>remote: Compressing objects: 100% (398/398), done.<br>remote: Total 25111 (delta 377), reused 704 (delta 306), pack-reused 24286<br>Receiving objects: 100% (25111/25111), 10.78 MiB | 50.17 MiB/s, done.<br>Resolving deltas: 100% (14299/14299), done.<br>ubuntu@atmosphere:~$ cd atmosphere/<br>ubuntu@atmosphere:~/atmosphere$ ls<br>CHANGELOG.md  Jenkinsfile  build   doc         galaxy.yml  hack      meta        playbooks    pyproject.toml              test-requirements.txt  tox.ini<br>Dockerfile    README.md    charts  flake.lock  go.mod      images    mkdocs.yml  plugins      release-please-config.json  tests                  zuul.d<br>Earthfile     atmosphere   cmd     flake.nix   go.sum      internal  molecule    poetry.lock  roles                       tools</pre><pre>ubuntu@atmosphere:~/atmosphere$ sudo poetry install --with dev<br>Creating virtualenv atmosphere-NEvTTHEY-py3.10 in /root/.cache/pypoetry/virtualenvs<br>Installing dependencies from lock file<br><br>Package operations: 89 installs, 0 updates, 0 removals<br><br>  - Installing attrs (23.2.0)<br>  - Installing pycparser (2.22)<br>  - Installing rpds-py (0.18.0)<br>  - Installing cffi (1.16.0)<br>  - Installing markupsafe (2.1.5)<br>  - Installing mdurl (0.1.2)<br>  - Installing referencing (0.35.0)<br>  - Installing cryptography (42.0.5)<br>  - Installing jinja2 (3.1.3)<br>  - Installing jsonschema-specifications (2023.12.1)<br>  - Installing markdown-it-py (3.0.0)<br>  - Installing packaging (24.0)<br>  - Installing pbr (6.0.0)<br>  - Installing pygments (2.17.2)<br>  - Installing pyyaml (6.0.1)<br>  - Installing resolvelib (1.0.1)<br>  - Installing wrapt (1.16.0)<br>  - Installing ansible-core (2.16.6)<br>  - Installing bracex (2.4)<br>  - Installing certifi (2024.2.2)<br>  - Installing charset-normalizer (3.3.2)<br>  - Installing click (8.1.7)<br>  - Installing debtcollector (3.0.0)<br>  - Installing idna (3.7)<br>  - Installing iso8601 (2.1.0)<br>  - Installing jsonschema (4.21.1)<br>  - Installing netaddr (0.8.0)<br>  - Installing netifaces (0.11.0)<br>  - Installing oslo-i18n (6.3.0)<br>  - Installing pyparsing (3.1.2)<br>  - Installing rich (13.7.1)<br>  - Installing subprocess-tee (0.4.1)<br>  - Installing tzdata (2024.1)<br>  - Installing urllib3 (2.2.1)<br>  - Installing ansible-compat (4.1.11)<br>  - Installing click-help-colors (0.9.4)<br>  - Installing decorator (5.1.1)<br>  - Installing distro (1.9.0)<br>  - Installing enrich (1.2.7)<br>  - Installing exceptiongroup (1.2.1)<br>  - Installing iniconfig (2.0.0)<br>  - Installing jsonpointer (2.4)<br>  - Installing mccabe (0.7.0)<br>  - Installing msgpack (1.0.8)<br>  - Installing os-service-types (1.7.0)<br>  - Installing oslo-utils (7.1.0)<br>  - Installing pluggy (1.5.0)<br>  - Installing pycodestyle (2.9.1)<br>  - Installing pyflakes (2.5.0)<br>  - Installing requests (2.31.0)<br>  - Installing rfc3986 (2.0.0)<br>  - Installing six (1.16.0)<br>  - Installing stevedore (5.2.0)<br>  - Installing tomli (2.0.1)<br>  - Installing typing-extensions (4.11.0)<br>  - Installing wcmatch (8.5.1)<br>  - Installing appdirs (1.4.4)<br>  - Installing coverage (7.5.0)<br>  - Installing docker (7.0.0)<br>  - Installing dogpile-cache (1.3.2)<br>  - Installing execnet (2.1.1)<br>  - Installing flake8 (5.0.4)<br>  - Installing isort (5.13.2)<br>  - Installing jmespath (1.0.1)<br>  - Installing jsonpatch (1.33)<br>  - Installing keystoneauth1 (5.6.0)<br>  - Installing molecule (6.0.3)<br>  - Installing munch (4.0.0)<br>  - Installing oslo-config (9.4.0)<br>  - Installing oslo-context (5.5.0)<br>  - Installing oslo-serialization (5.4.0)<br>  - Installing py (1.11.0)<br>  - Installing pyinotify (0.9.6)<br>  - Installing pytest (7.4.4)<br>  - Installing python-dateutil (2.9.0.post0)<br>  - Installing regex (2024.4.28)<br>  - Installing requestsexceptions (1.4.0)<br>  - Installing selinux (0.3.0)<br>  - Installing docker-image-py (0.1.12)<br>  - Installing flake8-isort (4.2.0)<br>  - Installing molecule-plugins (23.5.3)<br>  - Installing openstacksdk (0.62.0)<br>  - Installing oslo-log (5.5.1)<br>  - Installing pytest-cov (3.0.0)<br>  - Installing pytest-forked (1.6.0)<br>  - Installing pytest-mock (3.14.0)<br>  - Installing pytest-xdist (3.6.1)<br>  - Installing rjsonnet (0.5.4)<br>  - Installing ruyaml (0.91.0)<br><br>Installing the current project: atmosphere (1.10.4.post186.dev0+779cb921)</pre><p>Très rapidement, je lance le déploiement qui prend un peu moins d’une heure ici :</p><pre>ubuntu@atmosphere:~/atmosphere$ sudo poetry run molecule converge -s aio<br>INFO     aio scenario test matrix: dependency, create, prepare, converge<br>INFO     Performing prerun with role_name_check=0...<br>INFO     Running aio &gt; dependency<br>WARNING  Skipping, missing the requirements file.<br>WARNING  Skipping, missing the requirements file.<br>INFO     Running aio &gt; create<br><br>PLAY [Wait for user to read warning] *******************************************<br><br>TASK [Gathering Facts] *********************************************************<br>Monday 03 June 2024  12:02:39 +0000 (0:00:00.020)       0:00:00.020 ***********<br>ok: [localhost]<br>.<br>.<br>.<br>.<br>.<br>PLAY [Configure networking] ****************************************************<br><br>TASK [Gathering Facts] *********************************************************<br>Monday 03 June 2024  12:49:26 +0000 (0:00:00.418)       0:45:34.621 ***********<br>ok: [instance]<br><br>TASK [Add IP address to &quot;br-ex&quot;] ***********************************************<br>Monday 03 June 2024  12:49:28 +0000 (0:00:02.159)       0:45:36.781 ***********<br>ok: [instance]<br><br>TASK [Set &quot;br-ex&quot; interface to &quot;up&quot;] *******************************************<br>Monday 03 June 2024  12:49:28 +0000 (0:00:00.153)       0:45:36.934 ***********<br>ok: [instance]<br><br>PLAY RECAP *********************************************************************<br>instance                   : ok=669  changed=267  unreachable=0    failed=0    skipped=246  rescued=0    ignored=1   <br><br>Monday 03 June 2024  12:49:28 +0000 (0:00:00.304)       0:45:37.239 ***********<br>===============================================================================<br>vexxhost.atmosphere.percona_xtradb_cluster : Apply Percona XtraDB cluster - 203.51s<br>vexxhost.atmosphere.cinder : Deploy Helm chart ------------------------ 157.84s<br>vexxhost.atmosphere.keycloak : Deploy Helm chart ---------------------- 156.65s<br>vexxhost.atmosphere.heat : Deploy Helm chart -------------------------- 120.67s<br>vexxhost.atmosphere.manila : Deploy Helm chart ------------------------ 104.84s<br>vexxhost.atmosphere.nova : Deploy Helm chart -------------------------- 100.67s<br>vexxhost.ceph.osd : Install OSDs --------------------------------------- 89.67s<br>vexxhost.atmosphere.glance : Deploy Helm chart ------------------------- 88.95s<br>vexxhost.atmosphere.magnum : Deploy Helm chart ------------------------- 88.06s<br>vexxhost.atmosphere.octavia : Deploy Helm chart ------------------------ 83.51s<br>vexxhost.atmosphere.keystone : Deploy Helm chart ----------------------- 80.67s<br>vexxhost.atmosphere.neutron : Deploy Helm chart ------------------------ 74.13s<br>vexxhost.atmosphere.barbican : Deploy Helm chart ----------------------- 67.48s<br>vexxhost.ceph.mon : Run Bootstrap coomand ------------------------------ 62.21s<br>vexxhost.atmosphere.placement : Deploy Helm chart ---------------------- 58.82s<br>vexxhost.kubernetes.cluster_api : Set node selector for Cluster API components -- 57.15s<br>vexxhost.atmosphere.glance_image : Download image ---------------------- 53.93s<br>vexxhost.atmosphere.glance_image : Check if image exists --------------- 50.38s<br>vexxhost.atmosphere.neutron : Create networks -------------------------- 36.62s<br>vexxhost.atmosphere.rabbitmq : Deploy cluster -------------------------- 35.65s</pre><p>Le cluster est déployé et je peux vérifier les accès disponibles localement sur ce serveur physique :</p><pre>root@instance:~# apt install python3-openstackclient -y<br><br>root@instance:~# source openrc<br>root@instance:~# openstack endpoint list<br>+----------------------------------+-----------+--------------+-----------------+---------+-----------+------------------------------------------------------------------------------+<br>| ID                               | Region    | Service Name | Service Type    | Enabled | Interface | URL                                                                          |<br>+----------------------------------+-----------+--------------+-----------------+---------+-----------+------------------------------------------------------------------------------+<br>| 0584539654844f7f956088e43836ed4c | RegionOne | swift        | object-store    | True    | public    | https://object-store.131-153-200-197.nip.io/swift/v1/%(tenant_id)s           |<br>| 069df7eb37584d91a22a95e7d36493d3 | RegionOne | manila       | share           | True    | internal  | http://manila-api.openstack.svc.cluster.local:8786/v1                        |<br>| 08b5e9b96ddf4ce79f270f582dc6bf7b | RegionOne | manilav2     | sharev2         | True    | public    | https://share.131-153-200-197.nip.io/v2                                      |<br>| 0b95720b8c0e4de692acf18b769ce8be | RegionOne | heat-cfn     | cloudformation  | True    | admin     | http://heat-cfn.openstack.svc.cluster.local:8000/v1                          |<br>| 120958efeb924a0a98bf03ce807c0ace | RegionOne | cinderv3     | volumev3        | True    | internal  | http://cinder-api.openstack.svc.cluster.local:8776/v3/%(tenant_id)s          |<br>| 1427e413681e4518ac03d768bb44cb60 | RegionOne | placement    | placement       | True    | admin     | http://placement-api.openstack.svc.cluster.local:8778/                       |<br>| 1611e222d7b8447596aa44c0965aec1a | RegionOne | cinderv3     | volumev3        | True    | public    | https://volume.131-153-200-197.nip.io/v3/%(tenant_id)s                       |<br>| 19047158ec1446b5b746682bc8d9dd93 | RegionOne | heat-cfn     | cloudformation  | True    | internal  | http://heat-cfn.openstack.svc.cluster.local:8000/v1                          |<br>| 1e04bacc8aae44b3818de40e386cf68e | RegionOne | barbican     | key-manager     | True    | admin     | http://barbican-api.openstack.svc.cluster.local:9311/                        |<br>| 27d7b0d81a104b54a3dcb8632297707f | RegionOne | keystone     | identity        | True    | admin     | http://keystone-api.openstack.svc.cluster.local:5000/                        |<br>| 2c4218a3da784f98890bcb6ac6cb20ae | RegionOne | heat         | orchestration   | True    | admin     | http://heat-api.openstack.svc.cluster.local:8004/v1/%(project_id)s           |<br>| 2f19518bd66c421eb6a5e25f7c93c96e | RegionOne | manila       | share           | True    | public    | http://manila.openstack.svc.cluster.local/v1                                 |<br>| 3578d37453854cfbafdc18f2be4f0a62 | RegionOne | glance       | image           | True    | public    | https://image.131-153-200-197.nip.io/                                        |<br>| 3a2e106afdbf43689676c85718319f88 | RegionOne | glance       | image           | True    | admin     | http://glance-api.openstack.svc.cluster.local:9292/                          |<br>| 3e3240df5df847bc84c204e0b18783f1 | RegionOne | glance       | image           | True    | internal  | http://glance-api.openstack.svc.cluster.local:9292/                          |<br>| 3f51c888203c433ea31d2ca67cf3e359 | RegionOne | manilav2     | sharev2         | True    | admin     | http://manila-api.openstack.svc.cluster.local:8786/v2                        |<br>| 44f08551b541410d8bb28b3a148dca0f | RegionOne | heat         | orchestration   | True    | internal  | http://heat-api.openstack.svc.cluster.local:8004/v1/%(project_id)s           |<br>| 6501cca34cd5401d8561522f062ec126 | RegionOne | magnum       | container-infra | True    | internal  | http://magnum-api.openstack.svc.cluster.local:9511/v1                        |<br>| 65c4f687017d4ff4b774a61cd670de52 | RegionOne | barbican     | key-manager     | True    | public    | https://key-manager.131-153-200-197.nip.io/                                  |<br>| 695342e32bf84ae48cc0c873227ce1ce | RegionOne | heat         | orchestration   | True    | public    | https://orchestration.131-153-200-197.nip.io/v1/%(project_id)s               |<br>| 71af00dd937e49c28827dadbe6d55bbe | RegionOne | swift        | object-store    | True    | internal  | http://rook-ceph-rgw-ceph.openstack.svc.cluster.local/swift/v1/%(tenant_id)s |<br>| 7ada3efd05b64af1ae726d495fe61a6e | RegionOne | cinderv3     | volumev3        | True    | admin     | http://cinder-api.openstack.svc.cluster.local:8776/v3/%(tenant_id)s          |<br>| 87e74af69cbb4577b4dd29d106aed5fa | RegionOne | magnum       | container-infra | True    | public    | https://container-infra.131-153-200-197.nip.io/v1                            |<br>| 8dae31f3eed946eea30025e56fbfd83a | RegionOne | nova         | compute         | True    | admin     | http://nova-api.openstack.svc.cluster.local:8774/v2.1                        |<br>| 8e562226dccc4df0af3c8cdfdec95084 | RegionOne | barbican     | key-manager     | True    | internal  | http://barbican-api.openstack.svc.cluster.local:9311/                        |<br>| 8f629f7e748d4c3087bf17aaa0ce2e47 | RegionOne | manila       | share           | True    | admin     | http://manila-api.openstack.svc.cluster.local:8786/v1                        |<br>| 91149164a0584145b6344ae1d525457b | RegionOne | keystone     | identity        | True    | public    | https://identity.131-153-200-197.nip.io/                                     |<br>| a936e3ca42a54b6e97672f20e17c095b | RegionOne | neutron      | network         | True    | admin     | http://neutron-server.openstack.svc.cluster.local:9696/                      |<br>| b987ba9af66c4a14ba42d1fd8c1b2285 | RegionOne | placement    | placement       | True    | public    | https://placement.131-153-200-197.nip.io/                                    |<br>| b9e2e43e90d649d5b6089c7474ba30cd | RegionOne | octavia      | load-balancer   | True    | internal  | http://octavia-api.openstack.svc.cluster.local:9876/                         |<br>| bf2839c099f946e39d21a0b6bcad0b87 | RegionOne | neutron      | network         | True    | public    | https://network.131-153-200-197.nip.io/                                      |<br>| bf959da766554e91972fe1da9cff6d8e | RegionOne | heat-cfn     | cloudformation  | True    | public    | https://cloudformation.131-153-200-197.nip.io/v1                             |<br>| d027a62b34ca4eaabc508c04ad8f94e7 | RegionOne | magnum       | container-infra | True    | admin     | http://magnum-api.openstack.svc.cluster.local:9511/v1                        |<br>| d3e857109be14bfabf82e962068b54af | RegionOne | nova         | compute         | True    | public    | https://compute.131-153-200-197.nip.io/v2.1                                  |<br>| d6985c01aca54ec49e0ec1c728fc271b | RegionOne | nova         | compute         | True    | internal  | http://nova-api.openstack.svc.cluster.local:8774/v2.1                        |<br>| d74feae56d034bd7ad421e4588f0731e | RegionOne | octavia      | load-balancer   | True    | admin     | http://octavia-api.openstack.svc.cluster.local:9876/                         |<br>| e7bcb22c547e41489cc7d5732bca4a84 | RegionOne | manilav2     | sharev2         | True    | internal  | http://manila-api.openstack.svc.cluster.local:8786/v2                        |<br>| f005b62e7769497eb54b0c0a3fa3c587 | RegionOne | octavia      | load-balancer   | True    | public    | https://load-balancer.131-153-200-197.nip.io/                                |<br>| f40bb006a4984428b581042a78539ef8 | RegionOne | neutron      | network         | True    | internal  | http://neutron-server.openstack.svc.cluster.local:9696/                      |<br>| f4d8af60368645c7a5f1d9605afb5494 | RegionOne | placement    | placement       | True    | internal  | http://placement-api.openstack.svc.cluster.local:8778/                       |<br>| f5aa8f8ba519480199f224800480e8cb | RegionOne | keystone     | identity        | True    | internal  | http://keystone-api.openstack.svc.cluster.local:5000/                        |<br>+----------------------------------+-----------+--------------+-----------------+---------+-----------+------------------------------------------------------------------------------+</pre><p>Ainsi que des accès via l’Ingress Controller du cluster Kubernetes sous-jacent :</p><pre>root@instance:~# kubectl cluster-info<br>Kubernetes control plane is running at https://10.96.240.10:6443<br>CoreDNS is running at https://10.96.240.10:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy<br><br>To further debug and diagnose cluster problems, use &#39;kubectl cluster-info dump&#39;.<br>root@instance:~# kubectl get nodes -o wide<br>NAME       STATUS   ROLES           AGE   VERSION   INTERNAL-IP       EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION       CONTAINER-RUNTIME<br>instance   Ready    control-plane   60m   v1.28.4   131.153.200.197   &lt;none&gt;        Ubuntu 22.04.4 LTS   5.15.0-105-generic   containerd://1.7.9<br>root@instance:~# kubectl get ing -A<br>NAMESPACE     NAME                                 CLASS        HOSTS                                             ADDRESS        PORTS     AGE<br>auth-system   keycloak                             atmosphere   keycloak.131-153-200-197.nip.io                   10.98.36.135   80, 443   54m<br>monitoring    kube-prometheus-stack-alertmanager   atmosphere   alertmanager.131-153-200-197.nip.io               10.98.36.135   80, 443   53m<br>monitoring    kube-prometheus-stack-grafana        atmosphere   grafana.131-153-200-197.nip.io                    10.98.36.135   80, 443   53m<br>monitoring    kube-prometheus-stack-prometheus     atmosphere   prometheus.131-153-200-197.nip.io                 10.98.36.135   80, 443   53m<br>openstack     cloudformation                       atmosphere   cloudformation.131-153-200-197.nip.io             10.98.36.135   80, 443   33m<br>openstack     compute                              atmosphere   compute.131-153-200-197.nip.io                    10.98.36.135   80, 443   38m<br>openstack     compute-novnc-proxy                  atmosphere   vnc.131-153-200-197.nip.io                        10.98.36.135   80, 443   38m<br>openstack     container-infra                      atmosphere   container-infra.131-153-200-197.nip.io            10.98.36.135   80, 443   27m<br>openstack     container-infra-registry             atmosphere   container-infra-registry.131-153-200-197.nip.io   10.98.36.135   80, 443   27m<br>openstack     dashboard                            atmosphere   dashboard.131-153-200-197.nip.io                  10.98.36.135   80, 443   23m<br>openstack     identity                             atmosphere   identity.131-153-200-197.nip.io                   10.98.36.135   80, 443   51m<br>openstack     image                                atmosphere   image.131-153-200-197.nip.io                      10.98.36.135   80, 443   46m<br>openstack     key-manager                          atmosphere   key-manager.131-153-200-197.nip.io                10.98.36.135   80, 443   49m<br>openstack     load-balancer                        atmosphere   load-balancer.131-153-200-197.nip.io              10.98.36.135   80, 443   30m<br>openstack     network                              atmosphere   network.131-153-200-197.nip.io                    10.98.36.135   80, 443   36m<br>openstack     orchestration                        atmosphere   orchestration.131-153-200-197.nip.io              10.98.36.135   80, 443   33m<br>openstack     placement                            atmosphere   placement.131-153-200-197.nip.io                  10.98.36.135   80, 443   41m<br>openstack     rook-ceph-cluster                    atmosphere   object-store.131-153-200-197.nip.io               10.98.36.135   80, 443   48m<br>openstack     sharev2                              atmosphere   share.131-153-200-197.nip.io                      10.98.36.135   80, 443   23m<br>openstack     volumev3                             atmosphere   volume.131-153-200-197.nip.io                     10.98.36.135   80, 443   42m</pre><p>Le domaine WildCard utilisé ici me donne accès au Dashboard Horizon pour plus de simplicité :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DgAT7LOW2SUDS1_Uuu4rfQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZDPH1m97k1ZLtooPAasgoA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WERMZDhjH5dqW1vbWlADzg.png" /></figure><p>Je charge une image locale d’Ubuntu 24.04 LTS dans le cluster :</p><pre>root@instance:~# cat openrc <br># Ansible managed: Do NOT edit this file manually!<br><br>export OS_IDENTITY_API_VERSION=3<br><br>export OS_AUTH_URL=&quot;https://identity.131-153-200-197.nip.io/v3&quot;<br>export OS_AUTH_TYPE=password<br>export OS_REGION_NAME=&quot;RegionOne&quot;<br>export OS_USER_DOMAIN_NAME=Default<br>export OS_USERNAME=&quot;admin-RegionOne&quot;<br>export OS_PASSWORD=&quot;lzi232PTaHpzoC2HjwSLKepZELQd6ENJ&quot;<br>export OS_PROJECT_DOMAIN_NAME=Default<br>export OS_PROJECT_NAME=admin<br><br>export OS_CACERT=/usr/local/share/ca-certificates/atmosphere.crt</pre><pre>root@instance:~# wget -c https://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img<br><br>Saving to: ‘noble-server-cloudimg-amd64.img’<br><br>noble-server-cloudimg-amd64.img                 100%[=====================================================================================================&gt;] 454.00M  17.9MB/s    in 30s     <br><br>2024-06-03 13:22:40 (15.3 MB/s) - ‘noble-server-cloudimg-amd64.img’ saved [476053504/476053504]<br><br>root@instance:~# openstack image create --public --container-format bare --disk-format qcow2 --file ~/noble-server-cloudimg-amd64.img ubuntu-24.04<br>+------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+<br>| Field            | Value                                                                                                                                                            |<br>+------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+<br>| container_format | bare                                                                                                                                                             |<br>| created_at       | 2024-06-03T13:23:12Z                                                                                                                                             |<br>| disk_format      | qcow2                                                                                                                                                            |<br>| file             | /v2/images/81d8eafa-4054-455c-9640-4e83c0566d21/file                                                                                                             |<br>| id               | 81d8eafa-4054-455c-9640-4e83c0566d21                                                                                                                             |<br>| min_disk         | 0                                                                                                                                                                |<br>| min_ram          | 0                                                                                                                                                                |<br>| name             | ubuntu-24.04                                                                                                                                                     |<br>| owner            | 43321f42e8434f8aa53531bd104e2809                                                                                                                                 |<br>| properties       | locations=&#39;[]&#39;, os_hidden=&#39;False&#39;, owner_specified.openstack.md5=&#39;&#39;, owner_specified.openstack.object=&#39;images/ubuntu-24.04&#39;, owner_specified.openstack.sha256=&#39;&#39; |<br>| protected        | False                                                                                                                                                            |<br>| schema           | /v2/schemas/image                                                                                                                                                |<br>| status           | queued                                                                                                                                                           |<br>| tags             |                                                                                                                                                                  |<br>| updated_at       | 2024-06-03T13:23:12Z                                                                                                                                             |<br>| visibility       | public                                                                                                                                                           |<br>+------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+<br><br>root@instance:~# openstack image list<br>+--------------------------------------+---------------------------+--------+<br>| ID                                   | Name                      | Status |<br>+--------------------------------------+---------------------------+--------+<br>| 04e2f39a-e4ff-426b-aeee-b82acd3bf611 | amphora-x64-haproxy       | active |<br>| 49a3b09d-c191-4c36-8541-31efaffb404d | cirros                    | active |<br>| b7e75cdb-37b0-4f2a-badf-cfdee7bca83d | manila-service-image      | active |<br>| 3c5df46c-7015-411c-8009-afa6695672a6 | ubuntu-2204-kube-v1.27.8s | active |<br>| 81d8eafa-4054-455c-9640-4e83c0566d21 | ubuntu-24.04              | active |<br>+--------------------------------------+---------------------------+--------+</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8u2DwINnORNfR-t1ewHMvg.png" /></figure><p>Configuration d’une topologie réseau pour un rapide test :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MpiV-Sd046CPZj3qgpIVBg.png" /></figure><p>Avec l’image chargée dans Glance, lancement de trois petites instances Ubuntu 24.04 LTS …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0_x7xPMDO2Vyvho5RJ_PEQ.png" /></figure><pre>root@instance:~# openstack server list<br>+--------------------------------------+-------+--------+--------------------------------------+--------------+----------+<br>| ID                                   | Name  | Status | Networks                             | Image        | Flavor   |<br>+--------------------------------------+-------+--------+--------------------------------------+--------------+----------+<br>| 07d6bf6e-edff-4729-9133-31849ea6fe87 | k0s-3 | ACTIVE | network1=10.96.250.216, 11.12.13.185 | ubuntu-24.04 | m1.small |<br>| afd10cda-f99c-4877-9948-a7f25b5e756a | k0s-1 | ACTIVE | network1=10.96.250.211, 11.12.13.99  | ubuntu-24.04 | m1.small |<br>| d70230a1-9fdf-40d9-959d-c9960479b4a5 | k0s-2 | ACTIVE | network1=10.96.250.208, 11.12.13.80  | ubuntu-24.04 | m1.small |<br>+--------------------------------------+-------+--------+--------------------------------------+--------------+----------+</pre><p>Un cluster kubernetes simple sur la base de ces trois instances est alors possible avec k0sctl.</p><p><a href="https://github.com/k0sproject/k0sctl">GitHub - k0sproject/k0sctl: A bootstrapping and management tool for k0s clusters.</a></p><pre>root@instance:~# wget -c https://github.com/k0sproject/k0sctl/releases/download/v0.17.8/k0sctl-linux-x64<br>root@instance:~# mv k0sctl-linux-x64 /usr/local/bin/k0sctl &amp;&amp; chmod +x /usr/local/bin/k0sctl <br>root@instance:~# k0sctl<br>NAME:<br>   k0sctl - k0s cluster management tool<br><br>USAGE:<br>   k0sctl [global options] command [command options] <br><br>COMMANDS:<br>   version     Output k0sctl version<br>   apply       Apply a k0sctl configuration<br>   kubeconfig  Output the admin kubeconfig of the cluster<br>   init        Create a configuration template<br>   reset       Remove traces of k0s from all of the hosts<br>   backup      Take backup of existing clusters state<br>   config      Configuration related sub-commands<br>   completion  <br>   help, h     Shows a list of commands or help for one command<br><br>GLOBAL OPTIONS:<br>   --debug, -d  Enable debug logging (default: false) [$DEBUG]<br>   --trace      Enable trace logging (default: false) [$TRACE]<br>   --no-redact  Do not hide sensitive information in the output (default: false)<br>   --help, -h   show help</pre><pre>root@instance:~# k0sctl init --k0s &gt; k0sctl.yaml<br><br>root@instance:~# cat k0sctl.yaml <br>apiVersion: k0sctl.k0sproject.io/v1beta1<br>kind: Cluster<br>metadata:<br>  name: k0s-cluster<br>spec:<br>  hosts:<br>  - ssh:<br>      address: 10.96.250.211<br>      user: ubuntu<br>      port: 22<br>      keyPath: /root/.ssh/id_rsa<br>    role: controller<br>  - ssh:<br>      address: 10.96.250.208<br>      user: ubuntu<br>      port: 22<br>      keyPath: /root/.ssh/id_rsa<br>    role: worker<br>  - ssh:<br>      address: 10.96.250.216<br>      user: ubuntu<br>      port: 22<br>      keyPath: /root/.ssh/id_rsa<br>    role: worker<br>  k0s:<br>    config:<br>      apiVersion: k0s.k0sproject.io/v1beta1<br>      kind: Cluster<br>      metadata:<br>        name: k0s<br>      spec:<br>        api:<br>          k0sApiPort: 9443<br>          port: 6443<br>        installConfig:<br>          users:<br>            etcdUser: etcd<br>            kineUser: kube-apiserver<br>            konnectivityUser: konnectivity-server<br>            kubeAPIserverUser: kube-apiserver<br>            kubeSchedulerUser: kube-scheduler<br>        konnectivity:<br>          adminPort: 8133<br>          agentPort: 8132<br>        network:<br>          kubeProxy:<br>            disabled: false<br>            mode: iptables<br>          kuberouter:<br>            autoMTU: true<br>            mtu: 0<br>            peerRouterASNs: &quot;&quot;<br>            peerRouterIPs: &quot;&quot;<br>          podCIDR: 10.244.0.0/16<br>          provider: kuberouter<br>          serviceCIDR: 10.96.0.0/12<br>        podSecurityPolicy:<br>          defaultPolicy: 00-k0s-privileged<br>        storage:<br>          type: etcd<br>        telemetry:<br>          enabled: true</pre><pre>root@instance:~# k0sctl apply --config k0sctl.yaml <br><br>⠀⣿⣿⡇⠀⠀⢀⣴⣾⣿⠟⠁⢸⣿⣿⣿⣿⣿⣿⣿⡿⠛⠁⠀⢸⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠀█████████ █████████ ███<br>⠀⣿⣿⡇⣠⣶⣿⡿⠋⠀⠀⠀⢸⣿⡇⠀⠀⠀⣠⠀⠀⢀⣠⡆⢸⣿⣿⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀███          ███    ███<br>⠀⣿⣿⣿⣿⣟⠋⠀⠀⠀⠀⠀⢸⣿⡇⠀⢰⣾⣿⠀⠀⣿⣿⡇⢸⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠀███          ███    ███<br>⠀⣿⣿⡏⠻⣿⣷⣤⡀⠀⠀⠀⠸⠛⠁⠀⠸⠋⠁⠀⠀⣿⣿⡇⠈⠉⠉⠉⠉⠉⠉⠉⠉⢹⣿⣿⠀███          ███    ███<br>⠀⣿⣿⡇⠀⠀⠙⢿⣿⣦⣀⠀⠀⠀⣠⣶⣶⣶⣶⣶⣶⣿⣿⡇⢰⣶⣶⣶⣶⣶⣶⣶⣶⣾⣿⣿⠀█████████    ███    ██████████<br>k0sctl v0.17.8 Copyright 2023, k0sctl authors.<br>Anonymized telemetry of usage will be sent to the authors.<br>By continuing to use k0sctl you agree to these terms:<br>https://k0sproject.io/licenses/eula<br>INFO ==&gt; Running phase: Set k0s version  <br>INFO Looking up latest stable k0s version         <br>INFO Using k0s version v1.30.1+k0s.0              <br>INFO ==&gt; Running phase: Connect to hosts <br>INFO [ssh] 10.96.250.216:22: connected            <br>INFO [ssh] 10.96.250.208:22: connected            <br>INFO [ssh] 10.96.250.211:22: connected            <br>INFO ==&gt; Running phase: Detect host operating systems <br>INFO [ssh] 10.96.250.216:22: is running Ubuntu 24.04 LTS <br>INFO [ssh] 10.96.250.208:22: is running Ubuntu 24.04 LTS <br>INFO [ssh] 10.96.250.211:22: is running Ubuntu 24.04 LTS <br>INFO ==&gt; Running phase: Acquire exclusive host lock <br>INFO ==&gt; Running phase: Prepare hosts    <br>INFO ==&gt; Running phase: Gather host facts <br>INFO [ssh] 10.96.250.216:22: using k0s-3 as hostname <br>INFO [ssh] 10.96.250.211:22: using k0s-1 as hostname <br>INFO [ssh] 10.96.250.208:22: using k0s-2 as hostname <br>INFO [ssh] 10.96.250.211:22: discovered ens3 as private interface <br>INFO [ssh] 10.96.250.208:22: discovered ens3 as private interface <br>INFO [ssh] 10.96.250.216:22: discovered ens3 as private interface <br>INFO [ssh] 10.96.250.211:22: discovered 11.12.13.99 as private address <br>INFO [ssh] 10.96.250.208:22: discovered 11.12.13.80 as private address <br>INFO [ssh] 10.96.250.216:22: discovered 11.12.13.185 as private address <br>INFO ==&gt; Running phase: Validate hosts   <br>INFO ==&gt; Running phase: Validate facts   <br>INFO ==&gt; Running phase: Download k0s on hosts <br>INFO [ssh] 10.96.250.216:22: downloading k0s v1.30.1+k0s.0 <br>INFO [ssh] 10.96.250.211:22: downloading k0s v1.30.1+k0s.0 <br>INFO [ssh] 10.96.250.208:22: downloading k0s v1.30.1+k0s.0 <br>INFO ==&gt; Running phase: Install k0s binaries on hosts <br>INFO [ssh] 10.96.250.211:22: validating configuration <br>INFO ==&gt; Running phase: Configure k0s    <br>INFO [ssh] 10.96.250.211:22: installing new configuration <br>INFO ==&gt; Running phase: Initialize the k0s cluster <br>INFO [ssh] 10.96.250.211:22: installing k0s controller <br>INFO [ssh] 10.96.250.211:22: waiting for the k0s service to start <br>INFO [ssh] 10.96.250.211:22: waiting for kubernetes api to respond <br>INFO ==&gt; Running phase: Install workers  <br>INFO [ssh] 10.96.250.216:22: validating api connection to https://11.12.13.99:6443 <br>INFO [ssh] 10.96.250.208:22: validating api connection to https://11.12.13.99:6443 <br>INFO [ssh] 10.96.250.211:22: generating a join token for worker 1 <br>INFO [ssh] 10.96.250.211:22: generating a join token for worker 2 <br>INFO [ssh] 10.96.250.216:22: writing join token   <br>INFO [ssh] 10.96.250.208:22: writing join token   <br>INFO [ssh] 10.96.250.216:22: installing k0s worker <br>INFO [ssh] 10.96.250.208:22: installing k0s worker <br>INFO [ssh] 10.96.250.216:22: starting service     <br>INFO [ssh] 10.96.250.216:22: waiting for node to become ready <br>INFO [ssh] 10.96.250.208:22: starting service     <br>INFO [ssh] 10.96.250.208:22: waiting for node to become ready <br>INFO ==&gt; Running phase: Release exclusive host lock <br>INFO ==&gt; Running phase: Disconnect from hosts <br>INFO ==&gt; Finished in 42s                 <br>INFO k0s cluster version v1.30.1+k0s.0 is now installed <br>INFO Tip: To access the cluster you can now fetch the admin kubeconfig using: <br>INFO      k0sctl kubeconfig  </pre><p>Kubernetes via k0s est actif et accessible via son fichier kubeconfigspécifique :</p><pre>root@instance:~# k0sctl kubeconfig &gt; kubeconfig<br>root@instance:~# kubectl --kubeconfig=kubeconfig cluster-info<br>Kubernetes control plane is running at https://10.96.250.211:6443<br>CoreDNS is running at https://10.96.250.211:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy<br><br>To further debug and diagnose cluster problems, use &#39;kubectl cluster-info dump&#39;.<br>root@instance:~# kubectl --kubeconfig=kubeconfig get nodes -o wide<br>NAME    STATUS   ROLES    AGE     VERSION       INTERNAL-IP    EXTERNAL-IP   OS-IMAGE           KERNEL-VERSION     CONTAINER-RUNTIME<br>k0s-2   Ready    &lt;none&gt;   2m41s   v1.30.1+k0s   11.12.13.80    &lt;none&gt;        Ubuntu 24.04 LTS   6.8.0-31-generic   containerd://1.7.17<br>k0s-3   Ready    &lt;none&gt;   2m41s   v1.30.1+k0s   11.12.13.185   &lt;none&gt;        Ubuntu 24.04 LTS   6.8.0-31-generic   containerd://1.7.17</pre><pre>root@instance:~# kubectl --kubeconfig=kubeconfig get po,svc -A<br>NAMESPACE     NAME                                  READY   STATUS    RESTARTS   AGE<br>kube-system   pod/coredns-6997b8f8bd-957bd          1/1     Running   0          2m41s<br>kube-system   pod/coredns-6997b8f8bd-ddr5t          1/1     Running   0          2m41s<br>kube-system   pod/konnectivity-agent-2bxgl          1/1     Running   0          2m51s<br>kube-system   pod/konnectivity-agent-4gfsw          1/1     Running   0          2m51s<br>kube-system   pod/kube-proxy-2cq5w                  1/1     Running   0          2m51s<br>kube-system   pod/kube-proxy-m6rnv                  1/1     Running   0          2m51s<br>kube-system   pod/kube-router-p9s4t                 1/1     Running   0          2m51s<br>kube-system   pod/kube-router-qhcp4                 1/1     Running   0          2m51s<br>kube-system   pod/metrics-server-5cd4986bbc-rf4wc   1/1     Running   0          2m57s<br><br>NAMESPACE     NAME                     TYPE        CLUSTER-IP    EXTERNAL-IP   PORT(S)                  AGE<br>default       service/kubernetes       ClusterIP   10.96.0.1     &lt;none&gt;        443/TCP                  3m15s<br>kube-system   service/kube-dns         ClusterIP   10.96.0.10    &lt;none&gt;        53/UDP,53/TCP,9153/TCP   3m5s<br>kube-system   service/metrics-server   ClusterIP   10.97.91.41   &lt;none&gt;        443/TCP                  3m1s</pre><p>Le démonstrateur FC en une commande (habituelle maintenant) :</p><pre>root@instance:~# cat test.yaml <br>---<br>apiVersion: apps/v1<br>kind: Deployment<br>metadata:<br>  name: fcdemo3<br>  labels:<br>    app: fcdemo3<br>spec:<br>  replicas: 4<br>  selector:<br>    matchLabels:<br>      app: fcdemo3<br>  template:<br>    metadata:<br>      labels:<br>        app: fcdemo3<br>    spec:<br>      containers:<br>      - name: fcdemo3<br>        image: mcas/franceconnect-demo2:latest<br>        ports:<br>        - containerPort: 3000<br>---<br>apiVersion: v1<br>kind: Service<br>metadata:<br>  name: fcdemo-service<br>spec:<br>  type: ClusterIP<br>  selector:<br>    app: fcdemo3<br>  ports:<br>  - protocol: TCP<br>    port: 80<br>    targetPort: 3000<br><br>root@instance:~# kubectl --kubeconfig=kubeconfig apply -f test.yaml<br>deployment.apps/fcdemo3 created<br>service/fcdemo-service created</pre><pre>root@instance:~# kubectl --kubeconfig=kubeconfig get po,svc<br>NAME                          READY   STATUS    RESTARTS   AGE<br>pod/fcdemo3-85f6bd87c-7jvpk   1/1     Running   0          13s<br>pod/fcdemo3-85f6bd87c-btv9m   1/1     Running   0          13s<br>pod/fcdemo3-85f6bd87c-nlw9x   1/1     Running   0          13s<br>pod/fcdemo3-85f6bd87c-v66bs   1/1     Running   0          13s<br><br>NAME                     TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)   AGE<br>service/fcdemo-service   ClusterIP   10.98.123.24   &lt;none&gt;        80/TCP    13s<br>service/kubernetes       ClusterIP   10.96.0.1      &lt;none&gt;        443/TCP   8m19s</pre><p>Redirection de port ici pour accès local à ce dernier …</p><pre>root@instance:~# kubectl --kubeconfig=kubeconfig port-forward service/fcdemo-service 12222:80 --address=&#39;0.0.0.0&#39;<br>Forwarding from 0.0.0.0:12222 -&gt; 3000</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rSxXqKBliaa96EQ1njsfyg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IcCUKsL8xABvl4OtHE9AvQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mg3woS3pejwCghRtYJRxFg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xXzCk76pCz6SZub5y0IbHw.png" /></figure><p>Sachant qu’Atmosphere disposait de Magnum pour déployer un cluster Kubernetes intrinsèque …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4_SotIS5Dav1vtG8I3nFQw.png" /></figure><p>Pour conclure, Atmosphere est un projet pour un déploiement simplifié d’un cluster Openstack conteneurisé dans un cluster Kubernetes de base (en reprenant OpenStack Helm) et que l’on retrouve également dans la nouvelle mouture de Canonical MicroStack par exemple …</p><p><a href="https://microstack.run/">OpenStack for the edge, micro clouds and developers</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*Ln7ClaZW7nPlURrI.png" /></figure><p>À suivre !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ac8c46b4232" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gérer des conteneurs qui ressemblent à des machines virtuelles avec Bootloose (successeur de…]]></title>
            <link>https://deep75.medium.com/g%C3%A9rer-des-conteneurs-qui-ressemblent-%C3%A0-des-machines-virtuelles-avec-bootloose-successeur-de-c75f97ce7e13?source=rss-9f1ca3c659fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/c75f97ce7e13</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Karim]]></dc:creator>
            <pubDate>Sun, 31 Mar 2024 18:02:05 GMT</pubDate>
            <atom:updated>2024-03-31T18:02:05.070Z</atom:updated>
            <content:encoded><![CDATA[<h3>Gérer des conteneurs qui ressemblent à des machines virtuelles avec Bootloose (successeur de Footloose) …</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mZMaAMzlDcpc4PXduM2mTQ.png" /></figure><p>Dans plusieurs articles précédents, j’avais décrit l’usage de Footloose, un binaire écrit en Go qui permettait de créer des conteneurs qui ressemblent à des machines virtuelles.</p><ul><li><a href="https://deep75.medium.com/weave-ignite-et-weave-footloose-dans-scaleway-quand-les-machines-virtuelles-se-prennent-pour-des-e28f5312a59f">Weave Ignite et Weave Footloose dans Scaleway : quand les machines virtuelles se prennent pour des…</a></li><li><a href="https://deep75.medium.com/des-clusters-kubernetes-imbriqu%C3%A9s-avec-ignite-firecracker-containerd-kind-et-rancher-34e5e92c257b">Des clusters Kubernetes imbriqués avec Ignite, Firecracker, Containerd, Kind et Rancher …</a></li></ul><blockquote>Ces conteneurs exécutent systemd en tant que PID 1 et un démon ssh qui peut être utilisé pour se connecter au conteneur. Ces “machines” se comportent comme des VM, il est même possible d’y faire tourner dockerd.</blockquote><p><a href="https://github.com/weaveworks/footloose">GitHub - weaveworks/footloose: Container Machines - Containers that look like Virtual Machines</a></p><blockquote>Footloose peut être utilisé pour une variété de tâches, partout où vous aimeriez avoir des machines virtuelles mais voulez des temps de démarrage rapides ou avez besoin de plusieurs d’entre elles.</blockquote><p>C’est au tour de l’équipe à l’origine de k0s de reprendre le flambeau avec Bootloose</p><p><a href="https://github.com/k0sproject/bootloose">GitHub - k0sproject/bootloose: Manage containers that look like virtual machines</a></p><p>Sur le même principe …</p><p>Illustration avec le lancement d’une instance Ubuntu 22.04 LTS en ARM64 Bits dans Hetzner Cloud :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jm7aslQiOonyc2E6FW31CQ.png" /></figure><p>dans laquelle je commence par installer le moteurDocker :</p><pre>root@ubuntu-16gb-hel1-1:~# curl -fsSL https://get.docker.com | sh -<br># Executing docker install script, commit: e5543d473431b782227f8908005543bb4389b8de<br>+ sh -c apt-get update -qq &gt;/dev/null<br>+ sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl &gt;/dev/null<br>+ sh -c install -m 0755 -d /etc/apt/keyrings<br>+ sh -c curl -fsSL &quot;https://download.docker.com/linux/ubuntu/gpg&quot; | gpg --dearmor --yes -o /etc/apt/keyrings/docker.gpg<br>+ sh -c chmod a+r /etc/apt/keyrings/docker.gpg<br>+ sh -c echo &quot;deb [arch=arm64 signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu jammy stable&quot; &gt; /etc/apt/sources.list.d/docker.list<br>+ sh -c apt-get update -qq &gt;/dev/null<br>+ sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq docker-ce docker-ce-cli containerd.io docker-compose-plugin docker-ce-rootless-extras docker-buildx-plugin &gt;/dev/null<br>+ sh -c docker version<br>Client: Docker Engine - Community<br> Version:           26.0.0<br> API version:       1.45<br> Go version:        go1.21.8<br> Git commit:        2ae903e<br> Built:             Wed Mar 20 15:18:14 2024<br> OS/Arch:           linux/arm64<br> Context:           default<br><br>Server: Docker Engine - Community<br> Engine:<br>  Version:          26.0.0<br>  API version:      1.45 (minimum version 1.24)<br>  Go version:       go1.21.8<br>  Git commit:       8b79278<br>  Built:            Wed Mar 20 15:18:14 2024<br>  OS/Arch:          linux/arm64<br>  Experimental:     false<br> containerd:<br>  Version:          1.6.28<br>  GitCommit:        ae07eda36dd25f8a1b98dfbf587313b99c0190bb<br> runc:<br>  Version:          1.1.12<br>  GitCommit:        v1.1.12-0-g51d5e94<br> docker-init:<br>  Version:          0.19.0<br>  GitCommit:        de40ad0<br><br>================================================================================<br><br>To run Docker as a non-privileged user, consider setting up the<br>Docker daemon in rootless mode for your user:<br><br>    dockerd-rootless-setuptool.sh install<br><br>Visit https://docs.docker.com/go/rootless/ to learn about rootless mode.<br><br><br>To run the Docker daemon as a fully privileged service, but granting non-root<br>users access, refer to https://docs.docker.com/go/daemon-access/<br><br>WARNING: Access to the remote API on a privileged Docker daemon is equivalent<br>         to root access on the host. Refer to the &#39;Docker daemon attack surface&#39;<br>         documentation for details: https://docs.docker.com/go/attack-surface/<br><br>================================================================================<br><br>root@ubuntu-16gb-hel1-1:~# docker ps -a<br>CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES</pre><p>Puis récupération du binaire Bootloose depuis GitHub :</p><pre>root@ubuntu-16gb-hel1-1:~# wget -c https://github.com/k0sproject/bootloose/releases/download/v0.7.3/bootloose-linux-arm64<br>HTTP request sent, awaiting response... 200 OK<br>Length: 6291456 (6.0M) [application/octet-stream]<br>Saving to: ‘bootloose-linux-arm64’<br><br>bootloose-linux-arm64                           100%[=====================================================================================================&gt;]   6.00M  21.8MB/s    in 0.3s    <br><br>(21.8 MB/s) - ‘bootloose-linux-arm64’ saved [6291456/6291456]<br><br>root@ubuntu-16gb-hel1-1:~# chmod +x bootloose-linux-arm64 <br>root@ubuntu-16gb-hel1-1:~# mv bootloose-linux-arm64 /usr/local/bin/bootloose<br>root@ubuntu-16gb-hel1-1:~# bootloose<br>bootloose - Container Machines<br><br>Usage:<br>  bootloose [command]<br><br>Available Commands:<br>  completion  Generate the autocompletion script for the specified shell<br>  config      Manage cluster configuration<br>  create      Create a cluster<br>  delete      Delete a cluster<br>  help        Help about any command<br>  show        Show all running machines or a single machine with a given hostname.<br>  ssh         SSH into a machine<br>  start       Start cluster machines<br>  stop        Stop cluster machines<br>  version     Print bootloose version<br><br>Flags:<br>  -c, --config string   Cluster configuration file (default &quot;bootloose.yaml&quot;)<br>  -h, --help            help for bootloose<br><br>Use &quot;bootloose [command] --help&quot; for more information about a command.</pre><p><a href="https://github.com/k0sproject/bootloose/releases">Releases · k0sproject/bootloose</a></p><p>Et création de de fichier de configuration YAML pour créer mes instances avec cette image :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XGW6u6coU1MRcG_CdRQDjA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*Fi6gpjp-YY3DKdME.jpg" /></figure><pre>root@ubuntu-16gb-hel1-1:~# bootloose config create --replicas 3 --image quay.io/k0sproject/bootloose-ubuntu22.04:latest</pre><pre>root@ubuntu-16gb-hel1-1:~# cat bootloose.yaml <br>cluster:<br>  name: cluster<br>  privateKey: ~/.ssh/id_rsa<br>machines:<br>- count: 3<br>  spec:<br>    image: quay.io/k0sproject/bootloose-ubuntu22.04:latest<br>    name: node%d<br>    portMappings:<br>    - containerPort: 22<br>    privileged: true<br>    volumes:<br>    - type: volume<br>      destination: /var/lib/k0s</pre><pre>root@ubuntu-16gb-hel1-1:~# bootloose create<br>INFO[0000] Docker Image: quay.io/k0sproject/bootloose-ubuntu22.04:latest present locally <br>INFO[0000] Creating machine: cluster-node0 ...          <br>INFO[0000] Creating machine: cluster-node1 ...          <br>INFO[0000] Creating machine: cluster-node2 ...  </pre><pre>root@ubuntu-16gb-hel1-1:~# docker ps -a<br>CONTAINER ID   IMAGE                                             COMMAND        CREATED              STATUS              PORTS                                     NAMES<br>f452da977dd6   quay.io/k0sproject/bootloose-ubuntu22.04:latest   &quot;/sbin/init&quot;   About a minute ago   Up About a minute   0.0.0.0:32770-&gt;22/tcp, :::32770-&gt;22/tcp   cluster-node2<br>790a6594d4a3   quay.io/k0sproject/bootloose-ubuntu22.04:latest   &quot;/sbin/init&quot;   About a minute ago   Up About a minute   0.0.0.0:32769-&gt;22/tcp, :::32769-&gt;22/tcp   cluster-node1<br>c674c7d3551f   quay.io/k0sproject/bootloose-ubuntu22.04:latest   &quot;/sbin/init&quot;   About a minute ago   Up About a minute   0.0.0.0:32768-&gt;22/tcp, :::32768-&gt;22/tcp   cluster-node0<br><br>root@ubuntu-16gb-hel1-1:~# docker inspect $(docker ps -aq) | grep IPAddress<br>            &quot;SecondaryIPAddresses&quot;: null,<br>            &quot;IPAddress&quot;: &quot;172.17.0.4&quot;,<br>                    &quot;IPAddress&quot;: &quot;172.17.0.4&quot;,<br>            &quot;SecondaryIPAddresses&quot;: null,<br>            &quot;IPAddress&quot;: &quot;172.17.0.3&quot;,<br>                    &quot;IPAddress&quot;: &quot;172.17.0.3&quot;,<br>            &quot;SecondaryIPAddresses&quot;: null,<br>            &quot;IPAddress&quot;: &quot;172.17.0.2&quot;,<br>                    &quot;IPAddress&quot;: &quot;172.17.0.2&quot;,<br><br>root@ubuntu-16gb-hel1-1:~# for i in {2..4}; do ssh root@172.17.0.$i &#39;hostname&#39;; done<br>Warning: Permanently added &#39;172.17.0.2&#39; (ED25519) to the list of known hosts.<br>node0<br>Warning: Permanently added &#39;172.17.0.3&#39; (ED25519) to the list of known hosts.<br>node1<br>Warning: Permanently added &#39;172.17.0.4&#39; (ED25519) to the list of known hosts.<br>node2</pre><p>Les instances sont donc accessibles en SSH et je vais utiliser k0sctl pour y créer un cluster Kubernetes via k0s:</p><p><a href="https://github.com/k0sproject/k0sctl">GitHub - k0sproject/k0sctl: A bootstrapping and management tool for k0s clusters.</a></p><pre>root@ubuntu-16gb-hel1-1:~# chmod +x k0sctl-linux-arm64 <br>root@ubuntu-16gb-hel1-1:~# mv k0sctl-linux-arm64 /usr/local/bin/k0sctl<br>root@ubuntu-16gb-hel1-1:~# k0sctl<br>NAME:<br>   k0sctl - k0s cluster management tool<br><br>USAGE:<br>   k0sctl [global options] command [command options] <br><br>COMMANDS:<br>   version     Output k0sctl version<br>   apply       Apply a k0sctl configuration<br>   kubeconfig  Output the admin kubeconfig of the cluster<br>   init        Create a configuration template<br>   reset       Remove traces of k0s from all of the hosts<br>   backup      Take backup of existing clusters state<br>   config      Configuration related sub-commands<br>   completion  <br>   help, h     Shows a list of commands or help for one command<br><br>GLOBAL OPTIONS:<br>   --debug, -d  Enable debug logging (default: false) [$DEBUG]<br>   --trace      Enable trace logging (default: false) [$TRACE]<br>   --no-redact  Do not hide sensitive information in the output (default: false)<br>   --help, -h   show help</pre><p>Initialisation du cluster dans Bootloose via ce fichier de configuration YAML :</p><pre>root@ubuntu-16gb-hel1-1:~# k0sctl init --k0s &gt; k0sctl.yaml</pre><pre>root@ubuntu-16gb-hel1-1:~# cat k0sctl.yaml <br>apiVersion: k0sctl.k0sproject.io/v1beta1<br>kind: Cluster<br>metadata:<br>  name: k0s-cluster<br>spec:<br>  hosts:<br>  - ssh:<br>      address: 172.17.0.2<br>      user: root<br>      port: 22<br>      keyPath: /root/.ssh/id_rsa<br>    role: controller<br>  - ssh:<br>      address: 172.17.0.3<br>      user: root<br>      port: 22<br>      keyPath: /root/.ssh/id_rsa<br>    role: worker<br>  - ssh:<br>      address: 172.17.0.4<br>      user: root<br>      port: 22<br>      keyPath: /root/.ssh/id_rsa<br>    role: worker<br>  k0s:<br>    version: null<br>    versionChannel: stable<br>    dynamicConfig: false<br>    config:<br>      apiVersion: k0s.k0sproject.io/v1beta1<br>      kind: Cluster<br>      metadata:<br>        name: k0s<br>      spec:<br>        api:<br>          k0sApiPort: 9443<br>          port: 6443<br>        installConfig:<br>          users:<br>            etcdUser: etcd<br>            kineUser: kube-apiserver<br>            konnectivityUser: konnectivity-server<br>            kubeAPIserverUser: kube-apiserver<br>            kubeSchedulerUser: kube-scheduler<br>        konnectivity:<br>          adminPort: 8133<br>          agentPort: 8132<br>        network:<br>          kubeProxy:<br>            disabled: false<br>            mode: iptables<br>          kuberouter:<br>            autoMTU: true<br>            mtu: 0<br>            peerRouterASNs: &quot;&quot;<br>            peerRouterIPs: &quot;&quot;<br>          podCIDR: 10.244.0.0/16<br>          provider: kuberouter<br>          serviceCIDR: 10.96.0.0/12<br>        podSecurityPolicy:<br>          defaultPolicy: 00-k0s-privileged<br>        storage:<br>          type: etcd<br>        telemetry:<br>          enabled: false</pre><p>Lancement de la création du cluster k0s avec ce fichier de configuration :</p><pre>root@ubuntu-16gb-hel1-1:~# k0sctl apply --config k0sctl.yaml <br><br>⠀⣿⣿⡇⠀⠀⢀⣴⣾⣿⠟⠁⢸⣿⣿⣿⣿⣿⣿⣿⡿⠛⠁⠀⢸⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠀█████████ █████████ ███<br>⠀⣿⣿⡇⣠⣶⣿⡿⠋⠀⠀⠀⢸⣿⡇⠀⠀⠀⣠⠀⠀⢀⣠⡆⢸⣿⣿⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀███          ███    ███<br>⠀⣿⣿⣿⣿⣟⠋⠀⠀⠀⠀⠀⢸⣿⡇⠀⢰⣾⣿⠀⠀⣿⣿⡇⢸⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠀███          ███    ███<br>⠀⣿⣿⡏⠻⣿⣷⣤⡀⠀⠀⠀⠸⠛⠁⠀⠸⠋⠁⠀⠀⣿⣿⡇⠈⠉⠉⠉⠉⠉⠉⠉⠉⢹⣿⣿⠀███          ███    ███<br>⠀⣿⣿⡇⠀⠀⠙⢿⣿⣦⣀⠀⠀⠀⣠⣶⣶⣶⣶⣶⣶⣿⣿⡇⢰⣶⣶⣶⣶⣶⣶⣶⣶⣾⣿⣿⠀█████████    ███    ██████████<br>k0sctl v0.17.5 Copyright 2023, k0sctl authors.<br>Anonymized telemetry of usage will be sent to the authors.<br>By continuing to use k0sctl you agree to these terms:<br>https://k0sproject.io/licenses/eula<br>INFO ==&gt; Running phase: Set k0s version  <br>INFO Looking up latest stable k0s version         <br>INFO Using k0s version v1.29.2+k0s.0              <br>INFO ==&gt; Running phase: Connect to hosts <br>INFO [ssh] 172.17.0.4:22: connected               <br>INFO [ssh] 172.17.0.3:22: connected               <br>INFO [ssh] 172.17.0.2:22: connected               <br>INFO ==&gt; Running phase: Detect host operating systems <br>INFO [ssh] 172.17.0.4:22: is running Ubuntu 22.04.3 LTS <br>INFO [ssh] 172.17.0.2:22: is running Ubuntu 22.04.3 LTS <br>INFO [ssh] 172.17.0.3:22: is running Ubuntu 22.04.3 LTS <br>INFO ==&gt; Running phase: Acquire exclusive host lock <br>INFO ==&gt; Running phase: Prepare hosts    <br>INFO [ssh] 172.17.0.2:22: is a container, applying a fix <br>INFO [ssh] 172.17.0.3:22: is a container, applying a fix <br>INFO [ssh] 172.17.0.4:22: is a container, applying a fix <br>INFO ==&gt; Running phase: Gather host facts <br>INFO [ssh] 172.17.0.4:22: using node2 as hostname <br>INFO [ssh] 172.17.0.3:22: using node1 as hostname <br>INFO [ssh] 172.17.0.2:22: using node0 as hostname <br>INFO [ssh] 172.17.0.4:22: discovered eth0 as private interface <br>INFO [ssh] 172.17.0.3:22: discovered eth0 as private interface <br>INFO [ssh] 172.17.0.2:22: discovered eth0 as private interface <br>INFO ==&gt; Running phase: Validate hosts   <br>INFO ==&gt; Running phase: Validate facts   <br>INFO ==&gt; Running phase: Download k0s on hosts <br>INFO [ssh] 172.17.0.4:22: downloading k0s v1.29.2+k0s.0 <br>INFO [ssh] 172.17.0.3:22: downloading k0s v1.29.2+k0s.0 <br>INFO [ssh] 172.17.0.2:22: downloading k0s v1.29.2+k0s.0 <br>INFO ==&gt; Running phase: Install k0s binaries on hosts <br>INFO [ssh] 172.17.0.2:22: validating configuration <br>INFO ==&gt; Running phase: Configure k0s    <br>INFO [ssh] 172.17.0.2:22: installing new configuration <br>INFO ==&gt; Running phase: Initialize the k0s cluster <br>INFO [ssh] 172.17.0.2:22: installing k0s controller <br>INFO [ssh] 172.17.0.2:22: waiting for the k0s service to start <br>INFO [ssh] 172.17.0.2:22: waiting for kubernetes api to respond <br>INFO ==&gt; Running phase: Install workers  <br>INFO [ssh] 172.17.0.3:22: validating api connection to https://172.17.0.2:6443 <br>INFO [ssh] 172.17.0.4:22: validating api connection to https://172.17.0.2:6443 <br>INFO [ssh] 172.17.0.2:22: generating a join token for worker 1 <br>INFO [ssh] 172.17.0.2:22: generating a join token for worker 2 <br>INFO [ssh] 172.17.0.4:22: writing join token      <br>INFO [ssh] 172.17.0.3:22: writing join token      <br>INFO [ssh] 172.17.0.3:22: installing k0s worker   <br>INFO [ssh] 172.17.0.4:22: installing k0s worker   <br>INFO [ssh] 172.17.0.4:22: starting service        <br>INFO [ssh] 172.17.0.3:22: starting service        <br>INFO [ssh] 172.17.0.4:22: waiting for node to become ready <br>INFO [ssh] 172.17.0.3:22: waiting for node to become ready <br>INFO ==&gt; Running phase: Release exclusive host lock <br>INFO ==&gt; Running phase: Disconnect from hosts <br>INFO ==&gt; Finished in 48s                 <br>INFO k0s cluster version v1.29.2+k0s.0 is now installed <br>INFO Tip: To access the cluster you can now fetch the admin kubeconfig using: <br>INFO      k0sctl kubeconfig</pre><p>Je peux alors récupérer le fichier kubeconfig pour l’utilisation locale du client kubectl :</p><pre>root@ubuntu-16gb-hel1-1:~# mkdir .kube<br>root@ubuntu-16gb-hel1-1:~# k0sctl kubeconfig &gt; .kube/config<br>root@ubuntu-16gb-hel1-1:~# cat .kube/config<br>apiVersion: v1<br>clusters:<br>- cluster:<br>    certificate-authority-data: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSURBRENDQWVpZ0F3SUJBZ0lVSnhLUU9xRlVzZ0NnY0FiTWNDdEFSTXlmNDFVd0RRWUpLb1pJaHZjTkFRRUwKQlFBd0dERVdNQlFHQTFVRUF4TU5hM1ZpWlhKdVpYUmxjeTFqWVRBZUZ3MHlOREF6TXpFeE5qQXhNREJhRncwegpOREF6TWpreE5qQXhNREJhTUJneEZqQVVCZ05WQkFNVERXdDFZbVZ5Ym1WMFpYTXRZMkV3Z2dFaU1BMEdDU3FHClNJYjNEUUVCQVFVQUE0SUJEd0F3Z2dFS0FvSUJBUURXM3V4cVZtMUdMWWNJWlozMDIrajcwTXQ3Y1Y1Zkw3ZmYKcDNwaURhUVk1d1RGMHVmMEVWcDZqQXV5TVpNaGtWTzlSSmo2TGYyb0xNcVV1V0ZqVzFKdVZUVHY5U0JDc1FhVApudVpxVktyWnJ0Nkt5bm1zaVBuWTlMZW5wWklkdzA4NUZnOHdWdGFlclVmOUlaaUMrSEZPL1grdjlIOUFySlJJCjVNby80dzBaZEJjdXVUcEREVzZpcTNNMjF2b1pCR3Jwbk43TkcvWUpLcGNwM2xlbVV5d1JHL0dEMisyTlRML08KdEx5cmF4TDVWVkVYbENEbTFlTXJZOXBzSjNQcDJySmE0RmxyMGRVVFJRUHcycjhBUUxyTFhJUmFBYXpEV3lBLwpKR1NKZG81YUdrL3NxM2l3clRJb3c0UmlwRGRQWmV2UkdZSlRLaWZWOStRYk14bkVuUEZSQWdNQkFBR2pRakJBCk1BNEdBMVVkRHdFQi93UUVBd0lCQmpBUEJnTlZIUk1CQWY4RUJUQURBUUgvTUIwR0ExVWREZ1FXQkJScFl0V2MKMERrSlRaTDFxR0tkK284N1ZndTFBakFOQmdrcWhraUc5dzBCQVFzRkFBT0NBUUVBbWtGVTBYam14ZWRPMDFtegozWU9QS3hBeTg2N1NpMlM0WTRMcDNqL3NCcW9TWVlkYldzS3c2Wmx1aTdra2VYUEMvM0pJRTd4YjNoL0p6WWxvCnRZMEliOEpnUnZvVk1sV0ZHNitxMnNnZEo3cmx6blg1QXBQZkRqUXY5RUJHR3VXM21IY1UxbXVCUStrUG9JK2cKaU5OZzFITjRoYllYMVJOMitOK3pKcVNVaWh1WFZDbVhFa2YwQ05WU3VyTEZ6cGNKWWJpNWowVVcwYmRhVWFpTwpJRDJOd3VZcUhDNS96RDM0RDB6T1RVMzRtUTVsZDRUYUx4ZmlwRzZrWDVVSEJtT0U5d3lIbVZuY2VzelJ0alZTCnlFblNJV0g1cmM5Sk84RVBXLzVPRTJsb2E3a240U05iQU5NbUNFaVZtZE9IdU5NSHFGaUQxR2oxOWI5MzVpSnkKUnpGS2hBPT0KLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo=<br>    server: https://172.17.0.2:6443<br>  name: k0s-cluster<br>contexts:<br>- context:<br>    cluster: k0s-cluster<br>    user: admin<br>  name: k0s-cluster<br>current-context: k0s-cluster<br>kind: Config<br>preferences: {}<br>users:<br>- name: admin<br>  user:<br>    client-certificate-data: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSURXVENDQWtHZ0F3SUJBZ0lVY3lhN3dQUGVIR0c1eUM3WWdUV1FCZnlNM2lJd0RRWUpLb1pJaHZjTkFRRUwKQlFBd0dERVdNQlFHQTFVRUF4TU5hM1ZpWlhKdVpYUmxjeTFqWVRBZUZ3MHlOREF6TXpFeE5qQXhNREJhRncweQpOVEF6TXpFeE5qQXhNREJhTURReEZ6QVZCZ05WQkFvVERuTjVjM1JsYlRwdFlYTjBaWEp6TVJrd0Z3WURWUVFECkV4QnJkV0psY201bGRHVnpMV0ZrYldsdU1JSUJJakFOQmdrcWhraUc5dzBCQVFFRkFBT0NBUThBTUlJQkNnS0MKQVFFQTFrbjJONVorWEt0MW50N3A1QSt2YWQ5OU9DQ25DQ1FKN1JDeXUzTlRaZXlPWDlwK2lRNzBqaC9mWTZjagovNElFMDVDQlJNZzU1cGtVSWszc0k5anJqNFhBcmRaSnQ1QTFUbDZFY0tuWEQ2NzJyWFV4bVlsRG9FK3p6SitkClc1VnVkc0JmbXVqRnluTGJyT2xDYzZEMDlOWmo5b24zRVlGK0dhcXFBTG5wOU9mNENkaFdLL3hYcWVabFBPaFMKZ2RLdERYVzRXYjlEVEZpbytXQ2RObmR6NWd5SUF5OTM3akRzUG9ESEl2OXdEMkVkd2JSVzNMUERjRjhFaFpKWQpUcUV1Z2F0bzB6ek1vaVZzdkptNVZSU0ZjS2h6S1NkZW1obnFyaTBLWXFFTG9Oa2QwcnFkbFF2cnhCSUlvd1E1Cnl4TWhnOHhRb3pDSUtVZXY5SVhoVTlLT2VRSURBUUFCbzM4d2ZUQU9CZ05WSFE4QkFmOEVCQU1DQmFBd0hRWUQKVlIwbEJCWXdGQVlJS3dZQkJRVUhBd0VHQ0NzR0FRVUZCd01DTUF3R0ExVWRFd0VCL3dRQ01BQXdIUVlEVlIwTwpCQllFRk5SbjV4ek1qVXZSeFVtRXdmbzBLVm45cFgzME1COEdBMVVkSXdRWU1CYUFGR2xpMVp6UU9RbE5rdldvCllwMzZqenRXQzdVQ01BMEdDU3FHU0liM0RRRUJDd1VBQTRJQkFRQjRqU29XNmpnZmRkMlFGM0FRNWxJckVSMFkKQVJSV1RtNTdtTkZPM041OE1PZXR1UDAzOWxvSnIrbDY4aXVQcEUyd2VoL1hTNGxrM3B6dSszSS9IVDNlNW1PcwpiU0pGMXZWbHlaZnZTd1BveEMxcVBPakR3R28xQW1xUUpYRzhjc1E1WWVPR3lVN3BjdjY0KzRrL2xXQmovSEliCmQ4ZnVkMzh4cUo5SUV5SXdBU0lVenhVbllPZ1ZyOWlzRGtxTlk4czBtc3loQXpFYkNQdDQ2NFhiU0pqWG40aSsKOTFVK2FFZG1BMHN5Mi9jc2h6TFZCYzlOanJER1Yya0ZTL2hQNU9YZ0ZycEpEcnNnRVVOcjRudzNRaEl0RkJvdAp4Q2VXYkxTdXFPWTJjcnVvU1hWdmMrdFkyV0xWZ0RQVDRkZ3E3UGhhZm5oTUJkNmxyME55WFNuVzdOWFQKLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo=<br>    client-key-data: LS0tLS1CRUdJTiBSU0EgUFJJVkFURSBLRVktLS0tLQpNSUlFcEFJQkFBS0NBUUVBMWtuMk41WitYS3QxbnQ3cDVBK3ZhZDk5T0NDbkNDUUo3UkN5dTNOVFpleU9YOXArCmlRNzBqaC9mWTZjai80SUUwNUNCUk1nNTVwa1VJazNzSTlqcmo0WEFyZFpKdDVBMVRsNkVjS25YRDY3MnJYVXgKbVlsRG9FK3p6SitkVzVWdWRzQmZtdWpGeW5MYnJPbENjNkQwOU5aajlvbjNFWUYrR2FxcUFMbnA5T2Y0Q2RoVwpLL3hYcWVabFBPaFNnZEt0RFhXNFdiOURURmlvK1dDZE5uZHo1Z3lJQXk5MzdqRHNQb0RISXY5d0QyRWR3YlJXCjNMUERjRjhFaFpKWVRxRXVnYXRvMHp6TW9pVnN2Sm01VlJTRmNLaHpLU2RlbWhucXJpMEtZcUVMb05rZDBycWQKbFF2cnhCSUlvd1E1eXhNaGc4eFFvekNJS1VldjlJWGhVOUtPZVFJREFRQUJBb0lCQUFhR3dpVDNSR24ySHVMegp6eFBQRm55Vy9lMVRzVUtpTmxzdUF3T0tnNk83REtzR3NJdmtGTGF2YWRKVEtObURVRHBSVUY2VDZvK0hZZ0daCmRmT3hpNXNYYThMZm4rY2pVVHhOektMUnlXY0U0U1p2UjA5eHlzbDdJL0s3ZWNOc1RhejROdkUwM2JGSXhrQUIKNnJBeTJzTUtOSWt4c29DcC9Qa3pKWEpZTnpQcVBtL05Kb3hja1h5KzVXRUxiY25Od2lxUUZzU09zT21ldEZ3YQpYcTZrSkVYRzIwVGpvQjg0SlFsNldNN0M5TFp0TWUrcnpsRGdsZFl1ZU92M1FWSE9FU0d2T0VuTFh3TEVSdkg3CmpPbUs4L040dU53L0NpTXJlUjh0WWR2dVBQNVA2Z1V5OUdmdXc2bkM4SzlTOE9CSVZmOWpxRjlsdG9wZndhNVMKRmdCd1BnRUNnWUVBNEI4T0hVZmp1ajR1amNyU01RYm0xQzRhN0QxckJ3YmxuY2RuNFlSYndpKzhOdmhEcGt5SQowMjBod1czRWpUTGJTSTB5UGJvNnQ4MWJEZk1xcjdudm1CblBZTDN2T1lmY3hDRklMcWJwSHd3M1h3aTBsM1BuCmhKVkZyaGJZckthSlVNcDZXVW9zTGdpVDE3MWx2ZnRRZFd5WGpWaGhLQ25SVTJSTExIOEg5NUVDZ1lFQTlNVGgKQWMyaTVSTnRzWDFFOTBFQjZUK0Rxekd3WkQ5WG1YVFQ4M3hrSzVENWV5UzIyUFpGa0NVU3pTSUZtVkpHSzh1ZwpuL2tQQTVZbWMzQUNiWEptVHlDQStSTkxhMU5TTDhGNXN4RzJ3Ris4OXNLVDBhT3VnNE5Ld1RHYkd6QVFKSjN0CitndmcwYXhJQW04b2RrU1RMbTg3K2N0UDVWK2QyNGNHVmh4VHhHa0NnWUVBaE5uancvZVpSZzBXQzNidW9hRTEKc3hDaFpPZ0RTV2NOTlRtK21pK2JOTUNYRVA2Wkd6ckM0SkVRTVZpZjZoTDdhVVpKUWMzaWdKRjZLQXE4Z3UzMAoySFIwT1NSZGFmemZJR09hSmcxS290emE5YnB6VWxPaUtUVlMySjh5VVNWbXdEMUZ5U2Z1aUZzTlNCVTgraUMrCjBOeE4rYnNwM0dUdGNFRkRUbHorbkFFQ2dZQXBOTS9RZHViNmU2Zlczb2p5dXgzd1A0SVNHdjVnRWczVVJzZTcKMFBBb0tYTG1tVXF6QWRxNkpwT2d0eDZNTGo2ajl0Ym10NDRnZzNHYnMzcWxKRUkzQmZqUWRjQVhwR0pNcWR5cwpHY3BUWG9xNFhBOTRsbjYxb3krOWtIVlZRV1VtVlBRUVNWbWkwc2NZcWMvOUFSUnFGODNZQXJORG9USTVGK1VvCk1BS21LUUtCZ1FDZ0tSOEpYMkpOakR6QjVWd3lwdmo3SDdFNFV4Q1FBVXdZZ1JVZ0VCUThZZElPUitSWTFuREEKUWRLd1NOaWxodWxrTjFERFVCZmZqUHhJWndTNExJZEkyN0lqTHlqMFUvbDFrMkludU94OFdHck1hUnp6WXRGcgpTTjhQV2x6eERZTHNHaVpyR2MzVXk0Znd6Ty9lV2xFUFpod0NRVk5lTFpHcFRCYVpvbUIxQkE9PQotLS0tLUVORCBSU0EgUFJJVkFURSBLRVktLS0tLQo=</pre><pre>root@ubuntu-16gb-hel1-1:~# curl -LO https://dl.k8s.io/release/v1.29.2/bin/linux/arm64/kubectl &amp;&amp; chmod +x kubectl &amp;&amp; mv kubectl /usr/local/bin/<br><br>root@ubuntu-16gb-hel1-1:~# chmod 400 .kube/config<br>root@ubuntu-16gb-hel1-1:~# kubectl cluster-info<br>Kubernetes control plane is running at https://172.17.0.2:6443<br>CoreDNS is running at https://172.17.0.2:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy<br><br>To further debug and diagnose cluster problems, use &#39;kubectl cluster-info dump&#39;.</pre><p>Le cluster est alors opérationnel et actif avec deux noeuds Workers :</p><pre>root@ubuntu-16gb-hel1-1:~# kubectl get nodes -o wide<br>NAME    STATUS   ROLES    AGE     VERSION       INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION       CONTAINER-RUNTIME<br>node1   Ready    &lt;none&gt;   4m58s   v1.29.2+k0s   172.17.0.3    &lt;none&gt;        Ubuntu 22.04.3 LTS   5.15.0-100-generic   containerd://1.7.13<br>node2   Ready    &lt;none&gt;   4m58s   v1.29.2+k0s   172.17.0.4    &lt;none&gt;        Ubuntu 22.04.3 LTS   5.15.0-100-generic   containerd://1.7.13<br><br>root@ubuntu-16gb-hel1-1:~# kubectl get po,svc -A<br>NAMESPACE     NAME                                  READY   STATUS    RESTARTS   AGE<br>kube-system   pod/coredns-555d98c87b-7dxxh          1/1     Running   0          5m<br>kube-system   pod/coredns-555d98c87b-9ngzm          1/1     Running   0          5m<br>kube-system   pod/konnectivity-agent-4fb6m          1/1     Running   0          5m5s<br>kube-system   pod/konnectivity-agent-kj99g          1/1     Running   0          5m5s<br>kube-system   pod/kube-proxy-6pbnw                  1/1     Running   0          5m5s<br>kube-system   pod/kube-proxy-xg4mh                  1/1     Running   0          5m5s<br>kube-system   pod/kube-router-tvzsb                 1/1     Running   0          5m5s<br>kube-system   pod/kube-router-wt97k                 1/1     Running   0          5m5s<br>kube-system   pod/metrics-server-7556957bb7-qtgd2   1/1     Running   0          5m6s<br><br>NAMESPACE     NAME                     TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                  AGE<br>default       service/kubernetes       ClusterIP   10.96.0.1        &lt;none&gt;        443/TCP                  5m23s<br>kube-system   service/kube-dns         ClusterIP   10.96.0.10       &lt;none&gt;        53/UDP,53/TCP,9153/TCP   5m14s<br>kube-system   service/metrics-server   ClusterIP   10.100.127.105   &lt;none&gt;        443/TCP                  5m10s</pre><p>Je vais utiliser l’image Docker du projet Kasmweb pour obtenir un Desktop en ligne au sein de ce cluster :</p><ul><li><a href="https://hub.docker.com/r/kasmweb/ubuntu-jammy-dind">Docker</a></li><li><a href="https://kasmweb.com/docs/latest/guide/custom_images.html#rolling-docker-images">Default Docker Images - Kasm 1.15.0 documentation</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NS8iJRg5CP2j1kb2h_2g8A.png" /></figure><p>Pour cela conversion de la formule donnée dans le Docker Hub en fichier YAML pour docker-compose via Composerize :</p><p><a href="https://www.composerize.com/">Composerize</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aZ-mIuYCwR7DN3lf-Emd7Q.png" /></figure><p>Puis conversion en manifests YAML via Kompose:</p><pre>root@ubuntu-16gb-hel1-1:~# cat docker-compose.yml <br>name: ubuntu<br>services:<br>    ubuntu-jammy-dind:<br>        stdin_open: true<br>        tty: true<br>        shm_size: 512m<br>        ports:<br>            - 6901:6901<br>        environment:<br>            - VNC_PW=password<br>        image: kasmweb/ubuntu-jammy-dind:1.14.0-rolling<br><br>root@ubuntu-16gb-hel1-1:~# ./kompose convert<br>INFO Kubernetes file &quot;ubuntu-jammy-dind-service.yaml&quot; created <br>INFO Kubernetes file &quot;ubuntu-jammy-dind-deployment.yaml&quot; created <br><br>root@ubuntu-16gb-hel1-1:~# cat ubuntu-jammy-dind-deployment.yaml <br>apiVersion: apps/v1<br>kind: Deployment<br>metadata:<br>  annotations:<br>    kompose.cmd: ./kompose convert<br>    kompose.version: 1.32.0 (765fde254)<br>  labels:<br>    io.kompose.service: ubuntu-jammy-dind<br>  name: ubuntu-jammy-dind<br>spec:<br>  replicas: 1<br>  selector:<br>    matchLabels:<br>      io.kompose.service: ubuntu-jammy-dind<br>  template:<br>    metadata:<br>      annotations:<br>        kompose.cmd: ./kompose convert<br>        kompose.version: 1.32.0 (765fde254)<br>      labels:<br>        io.kompose.network/ubuntu-default: &quot;true&quot;<br>        io.kompose.service: ubuntu-jammy-dind<br>    spec:<br>      containers:<br>        - env:<br>            - name: VNC_PW<br>              value: password<br>          image: kasmweb/ubuntu-jammy-dind:1.14.0-rolling<br>          name: ubuntu-jammy-dind<br>          ports:<br>            - containerPort: 6901<br>              hostPort: 6901<br>              protocol: TCP<br>          stdin: true<br>          tty: true<br>      restartPolicy: Always<br><br>root@ubuntu-16gb-hel1-1:~# cat ubuntu-jammy-dind-service.yaml <br>apiVersion: v1<br>kind: Service<br>metadata:<br>  annotations:<br>    kompose.cmd: ./kompose convert<br>    kompose.version: 1.32.0 (765fde254)<br>  labels:<br>    io.kompose.service: ubuntu-jammy-dind<br>  name: ubuntu-jammy-dind<br>spec:<br>  ports:<br>    - name: &quot;6901&quot;<br>      port: 6901<br>      targetPort: 6901<br>  selector:<br>    io.kompose.service: ubuntu-jammy-dind</pre><p>Déploiement de ces derniers dans le cluster k0s…</p><pre><br>root@ubuntu-16gb-hel1-1:~# kubectl apply -f ubuntu-jammy-dind-deployment.yaml <br>deployment.apps/ubuntu-jammy-dind created<br>root@ubuntu-16gb-hel1-1:~# kubectl apply -f ubuntu-jammy-dind-service.yaml <br>service/ubuntu-jammy-dind created</pre><pre>root@ubuntu-16gb-hel1-1:~# kubectl get po,svc -A<br>NAMESPACE     NAME                                     READY   STATUS    RESTARTS   AGE<br>default       pod/ubuntu-jammy-dind-5d84c9847f-vhftx   1/1     Running   0          3m37s<br>kube-system   pod/coredns-555d98c87b-7dxxh             1/1     Running   0          24m<br>kube-system   pod/coredns-555d98c87b-9ngzm             1/1     Running   0          24m<br>kube-system   pod/konnectivity-agent-4fb6m             1/1     Running   0          24m<br>kube-system   pod/konnectivity-agent-kj99g             1/1     Running   0          24m<br>kube-system   pod/kube-proxy-6pbnw                     1/1     Running   0          24m<br>kube-system   pod/kube-proxy-xg4mh                     1/1     Running   0          24m<br>kube-system   pod/kube-router-tvzsb                    1/1     Running   0          24m<br>kube-system   pod/kube-router-wt97k                    1/1     Running   0          24m<br>kube-system   pod/metrics-server-7556957bb7-qtgd2      1/1     Running   0          24m<br><br>NAMESPACE     NAME                        TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                  AGE<br>default       service/kubernetes          ClusterIP   10.96.0.1        &lt;none&gt;        443/TCP                  24m<br>default       service/ubuntu-jammy-dind   ClusterIP   10.97.43.198     &lt;none&gt;        6901/TCP                 3m30s<br>kube-system   service/kube-dns            ClusterIP   10.96.0.10       &lt;none&gt;        53/UDP,53/TCP,9153/TCP   24m<br>kube-system   service/metrics-server      ClusterIP   10.100.127.105   &lt;none&gt;        443/TCP                  24m</pre><p>J’expose le service via kubectl pour accéder au Desktop via NoVNC et les identifiants par défaut :</p><pre><br>root@ubuntu-16gb-hel1-1:~# kubectl port-forward svc/ubuntu-jammy-dind 6901:6901 --address=&#39;0.0.0.0&#39;<br>Forwarding from 0.0.0.0:6901 -&gt; 6901</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k1KxTss0lZSEc6ERX5Oeng.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DlKO4urSYceyHDvkXeuSxA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bQoC1TdQ9uDZRok8WgsJSw.png" /></figure><p>Comme dans l’article précédent, récupération d’Ollama en test …</p><pre>curl -fsSL https://ollama.com/install.sh | sh</pre><ul><li><a href="https://github.com/ollama/ollama">GitHub - ollama/ollama: Get up and running with Kimi, GLM, MiniMax, DeepSeek, gpt-oss, Qwen, Gemma and other models.</a></li><li><a href="https://ollama.com/library?sort=newest">library</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gPAyw9iANitlQs4T2vnVxA.png" /></figure><p>avec Llama2 :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4jQc0QRgLm47GJsB7m8XGA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i3GTmWgsdf_h1xFChh9sDg.png" /></figure><p>D’autres exemples d’utilisation peuvent se retrouver dans le dépôt GitHub avec notamment Ansible ou Ignite …</p><ul><li><a href="https://github.com/k0sproject/bootloose/tree/main/examples">bootloose/examples at main · k0sproject/bootloose</a></li><li><a href="https://github.com/k0sproject/k0sctl/tree/main/examples/bootloose">k0sctl/examples/bootloose at main · k0sproject/k0sctl</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/0*cLK9IPxsEhzb31H-.jpg" /></figure><p>À suivre !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c75f97ce7e13" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Installer Canonical Kubernetes dans LXD avec Juju …]]></title>
            <link>https://deep75.medium.com/installer-canonical-kubernetes-dans-lxd-avec-juju-1b845780a52b?source=rss-9f1ca3c659fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b845780a52b</guid>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Karim]]></dc:creator>
            <pubDate>Sun, 31 Mar 2024 14:48:42 GMT</pubDate>
            <atom:updated>2024-03-31T14:51:05.891Z</atom:updated>
            <content:encoded><![CDATA[<h3>Installer Canonical Kubernetes dans LXD avec Juju …</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Yn7ODjvNPdTK9xvWjHCBw.png" /></figure><p>Canonical Kubernetes que l’on a pu aborder dans l’article précédent,</p><p><a href="https://deep75.medium.com/k8s-snap-canonical-kubernetes-pour-un-d%C3%A9ploiement-simple-et-rapide-dun-cluster-k8s-3a60f52838b4">k8s-snap (Canonical Kubernetes) pour un déploiement simple et rapide d’un cluster k8s …</a></p><blockquote>peut également être installé dans LXD. C’est un excellent moyen, par exemple, de tester Canonical Kubernetes en cluster sans avoir besoin de plusieurs hôtes physiques.</blockquote><p><a href="https://ubuntu.com/blog/lxd-5-easy-pieces">LXD: five easy pieces | Ubuntu</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*duocFt98fgPLpc0U.png" /></figure><p>Je pars donc d’une simple instance Ubuntu 22.04 LTS dans DigitalOcean :</p><pre>curl -X POST -H &#39;Content-Type: application/json&#39; \<br>    -H &#39;Authorization: Bearer &#39;$TOKEN&#39;&#39; \<br>    -d &#39;{&quot;name&quot;:&quot;lxd&quot;,<br>        &quot;size&quot;:&quot;s-4vcpu-16gb-amd&quot;,<br>        &quot;region&quot;:&quot;fra1&quot;,<br>        &quot;image&quot;:&quot;ubuntu-22-04-x64&quot;,<br>        &quot;vpc_uuid&quot;:&quot;XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX&quot;}&#39; \<br>    &quot;https://api.digitalocean.com/v2/droplets&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P5E2FNUOZ2BGQ2LcczaK2w.png" /></figure><p>et j’y installe et initie LXD ainsi que de l’orchestrateur Juju :</p><pre>root@lxd:~# snap remove lxd --purge &amp;&amp; snap install lxd --candidate<br>lxd removed<br>lxd (candidate) 5.21.0-eb655b9 from Canonical✓ installed<br>root@lxd:~# snap list<br>Name    Version         Rev    Tracking          Publisher   Notes<br>core20  20230207        1828   latest/stable     canonical✓  base<br>core22  20240111        1122   latest/stable     canonical✓  base<br>lxd     5.21.0-eb655b9  27957  latest/candidate  canonical✓  -<br>snapd   2.58.2          18357  latest/stable     canonical✓  snapd</pre><pre>root@lxd:~# lxd init<br>Would you like to use LXD clustering? (yes/no) [default=no]: <br>Do you want to configure a new storage pool? (yes/no) [default=yes]: <br>Name of the new storage pool [default=default]: <br>Name of the storage backend to use (dir, lvm, powerflex, zfs, btrfs, ceph) [default=zfs]: dir<br>Would you like to connect to a MAAS server? (yes/no) [default=no]: <br>Would you like to create a new local network bridge? (yes/no) [default=yes]: <br>What should the new bridge be called? [default=lxdbr0]: <br>What IPv4 address should be used? (CIDR subnet notation, “auto” or “none”) [default=auto]: <br>What IPv6 address should be used? (CIDR subnet notation, “auto” or “none”) [default=auto]: none<br>Would you like the LXD server to be available over the network? (yes/no) [default=no]: <br>Would you like stale cached images to be updated automatically? (yes/no) [default=yes]: <br>Would you like a YAML &quot;lxd init&quot; preseed to be printed? (yes/no) [default=no]: </pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uFEnpXiimTcBHrHk9ntjpw.png" /></figure><p><a href="https://juju.is/">The simplest way to deploy and maintain applications in the cloud</a></p><pre>root@lxd:~# snap install juju<br>juju (3/stable) 3.4.0 from Canonical✓ installed</pre><blockquote>Edition du profil par défaut dans LXD pour lui permettre de prendre en charge Canonical Kubernetes avec ce modèle …</blockquote><p><a href="https://documentation.ubuntu.com/canonical-kubernetes/main/howto/install/lxd/">Install Canonical Kubernetes in LXD</a></p><pre>name: default<br>description: Default LXD profile<br>config:<br>  boot.autostart: &quot;true&quot;<br>  linux.kernel_modules: ip_vs,ip_vs_rr,ip_vs_wrr,ip_vs_sh,ip_tables,ip6_tables,iptable_raw,netlink_diag,nf_nat,overlay,br_netfilter,xt_socket<br>  raw.lxc: |<br>    lxc.apparmor.profile=unconfined<br>    lxc.mount.auto=proc:rw sys:rw cgroup:rw<br>    lxc.cgroup.devices.allow=a<br>    lxc.cap.drop=<br>  security.nesting: &quot;true&quot;<br>  security.privileged: &quot;true&quot;<br>devices:<br>  aadisable2:<br>    path: /dev/kmsg<br>    source: /dev/kmsg<br>    type: unix-char<br>  dev-loop-control:<br>    major: &quot;10&quot;<br>    minor: &quot;237&quot;<br>    path: /dev/loop-control<br>    type: unix-char<br>  dev-loop0:<br>    major: &quot;7&quot;<br>    minor: &quot;0&quot;<br>    path: /dev/loop0<br>    type: unix-block<br>  dev-loop1:<br>    major: &quot;7&quot;<br>    minor: &quot;1&quot;<br>    path: /dev/loop1<br>    type: unix-block<br>  dev-loop2:<br>    major: &quot;7&quot;<br>    minor: &quot;2&quot;<br>    path: /dev/loop2<br>    type: unix-block<br>  dev-loop3:<br>    major: &quot;7&quot;<br>    minor: &quot;3&quot;<br>    path: /dev/loop3<br>    type: unix-block<br>  dev-loop4:<br>    major: &quot;7&quot;<br>    minor: &quot;4&quot;<br>    path: /dev/loop4<br>    type: unix-block<br>  dev-loop5:<br>    major: &quot;7&quot;<br>    minor: &quot;5&quot;<br>    path: /dev/loop5<br>    type: unix-block<br>  dev-loop6:<br>    major: &quot;7&quot;<br>    minor: &quot;6&quot;<br>    path: /dev/loop6<br>    type: unix-block<br>  dev-loop7:<br>    major: &quot;7&quot;<br>    minor: &quot;7&quot;<br>    path: /dev/loop7<br>    type: unix-block<br>  dev-loop8:<br>    major: &quot;7&quot;<br>    minor: &quot;8&quot;<br>    path: /dev/loop8<br>    type: unix-block<br>  dev-loop9:<br>    major: &quot;7&quot;<br>    minor: &quot;9&quot;<br>    path: /dev/loop9<br>    type: unix-block<br>  dev-loop10:<br>    major: &quot;7&quot;<br>    minor: &quot;10&quot;<br>    path: /dev/loop10<br>    type: unix-block<br>  dev-loop11:<br>    major: &quot;7&quot;<br>    minor: &quot;11&quot;<br>    path: /dev/loop11<br>    type: unix-block<br>  dev-loop12:<br>    major: &quot;7&quot;<br>    minor: &quot;12&quot;<br>    path: /dev/loop12<br>    type: unix-block<br>  dev-loop13:<br>    major: &quot;7&quot;<br>    minor: &quot;13&quot;<br>    path: /dev/loop13<br>    type: unix-block<br>  dev-loop14:<br>    major: &quot;7&quot;<br>    minor: &quot;14&quot;<br>    path: /dev/loop14<br>    type: unix-block<br>  dev-loop15:<br>    major: &quot;7&quot;<br>    minor: &quot;15&quot;<br>    path: /dev/loop15<br>    type: unix-block<br>  dev-loop16:<br>    major: &quot;7&quot;<br>    minor: &quot;16&quot;<br>    path: /dev/loop16<br>    type: unix-block<br>  eth0:<br>    name: eth0<br>    network: lxdbr0<br>    type: nic<br>  root:<br>    path: /<br>    pool: default<br>    type: disk<br>used_by: []</pre><p>Application de ce profil par défaut dans LXD :</p><pre>root@lxd:~# lxc profile edit default &lt; lxd-profile-default.yaml<br><br>root@lxd:~# lxc profile show default<br>name: default<br>description: Default LXD profile<br>config:<br>  boot.autostart: &quot;true&quot;<br>  linux.kernel_modules: ip_vs,ip_vs_rr,ip_vs_wrr,ip_vs_sh,ip_tables,ip6_tables,iptable_raw,netlink_diag,nf_nat,overlay,br_netfilter,xt_socket<br>  raw.lxc: |<br>    lxc.apparmor.profile=unconfined<br>    lxc.mount.auto=proc:rw sys:rw cgroup:rw<br>    lxc.cgroup.devices.allow=a<br>    lxc.cap.drop=<br>  security.nesting: &quot;true&quot;<br>  security.privileged: &quot;true&quot;<br>devices:<br>  aadisable2:<br>    path: /dev/kmsg<br>    source: /dev/kmsg<br>    type: unix-char<br>  dev-loop-control:<br>    major: &quot;10&quot;<br>    minor: &quot;237&quot;<br>    path: /dev/loop-control<br>    type: unix-char<br>  dev-loop0:<br>    major: &quot;7&quot;<br>    minor: &quot;0&quot;<br>    path: /dev/loop0<br>    type: unix-block<br>  dev-loop1:<br>    major: &quot;7&quot;<br>    minor: &quot;1&quot;<br>    path: /dev/loop1<br>    type: unix-block<br>  dev-loop2:<br>    major: &quot;7&quot;<br>    minor: &quot;2&quot;<br>    path: /dev/loop2<br>    type: unix-block<br>  dev-loop3:<br>    major: &quot;7&quot;<br>    minor: &quot;3&quot;<br>    path: /dev/loop3<br>    type: unix-block<br>  dev-loop4:<br>    major: &quot;7&quot;<br>    minor: &quot;4&quot;<br>    path: /dev/loop4<br>    type: unix-block<br>  dev-loop5:<br>    major: &quot;7&quot;<br>    minor: &quot;5&quot;<br>    path: /dev/loop5<br>    type: unix-block<br>  dev-loop6:<br>    major: &quot;7&quot;<br>    minor: &quot;6&quot;<br>    path: /dev/loop6<br>    type: unix-block<br>  dev-loop7:<br>    major: &quot;7&quot;<br>    minor: &quot;7&quot;<br>    path: /dev/loop7<br>    type: unix-block<br>  dev-loop8:<br>    major: &quot;7&quot;<br>    minor: &quot;8&quot;<br>    path: /dev/loop8<br>    type: unix-block<br>  dev-loop9:<br>    major: &quot;7&quot;<br>    minor: &quot;9&quot;<br>    path: /dev/loop9<br>    type: unix-block<br>  dev-loop10:<br>    major: &quot;7&quot;<br>    minor: &quot;10&quot;<br>    path: /dev/loop10<br>    type: unix-block<br>  dev-loop11:<br>    major: &quot;7&quot;<br>    minor: &quot;11&quot;<br>    path: /dev/loop11<br>    type: unix-block<br>  dev-loop12:<br>    major: &quot;7&quot;<br>    minor: &quot;12&quot;<br>    path: /dev/loop12<br>    type: unix-block<br>  dev-loop13:<br>    major: &quot;7&quot;<br>    minor: &quot;13&quot;<br>    path: /dev/loop13<br>    type: unix-block<br>  dev-loop14:<br>    major: &quot;7&quot;<br>    minor: &quot;14&quot;<br>    path: /dev/loop14<br>    type: unix-block<br>  dev-loop15:<br>    major: &quot;7&quot;<br>    minor: &quot;15&quot;<br>    path: /dev/loop15<br>    type: unix-block<br>  dev-loop16:<br>    major: &quot;7&quot;<br>    minor: &quot;16&quot;<br>    path: /dev/loop16<br>    type: unix-block<br>  eth0:<br>    name: eth0<br>    network: lxdbr0<br>    type: nic<br>  root:<br>    path: /<br>    pool: default<br>    type: disk<br>used_by: []</pre><p>Suivi du lancement d’un contrôleur local dans LXD pour Juju :</p><pre>root@lxd:~# mkdir -p ~/.local/share/juju<br><br>root@lxd:~# juju bootstrap localhost lxd<br>Creating Juju controller &quot;lxd&quot; on localhost/localhost<br>Looking for packaged Juju agent version 3.4.0 for amd64<br>Located Juju agent version 3.4.0-ubuntu-amd64 at https://streams.canonical.com/juju/tools/agent/3.4.0/juju-3.4.0-linux-amd64.tgz<br>To configure your system to better support LXD containers, please see: https://documentation.ubuntu.com/lxd/en/latest/explanation/performance_tuning/<br>Launching controller instance(s) on localhost/localhost...<br> - juju-b6d031-0 (arch=amd64)                 <br>Installing Juju agent on bootstrap instance<br>Waiting for address<br>Attempting to connect to 10.11.106.167:22<br>Connected to 10.11.106.167<br>Running machine configuration script...<br>Bootstrap agent now started<br>Contacting Juju controller at 10.11.106.167 to verify accessibility...<br><br>Bootstrap complete, controller &quot;lxd&quot; is now available<br>Controller machines are in the &quot;controller&quot; model<br><br>Now you can run<br>        juju add-model &lt;model-name&gt;<br>to create a new model to deploy workloads.<br><br>root@lxd:~# juju controllers<br>Use --refresh option with this command to see the latest information.<br><br>Controller  Model  User   Access     Cloud/Region         Models  Nodes    HA  Version<br>lxd*        -      admin  superuser  localhost/localhost       1      1  none  3.4.0  <br><br>root@lxd:~# lxc ls<br>+---------------+---------+----------------------+------+-----------+-----------+<br>|     NAME      |  STATE  |         IPV4         | IPV6 |   TYPE    | SNAPSHOTS |<br>+---------------+---------+----------------------+------+-----------+-----------+<br>| juju-b6d031-0 | RUNNING | 10.11.106.167 (eth0) |      | CONTAINER | 0         |<br>+---------------+---------+----------------------+------+-----------+-----------+</pre><p>Visualisation des Charms pour Canonical Kubernetes avant installation :</p><pre>root@lxd:~# juju info k8s<br>name: k8s<br>publisher: Canonical Kubernetes<br>summary: A machine charm for K8s<br>description: &quot;A machine charm which operates a complete Kubernetes cluster.\n\nThis<br>  charm installs and operates a Kubernetes cluster via the k8s snap. It exposes\nrelations<br>  to co-operate with other kubernetes components such as optional CNIs, \noptional<br>  cloud-providers, optional schedulers, external backing stores, and external\ncertificate<br>  storage.\n\nThis charm provides the following running components:\n* kube-apiserver\n*<br>  kube-scheduler\n* kube-controller-manager\n* kube-proxy\n* kubelet\n* containerd\n\nThis<br>  charm can optionally disable the following components:\n* A Kubernetes Backing Store\n*<br>  A Kubernetes CNI\n&quot;<br>store-url: https://charmhub.io/k8s<br>charm-id: 5GG4ydqob6yLrcZ3rrscqL0gVJvK53Ij<br>supports: ubuntu@20.04, ubuntu@22.04<br>subordinate: false<br>relations:<br>  provides:<br>    cos-agent: cos_agent<br>    cos-worker-tokens: cos-tokens<br>    k8s-cluster: k8s-cluster<br>  requires: {}<br>channels: |<br>  latest/stable:     –<br>  latest/candidate:  –<br>  latest/beta:       –<br>  latest/edge:       26  2024-03-29  (26)  3MB  amd64  ubuntu@20.04, ubuntu@22.04<br><br><br>root@lxd:~# juju info k8s-worker<br>name: k8s-worker<br>publisher: Canonical Kubernetes<br>summary: A machine charm for a K8s Worker<br>description: |<br>  A machine charm which operates a Kubernetes worker.<br><br>  This charm installs and operates a Kubernetes worker via the k8s snap. It exposes<br>  relations to co-operate with other kubernetes components<br><br>  This charm provides the following running components:<br>  * kube-proxy<br>  * kubelet<br>  * containerd<br>store-url: https://charmhub.io/k8s-worker<br>charm-id: ZL6PvT8yleZOMih0oKRYPgQI4FntLB48<br>supports: ubuntu@20.04, ubuntu@22.04<br>subordinate: false<br>relations:<br>  provides:<br>    cos-agent: cos_agent<br>  requires:<br>    cluster: k8s-cluster<br>    cos-tokens: cos-tokens<br>channels: |<br>  latest/stable:     –<br>  latest/candidate:  –<br>  latest/beta:       –<br>  latest/edge:       27  2024-03-29  (27)  6MB  amd64  ubuntu@20.04, ubuntu@22.04</pre><p>qui peuvent être installés avec Juju, avec ici le noeud contrôleur du futur cluster Kubernetes …</p><p><a href="https://documentation.ubuntu.com/canonical-kubernetes/main/howto/install/charm/">Install Canonical Kubernetes from a charm</a></p><pre>root@lxd:~# juju add-model k8s<br>Added &#39;k8s&#39; model on localhost/localhost with credential &#39;localhost&#39; for user &#39;admin&#39;<br>root@lxd:~# juju deploy k8s --channel=latest/edge<br>Deployed &quot;k8s&quot; from charm-hub charm &quot;k8s&quot;, revision 26 in channel latest/edge on ubuntu@22.04/stable</pre><pre>root@lxd:~# juju status<br>Model  Controller  Cloud/Region         Version  SLA          Timestamp<br>k8s    lxd         localhost/localhost  3.4.0    unsupported  12:37:00Z<br><br>App  Version  Status   Scale  Charm  Channel      Rev  Exposed  Message<br>k8s           waiting      1  k8s    latest/edge   26  no       Cluster not yet ready<br><br>Unit    Workload  Agent  Machine  Public address  Ports  Message<br>k8s/0*  waiting   idle   0        10.11.106.116          Cluster not yet ready<br><br>Machine  State    Address        Inst id        Base          AZ  Message<br>0        started  10.11.106.116  juju-85fd7d-0  ubuntu@22.04      Running</pre><p>Déploiement de deux noeuds Workers :</p><pre>root@lxd:~# juju deploy k8s-worker --channel=latest/edge -n 2<br>Deployed &quot;k8s-worker&quot; from charm-hub charm &quot;k8s-worker&quot;, revision 27 in channel latest/edge on ubuntu@22.04/stable<br>root@lxd:~# juju integrate k8s k8s-worker:cluster</pre><p>Le cluster Kubernetes est alors actif et opérationnel :</p><pre>root@lxd:~# juju status<br>Model  Controller  Cloud/Region         Version  SLA          Timestamp<br>k8s    lxd         localhost/localhost  3.4.0    unsupported  12:39:53Z<br><br>App         Version  Status  Scale  Charm       Channel      Rev  Exposed  Message<br>k8s         1.29.3   active      1  k8s         latest/edge   26  no       Ready<br>k8s-worker  1.29.3   active      2  k8s-worker  latest/edge   27  no       Ready<br><br>Unit           Workload  Agent  Machine  Public address  Ports     Message<br>k8s-worker/0*  active    idle   1        10.11.106.20              Ready<br>k8s-worker/1   active    idle   2        10.11.106.178             Ready<br>k8s/0*         active    idle   0        10.11.106.116   6443/tcp  Ready<br><br>Machine  State    Address        Inst id        Base          AZ  Message<br>0        started  10.11.106.116  juju-85fd7d-0  ubuntu@22.04      Running<br>1        started  10.11.106.20   juju-85fd7d-1  ubuntu@22.04      Running<br>2        started  10.11.106.178  juju-85fd7d-2  ubuntu@22.04      Running</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/535/1*RYXL6HDuXE32TYP7iijO2g.jpeg" /></figure><p>Connexion au noeud Contrôleur du cluster pour vérifier son statut :</p><pre>root@lxd:~# juju ssh k8s/0<br><br>The programs included with the Ubuntu system are free software;<br>the exact distribution terms for each program are described in the<br>individual files in /usr/share/doc/*/copyright.<br><br>Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by<br>applicable law.<br><br>To run a command as administrator (user &quot;root&quot;), use &quot;sudo &lt;command&gt;&quot;.<br>See &quot;man sudo_root&quot; for details.<br><br>ubuntu@juju-85fd7d-0:~$ sudo k8s status<br>status: ready<br>high-availability: no<br>datastore:<br>  voter-nodes:<br>    - 10.11.106.116:6400<br>  standby-nodes: none<br>  spare-nodes: none<br><br>network:<br>  enabled: true<br>dns:<br>  enabled: true<br>  cluster-domain: cluster.local<br>  service-ip: 10.152.183.28<br>  upstream-nameservers:<br>  - /etc/resolv.conf<br>metrics-server:<br>  enabled: true<br><br>ubuntu@juju-85fd7d-0:~$ sudo k8s kubectl cluster-info<br>Kubernetes control plane is running at https://127.0.0.1:6443<br>CoreDNS is running at https://127.0.0.1:6443/api/v1/namespaces/kube-system/services/coredns:udp-53/proxy<br><br>To further debug and diagnose cluster problems, use &#39;kubectl cluster-info dump&#39;.<br>ubuntu@juju-85fd7d-0:~$ sudo k8s kubectl get nodes -o wide<br>NAME            STATUS   ROLES                  AGE     VERSION   INTERNAL-IP     EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME<br>juju-85fd7d-0   Ready    control-plane,worker   7m10s   v1.29.3   10.11.106.116   &lt;none&gt;        Ubuntu 22.04.4 LTS   5.15.0-67-generic   containerd://1.6.28<br>juju-85fd7d-1   Ready    worker                 3m23s   v1.29.3   10.11.106.20    &lt;none&gt;        Ubuntu 22.04.4 LTS   5.15.0-67-generic   containerd://1.6.28<br>juju-85fd7d-2   Ready    worker                 3m10s   v1.29.3   10.11.106.178   &lt;none&gt;        Ubuntu 22.04.4 LTS   5.15.0-67-generic   containerd://1.6.28<br>ubuntu@juju-85fd7d-0:~$ sudo k8s kubectl get po,svc -A<br>NAMESPACE     NAME                                   READY   STATUS    RESTARTS   AGE<br>kube-system   pod/cilium-b5hkt                       1/1     Running   0          7m13s<br>kube-system   pod/cilium-gghfz                       1/1     Running   0          3m17s<br>kube-system   pod/cilium-kzwpz                       1/1     Running   0          3m30s<br>kube-system   pod/cilium-operator-597b55b886-jhqkq   1/1     Running   0          7m13s<br>kube-system   pod/coredns-66579b5b88-x9dv2           1/1     Running   0          7m13s<br>kube-system   pod/metrics-server-57db9dfb7b-lnllv    1/1     Running   0          7m13s<br><br>NAMESPACE     NAME                     TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)         AGE<br>default       service/kubernetes       ClusterIP   10.152.183.1     &lt;none&gt;        443/TCP         7m20s<br>kube-system   service/coredns          ClusterIP   10.152.183.28    &lt;none&gt;        53/UDP,53/TCP   7m21s<br>kube-system   service/hubble-peer      ClusterIP   10.152.183.184   &lt;none&gt;        443/TCP         7m21s<br>kube-system   service/metrics-server   ClusterIP   10.152.183.60    &lt;none&gt;        443/TCP         7m20s</pre><p>Je peux récupérer le fichierkubeconfigavec Juju :</p><pre>root@lxd:~# juju ssh k8s/0 &#39;sudo k8s config&#39;<br>apiVersion: v1<br>clusters:<br>- cluster:<br>    certificate-authority-data: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSURHekNDQWdPZ0F3SUJBZ0lRQ2RCNysvUWI1Ums4MzdmRGJhWlp2ekFOQmdrcWhraUc5dzBCQVFzRkFEQVkKTVJZd0ZBWURWUVFERXcxcmRXSmxjbTVsZEdWekxXTmhNQjRYRFRJME1ETXpNVEV5TXpVeE1Gb1hEVFEwTURNegpNVEV5TXpVeE1Gb3dHREVXTUJRR0ExVUVBeE1OYTNWaVpYSnVaWFJsY3kxallUQ0NBU0l3RFFZSktvWklodmNOCkFRRUJCUUFEZ2dFUEFEQ0NBUW9DZ2dFQkFNK1VRNllEVS9vaEVrWjhGcHlnQ0Y3N1JHaWdEMUdEZUR5ekdCeTIKZjhleVhZMGRUWlFJcmw0amtIL29SS2tiRnB4QnZVSVlzWFV5RlpkOUxKM3VFMWhPQTNDNXYzM0VOUVhrdU5pNQpELy9kRHNyZ0pHWitzTnJKSTIzSWZOV1VXanNLc1hzejFzZXN5cHRYb2dYbytkTkxxRitVTjFnUjVBOTZ6VVB0ClZOZFJLKzUyaTFxcWcxeUFhczcybVhwVkNQZUxxSi9adXhDSFhTcE8rcWt0Q2pSeUVTKzJmVFVTaUhtRlQ5clMKVG9vZndTZ0RkWHJlMmsvN3NFSjg5aGk2NFpQeVQyZDFPYzcxbzEyQUlyZ0VBYlorZnJ0NnFCSVhENkkxSEJzKwphZlh1UmVmTyswUEFVYzgxN25QaGhTWW1OcGJrdk5vdFF4WlRZRGRONEhEbEJUVUNBd0VBQWFOaE1GOHdEZ1lEClZSMFBBUUgvQkFRREFnS0VNQjBHQTFVZEpRUVdNQlFHQ0NzR0FRVUZCd01DQmdnckJnRUZCUWNEQVRBUEJnTlYKSFJNQkFmOEVCVEFEQVFIL01CMEdBMVVkRGdRV0JCUnFobUlNNzlRVnFYMks1YXVuVUdBMENYOTBkVEFOQmdrcQpoa2lHOXcwQkFRc0ZBQU9DQVFFQWNnaUJad0R3MTlVVlFaQVpHRCs5THFSOFBycXJyMlRqVFh0Q1RkbzFGWWZICnlla2IzdmV1YjJUblNOT2RUeEhjWmtlR2d3QXFYV216Z1MrSHl5TFZSTlY2WTNJK0ZKQmJpVkJJOTV0TlRmaG4KMEZvSEVzWUNSY3Q5L1JVQkVOTTFsZDY1bWFVNFc2TWFvdE5MOVpSczNGTDJ3SmRKTjdCVEJIamxYZzhrckkrOQpOdlcvTWZCS0FvcWRleXNBMHJHY3RlczVWZm1YUDRMa1hxNXhQNmV1MWhmSU1ObXM1UTk4QTdsck9TZG5BNzJYClFNKzBBc1ovckhZQ0hnRUFqNjdIK0drTFhQeEFzelZ4UTZpRHRJMmhyWVVKYmNFSTg1REF0RFNhc2xGS2JHLzMKNU53b1U0VTZjVXMxcHZiTjFsVFZvTGVFTHFoYU9EMkdiUnRYb0h4UnFBPT0KLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo=<br>    server: https://10.11.106.116:6443<br>  name: k8s<br>contexts:<br>- context:<br>    cluster: k8s<br>    user: k8s-user<br>  name: k8s<br>current-context: k8s<br>kind: Config<br>preferences: {}<br>users:<br>- name: k8s-user<br>  user:<br>    token: token::00669e4efab3674984256068943beee135d06d1a<br><br>Connection to 10.11.106.116 closed.</pre><p>Pour bénéficier localement du client kubectl :</p><pre>root@lxd:~# juju expose k8s<br>root@lxd:~# snap install kubectl --classic<br>snap &quot;kubectl&quot; is already installed, see &#39;snap help refresh&#39;<br>root@lxd:~# mkdir .kube<br>root@lxd:~# juju ssh k8s/0 &#39;sudo k8s config&#39; &gt; .kube/config<br>Connection to 10.11.106.116 closed.<br>root@lxd:~# chmod 400 .kube/config<br>root@lxd:~# kubectl cluster-info<br>Kubernetes control plane is running at https://10.11.106.116:6443<br>CoreDNS is running at https://10.11.106.116:6443/api/v1/namespaces/kube-system/services/coredns:udp-53/proxy<br><br>To further debug and diagnose cluster problems, use &#39;kubectl cluster-info dump&#39;.<br>root@lxd:~# kubectl get nodes -o wide<br>NAME            STATUS   ROLES                  AGE     VERSION   INTERNAL-IP     EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME<br>juju-85fd7d-0   Ready    control-plane,worker   11m     v1.29.3   10.11.106.116   &lt;none&gt;        Ubuntu 22.04.4 LTS   5.15.0-67-generic   containerd://1.6.28<br>juju-85fd7d-1   Ready    worker                 7m47s   v1.29.3   10.11.106.20    &lt;none&gt;        Ubuntu 22.04.4 LTS   5.15.0-67-generic   containerd://1.6.28<br>juju-85fd7d-2   Ready    worker                 7m34s   v1.29.3   10.11.106.178   &lt;none&gt;        Ubuntu 22.04.4 LTS   5.15.0-67-generic   containerd://1.6.28<br><br>root@lxd:~# lxc ls<br>+---------------+---------+--------------------------+------+-----------+-----------+<br>|     NAME      |  STATE  |           IPV4           | IPV6 |   TYPE    | SNAPSHOTS |<br>+---------------+---------+--------------------------+------+-----------+-----------+<br>| juju-85fd7d-0 | RUNNING | 10.11.106.116 (eth0)     |      | CONTAINER | 0         |<br>|               |         | 10.1.0.231 (cilium_host) |      |           |           |<br>+---------------+---------+--------------------------+------+-----------+-----------+<br>| juju-85fd7d-1 | RUNNING | 10.11.106.20 (eth0)      |      | CONTAINER | 0         |<br>|               |         | 10.1.1.16 (cilium_host)  |      |           |           |<br>+---------------+---------+--------------------------+------+-----------+-----------+<br>| juju-85fd7d-2 | RUNNING | 10.11.106.178 (eth0)     |      | CONTAINER | 0         |<br>|               |         | 10.1.2.20 (cilium_host)  |      |           |           |<br>+---------------+---------+--------------------------+------+-----------+-----------+<br>| juju-b6d031-0 | RUNNING | 10.11.106.167 (eth0)     |      | CONTAINER | 0         |<br>+---------------+---------+--------------------------+------+-----------+-----------+</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*ILSNou-WNpAWHzy3_8g9Wg.jpeg" /></figure><p>Comme dans l’article précédent, je peux bénéficier d’Ollama et des LLM ouverts via Helm :</p><ul><li><a href="https://ollama.com/">Ollama · Run AI models locally and in the cloud</a></li><li><a href="https://github.com/otwld/ollama-helm">GitHub - otwld/ollama-helm: Helm chart for Ollama on Kubernetes</a></li></ul><pre>root@lxd:~# curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash<br>Downloading https://get.helm.sh/helm-v3.14.3-linux-amd64.tar.gz<br>Verifying checksum... Done.<br>Preparing to install helm into /usr/local/bin<br>helm installed into /usr/local/bin/helm<br><br>root@lxd:~# helm ls<br>NAME    NAMESPACE       REVISION        UPDATED STATUS  CHART   APP VERSION</pre><pre>root@lxd:~# kubectl create namespace ollama<br>namespace/ollama created<br><br>root@lxd:~# helm install ollama ollama-helm/ollama --namespace ollama<br>NAME: ollama<br>LAST DEPLOYED:<br>NAMESPACE: ollama<br>STATUS: deployed<br>REVISION: 1<br>NOTES:<br>1. Get the application URL by running these commands:<br>  export POD_NAME=$(kubectl get pods --namespace ollama -l &quot;app.kubernetes.io/name=ollama,app.kubernetes.io/instance=ollama&quot; -o jsonpath=&quot;{.items[0].metadata.name}&quot;)<br>  export CONTAINER_PORT=$(kubectl get pod --namespace ollama $POD_NAME -o jsonpath=&quot;{.spec.containers[0].ports[0].containerPort}&quot;)<br>  echo &quot;Visit http://127.0.0.1:8080 to use your application&quot;<br>  kubectl --namespace ollama port-forward $POD_NAME 8080:$CONTAINER_PORT</pre><pre>root@lxd:~# helm ls --namespace ollama<br>NAME    NAMESPACE       REVISION        UPDATED                                 STATUS          CHART           APP VERSION<br>ollama  ollama          1               2024-03-31 13:11:43.199405708 +0000 UTC deployed        ollama-0.21.1   0.1.30    <br><br>root@lxd:~# kubectl get po,svc -n ollama<br>NAME                          READY   STATUS    RESTARTS   AGE<br>pod/ollama-75c7b79658-rnf7h   1/1     Running   0          94s<br><br>NAME             TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)     AGE<br>service/ollama   ClusterIP   10.152.183.78   &lt;none&gt;        11434/TCP   94s</pre><p>Et je peux exposer localement l’API RESTful d’Ollama :</p><pre>root@lxd:~# kubectl port-forward service/ollama -n ollama 11434:11434 --address=&#39;0.0.0.0&#39;<br>Forwarding from 0.0.0.0:11434 -&gt; 11434<br><br>root@lxd:~# netstat -tunlp<br>Active Internet connections (only servers)<br>Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    <br>tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1399/sshd: /usr/sbi <br>tcp        0      0 10.11.106.1:53          0.0.0.0:*               LISTEN      9929/dnsmasq        <br>tcp        0      0 0.0.0.0:11434           0.0.0.0:*               LISTEN      52634/kubectl       <br>tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      623/systemd-resolve <br>tcp6       0      0 :::8443                 :::*                    LISTEN      9784/lxd            <br>tcp6       0      0 :::22                   :::*                    LISTEN      1399/sshd: /usr/sbi <br>udp        0      0 10.11.106.1:53          0.0.0.0:*                           9929/dnsmasq        <br>udp        0      0 127.0.0.53:53           0.0.0.0:*                           623/systemd-resolve <br>udp        0      0 0.0.0.0:67              0.0.0.0:*                           9929/dnsmasq    </pre><p>Récupération du client Ollama via GitHub :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9roIeJ1BGnfVeXfC" /></figure><p><a href="https://github.com/ollama/ollama/releases">Releases · ollama/ollama</a></p><pre>root@lxd:~# wget -c https://github.com/ollama/ollama/releases/download/v0.1.30/ollama-linux-amd64 &amp;&amp; chmod +x ollama-linux-amd64 &amp;&amp; mv ollama-linux-amd64 /usr/local/bin/ollama<br>Resolving objects.githubusercontent.com (objects.githubusercontent.com)... 185.199.111.133, 185.199.108.133, 185.199.109.133, ...<br>Connecting to objects.githubusercontent.com (objects.githubusercontent.com)|185.199.111.133|:443... connected.<br>HTTP request sent, awaiting response... 200 OK<br>Length: 297108760 (283M) [application/octet-stream]<br>Saving to: ‘ollama-linux-amd64’<br><br>ollama-linux-amd64                              100%[=====================================================================================================&gt;] 283.34M   351MB/s    in 0.8s    <br><br>(351 MB/s) - ‘ollama-linux-amd64’ saved [297108760/297108760]</pre><p>Pour exécuter par exemple ici Code Llama, une famille de LLM pour le code basée sur Llama 2 :</p><ul><li><a href="https://huggingface.co/docs/transformers/model_doc/code_llama">CodeLlama</a></li><li><a href="https://github.com/meta-llama/codellama">GitHub - meta-llama/codellama: Inference code for CodeLlama models</a></li></ul><pre>root@lxd:~# ollama run codellama<br>pulling manifest <br>pulling 3a43f93b78ec... 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 3.8 GB                         <br>pulling 8c17c2ebb0ea... 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 7.0 KB                         <br>pulling 590d74a5569b... 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 4.8 KB                         <br>pulling 2e0493f67d0c... 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏   59 B                         <br>pulling 7f6a57943a88... 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  120 B                         <br>pulling 316526ac7323... 100% ▕██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  529 B                         <br>verifying sha256 digest <br>writing manifest <br>removing any unused layers <br>success </pre><p>Avec ces petits exemples à parfaire …</p><pre>&gt;&gt;&gt; How deploy manifest with Juju inside Kubernetes cluster ?<br><br>To deploy a manifest file with Juju inside a Kubernetes cluster, you can follow these steps:<br><br>1. Install Juju on your local machine and connect it to the Kubernetes cluster that you want to deploy the manifest file to.<br>2. Create a Juju model for the Kubernetes cluster by running the following command:<br>```<br>juju add-model &lt;cluster-name&gt;<br>```<br>Replace `&lt;cluster-name&gt;` with the name of your Kubernetes cluster.<br>3. Set the deployment environment to the Kubernetes cluster that you want to deploy the manifest file to by running the following command:<br>```<br>juju set-environment &lt;cluster-name&gt;<br>```<br>4. Create a new Juju application using the `juju add` command, passing in the name of the application and the path to the manifest file as arguments. For example:<br>```<br>juju add my-application manifests/my-application.yaml<br>```<br>Replace `&lt;my-application&gt;` with the name of your application and `&lt;manifests/my-application.yaml&gt;` with the path to your manifest file.<br>5. Deploy the application by running the following command:<br>```<br>juju deploy my-application<br>```<br>This will deploy the application using the configuration specified in the manifest file.<br>6. Once the deployment is complete, you can manage the application using standard Juju commands, such as `juju status` to view the status of the application and `juju logs` to view the<br>logs for the application.<br>7. To remove the application from the Kubernetes cluster, you can use the `juju destroy` command:<br>```<br>juju destroy my-application<br>```<br>This will destroy the application and all its resources in the Kubernetes cluster.<br><br>Note that this is a basic example of how to deploy a manifest file with Juju inside a Kubernetes cluster. There are many other options and features available in Juju, so you can <br>explore those as well.<br><br>&gt;&gt;&gt; How deploy a Pod with Rust inside Kubernetes ?<br><br>To deploy a Pod with Rust inside a Kubernetes cluster, you can follow these steps:<br><br>1. Install the `cargo` package on your local machine by running the following command:<br>```<br>sudo apt-get install cargo<br>```<br>2. Create a new Rust project using the `cargo new` command, passing in the name of your project as an argument. For example:<br>```<br>cargo new my-rust-project<br>```<br>3. Change into the directory of your new project by running the following command:<br>```<br>cd my-rust-project<br>```<br>4. Add the `kubernetes` crate to your project&#39;s dependencies by adding the following line to your `Cargo.toml` file:<br>```<br>[dependencies]<br>kubernetes = &quot;0.18&quot;<br>```<br>5. Create a new Rust file for your Kubernetes deployment, such as `deployment.rs`, and add the following code to it:<br>```rust<br>use kubernetes::api::Api;<br>use kubernetes::config::Configuration;<br>use kubernetes::apis::CoreApi;<br><br>fn main() {<br>    let config = Configuration::new(&quot;https://&lt;your-kubernetes-cluster&gt;&quot;);<br>    let client = Api::all(config);<br>    let pod = client.create_namespaced_pod(<br>        &quot;default&quot;,<br>        &amp;Api::Pod(&quot;my-rust-deployment&quot;),<br>        None,<br>    );<br>}<br>```<br>Replace `&lt;your-kubernetes-cluster&gt;` with the URL of your Kubernetes cluster.<br>6. Compile your Rust code by running the following command:<br>```<br>cargo build --release<br>```<br>7. Run your Rust code by running the following command:<br>```<br>./target/release/deployment<br>```<br>This will deploy a new Pod with Rust inside the `default` namespace of your Kubernetes cluster. You can view the status of your Pod using the `kubectl get pods` command.<br><br>Note that this is a basic example of how to deploy a Pod with Rust inside a Kubernetes cluster. There are many other options and features available in Rust, so you can explore those as<br>well<br><br>&gt;&gt;&gt; Send a message (/? for help)</pre><p>Canonical Kubernetes peut également être installé à l’intérieur d’un conteneur LXD en utilisant le profil énoncé çi-dessus comme le précise cette documentation détaillée …</p><p><a href="https://documentation.ubuntu.com/canonical-kubernetes/main/howto/install/lxd/">Install Canonical Kubernetes in LXD</a></p><p>Sans compter qu’Ollama et une interface graphique conviviale avec Open WebUI pourraient être installé via Snap ou Helm :</p><ul><li><a href="https://ubuntu.com//blog/deploying-open-language-models-on-ubuntu">Deploying Open Language Models on Ubuntu | Ubuntu</a></li><li><a href="https://docs.openwebui.com/getting-started/installation/">Alternative Installation | Open WebUI</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*fHy6aM2InvWnyH3JwlZISA.jpeg" /><figcaption><a href="https://maxime.walzberg.fr/articles/yollama/img/meme1.jpg">https://maxime.walzberg.fr/articles/yollama/img/meme1.jpg</a></figcaption></figure><p>À suivre !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b845780a52b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[k8s-snap (Canonical Kubernetes) pour un déploiement simple et rapide d’un cluster k8s …]]></title>
            <link>https://deep75.medium.com/k8s-snap-canonical-kubernetes-pour-un-d%C3%A9ploiement-simple-et-rapide-dun-cluster-k8s-3a60f52838b4?source=rss-9f1ca3c659fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a60f52838b4</guid>
            <category><![CDATA[ovh]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[llm]]></category>
            <dc:creator><![CDATA[Karim]]></dc:creator>
            <pubDate>Sun, 25 Feb 2024 21:45:59 GMT</pubDate>
            <atom:updated>2024-02-25T21:45:59.057Z</atom:updated>
            <content:encoded><![CDATA[<h3>k8s-snap (Canonical Kubernetes) pour un déploiement simple et rapide d’un cluster k8s : application à Ollama …</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oD8pTT1WTzCB0kQzeTuR_w.png" /></figure><p>Focus sur Canonical Kubernetes, une distribution Kubernetes minimaliste (à l’image de k0s/k3s) livrée en quelques clics via Snap. L’accent est notamment mis sur des opérations simplifiées et une posture de sécurité renforcée sur n’importe quelle infrastructure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7ee6sReX_IYzffBr" /></figure><ul><li><a href="https://github.com/canonical/k8s-snap">GitHub - canonical/k8s-snap: Canonical Kubernetes is an opinionated and CNCF conformant Kubernetes operated by Snaps and Charms, which come together to bring simplified operations and an enhanced security posture on any infrastructure.</a></li><li><a href="https://snapcraft.io/k8s">Install Canonical Kubernetes on Linux | Snap Store</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fzQa2CSFE0X3AXHO.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*M_kQ2Y-s8x1wcvml.jpg" /></figure><p>Pour cela, déploiement sur une instance Ubuntu 22.04 LTS dans OVH qui autorise la virtualisation imbriquée :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bDjr5fJfPwnxaLoo4GouMA.png" /></figure><p>Je commence par y installer Multipass pour lancer un groupe de trois machines virtuelles :</p><p><a href="https://multipass.run/">Multipass orchestrates virtual Ubuntu instances</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0zMjJHQdIbZz-nYuroJutg.png" /></figure><p>Dès lors lancement des trois VMs Ubuntu 22.04 LTS pour initier l’ossature du futur cluster k8s :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vHYLpHsjeUyDllEXqyZZ6g.png" /></figure><p>Dans la première machine virtuelle qui va supporter la plan de contrôle, installation de k8s-snap rapidement via Snap :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ixipmASq82vKfCIIL60Ugw.png" /></figure><p>Le cluster k8s est initialisé et prêt pour rattacher un noeud Worker :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cIyiP_B1WrqnxvtQdCv-dw.png" /></figure><p>Pour cela génération d’un token :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x3TTSQqk3tSa91CSDQGR1g.png" /></figure><p>Dès lors, il est possible de rattacher le nouveau noeud Worker au cluster via ce token généré précedemment :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1RU96f0nODsKUVB1j8r-Pw.png" /></figure><p>Rattachement d’un autre noeud Worker avec ce même token :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bGt2I6O53u_DRct2yurbVQ.png" /></figure><p>Les noeuds Worker sont alors opérationnels dans le cluster :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZEy77_KktatLVUC1V0MpnQ.png" /></figure><p>Il est possible de récupérer le fichier kubeconfig pour pouvoir utiliser le client kubectl :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tkgG2ODW02nnnpGCq61reg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GJd2BdQuYLgIXrS7r8XsSg.png" /></figure><p>Lancement d’un Pod Ubuntu très rapidement :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kj5r3sB_gulqF5XY_lvSkg.png" /></figure><p>qui va servir ici au lancement d’Ollama :</p><p><a href="https://github.com/ollama/ollama">GitHub - ollama/ollama: Get up and running with Kimi, GLM, MiniMax, DeepSeek, gpt-oss, Qwen, Gemma and other models.</a></p><blockquote>Ollama est une plateforme qui permet aux utilisateurs d’exécuter de grands modèles de langages (LLM), tels que Mistral, Gemma, Llama 2 de Research Lab et d’autres … , directement sur leurs ordinateurs personnels plutôt que de dépendre uniquement de services en nuage. Il permet de télécharger des modèles pré-entraînés compatibles avec différents systèmes d’exploitation, notamment macOS, Linux et des versions préliminaires pour Windows. Les utilisateurs peuvent également personnaliser et développer leurs propres applications en utilisant ces modèles.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JG7emGIeQDukzD7uGLdx_A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*44_Mm1XHDdTa8q6J1-gmgQ.png" /></figure><p>Ici sans l’utilisation d’une carte GPU et en mode CPU uniquement via de petits LLMs comme le très récent Gemma :</p><ul><li><a href="https://www.lemondeinformatique.fr/actualites/lire-google-devoile-gemma-et-ses-2-modeles-ia-ouverts-93031.html">Google dévoile Gemma et ses 2 modèles IA ouverts - Le Monde Informatique</a></li><li><a href="https://blog.google/technology/developers/gemma-open-models/">Gemma: Introducing new state-of-the-art open models</a></li><li><a href="https://ollama.com/library/gemma">gemma</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rucrkioq8Ct7-fxX3qVB5Q.png" /></figure><p>avec une petite interrogation :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GHJ4Yaoc0goI96j5IUSmOA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tRrNA4dtBlQLg0kmS8NpgA.png" /></figure><p>La même chose avec un autre LLM :</p><ul><li><a href="https://ollama.com/library/qwen">qwen</a></li><li><a href="https://huggingface.co/Qwen">Qwen (Qwen)</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gVl9ha5nsSFkq9gaPs_12A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ca5b-kY_okmQAAZYWn8hjg.png" /></figure><p>avec une faible consommation de ressources …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LGRnRRnYeYFmQw50Oe-eEg.png" /></figure><p>Canonical Kubernetes est donc un moyen très rapide et très simple de déployer un cluster Kubernetes entièrement conforme.</p><blockquote>Cette distribution ajoute des pièces manquantes (par exemple, Ingress, DNS, Réseau) pour une expérience “Zéro-op”. Pour les clusters à un seul nœud, elle peut être déployée avec deux commandes. Et Ajouter de nouveaux nœuds avec seulement deux autres commandes …</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/0*1Wfz2CBsHS_aIaVn.jpg" /></figure><p>À suivre !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a60f52838b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Déployer un cluster Nomad et Consul très rapidement avec hashi-up …]]></title>
            <link>https://deep75.medium.com/d%C3%A9ployer-un-cluster-nomad-et-consul-tr%C3%A8s-rapidement-avec-hashi-up-76c75f27f84c?source=rss-9f1ca3c659fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/76c75f27f84c</guid>
            <category><![CDATA[opennebula]]></category>
            <category><![CDATA[nomad]]></category>
            <category><![CDATA[hashicorp]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Karim]]></dc:creator>
            <pubDate>Sat, 11 Mar 2023 17:16:05 GMT</pubDate>
            <atom:updated>2023-03-11T17:22:40.010Z</atom:updated>
            <content:encoded><![CDATA[<h3>Déployer un cluster Nomad et Consul très rapidement avec hashi-up …</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/855/0*qF6HFpBVho5EJxbq.png" /></figure><p>Hashi-up est un utilitaire léger qui permet d’installer HashiCorp Consul, Nomad ou Vault sur n’importe quel hôte Linux distant.</p><p><a href="https://deep75.medium.com/load-balancing-avec-haproxy-nomad-et-consul-56289d6c1494">Load Balancing avec HAProxy, Nomad et Consul …</a></p><blockquote>Tout ce dont vous avez besoin est un accès ssh et le binaire hashi-up pour construire son cluster.</blockquote><p><a href="https://github.com/jsiebens/hashi-up">GitHub - jsiebens/hashi-up: bootstrap HashiCorp Consul, Nomad, or Vault over SSH &lt; 1 minute</a></p><p>L’outil est écrit en Go et est compilé pour Linux, Windows, MacOS et même pour Raspberry Pi.</p><p><a href="https://johansiebens.dev/posts/2020/08/building-a-nomad-cluster-on-raspberry-pi-running-ubuntu-server/">Building a Nomad cluster on Raspberry Pi running Ubuntu server</a></p><blockquote>Ce projet est fortement inspiré du travail d’Alex Ellis qui a créé k3sup, un outil pour passer de zéro à KUBECONFIG avec k3s.</blockquote><ul><li><a href="https://deep75.medium.com/openstack-sur-lxd-avec-juju-et-k3sup-dans-phoenixnap-e5867a487497">OpenStack sur LXD avec Juju  et k3sup dans phoenixNAP …</a></li><li><a href="https://deep75.medium.com/acc%C3%A9der-%C3%A0-lensemble-du-cluster-kubernetes-avec-tailscale-c6a7990d77f">Accéder à l’ensemble du cluster Kubernetes avec Tailscale …</a></li><li><a href="https://github.com/alexellis/k3sup">GitHub - alexellis/k3sup: bootstrap K3s over SSH in &lt; 60s 🚀</a></li></ul><p>Implémentation avec le lancement d’un serveur Ubuntu 22.04 LTS autorisant la virtualisation imbriquée dans DigitalOcean :</p><pre>curl -X POST -H &#39;Content-Type: application/json&#39; \<br>    -H &#39;Authorization: Bearer &#39;$TOKEN&#39;&#39; \<br>    -d &#39;{&quot;name&quot;:&quot;minione&quot;,<br>        &quot;size&quot;:&quot;m-4vcpu-32gb&quot;,<br>        &quot;region&quot;:&quot;fra1&quot;,<br>        &quot;image&quot;:&quot;ubuntu-22-04-x64&quot;,<br>        &quot;monitoring&quot;:true,<br>        &quot;vpc_uuid&quot;:&quot;8b8c0544-e7b6-4d0a-977d-4406ea518f7a&quot;}&#39; \<br>    &quot;https://api.digitalocean.com/v2/droplets&quot;</pre><ul><li><a href="https://www.digitalocean.com/blog/introducing-premium-cpu-optimized-droplets">Introducing Premium CPU-Optimized Droplets | DigitalOcean</a></li><li><a href="https://www.digitalocean.com/">DigitalOcean | Cloud Infrastructure for Developers</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vSkuuqMmE14Wi4Z3lAZOyg.png" /></figure><p>Je vais y installer OpenNebula via le script miniONE :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-5ao6A9ExiYDx4h_huzocA.png" /></figure><ul><li><a href="https://opennebula.io/">OpenNebula - Open Source Cloud &amp; Edge Computing Platform</a></li><li><a href="https://github.com/OpenNebula/minione">GitHub - OpenNebula/minione: Easy to use deployment tool for an OpenNebula evaluation environment</a></li><li><a href="https://deep75.medium.com/opennebula-6-0-mutara-imbriqu%C3%A9-dans-lxd-application-au-d%C3%A9ploiement-dun-cluster-microk8s-1-21-d3f2cdee9e04">OpenNebula 6.0 “Mutara” imbriqué dans LXD : application au déploiement d’un cluster MicroK8s 1.21 …</a></li></ul><pre>root@minione:~# wget -c https://raw.githubusercontent.com/OpenNebula/minione/master/minione<br>--2023-03-11 14:21:46--  https://raw.githubusercontent.com/OpenNebula/minione/master/minione<br>Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.110.133, 185.199.109.133, 185.199.111.133, ...<br>Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.110.133|:443... connected.<br>HTTP request sent, awaiting response... 200 OK<br>Length: 51458 (50K) [text/plain]<br>Saving to: ‘minione’<br><br>minione                                      100%[=============================================================================================&gt;]  50.25K  --.-KB/s    in 0s      <br><br>2023-03-11 14:21:46 (149 MB/s) - ‘minione’ saved [51458/51458]</pre><p>Déploiement automatisé très rapidement avec lancement du script :</p><pre>root@minione:~# bash minione<br><br>### Checks &amp; detection<br>Checking augeas is installed  SKIP will try to install<br>Checking AppArmor  SKIP will try to modify<br>Checking for present ssh key  SKIP<br>Checking (iptables|netfilter)-persistent are installed  SKIP will try to install<br>Checking docker is installed  SKIP will try to install<br>Checking python3-pip is installed  SKIP will try to install<br>Checking ansible  SKIP will try to install<br>Checking terraform  SKIP will try to install<br>Checking unzip is installed  SKIP will try to install<br><br>### Main deployment steps:<br>Install OpenNebula frontend version 6.6<br>Install Terraform<br>Install Docker<br>Configure bridge minionebr with IP 172.16.100.1/24<br>Enable NAT over eth0<br>Modify AppArmor<br>Install OpenNebula KVM node<br>Export appliance and update VM template<br>Install  augeas-tools iptables-persistent netfilter-persistent python3-pip unzip<br>Install pip &#39;ansible==2.9.9&#39;<br><br>Do you agree? [yes/no]:<br>yes<br><br>### Installation<br>Updating APT cache  OK<br>Install  augeas-tools iptables-persistent netfilter-persistent python3-pip unzip  OK<br>Updating PIP  OK<br>Install from PyPI &#39;ansible==2.9.9&#39;  OK<br>Creating bridge interface minionebr  OK<br>Bring bridge interfaces up  OK<br>Enabling IPv4 forward  OK<br>Persisting IPv4 forward  OK<br>Configuring NAT using iptables  OK<br>Saving iptables changes  OK<br>Installing DNSMasq  OK<br>Starting DNSMasq  OK<br>Configuring repositories  OK<br>Updating APT cache  OK<br>Installing OpenNebula packages  OK<br>Installing opennebula-provision package   OK<br>Installing TerraForm  OK<br>Create docker packages repository  OK<br>Install docker  OK<br>Start docker service  OK<br>Enable docker service  OK<br>Installing OpenNebula kvm node packages  OK<br>Updating AppArmor  OK<br>Disable default libvirtd networking  OK<br>Restart libvirtd  OK<br><br>### Configuration<br>Generating ssh keypair in /root/.ssh-oneprovision/id_rsa  OK<br>Add oneadmin to docker group  OK<br>Update network hooks  OK<br>Switching OneGate endpoint in oned.conf  OK<br>Switching OneGate endpoint in onegate-server.conf  OK<br>Switching keep_empty_bridge on in OpenNebulaNetwork.conf  OK<br>Switching scheduler interval in oned.conf  OK<br>Setting initial password for current user and oneadmin  OK<br>Changing WebUI to listen on port 80  OK<br>Switching FireEdge public endpoint  OK<br>Starting OpenNebula services  OK<br>Enabling OpenNebula services  OK<br>Add ssh key to oneadmin user  OK<br>Update ssh configs to allow VM addresses reusing  OK<br>Ensure own hostname is resolvable  OK<br>Checking OpenNebula is working  OK<br>Disabling ssh from virtual network  OK<br>Adding localhost ssh key to known_hosts  OK<br>Testing ssh connection to localhost  OK<br>Updating datastores template  OK<br>Creating KVM host  OK<br>Restarting OpenNebula  OK<br>Creating virtual network  OK<br>Exporting [Alpine Linux 3.17] from Marketplace to local datastore  OK<br>Waiting until the image is ready  OK<br>Updating VM template  OK<br><br>### Report<br>OpenNebula 6.6 was installed<br>Sunstone is running on:<br>  http://164.90.215.231/<br>FireEdge is running on:<br>  http://164.90.215.231:2616/<br>Use following to login:<br>  user: oneadmin<br>  password: SyEnJiYuWC</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ieCHtpYOQ1j0HlnLPlZVKw.png" /></figure><p>chargement d’une image Ubuntu 22.04 LTS pour création de plusieures machines virtuelles :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DuJNpDTqzPe8ttSfyFPDGA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BqIC-QChw2U4Q2S_fLhqTg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L1XW6Qyqj7DPt3yaTzc2GA.png" /></figure><p>Lancement d’une première machine virtuelle sous Ubuntu :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_DIouHvTZI60F2pNxtd05g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qsoCPa-ts5RFYcb6yPG35A.png" /></figure><p>et installation de hashi-up :</p><pre>root@minione:~# curl -sLS https://get.hashi-up.dev | sh<br><br>Downloading package https://github.com/jsiebens/hashi-up/releases/download/v0.16.0/hashi-up as /tmp/hashi-up<br>Download complete.<br><br>Running with sufficient permissions to attempt to move hashi-up to /usr/local/bin<br>New version of hashi-up installed to /usr/local/bin<br>Version: 0.16.0<br>Git Commit: b062f5d<br><br>root@minione:~# hashi-up version<br>Version: 0.16.0<br>Git Commit: b062f5d</pre><p>pour la mise en place d’un serveur Consul :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*-lsWslDmXvzY6WOo.jpg" /></figure><ul><li><a href="https://github.com/jsiebens/hashi-up/blob/main/docs/consul.md">hashi-up/consul.md at main · jsiebens/hashi-up</a></li><li><a href="https://developer.hashicorp.com/consul/downloads">Install | Consul | HashiCorp Developer</a></li></ul><pre>root@minione:~# export IP=172.16.100.2<br><br>root@minione:~# hashi-up consul install --ssh-target-addr $IP --ssh-target-user root --server --client-addr 0.0.0.0 --ssh-target-key .ssh/id_rsa --version 1.15.1<br><br>[INFO] Uploading generated Consul configuration ...<br>[INFO] Installing Consul ...<br>[INFO] -&gt; User &#39;consul&#39; already exists, will not create again<br>[INFO] -&gt; Copying configuration files<br>[INFO] -&gt; Downloading consul_1.15.1_linux_amd64.zip<br>[INFO] -&gt; Downloading consul_1.15.1_SHA256SUMS<br>[INFO] -&gt; Verifying downloaded consul_1.15.1_linux_amd64.zip<br>consul_1.15.1_linux_amd64.zip: OK<br>[INFO] -&gt; Unpacking consul_1.15.1_linux_amd64.zip<br>[INFO] -&gt; Adding systemd service file /etc/systemd/system/consul.service<br>[INFO] -&gt; Enabling systemd service<br>[INFO] -&gt; Starting systemd service<br>[INFO] Done.</pre><p>J’utilise “le VPN du pauvre” avec sshuttle pour me connecter au dashboard du serveur Consul :</p><p><a href="https://sshuttle.readthedocs.io/en/stable/usage.html">Usage - sshuttle 1.1.1 documentation</a></p><pre>$ sshuttle --dns -NHr root@164.90.215.231 0.0.0.0/0                                                                                             ✔  base   15:45:09  <br>c : Connected to server.</pre><p>Ce qui peut me permettre d’atteindre le serveur Consul directement …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rdoxv5-AKu3HFKN4ZEHDnA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7v2kScc-Jm6Fc1mQmhCvZw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Al7dC8S12877LYLHLYzLrA.png" /></figure><p>Je peux y adjoindre un serveur Nomad avec hashi-up :</p><p><a href="https://developer.hashicorp.com/nomad/downloads">Install | Nomad | HashiCorp Developer</a></p><pre>root@minione:~# hashi-up nomad install --ssh-target-addr $IP --ssh-target-user root --server --ssh-target-key .ssh/id_rsa --version 1.5.0<br><br>[INFO] Uploading generated Nomad configuration ...<br>[INFO] Installing Nomad ...<br>[INFO] -&gt; Copying configuration files<br>[INFO] -&gt; Downloading nomad_1.5.0_linux_amd64.zip<br>[INFO] -&gt; Downloading nomad_1.5.0_SHA256SUMS<br>[INFO] -&gt; Verifying downloaded nomad_1.5.0_linux_amd64.zip<br>nomad_1.5.0_linux_amd64.zip: OK<br>[INFO] -&gt; Unpacking nomad_1.5.0_linux_amd64.zip<br>[INFO] -&gt; Adding systemd service file /etc/systemd/system/nomad.service<br>[INFO] -&gt; Enabling systemd service<br>Created symlink /etc/systemd/system/multi-user.target.wants/nomad.service → /etc/systemd/system/nomad.service.<br>[INFO] -&gt; Starting systemd service<br>[INFO] Done.</pre><p>Une interface graphique est également accessible pour Nomad à cette étape …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S66J6cN1oEpmXGdLaEQxPQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lu2janbxBp8bzQoEau7KaA.png" /></figure><p>Lancement de la partie cliente de Consul et Nomad avec trois autres machines virtuelles sous Ubuntu 22.04 LTS dans OpenNebula :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hq7dRU1vkhUN1uNjXoTbgg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jlgPVjdvL4e8BIh2mTN-pw.png" /></figure><p>Personnalisation de ces trois machines virtuelles avec Pyinfra, une autre alternative sous Python à Ansible avec pipx :</p><p><a href="https://pyinfra.com/">pyinfra - agentless infrastructure automation, in plain Python</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HDDZzTyXkF4wBXg79GqCYA.png" /></figure><pre>root@minione:~# pipx install pyinfra<br><br>  installed package pyinfra 2.6.2, installed using Python 3.10.6<br>  These apps are now globally available<br>    - pyinfra<br>⚠️  Note: &#39;/root/.local/bin&#39; is not on your PATH environment variable. These apps will not be globally accessible until your PATH is updated. Run `pipx ensurepath` to<br>    automatically add it, or manually modify your PATH in your shell config file (i.e. ~/.bashrc).<br>done! ✨ 🌟 ✨<br><br>root@minione:~# pipx ensurepath<br><br>Success! Added /root/.local/bin to the PATH environment variable.<br><br>Consider adding shell completions for pipx. Run &#39;pipx completions&#39; for instructions.<br><br>You will need to open a new terminal or re-login for the PATH changes to take effect.<br><br>Otherwise pipx is ready to go! ✨ 🌟 ✨<br><br>root@minione:~# source .bashrc<br><br>root@minione:~# pyinfra --help<br><br>Usage: pyinfra [OPTIONS] INVENTORY OPERATIONS...<br><br>  pyinfra manages the state of one or more servers. It can be used for<br>  app/service deployment, config management and ad-hoc command execution.<br><br>  Documentation: pyinfra.readthedocs.io<br><br>  # INVENTORY<br><br>  + a file (inventory.py)<br>  + hostname (host.net)<br>  + Comma separated hostnames:<br>    host-1.net,host-2.net,@local<br><br>  # OPERATIONS<br><br>  # Run one or more deploys against the inventory<br>  pyinfra INVENTORY deploy_web.py [deploy_db.py]...<br><br>  # Run a single operation against the inventory<br>  pyinfra INVENTORY server.user pyinfra home=/home/pyinfra<br><br>  # Execute an arbitrary command against the inventory<br>  pyinfra INVENTORY exec -- echo &quot;hello world&quot;<br><br>  # Run one or more facts against the inventory<br>  pyinfra INVENTORY fact server.LinuxName [server.Users]...<br>  pyinfra INVENTORY fact files.File path=/path/to/file...<br><br>  # Debug the inventory hosts and data<br>  pyinfra INVENTORY debug-inventory<br><br>Options:<br>  -v                              Print meta (-v), input (-vv) and output<br>                                  (-vvv).<br>  --dry                           Don&#39;t execute operations on the target<br>                                  hosts.<br>  --limit TEXT                    Restrict the target hosts by name and group<br>                                  name.<br>  --fail-percent INTEGER          % of hosts that need to fail before exiting<br>                                  early.<br>  --data TEXT                     Override data values, format key=value.<br>  --group-data TEXT               Paths to load additional group data from<br>                                  (overrides matching keys).<br>  --config TEXT                   Specify config file to use (default:<br>                                  config.py).<br>  --chdir TEXT                    Set the working directory before executing.<br>  --sudo                          Whether to execute operations with sudo.<br>  --sudo-user TEXT                Which user to sudo when sudoing.<br>  --use-sudo-password             Whether to use a password with sudo.<br>  --su-user TEXT                  Which user to su to.<br>  --shell-executable TEXT         Shell to use (ex: &quot;sh&quot;, &quot;cmd&quot;, &quot;ps&quot;).<br>  --parallel INTEGER              Number of operations to run in parallel.<br>  --no-wait                       Don&#39;t wait between operations for hosts.<br>  --serial                        Run operations in serial, host by host.<br>  --ssh-user, --user TEXT         SSH user to connect as.<br>  --ssh-port, --port INTEGER      SSH port to connect to.<br>  --ssh-key, --key PATH           SSH Private key filename.<br>  --ssh-key-password, --key-password TEXT<br>                                  SSH Private key password.<br>  --ssh-password, --password TEXT<br>                                  SSH password.<br>  --winrm-username TEXT           WINRM user to connect as.<br>  --winrm-password TEXT           WINRM password.<br>  --winrm-port TEXT               WINRM port to connect to.<br>  --winrm-transport TEXT          WINRM transport for use.<br>  --support                       Print useful information for support and<br>                                  exit.<br>  --quiet                         Hide most pyinfra output.<br>  --debug                         Print debug info.<br>  --debug-facts                   Print facts after generating operations and<br>                                  exit.<br>  --debug-operations              Print operations after generating and exit.<br>  --version                       Show the version and exit.<br>  --help                          Show this message and exit.</pre><pre>root@minione:~# pyinfra 172.16.100.4 exec -- hostnamectl set-hostname client0<br><br>--&gt; Loading config...<br><br>--&gt; Loading inventory...<br><br>--&gt; Connecting to hosts...<br>    No host key for 172.16.100.4 found in known_hosts<br>    [172.16.100.4] Connected<br>    [172.16.100.4] Ready: shell<br><br>--&gt; Proposed changes:<br>    Ungrouped:<br>    [172.16.100.4]   Operations: 1   Change: 1   No change: 0   <br><br><br>--&gt; Beginning operation run...<br>--&gt; Starting operation: Server/Shell (hostnamectl set-hostname client0)<br>    [172.16.100.4] Success<br><br><br>--&gt; Results:<br>    Ungrouped:<br>    [172.16.100.4]   Changed: 1   No change: 0   Errors: 0   <br><br>  <br>root@minione:~# pyinfra 172.16.100.3 exec -- hostnamectl set-hostname client1<br><br>--&gt; Loading config...<br><br>--&gt; Loading inventory...<br><br>--&gt; Connecting to hosts...<br>    No host key for 172.16.100.3 found in known_hosts<br>    [172.16.100.3] Connected<br>    [172.16.100.3] Ready: shell<br><br>--&gt; Proposed changes:<br>    Ungrouped:<br>    [172.16.100.3]   Operations: 1   Change: 1   No change: 0   <br><br><br>--&gt; Beginning operation run...<br>--&gt; Starting operation: Server/Shell (hostnamectl set-hostname client1)<br>    [172.16.100.3] Success<br><br><br>--&gt; Results:<br>    Ungrouped:<br>    [172.16.100.3]   Changed: 1   No change: 0   Errors: 0  <br> <br>root@minione:~# pyinfra 172.16.100.5 exec -- hostnamectl set-hostname client2<br><br>--&gt; Loading config...<br><br>--&gt; Loading inventory...<br><br>--&gt; Connecting to hosts...<br>    No host key for 172.16.100.5 found in known_hosts<br>    [172.16.100.5] Connected<br>    [172.16.100.5] Ready: shell<br><br>--&gt; Proposed changes:<br>    Ungrouped:<br>    [172.16.100.5]   Operations: 1   Change: 1   No change: 0   <br><br><br>--&gt; Beginning operation run...<br>--&gt; Starting operation: Server/Shell (hostnamectl set-hostname client2)<br>    [172.16.100.5] Success<br><br><br>--&gt; Results:<br>    Ungrouped:<br>    [172.16.100.5]   Changed: 1   No change: 0   Errors: 0  </pre><p>Par ce biais, insertion du moteur Docker dans ces machines virtuelles :</p><pre>root@minione:~# cat inventory.py <br><br>my_hosts = [&quot;172.16.100.4&quot;, &quot;172.16.100.3&quot;, &quot;172.16.100.5&quot;]<br><br>root@minione:~# pyinfra inventory.py exec -- &quot;curl -fsSL https://get.docker.com | sh -&quot;<br><br>--&gt; Loading config...<br><br>--&gt; Loading inventory...<br><br>--&gt; Connecting to hosts...<br>    No host key for 172.16.100.5 found in known_hosts<br>    No host key for 172.16.100.3 found in known_hosts<br>    [172.16.100.5] Connected<br>    No host key for 172.16.100.4 found in known_hosts<br>    [172.16.100.4] Connected<br>    [172.16.100.3] Connected<br>    [172.16.100.4] Ready: shell<br>    [172.16.100.3] Ready: shell<br>    [172.16.100.5] Ready: shell<br><br>--&gt; Proposed changes:<br>    Groups: inventory / my_hosts<br>    [172.16.100.4]   Operations: 1   Change: 1   No change: 0   <br>    [172.16.100.3]   Operations: 1   Change: 1   No change: 0   <br>    [172.16.100.5]   Operations: 1   Change: 1   No change: 0   <br><br><br>--&gt; Beginning operation run...<br>--&gt; Starting operation: Server/Shell (curl -fsSL https://get.docker.com | sh -)<br>[172.16.100.5] # Executing docker install script, commit: 66474034547a96caa0a25be56051ff8b726a1b28<br>[172.16.100.5] + sh -c apt-get update -qq &gt;/dev/null<br>[172.16.100.4] # Executing docker install script, commit: 66474034547a96caa0a25be56051ff8b726a1b28<br>[172.16.100.4] + sh -c apt-get update -qq &gt;/dev/null<br>[172.16.100.3] # Executing docker install script, commit: 66474034547a96caa0a25be56051ff8b726a1b28<br>[172.16.100.3] + sh -c apt-get update -qq &gt;/dev/null<br>[172.16.100.4] + sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl &gt;/dev/null<br>[172.16.100.5] + sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl &gt;/dev/null<br>[172.16.100.3] + sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl &gt;/dev/null<br>[172.16.100.5] + sh -c mkdir -p /etc/apt/keyrings &amp;&amp; chmod -R 0755 /etc/apt/keyrings<br>[172.16.100.5] + sh -c curl -fsSL &quot;https://download.docker.com/linux/ubuntu/gpg&quot; | gpg --dearmor --yes -o /etc/apt/keyrings/docker.gpg<br>[172.16.100.5] + sh -c chmod a+r /etc/apt/keyrings/docker.gpg<br>[172.16.100.5] + sh -c echo &quot;deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu jammy stable&quot; &gt; /etc/apt/sources.list.d/docker.list<br>[172.16.100.5] + sh -c apt-get update -qq &gt;/dev/null<br>[172.16.100.4] + sh -c mkdir -p /etc/apt/keyrings &amp;&amp; chmod -R 0755 /etc/apt/keyrings<br>[172.16.100.3] + sh -c mkdir -p /etc/apt/keyrings &amp;&amp; chmod -R 0755 /etc/apt/keyrings<br>[172.16.100.4] + sh -c curl -fsSL &quot;https://download.docker.com/linux/ubuntu/gpg&quot; | gpg --dearmor --yes -o /etc/apt/keyrings/docker.gpg<br>[172.16.100.3] + sh -c curl -fsSL &quot;https://download.docker.com/linux/ubuntu/gpg&quot; | gpg --dearmor --yes -o /etc/apt/keyrings/docker.gpg<br>[172.16.100.3] + sh -c chmod a+r /etc/apt/keyrings/docker.gpg<br>[172.16.100.3] + sh -c echo &quot;deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu jammy stable&quot; &gt; /etc/apt/sources.list.d/docker.list<br>[172.16.100.3] + sh -c apt-get update -qq &gt;/dev/null<br>[172.16.100.4] + sh -c chmod a+r /etc/apt/keyrings/docker.gpg<br>[172.16.100.4] + sh -c echo &quot;deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu jammy stable&quot; &gt; /etc/apt/sources.list.d/docker.list<br>[172.16.100.4] + sh -c apt-get update -qq &gt;/dev/null<br>[172.16.100.3] + sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq docker-ce docker-ce-cli containerd.io docker-scan-plugin docker-compose-plugin docker-ce-rootless-extras docker-buildx-plugin &gt;/dev/null<br>[172.16.100.4] + sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq docker-ce docker-ce-cli containerd.io docker-scan-plugin docker-compose-plugin docker-ce-rootless-extras docker-buildx-plugin &gt;/dev/null<br>[172.16.100.5] + sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq docker-ce docker-ce-cli containerd.io docker-scan-plugin docker-compose-plugin docker-ce-rootless-extras docker-buildx-plugin &gt;/dev/null<br>[172.16.100.5] + sh -c docker version<br>[172.16.100.4] + sh -c docker version<br>[172.16.100.3] + sh -c docker version<br>[172.16.100.5] Client: Docker Engine - Community<br>[172.16.100.5]  Version:           23.0.1<br>[172.16.100.5]  API version:       1.42<br>[172.16.100.5]  Go version:        go1.19.5<br>[172.16.100.5]  Git commit:        a5ee5b1<br>[172.16.100.5]  Built:             Thu Feb  9 19:47:01 2023<br>[172.16.100.5]  OS/Arch:           linux/amd64<br>[172.16.100.5]  Context:           default<br>[172.16.100.5] <br>[172.16.100.5] Server: Docker Engine - Community<br>[172.16.100.5]  Engine:<br>[172.16.100.5]   Version:          23.0.1<br>[172.16.100.5]   API version:      1.42 (minimum version 1.12)<br>[172.16.100.5]   Go version:       go1.19.5<br>[172.16.100.5]   Git commit:       bc3805a<br>[172.16.100.5]   Built:            Thu Feb  9 19:47:01 2023<br>[172.16.100.5]   OS/Arch:          linux/amd64<br>[172.16.100.5]   Experimental:     false<br>[172.16.100.5]  containerd:<br>[172.16.100.5]   Version:          1.6.18<br>[172.16.100.5]   GitCommit:        2456e983eb9e37e47538f59ea18f2043c9a73640<br>[172.16.100.5]  runc:<br>[172.16.100.5]   Version:          1.1.4<br>[172.16.100.5]   GitCommit:        v1.1.4-0-g5fd4c4d<br>[172.16.100.5]  docker-init:<br>[172.16.100.5]   Version:          0.19.0<br>[172.16.100.5]   GitCommit:        de40ad0<br>[172.16.100.5] <br>[172.16.100.5] ================================================================================<br>[172.16.100.5] <br>[172.16.100.5] To run Docker as a non-privileged user, consider setting up the<br>[172.16.100.5] Docker daemon in rootless mode for your user:<br>[172.16.100.5] <br>[172.16.100.5]     dockerd-rootless-setuptool.sh install<br>[172.16.100.5] <br>[172.16.100.5] Visit https://docs.docker.com/go/rootless/ to learn about rootless mode.<br>[172.16.100.5] <br>[172.16.100.5] <br>[172.16.100.5] To run the Docker daemon as a fully privileged service, but granting non-root<br>[172.16.100.5] users access, refer to https://docs.docker.com/go/daemon-access/<br>[172.16.100.5] <br>[172.16.100.5] WARNING: Access to the remote API on a privileged Docker daemon is equivalent<br>[172.16.100.5]          to root access on the host. Refer to the &#39;Docker daemon attack surface&#39;<br>[172.16.100.5]          documentation for details: https://docs.docker.com/go/attack-surface/<br>[172.16.100.5] <br>[172.16.100.5] ================================================================================<br>[172.16.100.5] <br>    [172.16.100.5] Success<br>[172.16.100.4] Client: Docker Engine - Community<br>[172.16.100.4]  Version:           23.0.1<br>[172.16.100.4]  API version:       1.42<br>[172.16.100.4]  Go version:        go1.19.5<br>[172.16.100.4]  Git commit:        a5ee5b1<br>[172.16.100.4]  Built:             Thu Feb  9 19:47:01 2023<br>[172.16.100.4]  OS/Arch:           linux/amd64<br>[172.16.100.4]  Context:           default<br>[172.16.100.4] <br>[172.16.100.4] Server: Docker Engine - Community<br>[172.16.100.4]  Engine:<br>[172.16.100.4]   Version:          23.0.1<br>[172.16.100.4]   API version:      1.42 (minimum version 1.12)<br>[172.16.100.4]   Go version:       go1.19.5<br>[172.16.100.4]   Git commit:       bc3805a<br>[172.16.100.4]   Built:            Thu Feb  9 19:47:01 2023<br>[172.16.100.4]   OS/Arch:          linux/amd64<br>[172.16.100.4]   Experimental:     false<br>[172.16.100.4]  containerd:<br>[172.16.100.4]   Version:          1.6.18<br>[172.16.100.4]   GitCommit:        2456e983eb9e37e47538f59ea18f2043c9a73640<br>[172.16.100.4]  runc:<br>[172.16.100.4]   Version:          1.1.4<br>[172.16.100.4]   GitCommit:        v1.1.4-0-g5fd4c4d<br>[172.16.100.4]  docker-init:<br>[172.16.100.4]   Version:          0.19.0<br>[172.16.100.4]   GitCommit:        de40ad0<br>[172.16.100.4] <br>[172.16.100.4] ================================================================================<br>[172.16.100.4] <br>[172.16.100.4] To run Docker as a non-privileged user, consider setting up the<br>[172.16.100.4] Docker daemon in rootless mode for your user:<br>[172.16.100.4] <br>[172.16.100.4]     dockerd-rootless-setuptool.sh install<br>[172.16.100.4] <br>[172.16.100.4] Visit https://docs.docker.com/go/rootless/ to learn about rootless mode.<br>[172.16.100.4] <br>[172.16.100.4] <br>[172.16.100.4] To run the Docker daemon as a fully privileged service, but granting non-root<br>[172.16.100.4] users access, refer to https://docs.docker.com/go/daemon-access/<br>[172.16.100.4] <br>[172.16.100.4] WARNING: Access to the remote API on a privileged Docker daemon is equivalent<br>[172.16.100.4]          to root access on the host. Refer to the &#39;Docker daemon attack surface&#39;<br>[172.16.100.4]          documentation for details: https://docs.docker.com/go/attack-surface/<br>[172.16.100.4] <br>[172.16.100.4] ================================================================================<br>[172.16.100.4] <br>    [172.16.100.4] Success<br>[172.16.100.3] Client: Docker Engine - Community<br>[172.16.100.3]  Version:           23.0.1<br>[172.16.100.3]  API version:       1.42<br>[172.16.100.3]  Go version:        go1.19.5<br>[172.16.100.3]  Git commit:        a5ee5b1<br>[172.16.100.3]  Built:             Thu Feb  9 19:47:01 2023<br>[172.16.100.3]  OS/Arch:           linux/amd64<br>[172.16.100.3]  Context:           default<br>[172.16.100.3] <br>[172.16.100.3] Server: Docker Engine - Community<br>[172.16.100.3]  Engine:<br>[172.16.100.3]   Version:          23.0.1<br>[172.16.100.3]   API version:      1.42 (minimum version 1.12)<br>[172.16.100.3]   Go version:       go1.19.5<br>[172.16.100.3]   Git commit:       bc3805a<br>[172.16.100.3]   Built:            Thu Feb  9 19:47:01 2023<br>[172.16.100.3]   OS/Arch:          linux/amd64<br>[172.16.100.3]   Experimental:     false<br>[172.16.100.3]  containerd:<br>[172.16.100.3]   Version:          1.6.18<br>[172.16.100.3]   GitCommit:        2456e983eb9e37e47538f59ea18f2043c9a73640<br>[172.16.100.3]  runc:<br>[172.16.100.3]   Version:          1.1.4<br>[172.16.100.3]   GitCommit:        v1.1.4-0-g5fd4c4d<br>[172.16.100.3]  docker-init:<br>[172.16.100.3]   Version:          0.19.0<br>[172.16.100.3]   GitCommit:        de40ad0<br>[172.16.100.3] <br>[172.16.100.3] ================================================================================<br>[172.16.100.3] <br>[172.16.100.3] To run Docker as a non-privileged user, consider setting up the<br>[172.16.100.3] Docker daemon in rootless mode for your user:<br>[172.16.100.3] <br>[172.16.100.3]     dockerd-rootless-setuptool.sh install<br>[172.16.100.3] <br>[172.16.100.3] Visit https://docs.docker.com/go/rootless/ to learn about rootless mode.<br>[172.16.100.3] <br>[172.16.100.3] <br>[172.16.100.3] To run the Docker daemon as a fully privileged service, but granting non-root<br>[172.16.100.3] users access, refer to https://docs.docker.com/go/daemon-access/<br>[172.16.100.3] <br>[172.16.100.3] WARNING: Access to the remote API on a privileged Docker daemon is equivalent<br>[172.16.100.3]          to root access on the host. Refer to the &#39;Docker daemon attack surface&#39;<br>[172.16.100.3]          documentation for details: https://docs.docker.com/go/attack-surface/<br>[172.16.100.3] <br>[172.16.100.3] ================================================================================<br>[172.16.100.3] <br>    [172.16.100.3] Success<br><br><br>--&gt; Results:<br>    Groups: inventory / my_hosts<br>    [172.16.100.4]   Changed: 1   No change: 0   Errors: 0   <br>    [172.16.100.3]   Changed: 1   No change: 0   Errors: 0   <br>    [172.16.100.5]   Changed: 1   No change: 0   Errors: 0 </pre><pre>root@minione:~# pyinfra inventory.py exec -- &quot;docker ps -a&quot;<br><br>--&gt; Loading config...<br><br>--&gt; Loading inventory...<br><br>--&gt; Connecting to hosts...<br>    No host key for 172.16.100.5 found in known_hosts<br>    No host key for 172.16.100.3 found in known_hosts<br>    No host key for 172.16.100.4 found in known_hosts<br>    [172.16.100.5] Connected<br>    [172.16.100.3] Connected<br>    [172.16.100.4] Connected<br>    [172.16.100.5] Ready: shell<br>    [172.16.100.3] Ready: shell<br>    [172.16.100.4] Ready: shell<br><br>--&gt; Proposed changes:<br>    Groups: inventory / my_hosts<br>    [172.16.100.5]   Operations: 1   Change: 1   No change: 0   <br>    [172.16.100.3]   Operations: 1   Change: 1   No change: 0   <br>    [172.16.100.4]   Operations: 1   Change: 1   No change: 0   <br><br><br>--&gt; Beginning operation run...<br>--&gt; Starting operation: Server/Shell (docker ps -a)<br>[172.16.100.5] CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES<br>    [172.16.100.5] Success<br>[172.16.100.4] CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES<br>    [172.16.100.4] Success<br>[172.16.100.3] CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES<br>    [172.16.100.3] Success<br><br><br>--&gt; Results:<br>    Groups: inventory / my_hosts<br>    [172.16.100.5]   Changed: 1   No change: 0   Errors: 0   <br>    [172.16.100.3]   Changed: 1   No change: 0   Errors: 0   <br>    [172.16.100.4]   Changed: 1   No change: 0   Errors: 0 </pre><p>Déploiement ensuite des clients Consul et Nomad toujours avec hashi-up :</p><pre>root@minione:~# export SERVER_IP=172.16.100.2<br>root@minione:~# export AGENT_1_IP=172.16.100.4<br>root@minione:~# export AGENT_2_IP=172.16.100.3<br>root@minione:~# export AGENT_3_IP=172.16.100.5<br><br>root@minione:~# hashi-up consul install --ssh-target-addr $AGENT_1_IP --ssh-target-user root --retry-join $SERVER_IP --ssh-target-key .ssh/id_rsa --version 1.15.1<br><br>[INFO] Uploading generated Consul configuration ...<br>[INFO] Installing Consul ...<br>[INFO] -&gt; Creating user named &#39;consul&#39;<br>[INFO] -&gt; Copying configuration files<br>[INFO] -&gt; Downloading consul_1.15.1_linux_amd64.zip<br>[INFO] -&gt; Downloading consul_1.15.1_SHA256SUMS<br>[INFO] -&gt; Verifying downloaded consul_1.15.1_linux_amd64.zip<br>consul_1.15.1_linux_amd64.zip: OK<br>[INFO] -&gt; Unpacking consul_1.15.1_linux_amd64.zip<br>[INFO] -&gt; Adding systemd service file /etc/systemd/system/consul.service<br>[INFO] -&gt; Enabling systemd service<br>Created symlink /etc/systemd/system/multi-user.target.wants/consul.service → /etc/systemd/system/consul.service.<br>[INFO] -&gt; Starting systemd service<br>[INFO] Done.<br><br>root@minione:~# hashi-up consul install --ssh-target-addr $AGENT_2_IP --ssh-target-user root --retry-join $SERVER_IP --ssh-target-key .ssh/id_rsa --version 1.15.1<br><br>[INFO] Uploading generated Consul configuration ...<br>[INFO] Installing Consul ...<br>[INFO] -&gt; Creating user named &#39;consul&#39;<br>[INFO] -&gt; Copying configuration files<br>[INFO] -&gt; Downloading consul_1.15.1_linux_amd64.zip<br>[INFO] -&gt; Downloading consul_1.15.1_SHA256SUMS<br>[INFO] -&gt; Verifying downloaded consul_1.15.1_linux_amd64.zip<br>consul_1.15.1_linux_amd64.zip: OK<br>[INFO] -&gt; Unpacking consul_1.15.1_linux_amd64.zip<br>[INFO] -&gt; Adding systemd service file /etc/systemd/system/consul.service<br>[INFO] -&gt; Enabling systemd service<br>Created symlink /etc/systemd/system/multi-user.target.wants/consul.service → /etc/systemd/system/consul.service.<br>[INFO] -&gt; Starting systemd service<br>[INFO] Done.<br><br>root@minione:~# hashi-up consul install --ssh-target-addr $AGENT_3_IP --ssh-target-user root --retry-join $SERVER_IP --ssh-target-key .ssh/id_rsa --version 1.15.1<br><br>[INFO] Uploading generated Consul configuration ...<br>[INFO] Installing Consul ...<br>[INFO] -&gt; Creating user named &#39;consul&#39;<br>[INFO] -&gt; Copying configuration files<br>[INFO] -&gt; Downloading consul_1.15.1_linux_amd64.zip<br>[INFO] -&gt; Downloading consul_1.15.1_SHA256SUMS<br>[INFO] -&gt; Verifying downloaded consul_1.15.1_linux_amd64.zip<br>consul_1.15.1_linux_amd64.zip: OK<br>[INFO] -&gt; Unpacking consul_1.15.1_linux_amd64.zip<br>[INFO] -&gt; Adding systemd service file /etc/systemd/system/consul.service<br>[INFO] -&gt; Enabling systemd service<br>Created symlink /etc/systemd/system/multi-user.target.wants/consul.service → /etc/systemd/system/consul.service.<br>[INFO] -&gt; Starting systemd service<br>[INFO] Done.</pre><pre>root@minione:~# hashi-up nomad install --ssh-target-addr $AGENT_1_IP --ssh-target-user root --client --retry-join $SERVER_IP --ssh-target-key .ssh/id_rsa --version 1.5.0<br><br>[INFO] Uploading generated Nomad configuration ...<br>[INFO] Installing Nomad ...<br>[INFO] -&gt; Copying configuration files<br>[INFO] -&gt; Downloading nomad_1.5.0_linux_amd64.zip<br>[INFO] -&gt; Downloading nomad_1.5.0_SHA256SUMS<br>[INFO] -&gt; Verifying downloaded nomad_1.5.0_linux_amd64.zip<br>nomad_1.5.0_linux_amd64.zip: OK<br>[INFO] -&gt; Unpacking nomad_1.5.0_linux_amd64.zip<br>[INFO] -&gt; Adding systemd service file /etc/systemd/system/nomad.service<br>[INFO] -&gt; Enabling systemd service<br>Created symlink /etc/systemd/system/multi-user.target.wants/nomad.service → /etc/systemd/system/nomad.service.<br>[INFO] -&gt; Starting systemd service<br>[INFO] Done.<br><br>root@minione:~# hashi-up nomad install --ssh-target-addr $AGENT_2_IP --ssh-target-user root --client --retry-join $SERVER_IP --ssh-target-key .ssh/id_rsa --version 1.5.0<br><br>[INFO] Uploading generated Nomad configuration ...<br>[INFO] Installing Nomad ...<br>[INFO] -&gt; Copying configuration files<br>[INFO] -&gt; Downloading nomad_1.5.0_linux_amd64.zip<br>[INFO] -&gt; Downloading nomad_1.5.0_SHA256SUMS<br>[INFO] -&gt; Verifying downloaded nomad_1.5.0_linux_amd64.zip<br>nomad_1.5.0_linux_amd64.zip: OK<br>[INFO] -&gt; Unpacking nomad_1.5.0_linux_amd64.zip<br>[INFO] -&gt; Adding systemd service file /etc/systemd/system/nomad.service<br>[INFO] -&gt; Enabling systemd service<br>Created symlink /etc/systemd/system/multi-user.target.wants/nomad.service → /etc/systemd/system/nomad.service.<br>[INFO] -&gt; Starting systemd service<br>[INFO] Done.<br><br>root@minione:~# hashi-up nomad install --ssh-target-addr $AGENT_3_IP --ssh-target-user root --client --retry-join $SERVER_IP --ssh-target-key .ssh/id_rsa --version 1.5.0<br><br>[INFO] Uploading generated Nomad configuration ...<br>[INFO] Installing Nomad ...<br>[INFO] -&gt; Copying configuration files<br>[INFO] -&gt; Downloading nomad_1.5.0_linux_amd64.zip<br>[INFO] -&gt; Downloading nomad_1.5.0_SHA256SUMS<br>[INFO] -&gt; Verifying downloaded nomad_1.5.0_linux_amd64.zip<br>nomad_1.5.0_linux_amd64.zip: OK<br>[INFO] -&gt; Unpacking nomad_1.5.0_linux_amd64.zip<br>[INFO] -&gt; Adding systemd service file /etc/systemd/system/nomad.service<br>[INFO] -&gt; Enabling systemd service<br>Created symlink /etc/systemd/system/multi-user.target.wants/nomad.service → /etc/systemd/system/nomad.service.<br>[INFO] -&gt; Starting systemd service<br>[INFO] Done.</pre><p>Les clients Nomad avec Consul sont présents :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lb1qHrmbg9AQvfTBGxQR5w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DiXt7v-O7E7tUeRcF9MOKQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*geUuFaQQYeBtVNcbc4QJzg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AySYSsKhLSQidsWP19Ef9A.png" /></figure><p>Lancement de Fabio qui s’intègre nativement avec Consul et fournit une interface Web optionnelle pour visualiser le routage. Le principal cas d’utilisation de Fabio est la distribution des requêtes HTTP(S) et TCP entrantes depuis Internet vers les services frontaux qui peuvent traiter ces requêtes.</p><p><a href="https://developer.hashicorp.com/nomad/tutorials/load-balancing/load-balancing-fabio">Load Balancing with Fabio | Nomad | HashiCorp Developer</a></p><p>Ici, je lance Fabio en tant que job système afin qu’il puisse acheminer le trafic entrant de manière homogène vers un groupe de serveurs quels que soient les nœuds clients sur lesquels il s’exécute. On peut donc placer tous les nœuds clients derrière un équilibreur de charge pour fournir à l’utilisateur final un point d’accès unique.</p><pre>job &quot;fabio&quot; {<br>  datacenters = [&quot;dc1&quot;]<br>  type = &quot;system&quot;<br><br>  group &quot;fabio&quot; {<br>    network {<br>      port &quot;lb&quot; {<br>        static = 9999<br>      }<br>      port &quot;ui&quot; {<br>        static = 9998<br>      }<br>    }<br>    task &quot;fabio&quot; {<br>      driver = &quot;docker&quot;<br>      config {<br>        image = &quot;fabiolb/fabio&quot;<br>        network_mode = &quot;host&quot;<br>        ports = [&quot;lb&quot;,&quot;ui&quot;]<br>      }<br><br>      resources {<br>        cpu    = 200<br>        memory = 128<br>      }<br>    }<br>  }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DG56Gy2WrOLwKk4Ei5Skig.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dqOSg4ROo1lOdnKqUMNuPw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*shf6tdjR4d1I4ZfBotxEkA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7TbzxpH79k1pWQmsncQbXA.png" /></figure><p>L’interface graphique de Fabio est disponible sur chacun des trois noeuds clients sur le port TCP 9998 :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*keaehZGrgTUf9GK7XdmbPw.png" /></figure><p>Exemple avec ce job et une image de base Nginx avec création de trois serveurs attenants :</p><pre>job &quot;webserver&quot; {<br>  datacenters = [&quot;dc1&quot;]<br>  type = &quot;service&quot;<br><br>  group &quot;webserver&quot; {<br>    count = 3<br>    network {<br>      port &quot;http&quot; {<br>        to = 8080<br>      }<br>    }<br><br>    service {<br>      name = &quot;nginx-webserver&quot;<br>      tags = [&quot;urlprefix-/&quot;]<br>      port = &quot;http&quot;<br>      check {<br>        name     = &quot;alive&quot;<br>        type     = &quot;http&quot;<br>        path     = &quot;/&quot;<br>        interval = &quot;10s&quot;<br>        timeout  = &quot;2s&quot;<br>      }<br>    }<br><br>    restart {<br>      attempts = 2<br>      interval = &quot;30m&quot;<br>      delay = &quot;15s&quot;<br>      mode = &quot;fail&quot;<br>    }<br><br>    task &quot;nginx&quot; {<br>      driver = &quot;docker&quot;<br>      config {<br>        image = &quot;bitnami/nginx:latest&quot;<br>        ports = [&quot;http&quot;]<br>      }<br>    }<br>  }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*31VpfVOOhm9VDqBQ2awkgg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5zuLmiNFinr6ZnjFX0rBfw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*elVeN-hc6aW9lhwFqFTPbg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5_KgBEHs5UvUwgCPS-ZezA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nRbaioUFYNaSvHaz4K13cA.png" /></figure><p>Fabio a détecté le déploiement de ces trois serveurs Nginx :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sSEKwVlfdTbbOKMwdfcznw.png" /></figure><p>en fournissant des ports d’accès à ces entités :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CNF076uc1Y2S0y0luIBuHw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gOWriF4NzdeUBZSkD-_5uA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CTvlh_7PaiMxDNtPOm9YSA.png" /></figure><p>Test d’une instance Alpine Linux avec un serveur OpenSSH qui mime le fonctionnement d’une machine virtuelle dans Nomad en utilisant cette image Docker :</p><p><a href="https://hub.docker.com/r/mcas/alpine-sshd">Docker</a></p><pre>job &quot;ssh&quot; {<br>  datacenters = [&quot;dc1&quot;]<br>  type = &quot;service&quot;<br><br>  group &quot;ssh&quot; {<br>    count = 1<br>    network {<br>      port &quot;ssh&quot; {<br>        to = 22<br>      }<br>    }<br><br>    service {<br>      name = &quot;sshd&quot;<br>      port = &quot;ssh&quot;<br>    }<br><br>    task &quot;openssh&quot; {<br>      driver = &quot;docker&quot;<br>      config {<br>        image = &quot;mcas/alpine-sshd:latest&quot;<br>        ports = [&quot;ssh&quot;]<br>      }<br>    }<br>  }<br>}</pre><p>Exécution du job via la dashboard du serveur Nomad :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Il7nhifyaDTS_FfZH96E7w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k91zDJ1s3EJetXF730AXfw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B8he3YlXW7HFVEUUYiiNpA.png" /></figure><p>Consul voit l’ensemble des instances déployées dans Nomad :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rd9VZ6K0CJX6HpljFFbruw.png" /></figure><p>en me donnant les informations sur le port d’accès à cette instance Alpine Linux :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mow4a4H2thytRuVoV-Kg3w.png" /></figure><p>Connexion locale à cette instance en SSH avec ce port d’accès :</p><pre>root@minione:~# ssh -p 26053 alpine@172.16.100.5<br>Warning: Permanently added &#39;[172.16.100.5]:26053&#39; (ED25519) to the list of known hosts.<br>alpine@172.16.100.5 password: <br>Welcome to Alpine!<br><br>The Alpine Wiki contains a large amount of how-to guides and general<br>information about administrating Alpine systems.<br>See &lt;https://wiki.alpinelinux.org/&gt;.<br><br>You can setup the system with the command: setup-alpine<br><br>You may change this message by editing /etc/motd.<br><br>1900f3e8b78a:~$ ps aux<br>PID   USER     TIME  COMMAND<br>    1 root      0:00 sshd: /usr/sbin/sshd -D -e [listener] 0 of 10-100 startups<br>   10 root      0:00 sshd: alpine [priv]<br>   12 alpine    0:00 sshd: alpine@pts/0<br>   13 alpine    0:00 -bash<br>   14 alpine    0:00 ps aux<br>1900f3e8b78a:~$ free -m<br>              total        used        free      shared  buff/cache   available<br>Mem:           5934         348        4982           1         604        5346<br>Swap:             0           0           0<br>1900f3e8b78a:~$ df -h<br>Filesystem                Size      Used Available Use% Mounted on<br>overlay                  19.2G      2.3G     16.9G  12% /<br>tmpfs                    64.0M         0     64.0M   0% /dev<br>shm                      64.0M         0     64.0M   0% /dev/shm<br>/dev/vda1                19.2G      2.3G     16.9G  12% /alloc<br>/dev/vda1                19.2G      2.3G     16.9G  12% /local<br>tmpfs                     1.0M         0      1.0M   0% /secrets<br>/dev/vda1                19.2G      2.3G     16.9G  12% /etc/resolv.conf<br>/dev/vda1                19.2G      2.3G     16.9G  12% /etc/hostname<br>/dev/vda1                19.2G      2.3G     16.9G  12% /etc/hosts<br>tmpfs                     2.9G         0      2.9G   0% /proc/acpi<br>tmpfs                    64.0M         0     64.0M   0% /proc/kcore<br>tmpfs                    64.0M         0     64.0M   0% /proc/keys<br>tmpfs                    64.0M         0     64.0M   0% /proc/timer_list<br>tmpfs                     2.9G         0      2.9G   0% /proc/scsi<br>tmpfs                     2.9G         0      2.9G   0% /sys/firmware</pre><p>Le sempiternel démonstrateur FC s’y exécute localement comme s’il s’agissait d’une machine virtuelle :</p><p><a href="https://github.com/france-connect/service-provider-example">GitHub - france-connect/service-provider-example: An implementation example of the FranceConnect button on a service provider&#39;s website.</a></p><pre>1900f3e8b78a:~/fcdemo3$ pm2 start start.sh <br><br>                        -------------<br><br>__/\\\\\\\\\\\\\____/\\\\____________/\\\\____/\\\\\\\\\_____<br> _\/\\\/////////\\\_\/\\\\\\________/\\\\\\__/\\\///////\\\___<br>  _\/\\\_______\/\\\_\/\\\//\\\____/\\\//\\\_\///______\//\\\__<br>   _\/\\\\\\\\\\\\\/__\/\\\\///\\\/\\\/_\/\\\___________/\\\/___<br>    _\/\\\/////////____\/\\\__\///\\\/___\/\\\________/\\\//_____<br>     _\/\\\_____________\/\\\____\///_____\/\\\_____/\\\//________<br>      _\/\\\_____________\/\\\_____________\/\\\___/\\\/___________<br>       _\/\\\_____________\/\\\_____________\/\\\__/\\\\\\\\\\\\\\\_<br>        _\///______________\///______________\///__\///////////////__<br><br><br>                          Runtime Edition<br><br>        PM2 is a Production Process Manager for Node.js applications<br>                     with a built-in Load Balancer.<br><br>                Start and Daemonize any application:<br>                $ pm2 start app.js<br><br>                Load Balance 4 instances of api.js:<br>                $ pm2 start api.js -i 4<br><br>                Monitor in production:<br>                $ pm2 monitor<br><br>                Make pm2 auto-boot at server restart:<br>                $ pm2 startup<br><br>                To go further checkout:<br>                http://pm2.io/<br><br><br>                        -------------<br><br>[PM2] Spawning PM2 daemon with pm2_home=/home/alpine/.pm2<br>[PM2] PM2 Successfully daemonized<br>[PM2] Starting /home/alpine/fcdemo3/start.sh in fork_mode (1 instance)<br>[PM2] Done.<br>┌─────┬──────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐<br>│ id  │ name     │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │<br>├─────┼──────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤<br>│ 0   │ start    │ default     │ 0.0.0   │ fork    │ 466      │ 0s     │ 0    │ online    │ 0%       │ 1.7mb    │ alpine   │ disabled │<br>└─────┴──────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘<br><br>1900f3e8b78a:~/fcdemo3$ pm2 log start<br><br>[TAILING] Tailing last 15 lines for [start] process (change the value with --lines option)<br>/home/alpine/.pm2/logs/start-error.log last 15 lines:<br>/home/alpine/.pm2/logs/start-out.log last 15 lines:<br>0|start    | <br>0|start    | &gt; service-provider-mock@0.0.0 start<br>0|start    | &gt; node ./bin/www<br>0|start    | <br>0|start    | Server listening on http://0.0.0.0:3000</pre><pre>1900f3e8b78a:~$ curl http://localhost:3000<br>&lt;!doctype html&gt;<br>&lt;html lang=&quot;en&quot;&gt;<br>&lt;head&gt;<br>    &lt;meta charset=&quot;UTF-8&quot;&gt;<br>    &lt;meta name=&quot;viewport&quot;<br>          content=&quot;width=device-width, user-scalable=no, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0&quot;&gt;<br>    &lt;meta http-equiv=&quot;X-UA-Compatible&quot; content=&quot;ie=edge&quot;&gt;<br>    &lt;link rel=&quot;stylesheet&quot; href=&quot;https://cdnjs.cloudflare.com/ajax/libs/bulma/0.7.1/css/bulma.min.css&quot; integrity=&quot;sha256-zIG416V1ynj3Wgju/scU80KAEWOsO5rRLfVyRDuOv7Q=&quot; crossorigin=&quot;anonymous&quot; /&gt;<br>    &lt;title&gt;Démonstrateur Fournisseur de Service&lt;/title&gt;<br>&lt;/head&gt;<br><br>&lt;body&gt;<br>&lt;nav class=&quot;navbar&quot; role=&quot;navigation&quot; aria-label=&quot;main navigation&quot;&gt;<br>    &lt;div class=&quot;navbar-start&quot;&gt;<br>        &lt;div class=&quot;navbar-brand&quot;&gt;<br>            &lt;a class=&quot;navbar-item&quot; href=&quot;/&quot;&gt;<br>                &lt;img src=&quot;/img/fc_logo_v2.png&quot; alt=&quot;Démonstrateur Fournisseur de Service&quot;  height=&quot;28&quot;&gt;<br>            &lt;/a&gt;<br>        &lt;/div&gt;<br>        &lt;a href=&quot;/&quot; class=&quot;navbar-item&quot;&gt;<br>            Home<br>        &lt;/a&gt;<br>    &lt;/div&gt;<br>    &lt;div class=&quot;navbar-end&quot;&gt;<br>        &lt;div class=&quot;navbar-item&quot;&gt;<br>            <br>                &lt;div class=&quot;buttons&quot;&gt;<br>                    &lt;a class=&quot;button is-light&quot; href=&quot;/login&quot;&gt;Se connecter&lt;/a&gt;<br>                &lt;/div&gt;<br>            <br>        &lt;/div&gt;<br>    &lt;/div&gt;<br>&lt;/nav&gt;<br><br><br>&lt;section class=&quot;hero is-info is-medium&quot;&gt;<br>    &lt;div class=&quot;hero-body&quot;&gt;<br>        &lt;div class=&quot;container&quot;&gt;<br>            &lt;h1 class=&quot;title&quot;&gt;<br>                Bienvenue sur le démonstrateur de fournisseur de service<br>            &lt;/h1&gt;<br>            &lt;h2 class=&quot;subtitle&quot;&gt;<br>                Cliquez sur &quot;se connecter&quot; pour vous connecter via &lt;strong&gt;FranceConnect&lt;/strong&gt;<br>            &lt;/h2&gt;<br>        &lt;/div&gt;<br>    &lt;/div&gt;<br>&lt;/section&gt;</pre><p>Dans cet article, il est décrit la possibilité d’utiliser hashi-up pour provisionner un cluster avec Vault ou en mode HA pour le cluster Nomad et Consul :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/0*uGGpp8Io-iuLF-Xq.png" /></figure><ul><li><a href="https://johansiebens.dev/posts/2020/07/deploying-a-highly-available-nomad-cluster-with-hashi-up/">Deploying a highly-available Nomad cluster with hashi-up!</a></li><li><a href="https://johansiebens.dev/posts/2020/12/installing-hashicorp-vault-on-digitalocean-with-hashi-up/">Installing HashiCorp Vault on DigitalOcean with hashi-up</a></li></ul><blockquote>Ce cluster commun entre Nomad et Consul aurait pû être utilisé avec Waypoint pour y provisionner ses jobs comme avec cet exemple de fichier HCL …</blockquote><p><a href="https://developer.hashicorp.com/waypoint">Waypoint | HashiCorp Developer</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DFD-Qcr6yk8QOzmFsdUFdw.png" /></figure><p><a href="https://developer.hashicorp.com/waypoint/tutorials/get-started-nomad/get-started-nomad">Deploy an Application to Nomad | Waypoint | HashiCorp Developer</a></p><pre># Copyright (c) HashiCorp, Inc.<br># SPDX-License-Identifier: MPL-2.0<br><br>project = &quot;nomad-nodejs&quot;<br><br>app &quot;nomad-nodejs-web&quot; {<br><br>  build {<br>    use &quot;pack&quot; {}<br>    registry {<br>      use &quot;docker&quot; {<br>        image = &quot;nomad-nodejs-web&quot;<br>        tag   = &quot;1&quot;<br>        local = true<br>      }<br>    }<br>  }<br><br>  deploy {<br>    use &quot;nomad&quot; {<br>      // these options both default to the values shown, but are left here to<br>      // show they are configurable<br>      datacenter = &quot;dc1&quot;<br>      namespace  = &quot;default&quot;<br>    }<br>  }<br><br>}</pre><p>On en allant beaucoup plus loin avec cet exemple de déploiement Blue/Green …</p><ul><li><a href="https://www.redhat.com/en/topics/devops/what-is-blue-green-deployment">What is blue green deployment?</a></li><li><a href="https://www.infralovers.com/en/articles/2022/10/05/bluegreen-deployments-with-nomad-and-waypoint/">Blue/Green Deployments with HashiCorp Nomad and Waypoint</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YsnvV7z3Js-4uZOT-0S7bg.png" /><figcaption><a href="https://t.ly/DCtM">https://t.ly/DCtM</a></figcaption></figure><p>À suivre !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76c75f27f84c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Effectuer des opérations de base autour des machines virtuelles avec kubevirt-manager …]]></title>
            <link>https://deep75.medium.com/effectuer-des-op%C3%A9rations-de-base-autour-des-machines-virtuelles-avec-kubevirt-manager-d403226f1265?source=rss-9f1ca3c659fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/d403226f1265</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[virtualisation]]></category>
            <category><![CDATA[kubevirt]]></category>
            <dc:creator><![CDATA[Karim]]></dc:creator>
            <pubDate>Thu, 09 Mar 2023 14:35:11 GMT</pubDate>
            <atom:updated>2023-03-09T15:02:36.611Z</atom:updated>
            <content:encoded><![CDATA[<h3>Effectuer des opérations de base autour des machines virtuelles avec KubeVirt Manager …</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*K3Zu0cib5b0B9D2j.png" /></figure><p>Kubevirt permet comme on l’a vu dans plusieurs articles précedemment de fournir une plateforme de développement unifiée où les développeurs peuvent construire, modifier et déployer des applications résidant à la fois dans des conteneurs d’application et dans des machines virtuelles dans un environnement commun et partagé.</p><ul><li><a href="https://kubevirt.io/">KubeVirt.io</a></li><li><a href="https://deep75.medium.com/deployer-kubevirt-en-utilisant-hyperconverged-cluster-operator-hco-et-g%C3%A9rer-ses-vms-dans-8fcb128be39d">Deployer KubeVirt en utilisant Hyperconverged Cluster Operator (HCO) et gérer ses VMs dans…</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*vFvPPdQjh-kabZDM.png" /><figcaption><a href="https://kubevirt.io/2020/KubeVirt_deep_dive-virtualized_gpu_workloads.html">https://kubevirt.io/2020/KubeVirt_deep_dive-virtualized_gpu_workloads.html</a></figcaption></figure><p>Même si d’autres solutions alternatives de création et d’utilisations de machines virtuelles existent pour Kubernetes :</p><ul><li><a href="https://deep75.medium.com/neonvm-api-de-virtualisation-l%C3%A9g%C3%A8re-bas%C3%A9e-sur-qemu-pour-kubernetes-ca72a44dd97">NeonVM : API de virtualisation légère basée sur QEMU pour Kubernetes …</a></li><li><a href="https://deep75.medium.com/kubefire-cr%C3%A9er-et-g%C3%A8rer-des-clusters-kubernetes-en-utilisant-des-microvms-avec-firecracker-818a7a45c664">KubeFire : Créer et gèrer des clusters Kubernetes en utilisant des microVMs avec Firecracker …</a></li><li><a href="https://deep75.medium.com/virtink-un-module-compl%C3%A9mentaire-de-virtualisation-l%C3%A9g%C3%A8re-pour-kubernetes-4287edb7e1d0">Virtink : un module complémentaire de virtualisation légère pour Kubernetes …</a></li></ul><blockquote>Une solution existait pour gérer ses machines virtuelles graphiquement dans Kubernetes et KubeVirt avec OpenShift Web Console :</blockquote><ul><li><a href="https://kubevirt.io/2020/OKD-web-console-install.html">Managing KubeVirt with OpenShift Web Console | KubeVirt.io</a></li><li><a href="https://docs.okd.io/latest/virt/virtual_machines/virt-accessing-vm-consoles.html">Accessing virtual machine consoles - Virtual machines | Virtualization | OKD 4</a></li><li><a href="https://deep75.medium.com/aper%C3%A7u-de-microshift-une-impl%C3%A9mentation-l%C3%A9g%C3%A8re-dopenshift-e60b725849ce">Aperçu de Microshift, une implémentation légère d’OpenShift …</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*8hmr_O55uoiBH_Pj.jpg" /></figure><p>Ici focus sur KubeVirt Manager, un projet récent qui fournit un Frontend Angular simple pour faire fonctionner KubeVirt.</p><blockquote>Cet outil vous permet d’effectuer des opérations de base autour des machines virtuelles, des instances de machines virtuelles et des disques :</blockquote><p><a href="https://github.com/kubevirt-manager/kubevirt-manager">GitHub - kubevirt-manager/kubevirt-manager: Kubevirt Web UI / Web Interface Manager</a></p><p>Application rapide avec le déploiement d’un cluster AKS dans Azure avec un Scale Set utilisant des instances Spot et ces paramètres :</p><ul><li><a href="https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/deploy-cli">Azure deployment templates with Azure CLI - Azure Resource Manager - Azure Resource Manager</a></li><li><a href="https://learn.microsoft.com/en-us/azure/aks/spot-node-pool">Add an Azure Spot node pool to an Azure Kubernetes Service (AKS) cluster - Azure Kubernetes Service</a></li></ul><pre>{<br>    &quot;$schema&quot;: &quot;https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#&quot;,<br>    &quot;contentVersion&quot;: &quot;1.0.0.0&quot;,<br>    &quot;parameters&quot;: {<br>        &quot;resourceName&quot;: {<br>            &quot;value&quot;: &quot;AKS&quot;<br>        },<br>        &quot;location&quot;: {<br>            &quot;value&quot;: &quot;francecentral&quot;<br>        },<br>        &quot;dnsPrefix&quot;: {<br>            &quot;value&quot;: &quot;AKS-dns&quot;<br>        },<br>        &quot;kubernetesVersion&quot;: {<br>            &quot;value&quot;: &quot;1.26.0&quot;<br>        },<br>        &quot;networkPlugin&quot;: {<br>            &quot;value&quot;: &quot;kubenet&quot;<br>        },<br>        &quot;enableRBAC&quot;: {<br>            &quot;value&quot;: true<br>        },<br>        &quot;nodeResourceGroup&quot;: {<br>            &quot;value&quot;: &quot;MC_RG-AKS_AKS_francecentral&quot;<br>        },<br>        &quot;upgradeChannel&quot;: {<br>            &quot;value&quot;: &quot;none&quot;<br>        },<br>        &quot;adminGroupObjectIDs&quot;: {<br>            &quot;value&quot;: []<br>        },<br>        &quot;disableLocalAccounts&quot;: {<br>            &quot;value&quot;: false<br>        },<br>        &quot;azureRbac&quot;: {<br>            &quot;value&quot;: false<br>        },<br>        &quot;enablePrivateCluster&quot;: {<br>            &quot;value&quot;: false<br>        },<br>        &quot;enableHttpApplicationRouting&quot;: {<br>            &quot;value&quot;: false<br>        },<br>        &quot;enableAzurePolicy&quot;: {<br>            &quot;value&quot;: false<br>        },<br>        &quot;enableSecretStoreCSIDriver&quot;: {<br>            &quot;value&quot;: false<br>        },<br>        &quot;vmssNodePool&quot;: {<br>            &quot;value&quot;: true<br>        }<br>    }<br>}</pre><p><a href="https://deep75.medium.com/mise-en-oeuvre-dun-cluster-kubernetes-1-14-avec-des-noeuds-windows-via-aks-engine-8c7400a7037c">Mise en oeuvre d’un cluster Kubernetes 1.14 avec des noeuds Windows via AKS-Engine …</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pshgUiqxLac4_mO8Az4yBg.png" /></figure><p>Le cluster AKS est déployé avec récupération des identifiants :</p><pre>$ az aks get-credentials --resource-group RG-AKS --name AKS<br>Merged &quot;AKS&quot; as current context in /home/cert/.kube/config<br><br>$ kubectl cluster-info<br>Kubernetes control plane is running at https://aks-dns-bn9a54nt.hcp.francecentral.azmk8s.io:443<br>CoreDNS is running at https://aks-dns-bn9a54nt.hcp.francecentral.azmk8s.io:443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy<br>Metrics-server is running at https://aks-dns-bn9a54nt.hcp.francecentral.azmk8s.io:443/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy<br><br>To further debug and diagnose cluster problems, use &#39;kubectl cluster-info dump&#39;.<br><br>$ kubectl get po,svc -A<br>NAMESPACE     NAME                                      READY   STATUS    RESTARTS   AGE<br>kube-system   pod/azure-ip-masq-agent-6g72l             1/1     Running   0          6m18s<br>kube-system   pod/azure-ip-masq-agent-nzbf5             1/1     Running   0          6m20s<br>kube-system   pod/azure-ip-masq-agent-rj6mj             1/1     Running   0          6m6s<br>kube-system   pod/cloud-node-manager-rfpcf              1/1     Running   0          6m18s<br>kube-system   pod/cloud-node-manager-rg5jm              1/1     Running   0          6m6s<br>kube-system   pod/cloud-node-manager-zpsgs              1/1     Running   0          6m20s<br>kube-system   pod/coredns-78669d9946-txcm8              1/1     Running   0          4m26s<br>kube-system   pod/coredns-78669d9946-zt9b5              1/1     Running   0          6m30s<br>kube-system   pod/coredns-autoscaler-5b5c4f5b4f-zl2hq   1/1     Running   0          6m30s<br>kube-system   pod/csi-azuredisk-node-44ffr              3/3     Running   0          6m20s<br>kube-system   pod/csi-azuredisk-node-m2s5r              3/3     Running   0          6m18s<br>kube-system   pod/csi-azuredisk-node-v4dc8              3/3     Running   0          6m6s<br>kube-system   pod/csi-azurefile-node-5pzl4              3/3     Running   0          6m18s<br>kube-system   pod/csi-azurefile-node-mqxw4              3/3     Running   0          6m6s<br>kube-system   pod/csi-azurefile-node-nfvct              3/3     Running   0          6m20s<br>kube-system   pod/konnectivity-agent-f94c65c6f-bjcwq    1/1     Running   0          6m29s<br>kube-system   pod/konnectivity-agent-f94c65c6f-rdbfl    1/1     Running   0          6m29s<br>kube-system   pod/kube-proxy-52svq                      1/1     Running   0          6m18s<br>kube-system   pod/kube-proxy-cnplk                      1/1     Running   0          6m6s<br>kube-system   pod/kube-proxy-dnjjp                      1/1     Running   0          6m20s<br>kube-system   pod/metrics-server-5f6654d4df-nqj2w       2/2     Running   0          4m20s<br>kube-system   pod/metrics-server-5f6654d4df-qk22x       2/2     Running   0          4m20s<br><br>NAMESPACE     NAME                     TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)         AGE<br>default       service/kubernetes       ClusterIP   10.0.0.1       &lt;none&gt;        443/TCP         7m4s<br>kube-system   service/kube-dns         ClusterIP   10.0.0.10      &lt;none&gt;        53/UDP,53/TCP   6m31s<br>kube-system   service/metrics-server   ClusterIP   10.0.139.110   &lt;none&gt;        443/TCP         6m30s<br><br>$ kubectl get nodes -o wide<br>NAME                                STATUS   ROLES   AGE     VERSION   INTERNAL-IP   EXTERNAL-IP     OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME<br>aks-agentpool-16963728-vmss000000   Ready    agent   6m15s   v1.26.0   10.224.0.5    &lt;none&gt;          Ubuntu 22.04.1 LTS   5.15.0-1033-azure   containerd://1.6.17+azure-1<br>aks-userpool-16963728-vmss000000    Ready    agent   6m27s   v1.26.0   10.224.0.4    20.111.27.134   Ubuntu 22.04.1 LTS   5.15.0-1033-azure   containerd://1.6.17+azure-1<br>aks-userpool-16963728-vmss000001    Ready    agent   6m29s   v1.26.0   10.224.0.6    20.111.27.202   Ubuntu 22.04.1 LTS   5.15.0-1033-azure   containerd://1.6.17+azure-1</pre><p>J’utilise ici un pool de Noeud Spot avec des instances Esv5 qui autorise la virtualisation imbriquée pour cette expérience :</p><p><a href="https://learn.microsoft.com/en-us/azure/virtual-machines/ev5-esv5-series">Ev5 and Esv5-series - Azure Virtual Machines</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*vc3ahIgRfWN5axw_YH3NEA.png" /></figure><p>Ce qui permet le déploiement de KubeVirt via HCO (Hyperconverged Cluster Operator) :</p><p><a href="https://github.com/kubevirt/hyperconverged-cluster-operator">GitHub - kubevirt/hyperconverged-cluster-operator: Operator pattern for managing multi-operator products</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/0*7xvtc18DqlXZFKKM.jpg" /></figure><p>avec ce script unifié :</p><pre>curl https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/main/deploy/deploy.sh | bash</pre><pre>$ curl https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/main/deploy/deploy.sh | bash<br><br>+ hco_namespace=kubevirt-hyperconverged<br>+ IS_OPENSHIFT=false<br>+ kubectl api-resources<br>+ grep clusterversions<br>+ grep config.openshift.io<br>+ kubectl create ns kubevirt-hyperconverged --dry-run=true -o yaml<br>+ kubectl apply -f -<br>W0309 13:38:03.250568    3638 helpers.go:677] --dry-run=true is deprecated (boolean value) and can be replaced with --dry-run=client.<br>namespace/kubevirt-hyperconverged created<br>+ namespaces=(&quot;openshift&quot;)<br>+ for namespace in ${namespaces[@]}<br>++ kubectl get ns openshift<br>Error from server (NotFound): namespaces &quot;openshift&quot; not found<br>+ [[ &#39;&#39; == &#39;&#39; ]]<br>+ kubectl create ns openshift --dry-run=true -o yaml<br>+ kubectl apply -f -<br>W0309 13:38:04.072929    3667 helpers.go:677] --dry-run=true is deprecated (boolean value) and can be replaced with --dry-run=client.<br>namespace/openshift created<br>+ LABEL_SELECTOR_ARG=<br>+ &#39;[&#39; false &#39;!=&#39; true &#39;]&#39;<br>+ LABEL_SELECTOR_ARG=&#39;-l name!=ssp-operator,name!=hyperconverged-cluster-cli-download&#39;<br>+ kubectl apply -l &#39;name!=ssp-operator,name!=hyperconverged-cluster-cli-download&#39; -f https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/main/deploy/crds/cluster-network-addons00.crd.yaml<br>customresourcedefinition.apiextensions.k8s.io/networkaddonsconfigs.networkaddonsoperator.network.kubevirt.io created<br>+ kubectl apply -l &#39;name!=ssp-operator,name!=hyperconverged-cluster-cli-download&#39; -f https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/main/deploy/crds/containerized-data-importer00.crd.yaml<br>customresourcedefinition.apiextensions.k8s.io/cdis.cdi.kubevirt.io created<br>+ kubectl apply -l &#39;name!=ssp-operator,name!=hyperconverged-cluster-cli-download&#39; -f https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/main/deploy/crds/hco00.crd.yaml<br>customresourcedefinition.apiextensions.k8s.io/hyperconvergeds.hco.kubevirt.io created<br>+ kubectl apply -l &#39;name!=ssp-operator,name!=hyperconverged-cluster-cli-download&#39; -f https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/main/deploy/crds/kubevirt00.crd.yaml<br>customresourcedefinition.apiextensions.k8s.io/kubevirts.kubevirt.io created<br>+ kubectl apply -l &#39;name!=ssp-operator,name!=hyperconverged-cluster-cli-download&#39; -f https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/main/deploy/crds/hostpath-provisioner00.crd.yaml<br>customresourcedefinition.apiextensions.k8s.io/hostpathprovisioners.hostpathprovisioner.kubevirt.io created<br>+ kubectl apply -l &#39;name!=ssp-operator,name!=hyperconverged-cluster-cli-download&#39; -f https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/main/deploy/crds/scheduling-scale-performance00.crd.yaml<br>customresourcedefinition.apiextensions.k8s.io/ssps.ssp.kubevirt.io created<br>+ kubectl apply -l &#39;name!=ssp-operator,name!=hyperconverged-cluster-cli-download&#39; -f https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/main/deploy/crds/tekton-tasks-operator00.crd.yaml<br>customresourcedefinition.apiextensions.k8s.io/tektontasks.tektontasks.kubevirt.io created<br>+ kubectl apply -l &#39;name!=ssp-operator,name!=hyperconverged-cluster-cli-download&#39; -f https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/main/deploy/cert-manager.yaml<br>customresourcedefinition.apiextensions.k8s.io/certificaterequests.cert-manager.io created<br>customresourcedefinition.apiextensions.k8s.io/certificates.cert-manager.io created<br>customresourcedefinition.apiextensions.k8s.io/challenges.acme.cert-manager.io created<br>customresourcedefinition.apiextensions.k8s.io/clusterissuers.cert-manager.io created<br>customresourcedefinition.apiextensions.k8s.io/issuers.cert-manager.io created<br>customresourcedefinition.apiextensions.k8s.io/orders.acme.cert-manager.io created<br>namespace/cert-manager created<br>serviceaccount/cert-manager-cainjector created<br>serviceaccount/cert-manager created<br>serviceaccount/cert-manager-webhook created<br>clusterrole.rbac.authorization.k8s.io/cert-manager-cainjector created<br>clusterrole.rbac.authorization.k8s.io/cert-manager-controller-issuers created<br>clusterrole.rbac.authorization.k8s.io/cert-manager-controller-clusterissuers created<br>clusterrole.rbac.authorization.k8s.io/cert-manager-controller-certificates created<br>clusterrole.rbac.authorization.k8s.io/cert-manager-controller-orders created<br>clusterrole.rbac.authorization.k8s.io/cert-manager-controller-challenges created<br>clusterrole.rbac.authorization.k8s.io/cert-manager-controller-ingress-shim created<br>clusterrole.rbac.authorization.k8s.io/cert-manager-view created<br>clusterrole.rbac.authorization.k8s.io/cert-manager-edit created<br>clusterrole.rbac.authorization.k8s.io/cert-manager-controller-approve:cert-manager-io created<br>clusterrole.rbac.authorization.k8s.io/cert-manager-controller-certificatesigningrequests created<br>clusterrole.rbac.authorization.k8s.io/cert-manager-webhook:subjectaccessreviews created<br>clusterrolebinding.rbac.authorization.k8s.io/cert-manager-cainjector created<br>clusterrolebinding.rbac.authorization.k8s.io/cert-manager-controller-issuers created<br>clusterrolebinding.rbac.authorization.k8s.io/cert-manager-controller-clusterissuers created<br>clusterrolebinding.rbac.authorization.k8s.io/cert-manager-controller-certificates created<br>clusterrolebinding.rbac.authorization.k8s.io/cert-manager-controller-orders created<br>clusterrolebinding.rbac.authorization.k8s.io/cert-manager-controller-challenges created<br>clusterrolebinding.rbac.authorization.k8s.io/cert-manager-controller-ingress-shim created<br>clusterrolebinding.rbac.authorization.k8s.io/cert-manager-controller-approve:cert-manager-io created<br>clusterrolebinding.rbac.authorization.k8s.io/cert-manager-controller-certificatesigningrequests created<br>clusterrolebinding.rbac.authorization.k8s.io/cert-manager-webhook:subjectaccessreviews created<br>role.rbac.authorization.k8s.io/cert-manager-cainjector:leaderelection created<br>role.rbac.authorization.k8s.io/cert-manager:leaderelection created<br>role.rbac.authorization.k8s.io/cert-manager-webhook:dynamic-serving created<br>rolebinding.rbac.authorization.k8s.io/cert-manager-cainjector:leaderelection created<br>rolebinding.rbac.authorization.k8s.io/cert-manager:leaderelection created<br>rolebinding.rbac.authorization.k8s.io/cert-manager-webhook:dynamic-serving created<br>service/cert-manager created<br>service/cert-manager-webhook created<br>deployment.apps/cert-manager-cainjector created<br>deployment.apps/cert-manager created<br>deployment.apps/cert-manager-webhook created<br>mutatingwebhookconfiguration.admissionregistration.k8s.io/cert-manager-webhook created<br>validatingwebhookconfiguration.admissionregistration.k8s.io/cert-manager-webhook created<br>+ kubectl -n cert-manager wait deployment/cert-manager --for=condition=Available --timeout=300s<br>deployment.apps/cert-manager condition met<br>+ kubectl -n cert-manager wait deployment/cert-manager-webhook --for=condition=Available --timeout=300s<br>deployment.apps/cert-manager-webhook condition met<br>+ kubectl apply -l &#39;name!=ssp-operator,name!=hyperconverged-cluster-cli-download&#39; -n kubevirt-hyperconverged -f https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/main/deploy/cluster_role.yaml<br>role.rbac.authorization.k8s.io/cluster-network-addons-operator created<br>role.rbac.authorization.k8s.io/kubevirt-operator created<br>role.rbac.authorization.k8s.io/tekton-tasks-operator created<br>role.rbac.authorization.k8s.io/cdi-operator created<br>role.rbac.authorization.k8s.io/hostpath-provisioner-operator created<br>clusterrole.rbac.authorization.k8s.io/hyperconverged-cluster-operator created<br>clusterrole.rbac.authorization.k8s.io/cluster-network-addons-operator created<br>clusterrole.rbac.authorization.k8s.io/kubevirt-operator created<br>clusterrole.rbac.authorization.k8s.io/tekton-tasks-operator created<br>clusterrole.rbac.authorization.k8s.io/cdi-operator created<br>clusterrole.rbac.authorization.k8s.io/hostpath-provisioner-operator created<br>+ kubectl apply -l &#39;name!=ssp-operator,name!=hyperconverged-cluster-cli-download&#39; -n kubevirt-hyperconverged -f https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/main/deploy/service_account.yaml<br>serviceaccount/cdi-operator created<br>serviceaccount/cluster-network-addons-operator created<br>serviceaccount/hostpath-provisioner-operator created<br>serviceaccount/hyperconverged-cluster-operator created<br>serviceaccount/kubevirt-operator created<br>serviceaccount/tekton-tasks-operator created<br>+ kubectl apply -l &#39;name!=ssp-operator,name!=hyperconverged-cluster-cli-download&#39; -n kubevirt-hyperconverged -f https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/main/deploy/cluster_role_binding.yaml<br>rolebinding.rbac.authorization.k8s.io/cluster-network-addons-operator created<br>rolebinding.rbac.authorization.k8s.io/kubevirt-operator created<br>rolebinding.rbac.authorization.k8s.io/tekton-tasks-operator created<br>rolebinding.rbac.authorization.k8s.io/cdi-operator created<br>rolebinding.rbac.authorization.k8s.io/hostpath-provisioner-operator created<br>clusterrolebinding.rbac.authorization.k8s.io/hyperconverged-cluster-operator created<br>clusterrolebinding.rbac.authorization.k8s.io/cluster-network-addons-operator created<br>clusterrolebinding.rbac.authorization.k8s.io/kubevirt-operator created<br>clusterrolebinding.rbac.authorization.k8s.io/tekton-tasks-operator created<br>clusterrolebinding.rbac.authorization.k8s.io/cdi-operator created<br>clusterrolebinding.rbac.authorization.k8s.io/hostpath-provisioner-operator created<br>+ kubectl apply -l &#39;name!=ssp-operator,name!=hyperconverged-cluster-cli-download&#39; -n kubevirt-hyperconverged -f https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/main/deploy/webhooks.yaml<br>issuer.cert-manager.io/selfsigned created<br>certificate.cert-manager.io/hyperconverged-cluster-webhook-service-cert created<br>validatingwebhookconfiguration.admissionregistration.k8s.io/validate-hco.kubevirt.io created<br>certificate.cert-manager.io/node-maintenance-operator-service-cert created<br>validatingwebhookconfiguration.admissionregistration.k8s.io/nodemaintenance-validation.kubevirt.io created<br>certificate.cert-manager.io/hostpath-provisioner-operator-webhook-service-cert created<br>validatingwebhookconfiguration.admissionregistration.k8s.io/hostpathprovisioner.kubevirt.io created<br>mutatingwebhookconfiguration.admissionregistration.k8s.io/mutate-hco.kubevirt.io created<br>+ kubectl apply -l &#39;name!=ssp-operator,name!=hyperconverged-cluster-cli-download&#39; -n kubevirt-hyperconverged -f https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/main/deploy/operator.yaml<br>deployment.apps/hyperconverged-cluster-operator created<br>deployment.apps/hyperconverged-cluster-webhook created<br>deployment.apps/cluster-network-addons-operator created<br>deployment.apps/virt-operator created<br>deployment.apps/tekton-tasks-operator created<br>deployment.apps/cdi-operator created<br>deployment.apps/hostpath-provisioner-operator created<br>service/hyperconverged-cluster-webhook-service created<br>service/hostpath-provisioner-operator-service created<br>+ kubectl -n kubevirt-hyperconverged wait deployment/hyperconverged-cluster-webhook --for=condition=Available --timeout=300s<br>deployment.apps/hyperconverged-cluster-webhook condition met<br>+ kubectl apply -l &#39;name!=ssp-operator,name!=hyperconverged-cluster-cli-download&#39; -n kubevirt-hyperconverged -f https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/main/deploy/hco.cr.yaml<br><br>hyperconverged.hco.kubevirt.io/kubevirt-hyperconverged created</pre><p>KubeVirt est alors déployé dans ce cluster :</p><pre>$ kubectl get po,svc -n kubevirt-hyperconverged<br><br>NAME                                                      READY   STATUS    RESTARTS   AGE<br>pod/bridge-marker-n7dgz                                   1/1     Running   0          3m14s<br>pod/bridge-marker-qld66                                   1/1     Running   0          3m14s<br>pod/bridge-marker-w9rjv                                   1/1     Running   0          3m14s<br>pod/cdi-apiserver-5b79dbb75c-2wjgl                        1/1     Running   0          2m41s<br>pod/cdi-deployment-68787cb469-l5cpl                       1/1     Running   0          2m37s<br>pod/cdi-operator-b5fc58cd7-b9f2s                          1/1     Running   0          3m24s<br>pod/cdi-uploadproxy-56d645d8d5-trt54                      1/1     Running   0          2m46s<br>pod/cluster-network-addons-operator-6f6765958d-rn2fn      2/2     Running   0          3m35s<br>pod/hostpath-provisioner-operator-7bb46fd5b7-cg2hb        1/1     Running   0          3m24s<br>pod/hyperconverged-cluster-operator-7df6b469b4-942tx      1/1     Running   0          3m35s<br>pod/hyperconverged-cluster-webhook-55cfd6cb69-46r8v       1/1     Running   0          3m35s<br>pod/kube-cni-linux-bridge-plugin-62jrn                    1/1     Running   0          3m14s<br>pod/kube-cni-linux-bridge-plugin-hqpsg                    1/1     Running   0          3m14s<br>pod/kube-cni-linux-bridge-plugin-nzkpp                    1/1     Running   0          3m14s<br>pod/kubemacpool-cert-manager-6dfd4bb587-b29pl             1/1     Running   0          3m14s<br>pod/kubemacpool-mac-controller-manager-646dd6f884-gxttc   2/2     Running   0          3m14s<br>pod/multus-ggncz                                          1/1     Running   0          3m15s<br>pod/multus-m2xjm                                          1/1     Running   0          3m15s<br>pod/multus-zjm8n                                          1/1     Running   0          3m15s<br>pod/tekton-tasks-operator-7d98668446-prr4b                1/1     Running   0          3m35s<br>pod/virt-api-94f856488-k7fcb                              1/1     Running   0          2m20s<br>pod/virt-controller-7bd9bdbccc-rn762                      1/1     Running   0          107s<br>pod/virt-exportproxy-5c8d7c5668-mwfnz                     1/1     Running   0          107s<br>pod/virt-handler-mzjv5                                    1/1     Running   0          107s<br>pod/virt-operator-6797b9bb9c-5jqj8                        1/1     Running   0          3m24s<br>pod/virt-operator-6797b9bb9c-rrm4n                        1/1     Running   0          3m24s<br><br>NAME                                             TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE<br>service/cdi-api                                  ClusterIP   10.0.59.53     &lt;none&gt;        443/TCP    2m41s<br>service/cdi-prometheus-metrics                   ClusterIP   10.0.220.94    &lt;none&gt;        8080/TCP   2m37s<br>service/cdi-uploadproxy                          ClusterIP   10.0.37.12     &lt;none&gt;        443/TCP    2m46s<br>service/hostpath-provisioner-operator-service    ClusterIP   10.0.118.100   &lt;none&gt;        9443/TCP   3m35s<br>service/hyperconverged-cluster-webhook-service   ClusterIP   10.0.122.49    &lt;none&gt;        4343/TCP   3m35s<br>service/kubemacpool-service                      ClusterIP   10.0.96.143    &lt;none&gt;        443/TCP    3m14s<br>service/kubevirt-operator-webhook                ClusterIP   10.0.145.178   &lt;none&gt;        443/TCP    2m22s<br>service/kubevirt-prometheus-metrics              ClusterIP   None           &lt;none&gt;        443/TCP    2m22s<br>service/virt-api                                 ClusterIP   10.0.230.208   &lt;none&gt;        443/TCP    2m22s<br>service/virt-exportproxy                         ClusterIP   10.0.218.176   &lt;none&gt;        443/TCP    2m22s</pre><p>KubeVirt Manager est mise en oeuvre via les manifests YAML fournis dans son dépôt GitHub :</p><pre>$ git clone https://github.com/kubevirt-manager/kubevirt-manager<br>Cloning into &#39;kubevirt-manager&#39;...<br>remote: Enumerating objects: 4464, done.<br>remote: Counting objects: 100% (1287/1287), done.<br>remote: Compressing objects: 100% (446/446), done.<br>remote: Total 4464 (delta 838), reused 1191 (delta 815), pack-reused 3177<br>Receiving objects: 100% (4464/4464), 67.53 MiB | 3.41 MiB/s, done.<br>Resolving deltas: 100% (1461/1461), done.</pre><pre>~/kubevirt-manager$ kubectl apply -f kubernetes/ns.yaml<br>namespace/kubevirt-manager created<br><br>~/kubevirt-manager$ cat kubernetes/ns.yaml <br><br>apiVersion: v1<br>kind: Namespace<br>metadata:<br>  name: kubevirt-manager<br>  labels:<br>    app: kubevirt-manager<br>    kubevirt-manager.io/version: 1.2.0</pre><pre>~/kubevirt-manager$ kubectl apply -f kubernetes/rbac.yaml<br><br>serviceaccount/kubevirt-manager created<br>clusterrole.rbac.authorization.k8s.io/kubevirt-manager created<br>clusterrolebinding.rbac.authorization.k8s.io/kubevirt-manager created</pre><pre>~/kubevirt-manager$ kubectl apply -f kubernetes/deployment.yaml<br>deployment.apps/kubevirt-manager created</pre><pre>~/kubevirt-manager$ kubectl apply -f kubernetes/pc.yaml<br>priorityclass.scheduling.k8s.io/vm-standard created<br>priorityclass.scheduling.k8s.io/vm-preemptible created<br><br>~/kubevirt-manager$ kubectl apply -f kubernetes/service.yaml<br>service/kubevirt-manager created</pre><p>KubeVirt Manager est déployé et je change en éditant le service d’exposition de ClusterIP à Load Balancer pour obtenir une exposition en HTTP :</p><p><a href="https://kubernetes.io/docs/concepts/services-networking/">Services, Load Balancing, and Networking</a></p><pre>$ kubectl get po,svc -n kubevirt-manager<br>NAME                                    READY   STATUS    RESTARTS   AGE<br>pod/kubevirt-manager-5858499887-wfrgn   1/1     Running   0          95s<br><br>NAME                       TYPE        CLUSTER-IP    EXTERNAL-IP   PORT(S)    AGE<br>service/kubevirt-manager   ClusterIP   10.0.173.82   &lt;none&gt;        8080/TCP   63s<br><br>$ kubectl edit -n kubevirt-manager service/kubevirt-manager<br>service/kubevirt-manager edited<br><br>$ kubectl get po,svc -n kubevirt-manager<br>NAME                                    READY   STATUS    RESTARTS   AGE<br>pod/kubevirt-manager-5858499887-wfrgn   1/1     Running   0          4m56s<br><br>NAME                       TYPE           CLUSTER-IP    EXTERNAL-IP    PORT(S)          AGE<br>service/kubevirt-manager   LoadBalancer   10.0.173.82   20.74.99.190   8080:30143/TCP   4m24s</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rvtP2hJjeECi_uXc1VLMYg.png" /></figure><p>Et j’y accède via l’adresse IP publique fournie dans AKS :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XRl9eCZyS-rxOlWypQtaig.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9n6cTGqnMpBkpeFGWSAXTw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KVDlUPqN_kYfRGl0f5cg6Q.png" /></figure><p>Krew est installé localement via Kubectl ainsi que le plugin correspondant pour Kubevirt :</p><p><a href="https://krew.sigs.k8s.io/docs/user-guide/quickstart/">Quickstart</a></p><pre>$ kubectl krew update<br>Updated the local copy of plugin index.<br><br>$ kubectl krew search virt<br>NAME                            DESCRIPTION                                         INSTALLED<br>pv-migrate                      Migrate data across persistent volumes              no<br>pvmigrate                       Migrates PVs between StorageClasses                 no<br>view-cert                       View certificate information stored in secrets      no<br>view-secret                     Decode Kubernetes secrets                           no<br>view-serviceaccount-kubeconfig  Show a kubeconfig setting to access the apiserv...  no<br>virt                            Control KubeVirt virtual machines using virtctl     yes</pre><p>Ce qui permet de lancer directement une petite machine virtuelle avec Cirros :</p><p><a href="https://github.com/cirros-dev/cirros">GitHub - cirros-dev/cirros</a></p><pre>$ kubectl apply -f https://raw.githubusercontent.com/kubevirt/demo/master/manifests/vm.yaml<br>virtualmachine.kubevirt.io/testvm created<br><br>$ cat vm.yaml<br><br>apiVersion: kubevirt.io/v1alpha3<br>kind: VirtualMachine<br>metadata:<br>  name: testvm<br>spec:<br>  running: false<br>  template:<br>    metadata:<br>      labels: <br>        kubevirt.io/size: small<br>        kubevirt.io/domain: testvm<br>    spec:<br>      domain:<br>        devices:<br>          disks:<br>          - disk:<br>              bus: virtio<br>            name: rootfs<br>          - disk:<br>              bus: virtio<br>            name: cloudinit<br>          interfaces:<br>          - name: default<br>            masquerade: {}<br>        resources:<br>          requests:<br>            memory: 64M<br>      networks:<br>      - name: default<br>        pod: {}<br>      volumes:<br>        - name: rootfs<br>          containerDisk:<br>            image: kubevirt/cirros-registry-disk-demo<br>        - name: cloudinit<br>          cloudInitNoCloud:<br>            userDataBase64: SGkuXG4= <br><br>$ kubectl describe vm testvm<br>Name:         testvm<br>Namespace:    default<br>Labels:       &lt;none&gt;<br>Annotations:  kubevirt.io/latest-observed-api-version: v1<br>              kubevirt.io/storage-observed-api-version: v1alpha3<br>API Version:  kubevirt.io/v1<br>Kind:         VirtualMachine<br>Metadata:<br>  Creation Timestamp:  2023-03-09T13:23:32Z<br>  Finalizers:<br>    kubevirt.io/virtualMachineControllerFinalize<br>  Generation:  1<br>  Managed Fields:<br>    API Version:  kubevirt.io/v1alpha3<br>    Fields Type:  FieldsV1<br>    fieldsV1:<br>      f:metadata:<br>        f:annotations:<br>          f:kubevirt.io/latest-observed-api-version:<br>          f:kubevirt.io/storage-observed-api-version:<br>        f:finalizers:<br>          .:<br>          v:&quot;kubevirt.io/virtualMachineControllerFinalize&quot;:<br>    Manager:      Go-http-client<br>    Operation:    Update<br>    Time:         2023-03-09T13:23:32Z<br>    API Version:  kubevirt.io/v1alpha3<br>    Fields Type:  FieldsV1<br>    fieldsV1:<br>      f:status:<br>        .:<br>        f:conditions:<br>        f:printableStatus:<br>        f:volumeSnapshotStatuses:<br>    Manager:      Go-http-client<br>    Operation:    Update<br>    Subresource:  status<br>    Time:         2023-03-09T13:23:32Z<br>    API Version:  kubevirt.io/v1alpha3<br>    Fields Type:  FieldsV1<br>    fieldsV1:<br>      f:metadata:<br>        f:annotations:<br>          .:<br>          f:kubectl.kubernetes.io/last-applied-configuration:<br>      f:spec:<br>        .:<br>        f:running:<br>        f:template:<br>          .:<br>          f:metadata:<br>            .:<br>            f:labels:<br>              .:<br>              f:kubevirt.io/domain:<br>              f:kubevirt.io/size:<br>          f:spec:<br>            .:<br>            f:domain:<br>              .:<br>              f:devices:<br>                .:<br>                f:disks:<br>                f:interfaces:<br>              f:resources:<br>                .:<br>                f:requests:<br>                  .:<br>                  f:memory:<br>            f:networks:<br>            f:volumes:<br>    Manager:         kubectl-client-side-apply<br>    Operation:       Update<br>    Time:            2023-03-09T13:23:32Z<br>  Resource Version:  39937<br>  UID:               01de5614-922a-4ae8-9bec-40eeb9a7c500<br>Spec:<br>  Running:  false<br>  Template:<br>    Metadata:<br>      Creation Timestamp:  &lt;nil&gt;<br>      Labels:<br>        kubevirt.io/domain:  testvm<br>        kubevirt.io/size:    small<br>    Spec:<br>      Domain:<br>        Devices:<br>          Disks:<br>            Disk:<br>              Bus:  virtio<br>            Name:   rootfs<br>            Disk:<br>              Bus:  virtio<br>            Name:   cloudinit<br>          Interfaces:<br>            Mac Address:  02:9d:e4:00:00:00<br>            Masquerade:<br>            Name:  default<br>        Machine:<br>          Type:  q35<br>        Resources:<br>          Requests:<br>            Memory:  64M<br>      Networks:<br>        Name:  default<br>        Pod:<br>      Volumes:<br>        Container Disk:<br>          Image:  kubevirt/cirros-registry-disk-demo<br>        Name:     rootfs<br>        Cloud Init No Cloud:<br>          userDataBase64:  SGkuXG4=<br>        Name:              cloudinit<br>Status:<br>  Conditions:<br>    Last Probe Time:       2023-03-09T13:23:32Z<br>    Last Transition Time:  2023-03-09T13:23:32Z<br>    Message:               VMI does not exist<br>    Reason:                VMINotExists<br>    Status:                False<br>    Type:                  Ready<br>  Printable Status:        Stopped<br>  Volume Snapshot Statuses:<br>    Enabled:  false<br>    Name:     rootfs<br>    Reason:   Snapshot is not supported for this volumeSource type [rootfs]<br>    Enabled:  false<br>    Name:     cloudinit<br>    Reason:   Snapshot is not supported for this volumeSource type [cloudinit]<br>Events:       &lt;none&gt;</pre><pre>$ kubectl virt start testvm<br>VM testvm was scheduled to start<br><br>$ kubectl describe vmi testvm<br>Name:         testvm<br>Namespace:    default<br>Labels:       kubevirt.io/domain=testvm<br>              kubevirt.io/size=small<br>Annotations:  kubevirt.io/latest-observed-api-version: v1<br>              kubevirt.io/storage-observed-api-version: v1alpha3<br>API Version:  kubevirt.io/v1<br>Kind:         VirtualMachineInstance<br>Metadata:<br>  Creation Timestamp:  2023-03-09T13:26:14Z<br>  Finalizers:<br>    kubevirt.io/virtualMachineControllerFinalize<br>    foregroundDeleteVirtualMachine<br>  Generation:  4<br>  Managed Fields:<br>    API Version:  kubevirt.io/v1alpha3<br>    Fields Type:  FieldsV1<br>    fieldsV1:<br>      f:metadata:<br>        f:annotations:<br>          .:<br>          f:kubevirt.io/latest-observed-api-version:<br>          f:kubevirt.io/storage-observed-api-version:<br>        f:finalizers:<br>          .:<br>          v:&quot;kubevirt.io/virtualMachineControllerFinalize&quot;:<br>        f:labels:<br>          .:<br>          f:kubevirt.io/domain:<br>          f:kubevirt.io/size:<br>        f:ownerReferences:<br>          .:<br>          k:{&quot;uid&quot;:&quot;01de5614-922a-4ae8-9bec-40eeb9a7c500&quot;}:<br>      f:spec:<br>        .:<br>        f:domain:<br>          .:<br>          f:devices:<br>            .:<br>            f:disks:<br>            f:interfaces:<br>          f:firmware:<br>            .:<br>            f:uuid:<br>          f:machine:<br>            .:<br>            f:type:<br>          f:resources:<br>            .:<br>            f:requests:<br>              .:<br>              f:memory:<br>        f:networks:<br>        f:volumes:<br>      f:status:<br>        .:<br>        f:activePods:<br>          .:<br>          f:f2afda42-6f8f-4bad-b35a-7591c3233cc1:<br>        f:conditions:<br>        f:guestOSInfo:<br>        f:phase:<br>        f:phaseTransitionTimestamps:<br>        f:qosClass:<br>        f:runtimeUser:<br>        f:virtualMachineRevisionName:<br>    Manager:    Go-http-client<br>    Operation:  Update<br>    Time:       2023-03-09T13:26:14Z<br>  Owner References:<br>    API Version:           kubevirt.io/v1<br>    Block Owner Deletion:  true<br>    Controller:            true<br>    Kind:                  VirtualMachine<br>    Name:                  testvm<br>    UID:                   01de5614-922a-4ae8-9bec-40eeb9a7c500<br>  Resource Version:        41728<br>  UID:                     745caf89-6e75-47d1-b094-91e6119f3cc4<br>Spec:<br>  Domain:<br>    Cpu:<br>      Cores:    1<br>      Model:    host-model<br>      Sockets:  1<br>      Threads:  1<br>    Devices:<br>      Disks:<br>        Disk:<br>          Bus:  virtio<br>        Name:   rootfs<br>        Disk:<br>          Bus:  virtio<br>        Name:   cloudinit<br>      Interfaces:<br>        Mac Address:  02:9d:e4:00:00:00<br>        Masquerade:<br>        Name:  default<br>    Features:<br>      Acpi:<br>        Enabled:  true<br>    Firmware:<br>      Uuid:  5a9fc181-957e-5c32-9e5a-2de5e9673531<br>    Machine:<br>      Type:  q35<br>    Resources:<br>      Requests:<br>        Memory:  64M<br>  Networks:<br>    Name:  default<br>    Pod:<br>  Volumes:<br>    Container Disk:<br>      Image:              kubevirt/cirros-registry-disk-demo<br>      Image Pull Policy:  Always<br>    Name:                 rootfs<br>    Cloud Init No Cloud:<br>      userDataBase64:  SGkuXG4=<br>    Name:              cloudinit<br>Status:<br>  Active Pods:<br>    f2afda42-6f8f-4bad-b35a-7591c3233cc1:  aks-agentpool-16963728-vmss000000<br>  Conditions:<br>    Last Probe Time:       2023-03-09T13:26:14Z<br>    Last Transition Time:  2023-03-09T13:26:14Z<br>    Message:               Guest VM is not reported as running<br>    Reason:                GuestNotRunning<br>    Status:                False<br>    Type:                  Ready<br>  Guest OS Info:<br>  Phase:  Scheduling<br>  Phase Transition Timestamps:<br>    Phase:                        Pending<br>    Phase Transition Timestamp:   2023-03-09T13:26:14Z<br>    Phase:                        Scheduling<br>    Phase Transition Timestamp:   2023-03-09T13:26:14Z<br>  Qos Class:                      Burstable<br>  Runtime User:                   107<br>  Virtual Machine Revision Name:  revision-start-vm-01de5614-922a-4ae8-9bec-40eeb9a7c500-2<br>Events:<br>  Type    Reason            Age   From                       Message<br>  ----    ------            ----  ----                       -------<br>  Normal  SuccessfulCreate  8s    virtualmachine-controller  Created virtual machine pod virt-launcher-testvm-b77hf</pre><p>Elle est en exécution dans KubeVirt :</p><pre>$ kubectl get vmis<br>NAME     AGE   PHASE     IP            NODENAME                            READY<br>testvm   61s   Running   10.244.2.38   aks-agentpool-16963728-vmss000000   True<br><br>$ kubectl get vms<br>NAME     AGE     STATUS    READY<br>testvm   3m47s   Running   True</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p32nJgYeypDrJwfcc3budQ.png" /></figure><p>avec sa console VNC fournie dans KubeVirt Manager :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iHlp8om-_htJo09lWxkajw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gzKOMtiGOvfZNzhS-Th2Bg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NqQOylWFSEQLdjzQ7t1YwA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z3xImKAQlZvXRZ9HZubnMQ.png" /></figure><p>Bien évidemment, je pouvais également accéder à la console de la machine virtuelle localement :</p><pre>$ kubectl virt console testvm<br><br>testvm login: cirros<br>Password: gocubsgo<br><br>$ ps aux<br>PID   USER     COMMAND<br>    1 root     init<br>    2 root     [kthreadd]<br>    3 root     [ksoftirqd/0]<br>    4 root     [kworker/0:0]<br>    5 root     [kworker/0:0H]<br>    7 root     [rcu_sched]<br>    8 root     [rcu_bh]<br>    9 root     [migration/0]<br>   10 root     [watchdog/0]<br>   11 root     [kdevtmpfs]<br>   12 root     [netns]<br>   13 root     [perf]<br>   14 root     [khungtaskd]<br>   15 root     [writeback]<br>   16 root     [ksmd]<br>   17 root     [crypto]<br>   18 root     [kintegrityd]<br>   19 root     [bioset]<br>   20 root     [kblockd]<br>   21 root     [ata_sff]<br>   22 root     [md]<br>   23 root     [devfreq_wq]La sup</pre><p>L’interruption peut se faire graphiquement ou via la ligne de commande habituelle :</p><pre>$ kubectl virt stop testvm<br>VM testvm was scheduled to stop<br><br>$ kubectl delete vm testvm<br>virtualmachine.kubevirt.io &quot;testvm&quot; deleted</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_rBQ71ciolH9dOHlrAozTQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SGMO6L4ytBLg8qdzEiicPA.png" /></figure><p>Avec les options graphiques, il serait possible de reproduire le schéma de création de machine virtuelle via “Containerized Data Importer (CDI)” …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5D6mb2HPMDu3jVC0" /></figure><p><a href="https://kubevirt.io/labs/kubernetes/lab2.html">Experiment with CDI | KubeVirt.io</a></p><p>KubeVirt Manager offre également une intégration avec Prometheus (et donc potentiellement à Grafana).</p><p><a href="https://github.com/kubevirt-manager/kubevirt-manager#prometheus-integration">GitHub - kubevirt-manager/kubevirt-manager: Kubevirt Web UI / Web Interface Manager</a></p><p>Ce projet encore jeune est en toujours développement et des fonctionnalités plus avancées sur le contrôle des machines virtuelles sont à espérer …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*YmVyW6IaiUM5JIJ_.jpg" /></figure><p>À suivre !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d403226f1265" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>