This message was deleted.
# k3d
a
This message was deleted.
p
My k3d config
Copy code
yaml
apiVersion: k3d.io/v1alpha5
kind: Simple
metadata:
  name: my-cluster
servers: 1
agents: 1
image: docker.io/rancher/k3s:v1.25.16-k3s4
volumes:
  # Deploy Jetstack
  - volume: $FEATURES_DIR/jetstack.yml:/var/lib/rancher/k3s/server/manifests/jetstack.yaml
    nodeFilters:
      - agent:*
registries:
  use:
    - "my-cluster-registry.localhost"
and my HelmChart CRD is
Copy code
---
apiVersion: <http://helm.cattle.io/v1|helm.cattle.io/v1>
kind: HelmChart
metadata:
  name: cert-manager
  namespace: kube-system
spec:
  repo: <https://charts.jetstack.io>
  chart: cert-manager
  createNamespace: true
  targetNamespace: cert-manager
  valuesContent: |-
    installCRDs: true
but I dont see the HelmChart getting created automatically
any clue ?
@wide-garage-9465 ^^
when I try to add a nodeFilter like
Copy code
....
    nodeFilters:
      - all
....
It gets picked up, does these manifests need to be in server nodes as well ?
my bad I thought
agents:*
works like
server:*
for some reason when I do
agent:0
I see the volume never gets mounted , I want an app to be distributed across agents .
I mean I want it to be on any agent
c
your nodefilter only mounts the manifest volume on agents. only servers apply manifests. why are you trying to put it on agents?
https://docs.k3s.io/installation/packaged-components
On server nodes, any file found in
/var/lib/rancher/k3s/server/manifests
will automatically be deployed to Kubernetes in a manner similar to
kubectl apply
, both on startup and when the file is changed on disk.
the fact that you’re mounting stuff into a “server” directory on agents might also be a clue
p
why are you trying to put it on agents?
I just want the resources to be on agents than in server. I am ok for the volume to be on server