mvk/src/content/docs/guides/vagrant/015-local-vagrant-cluster-ingress.md
jon brookes ff6341edf1 Remove outdated guides and restructure documentation for infctl and MVK
- Deleted the following guides:
  - Introduction to infctl
  - Local K3d Instance creation
  - Traefik ingress setup
  - Longhorn storage setup
  - Local Vagrant cluster setup
  - Quick Start guide for MVK
  - Minimal Viable Kubernetes overview

- Added new guides:
  - Local Development Environment setup
  - Initial Pipeline Run for infctl
  - Create a Vagrant 3 node cluster
  - Smoke test for Vagrant cluster
  - Add Longhorn Storage guide
  - Add Ingress guide
  - Smoke test for Ingress

- Updated index and navigation links to reflect new structure.
2025-08-25 18:49:33 +01:00

1.6 KiB

title description
Add Ingress A guide to adding ingress.

Prerequisites

This section follows on from Add Longhorn Storage. Be sure to complete that before commencing with this.

if not already shelled into the workstation, from /home/user/projects/infctl-cli we need to change directory to

cd vagrant/dev/ubuntu/

so we can ssh to the workstation

vagrant ssh workstation

Familiarise yourself with …

  • install_metallb.sh applies a kubernetes manifest to install metallb and then applies an IPAddressPool and L2Advertisement which will be used later by traefik to access a loadbalancer in order to expose services so that we can access them from outside of kubernetes. This is a key part of MVK and one which does not exist in Kubernetes as this is typically expected to be provided by a managed kubernetes cloud service.
  • install_traefik.sh sets up some custom variables to enable an internal dashboard, ports for ingress, log level and loadbalancer.

Run the pipelines …

The metallb pipeline can be run with :

LOG_FORMAT=basic infctl -f pipelines/vagrant-metallb.json

traefik ingress can be installed with

LOG_FORMAT=basic infctl -f pipelines/vagrant-ingress.json