add curl pod

Author: bruelea

docs/examples/example1-getting-started/README-ex1.md

@@ -11,14 +11,14 @@ Before prefixes and ip addresses can be claimed with the NetBox operator, a pref
 # 1.1 Claim a Prefix
 
 1. Apply  the manifest defining the prefix claim `kubectl apply --context kind-zurich -f docs/examples/example1-getting-started/simple_prefixclaim.yaml`
-2. Check that the prefix claim CR got a prefix addigned `kubectl get --context kind-zurich pxc,px -w`
+2. Check that the prefix claim CR got a prefix addigned `watch -n 1 kubectl get --context kind-zurich pxc,px`
 
 ![Example 1.1](simple_prefixclaim.drawio.svg)
 
 # 1.2 Dynamically Claim a Prefix with a Parent Prefix Selector
 
 1. Apply  the manifest defining the prefix claim `kubectl apply --context kind-zurich  -f docs/examples/example1-getting-started/dynamic-prefix-claim.yaml`
-2. Check if the frontend service got an external ip address assigned `kubectl get --context pxc,px -w`
+2. Check that the prefix claim CR got a prefix addigned `watch -n 1 kubectl get --context kind-zurich pxc,px`
 
 ![Example 1.2](dynamic-prefixclaim.drawio.svg)
 
@@ -29,7 +29,8 @@ This example uses [kro] to map the claimed prefix to a MetalLB IPAddressPool. Th
 1. Apply the kro resource graph definition, defining the mapping from the prefix claim to the metalLB ip address pool `kubectl apply -f docs/examples/set-up/metallb-ip-address-pool-netbox.yaml`
 2. Apply the manifests to create a deployment with a service and a metallb-ip-address-pool-netbox to create a metalLB IPAddressPool from the prefix claimed from NetBox `kubectl apply --context kind-zurich -f docs/examples/example1-getting-started/ip-address-pool.yaml`
 3. Apply the manifests to createa deployment with a service that gets a ip assigned from the metalLB pool created in the prevoius step. `kubectl apply --context kind-zurich -k docs/examples/example1-getting-started/sample-deployment.yaml`
-4. check if the frontend service got an external ip address assigned `kubectl get --context kind-zurich svc my-nginx -n nginx`
+4. check if the prefixclaim and ipaddresspool got created `watch -n 1 kubectl get --context kind-zurich pxc,ipaddresspools my-nginx -A`
+5. check if the service got an external ip address assigned `watch -n 1 kubectl get --context kind-zurich svc my-nginx -n nginx`
 
 
 ![Example 1.3](metallb-ipaddresspool-netbox.drawio.svg)

docs/examples/example1-getting-started/metallb-ipaddresspool-netbox.drawio.svg

@@ -4,6 +4,6 @@ This example shows how to claim multiple prefixes from different clusters and ma
 
 1. Create ip address pools on the london cluster `kubectl apply --context kind-london -f docs/examples/example2-multicluster/london-pools.yaml`
 2. Create ip address pool on the zurich cluster `kubectl create --context kind-zurich -f docs/examples/example2-multicluster/zurich-pools.yaml`
-3. Look up the created prefix claims and metalLB ipaddresspools `kubectl get --context kind-london pxc,ipaddresspools -A` and `kubectl get --context kind-zurich pxc,ipaddresspools -A`
+3. Look up the created prefix claims and metalLB ipaddresspools `watch -n 1 kubectl get --context kind-london pxc,ipaddresspools -A` and `watch -n 1 kubectl get --context kind-zurich pxc,ipaddresspools -A`
 
 ![Example 2](multicluster.drawio.svg)

docs/examples/example2-multicluster/README-ex2.md

@@ -20,6 +20,9 @@ kubectl config use-context kind-zurich
 kind load docker-image netbox-operator:build-local --name zurich
 kind load docker-image netbox-operator:build-local --name zurich  # fixes an issue with podman where the image is not correctly tagged after the first kind load docker-image
 kustomize build docs/examples/set-up/ | kubectl apply -f -
+kind load docker-image curlimages/curl --name zurich
+kind load docker-image curlimages/curl --name zurich
+kubectl run curl --image curlimages/curl --image-pull-policy=Never -- sleep infinity
 
 DEPLOYMENT_NAME=netbox-operator-controller-manager
 NAMESPACE=netbox-operator-system