Issue with KYPO-Lite Installation - Infinite Loop During

Infrastructure as Code & Cloud Native
, , , ,
1

Problem to solve

I’m encountering an issue during the installation of KYPO-Lite on my VPS. After following the instructions provided in the GitLab repository, I reached the step where I run the vagrant up command. However, the process gets stuck in an infinite loop. I expected the deployment to proceed normally and complete the setup, but it doesn’t seem to get past this point.

Here’s the code block where it seems to be looping indefinitely:

while true; do
        ((iterations++))
        echo "Iteration: $iterations"
        result=$(kubectl get crd | grep middlewares.traefik.containo.us)
        if [ $? -eq 0 ]; then
            echo "K3s cluster ready:"
            echo "$result"
            break
        else
            echo "K3s cluster initializing. Retrying..."
        fi
        sleep 1
    done

Steps to reproduce

  1. I followed the installation instructions in the repository README without making any changes to the Vagrant file.
  2. I executed the vagrant up command on a VPS that meets all the hardware and software requirements.
  3. The process enters the infinite loop described above and doesn’t progress beyond this stage.

Configuration

Here is the relevant section of the Vagrant file used in my setup:

Vagrant.configure(2) do |config|
  config.vm.box = "generic/ubuntu2204"
  config.vm.box_version = "4.2.16"
  config.vm.hostname = "openstack"
  config.vm.network :private_network, ip: "10.1.2.10"
  config.vm.provider :libvirt do |libvirt|
    libvirt.cpus = 8
    libvirt.memory = 45056
    libvirt.nested = true
    libvirt.machine_virtual_size = 250
  end
  # Additional provisioning code...
end

Versions

  • Self-managed
  • GitLab.com SaaS
  • Self-hosted Runners

Infrastructure-as-Code:

  • Terraform: N/A
  • Ansible: N/A

Cloud-native:

  • Kubernetes (kubectl version): Installed via Snap, version not specified

Helpful resources

I’ve searched the forum and checked the documentation provided in the repository, but I couldn’t find a solution to this specific issue.

Thanks for taking the time to be thorough in your request, it really helps!