-
-
Notifications
You must be signed in to change notification settings - Fork 500
Closed
Description
The goal would be to have a full embeded k3d config and avoid to manage several manifest files.
For instance with the auto-deploy manifest with the CLI:
k3d cluster create mycluster --k3s-server-arg '--no-deploy=traefik' --volume "$(pwd)/helm-ingress-nginx.yaml:/var/lib/rancher/k3s/server/manifests/helm-ingress-nginx.yaml" --port 8080:80@loadbalancer --port 8443:443@loadbalancer
With the actual K3d config file approach it is not possible to define the "helm-ingress-nginx.yaml" inside the k3d config:
apiVersion: k3d.io/v1alpha2
kind: Simple
name: mycluster
servers: 1
agents: 0
image: rancher/k3s:latest
options:
k3s:
extraServerArgs:
- "--no-deploy=traefik"
volumes:
- volume: "/myFullPath/helm-ingress-nginx.yaml:/var/lib/rancher/k3s/server/manifests/helm-ingress-nginx.yaml"
nodeFilters:
- server
ports:
- port: 8080:80
nodeFilters:
- loadbalancer
- port: 8443:443
nodeFilters:
- loadbalancer
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request
Type
Projects
Status
Done