From 4e6a73b4907005415998ce3e3e06618a44aba3fb Mon Sep 17 00:00:00 2001
From: David Young <davidy@funkypenguin.co.nz>
Date: Wed, 18 Oct 2023 09:29:15 +1300
Subject: [PATCH] Quick fix for metallb recipe (more fixes queued up)

Signed-off-by: David Young <davidy@funkypenguin.co.nz>
---
 docs/kubernetes/loadbalancer/metallb/index.md | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/docs/kubernetes/loadbalancer/metallb/index.md b/docs/kubernetes/loadbalancer/metallb/index.md
index 721e10e..bd54ca0 100644
--- a/docs/kubernetes/loadbalancer/metallb/index.md
+++ b/docs/kubernetes/loadbalancer/metallb/index.md
@@ -85,7 +85,7 @@ spec:
 Now that the "global" elements of this deployment (*Namespace and HelmRepository*) have been defined, we do some "flux-ception", and go one layer deeper, adding another Kustomization, telling flux to deploy any YAMLs found in the repo at `/metallb-system`. I create this example Kustomization in my flux repo:
 
 ```yaml title="/bootstrap/kustomizations/kustomization-metallb.yaml"
-apiVersion: kustomize.toolkit.fluxcd.io/v1beta1
+apiVersion: kustomize.toolkit.fluxcd.io/v1
 kind: Kustomization
 metadata:
   name: metallb--metallb-system
@@ -98,7 +98,6 @@ spec:
   sourceRef:
     kind: GitRepository
     name: flux-system
-  validation: server
   healthChecks:
     - apiVersion: apps/v1
       kind: Deployment
@@ -143,7 +142,7 @@ The simplest way to solve this chicken-and-egg problem is to create a **second**
 I create this example Kustomization in my flux repo:
 
 ```yaml title="/bootstrap/kustomizations/kustomization-config--metallb-system.yaml"
-apiVersion: kustomize.toolkit.fluxcd.io/v1beta1
+apiVersion: kustomize.toolkit.fluxcd.io/v1
 kind: Kustomization
 metadata:
   name: config--metallb-system
@@ -158,7 +157,6 @@ spec:
   sourceRef:
     kind: GitRepository
     name: flux-system
-  validation: server
   healthChecks:
     - apiVersion: apps/v1
       kind: Deployment