add traefik values for test purpose.

bootstrap.sh

@@ -2,7 +2,7 @@
 
 # k3s and set current context as k3s , k3s use trafik as ingress controller by default.
 (which k3s &> /dev/null && test -f /etc/rancher/k3s/k3s.yaml)  || \
-    curl -sfL https://get.k3s.io | sh -s - --write-kubeconfig-mode 644
+    curl -sfL https://get.k3s.io | sh -s - --write-kubeconfig-mode 644 --disable traefik
 
 export KUBECONFIG=/etc/rancher/k3s/k3s.yaml
 kubectl get namespace jitsi &> /dev/null || \
@@ -18,3 +18,17 @@ which helm &> /dev/null || \
 sudo -E helm repo add jitsi https://jitsi-contrib.github.io/jitsi-helm/
 sudo -E helm install shlug-jitsi jitsi/jitsi-meet -f values.yml -n jitsi
 
+# traefik set global argument for acme challenge needs.
+#  globalArguments:
+#  - "--global.checknewversion"
+#  - "--global.sendanonymoususage"
+#  - "--providers.kubernetescrd"
+#  - "--certificatesresolvers.myresolver.acme.tlschallenge"
+#  - "--certificatesresolvers.myresolver.acme.email=foo@you.com"
+#  - "--certificatesresolvers.myresolver.acme.storage=acme.json"
+#  Please note that this is the staging Let's Encrypt server.
+#  Once you get things working, you should remove that whole line altogether.
+#  - "--certificatesresolvers.myresolver.acme.caserver=https://acme-staging-v02.api.letsencrypt.org/directory"
+
+helm repo add traefik https://helm.traefik.io/traefik
+sudo -E helm upgrade traefik traefik/traefik  --install -n kube-system --reuse-values -f traefik-values.yml

traefik-values.yml

@@ -0,0 +1,73 @@
+globalArguments:
+  - "--api.insecure"
+  - "--accesslog"
+  - "--providers.kubernetescrd"
+#  - "--certificatesresolvers.shlug.acme.httpchallenge=true"
+#  - "--certificatesresolvers.shlug.acme.httpchallenge.entrypoint=web"
+  - "--certificatesresolvers.shlug.acme.email=webmaster@shlug.org"
+  - "--certificatesresolvers.shlug.acme.storage=/data/acme.json"
+  - "--certificatesresolvers.shlug.acme.caserver=https://acme-staging-v02.api.letsencrypt.org/directory"
+
+# Configure ports
+ports:
+  traefik:
+    port: 9000
+    expose: false
+    # The exposed port for this service
+    exposedPort: 9000
+    # The port protocol (TCP/UDP)
+    protocol: TCP
+  web:
+    port: 8000
+    # hostPort: 8000
+    expose: true
+    exposedPort: 80
+    # The port protocol (TCP/UDP)
+    protocol: TCP
+    # Use nodeport if set. This is useful if you have configured Traefik in a
+    # LoadBalancer
+    nodePort: 30080
+    # Port Redirections
+    # Added in 2.2, you can make permanent redirects via entrypoints.
+    # https://docs.traefik.io/routing/entrypoints/#redirection
+    # redirectTo: websecure
+  websecure:
+    port: 8443
+    # hostPort: 8443
+    expose: true
+    exposedPort: 443
+    # The port protocol (TCP/UDP)
+    protocol: TCP
+    nodePort: 30443
+    # Enable HTTP/3.
+    # Requires enabling experimental http3 feature and tls.
+    # Note that you cannot have a UDP entrypoint with the same port.
+    # http3: true
+    # Set TLS at the entrypoint
+    # https://doc.traefik.io/traefik/routing/entrypoints/#tls
+    tls:
+      enabled: true
+      # this is the name of a TLSOption definition
+      options: ""
+      certResolver: "httpchallenge"
+      domains: 
+        - main: jitsi-test.shlug.org
+
+      # - main: example.com
+      #   sans:
+      #     - foo.example.com
+      #     - bar.example.com
+  metrics:
+    port: 9100
+    # hostPort: 9100
+    # Defines whether the port is exposed if service.type is LoadBalancer or
+    # NodePort.
+    #
+    # You may not want to expose the metrics port on production deployments.
+    # If you want to access it from outside of your cluster,
+    # use `kubectl port-forward` or create a secure ingress
+    expose: false
+    # The exposed port for this service
+    exposedPort: 9100
+    # The port protocol (TCP/UDP)
+    protocol: TCP