This message was deleted.

I ran through the insecure-registry.start example in Windows 11 and I can see the provisioning scripts feature functioning. Two things that I had to take note of during testing 1. I needed to ensure that unix line endings were used in my provisioning script 2. I noticed that

insecure-registry.start

was renamed to

insecure-registry.start.sh

somewhere in the process.. reverting the name to

insecure-registry.start

ensured that the provisioning script worked in my environment Do you have specific examples that you can share?

Yes, sorry for the delay, I didn't receive any notification about this thread. I am provisioning the Nginx Ingress Controller for example. Here is one of my scripts (in %APPDATA%\rancher-desktop\provisioning folder):

cat 01-ingress-controller.start

#!/bin/sh -x

echo "Installing Nginx Ingress Controller using Helm Chart"

export KUBECONFIG=/etc/rancher/k3s/k3s.yaml

echo "Remove Traefik if exists"

helm uninstall traefik traefik-crd -n kube-system

cat <<EOF>/tmp/ingress-nginx-4.8.0.values.yaml

controller:

ingressClassResource:

default: true

service:

type: NodePort

nodePorts:

http: 30080

https: 30443

# tcp:

#   8080: 32808

EOF

helm upgrade --install ingress-nginx \

--namespace ingress-nginx --create-namespace \

<oci://registry.XXX.com/thirdparty-charts/bitnami-labs.github.io/ingress-nginx/ingress-nginx> \

--version 4.8.0 \

--values /tmp/ingress-nginx-4.8.0.values.yaml

sleep 60