Fix apt key warning for Helm repository

See merge request !29

Resolve "Clean install code to minimal installation"

Closes #24

See merge request !32

Resolve "Default installation without ingress controller"

Closes #22

See merge request !30

Resolve "install-eolebase3.sh download k3d install.sh script in /tmp without overwriting existing one"

Closes #19

See merge request !26

Resolve "Set k3s release TAG in install-eolebase3.sh to v1.24.4+k3s1"

Closes #20

See merge request !27

Otherwise, if we call install-eolebase3.sh multiple times, the install.sh
script used will always be the same.

Resolve "Set k3d release TAG in install-eolebase3.sh to v5.4.3"

Closes #18

See merge request !25

For now, v5.4.4 seems bugged on Ubuntu.

Resolve "Add the production mode."

Closes #15

See merge request !24

K3D is not clear for production, if we want to use this tool to provide
an safe for production single node cluster, we need another tool.

To to so, we install k3s in server mode (single node).

Fixes #15

Resolve "Setup ingress nginx as the default controller"

Closes #14

See merge request !22

Now you can use the option "-i | --ingress [none,traefik,nginx]" to
install (or not) the ingress controler.
You also can provide a domain name with option "-d | --domain" for the
"SSL certificate generation" (we need to support cert-manager later

Fixes #14

Resolve "In install script, errMsg() is not always called with an error code"

Closes #11

See merge request !21

Resolve "Add an option to install loki-stack in the cluster"

Closes #12

See merge request !20

Installed with helm in namespace loki-stack.
Option -l or --loki-stack to install the loki stack.
Option --loki-size to select the PVC's size.
Option --volume-size to select the PV's size.

Resolve "Add some bash completions even in a "screen""

Closes #7

See merge request !15

Also configure screen to use bash completions

Resolve "Check curl is installed before using it"

Closes #9

See merge request !16

Resolve "Cluster don't start at boot"

Closes #8

See merge request !18

'k3d cluster create' creates a cluster but also starts it.
It seems that starting a cluster already started creates a container
k3d-eole3-tools which should be deleted at the end of the start but is not...
It is this container which creates problems at reboot.
-> stop cluster before starting the service systemd
Also, on a server where eole3 is already installed, we must stop and disable
the service if we want the cluster to be operational when the script end

Resolve "Fix second stage of CI (installation of k3d)"

Closes #13

See merge request !19

Use lsb_release command instead of /etc/lsb_release
Run install script as superuser
Give up tests with microk8s
Delegate run of the script to the builder

Resolve "Fix coding style (shellcheck) on install-eolebase3.sh"

Closes #10

See merge request !17

fix(doc): update readme

See merge request !14

fix(k3d): adding -t, --traefik option to provide custom traefik install

Closes #6

See merge request !13

if -t or --traefik option is set, we disable the embeded traefik install
and replace it with a custom one. the user needs to provide a values
file. if the file name is empty (ex: -t "") we use a default one
provided by the install function.

Fixes #6

The readme is now accurate

fix(k3d): do not setup the eole proxyhub

Closes #5

See merge request !12

This configuration make download from eole harbor impossible,
removing it solves the issue.

Fixes #5

fix(k3d): better management of k3d cluster with single control plane and systemd service

Closes #4

See merge request !11