node-feature-discovery/deployment/base/rbac-topologyupdater/topologyupdater-clusterrole.yaml

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: nfd-topology-updater
rules:
- apiGroups:
  - ""
  resources:
  - nodes
  verbs:
  - get
  - list
- apiGroups:
  - ""
  resources:
  - nodes/proxy
  verbs:
  - get
- apiGroups:
  - ""
  resources:
  - pods
  verbs:
  - get
- apiGroups:
  - topology.node.k8s.io
  resources:
  - noderesourcetopologies
  verbs:
  - create
  - get
  - update
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: rbac.authorization.k8s.io/v1`
			`kind: ClusterRole`
			`metadata:`
			`name: nfd-topology-updater`
			`rules:`
			`- apiGroups:`
			`- ""`
			`resources:`
			`- nodes`
			`verbs:`
			`- get`
			`- list`
get kubelet config from configz Signed-off-by: Garrybest <garrybest@foxmail.com> 2022-11-07 19:58:40 +08:00			`- apiGroups:`
			`- ""`
			`resources:`
			`- nodes/proxy`
			`verbs:`
			`- get`
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			`- apiGroups:`
			`- ""`
			`resources:`
			`- pods`
			`verbs:`
			`- get`
nfd-topology-updater: update NodeResourceTopology objects directly Drop the gRPC communication to nfd-master and connect to the Kubernetes API server directly when updating NodeResourceTopology objects. Topology-updater already has connection to the API server for listing Pods so this is not that dramatic change. It also simplifies the code a lot as there is no need for the NFD gRPC client and no need for managing TLS certs/keys. This change aligns nfd-topology-updater with the future direction of nfd-worker where the gRPC API is being dropped and replaced by a CRD-based API. This patch also update deployment files and documentation to reflect this change. 2022-12-02 11:47:56 +02:00			`- apiGroups:`
			`- topology.node.k8s.io`
			`resources:`
			`- noderesourcetopologies`
			`verbs:`
			`- create`
			`- get`
			`- update`