mirrors/node-feature-discovery
mirrors/node-feature-discovery
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/node-feature-discovery.git synced 2025-03-12 03:36:58 +00:00
Code Activity
node-feature-discovery/deployment/components/common/kustomization.yaml

42 lines
903 B
YAML
Raw Normal View History

deployment: add kustomize base Implement functionality virtually replicating deployment templates for nfd-master and nfd-worker daemonset (nfd-master.yaml.template and nfd-worker-daemonset.yaml.template) by adding a kustomize overlay named "default". We split the resources into multiple bases (rbac, master and worker-daemonset) so that relevant parts are re-usable in other deployment scenarios added later (e.g. "one-shot job", and "combined daemonset"). This patch adds one component (components/common) doing the required kustomization for the example deployment.
2021-03-11 19:11:08 +02:00
apiVersion: kustomize.config.k8s.io/v1alpha1
kind: Component
patches:
- path: env.yaml
target:
labelSelector: app=nfd
name: nfd.*
- path: securitycontext.yaml
target:
labelSelector: app=nfd
name: nfd.*
- path: master-affinity.yaml
target:
labelSelector: app=nfd
name: nfd-master
- path: worker-mounts.yaml
target:
labelSelector: app=nfd
name: nfd-worker
kustomize: add standard-combined overlay Replicates nfd-daemonset-combined.yaml.template. In addition to the overlay we need to add a separate set of patches under components/common in order to handle the double-container pod.
2021-03-16 16:20:42 +02:00
# We need separate patches for the "combined" daemonset with two containers in the pod :/
- path: env-combined.yaml
target:
labelSelector: app=nfd
name: nfd
- path: securitycontext-combined.yaml
target:
labelSelector: app=nfd
name: nfd
- path: master-affinity.yaml
target:
labelSelector: app=nfd
name: nfd
- path: worker-mounts-combined.yaml
target:
labelSelector: app=nfd
name: nfd
Add master config file Similar to the nfd-worker, in this PR we want to support the dynamic run-time configurability through a config file for the nfd-master. We'll use a json or yaml configuration file along with the fsnotify in order to watch for changes in the config file. As a result, we're allowing dynamic control of logging params, allowed namespaces, extended resources, label whitelisting, and denied namespaces. Signed-off-by: AhmedGrati <ahmedgrati1999@gmail.com>
2023-03-05 22:56:46 +01:00
- path: master-mounts.yaml
target:
labelSelector: app=nfd
name: nfd-master
Copy permalink