fabianhardt / k3d-bootstrap-cluster Goto Github PK

When you try to create a cluster without Calico and NGINX (which is the k3d default normally), there is an Issue while templating the cluster.yaml file.
This is because the k3s.extraArgs section is empty.
`Creating K3D cluster

FATA[0000] Schema Validation failed for config file k3d-cluster.yaml: - options.k3s.extraArgs: Invalid type. Expected: array, given: null`

Kuma / Kong Mesh

It would be nice to have a Kuma / Kong mesh example as well. Version 2.0 of Kuma was recently released very freshly.
So another example would be possible here...

Currently the shell script create-sample.sh script deletes all k3d Clusters that have been configured, which might not be desired by users.

This behavior should be changed, so that only the Cluster created by the script is deleted while creating a new one.

Kyverno

It would be nice to have a Kyverno example too.
Maybe we should add this next...

In the current configuration, pods deployed to the cluster cannot call external services.

Trying to do so results in a connection timeout.

The issue seems is related to k3d-io/k3d#1017.

Sometimes, when bootstrapping a cluster with installing the httpbin example service, an error occurs:

Error from server (InternalError): error when creating "httpbin/sample-ingress-nginx.yaml": Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": failed to call webhook: Post "https://ingress-nginx-controller-admission.ingress-nginx.svc:443/networking/v1/ingresses?timeout=10s": no endpoints available for service "ingress-nginx-controller-admission"

This is because the Nginx Ingress Controller is not available yet.