node-feature-discovery/deployment/overlays/master-worker-topologyupdater/kustomization.yaml

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

namespace: node-feature-discovery

bases:
- ../../base/rbac
- ../../base/rbac-topologyupdater
- ../../base/nfd-crds
- ../../base/master
- ../../base/worker-daemonset
- ../../base/noderesourcetopologies-crd
- ../../base/topologyupdater-daemonset

resources:
- namespace.yaml

components:
- ../../components/worker-config
- ../../components/common
- ../../components/topology-updater
topologyupdater: manifests: topologyupdater deployment files - create an overlay for deployment of all components - create an overlay for just topologyupdater deployment (to be deployed in conjunction with the default overlay) - create a separate overlay for deployment of master and topologyupdater-job Signed-off-by: Swati Sehgal <swsehgal@redhat.com> 2021-08-26 16:09:29 +01:00			`apiVersion: kustomize.config.k8s.io/v1beta1`
			`kind: Kustomization`

			`namespace: node-feature-discovery`

			`bases:`
			`- ../../base/rbac`
			`- ../../base/rbac-topologyupdater`
pkg/apis/nfd: specify CRD for custom labeling rules Add a cluster-scoped Custom Resource Definition for specifying labeling rules. Nodes (node features, node objects) are cluster-level objects and thus the natural and encouraged setup is to only have one NFD deployment per cluster - the set of underlying features of the node stays the same independent of how many parallel NFD deployments you have. Our extension points (hooks, feature files and now CRs) can be be used by multiple actors (depending on us) simultaneously. Having the CRD cluster-scoped hopefully drives deployments in this direction. It also should make deployment of vendor-specific labeling rules easy as there is no need to worry about the namespace. This patch virtually replicates the source.custom.FeatureSpec in a CRD API (located in the pkg/apis/nfd/v1alpha1 package) with the notable exception that "MatchOn" legacy rules are not supported. Legacy rules are left out in order to keep the CRD simple and clean. The duplicate functionality in source/custom will be dropped by upcoming patches. This patch utilizes controller-gen (from sigs.k8s.io/controller-tools) for generating the CRD and deepcopy methods. Code can be (re-)generated with "make generate". Install controller-gen with: go install sigs.k8s.io/controller-tools/cmd/controller-gen@v0.7.0 Update kustomize and helm deployments to deploy the CRD. 2021-08-31 11:10:12 +03:00			`- ../../base/nfd-crds`
topologyupdater: manifests: topologyupdater deployment files - create an overlay for deployment of all components - create an overlay for just topologyupdater deployment (to be deployed in conjunction with the default overlay) - create a separate overlay for deployment of master and topologyupdater-job Signed-off-by: Swati Sehgal <swsehgal@redhat.com> 2021-08-26 16:09:29 +01:00			`- ../../base/master`
			`- ../../base/worker-daemonset`
			`- ../../base/noderesourcetopologies-crd`
			`- ../../base/topologyupdater-daemonset`

			`resources:`
			`- namespace.yaml`

			`components:`
			`- ../../components/worker-config`
			`- ../../components/common`
			`- ../../components/topology-updater`