feat(helm): update chart node-feature-discovery to 0.17.0 #787
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![chii-bot[bot]](https://avatars.githubusercontent.com/in/220539?s=60&v=4){kind=small}
chii-bot
bot
added
renovate/helm
type/minor
size/XS
|
Path: @@ -4,27 +4,54 @@
kind: ServiceAccount
metadata:
name: node-feature-discovery
+ namespace: default
labels:
app.kubernetes.io/name: node-feature-discovery
app.kubernetes.io/instance: node-feature-discovery
app.kubernetes.io/managed-by: Helm
---
-
+# Source: node-feature-discovery/templates/serviceaccount.yaml
+apiVersion: v1
+kind: ServiceAccount
+metadata:
+ name: node-feature-discovery-gc
+ namespace: default
+ labels:
+ app.kubernetes.io/name: node-feature-discovery
+ app.kubernetes.io/instance: node-feature-discovery
+ app.kubernetes.io/managed-by: Helm
---
+# Source: node-feature-discovery/templates/serviceaccount.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
name: node-feature-discovery-worker
+ namespace: default
+ labels:
+ app.kubernetes.io/name: node-feature-discovery
+ app.kubernetes.io/instance: node-feature-discovery
+ app.kubernetes.io/managed-by: Helm
+---
+# Source: node-feature-discovery/templates/nfd-master-conf.yaml
+apiVersion: v1
+kind: ConfigMap
+metadata:
+ name: node-feature-discovery-master-conf
+ namespace: default
labels:
app.kubernetes.io/name: node-feature-discovery
app.kubernetes.io/instance: node-feature-discovery
app.kubernetes.io/managed-by: Helm
+data:
+ nfd-master.conf: |-
+ null
---
# Source: node-feature-discovery/templates/nfd-worker-conf.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: node-feature-discovery-worker-conf
+ namespace: default
labels:
app.kubernetes.io/name: node-feature-discovery
app.kubernetes.io/instance: node-feature-discovery
@@ -73,171 +100,6 @@
- vendor
- device
---
-# Source: node-feature-discovery/templates/nodefeaturerule-crd.yaml
-apiVersion: apiextensions.k8s.io/v1
-kind: CustomResourceDefinition
-metadata:
- annotations:
- controller-gen.kubebuilder.io/version: v0.7.0
- creationTimestamp: null
- name: nodefeaturerules.nfd.k8s-sigs.io
-spec:
- group: nfd.k8s-sigs.io
- names:
- kind: NodeFeatureRule
- listKind: NodeFeatureRuleList
- plural: nodefeaturerules
- singular: nodefeaturerule
- scope: Cluster
- versions:
- - name: v1alpha1
- schema:
- openAPIV3Schema:
- description: NodeFeatureRule resource specifies a configuration for feature-based customization of node objects, such as node labeling.
- properties:
- apiVersion:
- description: 'APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
- type: string
- kind:
- description: 'Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
- type: string
- metadata:
- type: object
- spec:
- description: NodeFeatureRuleSpec describes a NodeFeatureRule.
- properties:
- rules:
- description: Rules is a list of node customization rules.
- items:
- description: Rule defines a rule for node customization such as labeling.
- properties:
- labels:
- additionalProperties:
- type: string
- description: Labels to create if the rule matches.
- type: object
- labelsTemplate:
- description: LabelsTemplate specifies a template to expand for dynamically generating multiple labels. Data (after template expansion) must be keys with an optional value (<key>[=<value>]) separated by newlines.
- type: string
- matchAny:
- description: MatchAny specifies a list of matchers one of which must match.
- items:
- description: MatchAnyElem specifies one sub-matcher of MatchAny.
- properties:
- matchFeatures:
- description: MatchFeatures specifies a set of matcher terms all of which must match.
- items:
- description: FeatureMatcherTerm defines requirements against one feature set. All requirements (specified as MatchExpressions) are evaluated against each element in the feature set.
- properties:
- feature:
- type: string
- matchExpressions:
- additionalProperties:
- description: "MatchExpression specifies an expression to evaluate against a set of input values. It contains an operator that is applied when matching the input and an array of values that the operator evaluates the input against. \n NB: CreateMatchExpression or MustCreateMatchExpression() should be used for creating new instances. NB: Validate() must be called if Op or Value fields are modified or if a new instance is created from scratch without using the helper functions."
- properties:
- op:
- description: Op is the operator to be applied.
- enum:
- - In
- - NotIn
- - InRegexp
- - Exists
- - DoesNotExist
- - Gt
- - Lt
- - GtLt
- - IsTrue
- - IsFalse
- type: string
- value:
- description: Value is the list of values that the operand evaluates the input against. Value should be empty if the operator is Exists, DoesNotExist, IsTrue or IsFalse. Value should contain exactly one element if the operator is Gt or Lt and exactly two elements if the operator is GtLt. In other cases Value should contain at least one element.
- items:
- type: string
- type: array
- required:
- - op
- type: object
- description: MatchExpressionSet contains a set of MatchExpressions, each of which is evaluated against a set of input values.
- type: object
- required:
- - feature
- - matchExpressions
- type: object
- type: array
- required:
- - matchFeatures
- type: object
- type: array
- matchFeatures:
- description: MatchFeatures specifies a set of matcher terms all of which must match.
- items:
- description: FeatureMatcherTerm defines requirements against one feature set. All requirements (specified as MatchExpressions) are evaluated against each element in the feature set.
- properties:
- feature:
- type: string
- matchExpressions:
- additionalProperties:
- description: "MatchExpression specifies an expression to evaluate against a set of input values. It contains an operator that is applied when matching the input and an array of values that the operator evaluates the input against. \n NB: CreateMatchExpression or MustCreateMatchExpression() should be used for creating new instances. NB: Validate() must be called if Op or Value fields are modified or if a new instance is created from scratch without using the helper functions."
- properties:
- op:
- description: Op is the operator to be applied.
- enum:
- - In
- - NotIn
- - InRegexp
- - Exists
- - DoesNotExist
- - Gt
- - Lt
- - GtLt
- - IsTrue
- - IsFalse
- type: string
- value:
- description: Value is the list of values that the operand evaluates the input against. Value should be empty if the operator is Exists, DoesNotExist, IsTrue or IsFalse. Value should contain exactly one element if the operator is Gt or Lt and exactly two elements if the operator is GtLt. In other cases Value should contain at least one element.
- items:
- type: string
- type: array
- required:
- - op
- type: object
- description: MatchExpressionSet contains a set of MatchExpressions, each of which is evaluated against a set of input values.
- type: object
- required:
- - feature
- - matchExpressions
- type: object
- type: array
- name:
- description: Name of the rule.
- type: string
- vars:
- additionalProperties:
- type: string
- description: Vars is the variables to store if the rule matches. Variables do not directly inflict any changes in the node object. However, they can be referenced from other rules enabling more complex rule hierarchies, without exposing intermediary output values as labels.
- type: object
- varsTemplate:
- description: VarsTemplate specifies a template to expand for dynamically generating multiple variables. Data (after template expansion) must be keys with an optional value (<key>[=<value>]) separated by newlines.
- type: string
- required:
- - name
- type: object
- type: array
- required:
- - rules
- type: object
- required:
- - spec
- type: object
- served: true
- storage: true
-status:
- acceptedNames:
- kind: ""
- plural: ""
- conditions: []
- storedVersions: []
----
# Source: node-feature-discovery/templates/clusterrole.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
@@ -251,7 +113,15 @@
- apiGroups:
- ""
resources:
+ - namespaces
+ verbs:
+ - watch
+ - list
+ - apiGroups:
+ - ""
+ resources:
- nodes
+ - nodes/status
verbs:
- get
- patch
@@ -260,11 +130,73 @@
- apiGroups:
- nfd.k8s-sigs.io
resources:
+ - nodefeatures
- nodefeaturerules
+ - nodefeaturegroups
verbs:
- get
- list
- watch
+ - apiGroups:
+ - nfd.k8s-sigs.io
+ resources:
+ - nodefeaturegroups/status
+ verbs:
+ - patch
+ - update
+ - apiGroups:
+ - coordination.k8s.io
+ resources:
+ - leases
+ verbs:
+ - create
+ - apiGroups:
+ - coordination.k8s.io
+ resources:
+ - leases
+ resourceNames:
+ - "nfd-master.nfd.kubernetes.io"
+ verbs:
+ - get
+ - update
+---
+# Source: node-feature-discovery/templates/clusterrole.yaml
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRole
+metadata:
+ name: node-feature-discovery-gc
+ labels:
+ app.kubernetes.io/name: node-feature-discovery
+ app.kubernetes.io/instance: node-feature-discovery
+ app.kubernetes.io/managed-by: Helm
+rules:
+ - apiGroups:
+ - ""
+ resources:
+ - nodes
+ verbs:
+ - list
+ - watch
+ - apiGroups:
+ - ""
+ resources:
+ - nodes/proxy
+ verbs:
+ - get
+ - apiGroups:
+ - topology.node.k8s.io
+ resources:
+ - noderesourcetopologies
+ verbs:
+ - delete
+ - list
+ - apiGroups:
+ - nfd.k8s-sigs.io
+ resources:
+ - nodefeatures
+ verbs:
+ - delete
+ - list
---
# Source: node-feature-discovery/templates/clusterrolebinding.yaml
apiVersion: rbac.authorization.k8s.io/v1
@@ -284,39 +216,82 @@
name: node-feature-discovery
namespace: default
---
-# Source: node-feature-discovery/templates/service.yaml
-apiVersion: v1
-kind: Service
+# Source: node-feature-discovery/templates/clusterrolebinding.yaml
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRoleBinding
metadata:
- name: node-feature-discovery-master
+ name: node-feature-discovery-gc
labels:
app.kubernetes.io/name: node-feature-discovery
app.kubernetes.io/instance: node-feature-discovery
app.kubernetes.io/managed-by: Helm
- role: master
-spec:
- type: ClusterIP
- ports:
- - port: 8080
- targetPort: grpc
- protocol: TCP
- name: grpc
- selector:
+roleRef:
+ apiGroup: rbac.authorization.k8s.io
+ kind: ClusterRole
+ name: node-feature-discovery-gc
+subjects:
+ - kind: ServiceAccount
+ name: node-feature-discovery-gc
+ namespace: default
+---
+# Source: node-feature-discovery/templates/role.yaml
+apiVersion: rbac.authorization.k8s.io/v1
+kind: Role
+metadata:
+ name: node-feature-discovery-worker
+ namespace: default
+ labels:
app.kubernetes.io/name: node-feature-discovery
app.kubernetes.io/instance: node-feature-discovery
+ app.kubernetes.io/managed-by: Helm
+rules:
+ - apiGroups:
+ - nfd.k8s-sigs.io
+ resources:
+ - nodefeatures
+ verbs:
+ - create
+ - get
+ - update
+ - apiGroups:
+ - ""
+ resources:
+ - pods
+ verbs:
+ - get
+---
+# Source: node-feature-discovery/templates/rolebinding.yaml
+apiVersion: rbac.authorization.k8s.io/v1
+kind: RoleBinding
+metadata:
+ name: node-feature-discovery-worker
+ namespace: default
+ labels:
+ app.kubernetes.io/name: node-feature-discovery
+ app.kubernetes.io/instance: node-feature-discovery
+ app.kubernetes.io/managed-by: Helm
+roleRef:
+ apiGroup: rbac.authorization.k8s.io
+ kind: Role
+ name: node-feature-discovery-worker
+subjects:
+ - kind: ServiceAccount
+ name: node-feature-discovery-worker
+ namespace: default
---
# Source: node-feature-discovery/templates/worker.yaml
apiVersion: apps/v1
kind: DaemonSet
metadata:
name: node-feature-discovery-worker
+ namespace: default
labels:
app.kubernetes.io/name: node-feature-discovery
app.kubernetes.io/instance: node-feature-discovery
app.kubernetes.io/managed-by: Helm
role: worker
- annotations: {}
spec:
+ revisionHistoryLimit:
selector:
matchLabels:
app.kubernetes.io/name: node-feature-discovery
@@ -329,11 +304,13 @@
app.kubernetes.io/instance: node-feature-discovery
role: worker
annotations:
+ checksum/config: 41a798e8bfc0ac6aa899c80ca166cfb48885bcb15a06a77b90d355a6d02ba51d
configmap.reloader.stakater.com/reload: node-feature-discovery-worker-conf
spec:
dnsPolicy: ClusterFirstWithHostNet
serviceAccountName: node-feature-discovery-worker
securityContext: {}
+ hostNetwork: false
containers:
- name: worker
securityContext:
@@ -343,18 +320,48 @@
- ALL
readOnlyRootFilesystem: true
runAsNonRoot: true
- image: "k8s.gcr.io/nfd/node-feature-discovery:v0.11.1"
+ image: "registry.k8s.io/nfd/node-feature-discovery:v0.17.0"
imagePullPolicy: IfNotPresent
+ livenessProbe:
+ grpc:
+ port: 8082
+ initialDelaySeconds: 10
+ readinessProbe:
+ grpc:
+ port: 8082
+ initialDelaySeconds: 5
+ failureThreshold: 10
env:
- name: NODE_NAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName
- resources: {}
+ - name: POD_NAME
+ valueFrom:
+ fieldRef:
+ fieldPath: metadata.name
+ - name: POD_UID
+ valueFrom:
+ fieldRef:
+ fieldPath: metadata.uid
+ resources:
+ limits:
+ memory: 512Mi
+ requests:
+ cpu: 5m
+ memory: 64Mi
command:
- "nfd-worker"
args:
- - "--server=node-feature-discovery-master:8080"
+ # Go over featureGate and add the feature-gate flag
+ - "-feature-gates=NodeFeatureGroupAPI=false"
+ - "-metrics=8081"
+ - "-grpc-health=8082"
+ ports:
+ - containerPort: 8081
+ name: metrics
+ - containerPort: 8082
+ name: health
volumeMounts:
- name: host-boot
mountPath: "/host-boot"
@@ -368,8 +375,11 @@
- name: host-usr-lib
mountPath: "/host-usr/lib"
readOnly: true
- - name: source-d
- mountPath: "/etc/kubernetes/node-feature-discovery/source.d/"
+ - name: host-lib
+ mountPath: "/host-lib"
+ readOnly: true
+ - name: host-proc-swaps
+ mountPath: "/host-proc/swaps"
readOnly: true
- name: features-d
mountPath: "/etc/kubernetes/node-feature-discovery/features.d/"
@@ -390,9 +400,12 @@
- name: host-usr-lib
hostPath:
path: "/usr/lib"
- - name: source-d
+ - name: host-lib
+ hostPath:
+ path: "/lib"
+ - name: host-proc-swaps
hostPath:
- path: "/etc/kubernetes/node-feature-discovery/source.d/"
+ path: "/proc/swaps"
- name: features-d
hostPath:
path: "/etc/kubernetes/node-feature-discovery/features.d/"
@@ -408,14 +421,15 @@
kind: Deployment
metadata:
name: node-feature-discovery-master
+ namespace: default
labels:
app.kubernetes.io/name: node-feature-discovery
app.kubernetes.io/instance: node-feature-discovery
app.kubernetes.io/managed-by: Helm
role: master
- annotations: {}
spec:
replicas: 1
+ revisionHistoryLimit:
selector:
matchLabels:
app.kubernetes.io/name: node-feature-discovery
@@ -427,10 +441,13 @@
app.kubernetes.io/name: node-feature-discovery
app.kubernetes.io/instance: node-feature-discovery
role: master
- annotations: {}
+ annotations:
+ checksum/config: 0e39572ff18dbc2e9f804d7adebf2a489376f319d8007872286385bf74c1eb3d
spec:
serviceAccountName: node-feature-discovery
+ enableServiceLinks: false
securityContext: {}
+ hostNetwork: false
containers:
- name: master
securityContext:
@@ -440,37 +457,238 @@
- ALL
readOnlyRootFilesystem: true
runAsNonRoot: true
- image: "k8s.gcr.io/nfd/node-feature-discovery:v0.11.1"
+ image: "registry.k8s.io/nfd/node-feature-discovery:v0.17.0"
imagePullPolicy: IfNotPresent
+ startupProbe:
+ grpc:
+ port: 8082
+ failureThreshold: 30
livenessProbe:
- exec:
- command:
- - "/usr/bin/grpc_health_probe"
- - "-addr=:8080"
- initialDelaySeconds: 10
- periodSeconds: 10
+ grpc:
+ port: 8082
readinessProbe:
- exec:
- command:
- - "/usr/bin/grpc_health_probe"
- - "-addr=:8080"
- initialDelaySeconds: 5
- periodSeconds: 10
+ grpc:
+ port: 8082
failureThreshold: 10
ports:
- - containerPort: 8080
- name: grpc
+ - containerPort: 8081
+ name: metrics
+ - containerPort: 8082
+ name: health
+ env:
+ - name: NODE_NAME
+ valueFrom:
+ fieldRef:
+ fieldPath: spec.nodeName
+ command:
+ - "nfd-master"
+ resources:
+ limits:
+ memory: 4Gi
+ requests:
+ cpu: 100m
+ memory: 128Mi
+ args:
+ - "-enable-leader-election"
+ # Go over featureGates and add the feature-gate flag
+ - "-feature-gates=NodeFeatureGroupAPI=false"
+ - "-metrics=8081"
+ - "-grpc-health=8082"
+ volumeMounts:
+ - name: nfd-master-conf
+ mountPath: "/etc/kubernetes/node-feature-discovery"
+ readOnly: true
+ volumes:
+ - name: nfd-master-conf
+ configMap:
+ name: node-feature-discovery-master-conf
+ items:
+ - key: nfd-master.conf
+ path: nfd-master.conf
+ affinity:
+ nodeAffinity:
+ preferredDuringSchedulingIgnoredDuringExecution:
+ - preference:
+ matchExpressions:
+ - key: node-role.kubernetes.io/master
+ operator: In
+ values:
+ - ""
+ weight: 1
+ - preference:
+ matchExpressions:
+ - key: node-role.kubernetes.io/control-plane
+ operator: In
+ values:
+ - ""
+ weight: 1
+ tolerations:
+ - effect: NoSchedule
+ key: node-role.kubernetes.io/master
+ operator: Equal
+ value: ""
+ - effect: NoSchedule
+ key: node-role.kubernetes.io/control-plane
+ operator: Equal
+ value: ""
+---
+# Source: node-feature-discovery/templates/nfd-gc.yaml
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+ name: node-feature-discovery-gc
+ namespace: default
+ labels:
+ app.kubernetes.io/name: node-feature-discovery
+ app.kubernetes.io/instance: node-feature-discovery
+ app.kubernetes.io/managed-by: Helm
+ role: gc
+spec:
+ replicas: 1
+ revisionHistoryLimit:
+ selector:
+ matchLabels:
+ app.kubernetes.io/name: node-feature-discovery
+ app.kubernetes.io/instance: node-feature-discovery
+ role: gc
+ template:
+ metadata:
+ labels:
+ app.kubernetes.io/name: node-feature-discovery
+ app.kubernetes.io/instance: node-feature-discovery
+ role: gc
+ spec:
+ serviceAccountName: node-feature-discovery-gc
+ dnsPolicy: ClusterFirstWithHostNet
+ securityContext: {}
+ hostNetwork: false
+ containers:
+ - name: gc
+ image: "registry.k8s.io/nfd/node-feature-discovery:v0.17.0"
+ imagePullPolicy: "IfNotPresent"
env:
- name: NODE_NAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName
command:
+ - "nfd-gc"
+ args:
+ - "-gc-interval=1h"
+ resources:
+ limits:
+ memory: 1Gi
+ requests:
+ cpu: 10m
+ memory: 128Mi
+ securityContext:
+ allowPrivilegeEscalation: false
+ capabilities:
+ drop: ["ALL"]
+ readOnlyRootFilesystem: true
+ runAsNonRoot: true
+ ports:
+ - name: metrics
+ containerPort: 8081
+---
+# Source: node-feature-discovery/templates/post-delete-job.yaml
+apiVersion: v1
+kind: ServiceAccount
+metadata:
+ name: node-feature-discovery-prune
+ namespace: default
+ labels:
+ app.kubernetes.io/name: node-feature-discovery
+ app.kubernetes.io/instance: node-feature-discovery
+ app.kubernetes.io/managed-by: Helm
+ annotations:
+ "helm.sh/hook": post-delete
+ "helm.sh/hook-delete-policy": before-hook-creation,hook-succeeded
+---
+# Source: node-feature-discovery/templates/post-delete-job.yaml
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRole
+metadata:
+ name: node-feature-discovery-prune
+ labels:
+ app.kubernetes.io/name: node-feature-discovery
+ app.kubernetes.io/instance: node-feature-discovery
+ app.kubernetes.io/managed-by: Helm
+ annotations:
+ "helm.sh/hook": post-delete
+ "helm.sh/hook-delete-policy": before-hook-creation,hook-succeeded
+rules:
+ - apiGroups:
+ - ""
+ resources:
+ - nodes
+ - nodes/status
+ verbs:
+ - get
+ - patch
+ - update
+ - list
+---
+# Source: node-feature-discovery/templates/post-delete-job.yaml
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRoleBinding
+metadata:
+ name: node-feature-discovery-prune
+ labels:
+ app.kubernetes.io/name: node-feature-discovery
+ app.kubernetes.io/instance: node-feature-discovery
+ app.kubernetes.io/managed-by: Helm
+ annotations:
+ "helm.sh/hook": post-delete
+ "helm.sh/hook-delete-policy": before-hook-creation,hook-succeeded
+roleRef:
+ apiGroup: rbac.authorization.k8s.io
+ kind: ClusterRole
+ name: node-feature-discovery-prune
+subjects:
+ - kind: ServiceAccount
+ name: node-feature-discovery-prune
+ namespace: default
+---
+# Source: node-feature-discovery/templates/post-delete-job.yaml
+apiVersion: batch/v1
+kind: Job
+metadata:
+ name: node-feature-discovery-prune
+ namespace: default
+ labels:
+ app.kubernetes.io/name: node-feature-discovery
+ app.kubernetes.io/instance: node-feature-discovery
+ app.kubernetes.io/managed-by: Helm
+ annotations:
+ "helm.sh/hook": post-delete
+ "helm.sh/hook-delete-policy": before-hook-creation,hook-succeeded
+spec:
+ template:
+ metadata:
+ labels:
+ app.kubernetes.io/name: node-feature-discovery
+ app.kubernetes.io/instance: node-feature-discovery
+ app.kubernetes.io/managed-by: Helm
+ role: prune
+ spec:
+ serviceAccountName: node-feature-discovery-prune
+ containers:
+ - name: nfd-master
+ securityContext:
+ allowPrivilegeEscalation: false
+ capabilities:
+ drop:
+ - ALL
+ readOnlyRootFilesystem: true
+ runAsNonRoot: true
+ image: "registry.k8s.io/nfd/node-feature-discovery:v0.17.0"
+ imagePullPolicy: IfNotPresent
+ command:
- "nfd-master"
- resources: {}
args:
- ## By default, disable NodeFeatureRules controller for other than the default instances
- - "-featurerules-controller=true"
+ - "-prune"
+ restartPolicy: Never
affinity:
nodeAffinity:
preferredDuringSchedulingIgnoredDuringExecution: |
MegaLinter status: ❌ ERROR
See errors details in artifact MegaLinter reports on CI Job page |
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
2d428a0 to
2b629dd
Compare
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
2b629dd to
7e5c862
Compare
|
You have successfully added a new Trivy configuration |
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
7e5c862 to
532b2ff
Compare
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
532b2ff to
08532ec
Compare
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
08532ec to
473d5f2
Compare
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
473d5f2 to
33afdca
Compare
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
33afdca to
1e58a24
Compare
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
1e58a24 to
489f60c
Compare
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
489f60c to
5b27360
Compare
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
5b27360 to
5ec673b
Compare
chii-bot
bot
changed the title
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
48eed0d to
3ce7d2b
Compare
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
3ce7d2b to
854f7c1
Compare
chii-bot
bot
changed the title
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
854f7c1 to
22016b4
Compare
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
22016b4 to
37b8fe2
Compare
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
37b8fe2 to
a77930b
Compare
chii-bot
bot
changed the title
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
a77930b to
bfa856a
Compare
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
bfa856a to
09c5887
Compare
chii-bot
bot
changed the title
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
09c5887 to
fb54782
Compare
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
fb54782 to
7c7dfeb
Compare
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
7c7dfeb to
4b23ec4
Compare
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
4b23ec4 to
013706a
Compare
chii-bot
bot
changed the title
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
013706a to
348536d
Compare
chii-bot
bot
changed the title
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
348536d to
2ee4e3b
Compare
chii-bot
bot
changed the title
| datasource | package | from | to | | ---------- | ---------------------- | ------ | ------ | | helm | node-feature-discovery | 0.11.1 | 0.17.0 |
chii-bot
bot
force-pushed
the
renovate/node-feature-discovery
branch
from
2ee4e3b to
103c515
Compare
chii-bot
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.11.1->0.17.0⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
kubernetes-sigs/node-feature-discovery
v0.17.0Compare Source
Changelog
Configurable restrictions (EXPERIMENTAL)
The nfd-master now has configuration options to restrict its capabilities, that is what modifications on node objects are allowed. See the nfd-master configuration file reference for documentation.
Image compatibity (EXPERIMENTAL)
There is an initiative to utilize NFD to implement system compatibility requirements for container images. As part of this work NFD v0.17 includes
nfdcommand line client for validating systems against image compatibility manifests. See the documentation for more details, including examples how to create container images with compatibility manifests and validating nodes.See the enhancement proposal for background information and design details.
Miscellaneous
Scalability
This release contains numerous fixes to fix issues and improve the scalability of NFD in larger clusters.
DMI features
Discovery of
system.dmiid.product_namewas added.CPUID features
Support for new CPUID flags were added, including AMX-FP8 and AVX-VNNI-INT16.
Helm chart
Numerous small improvements in the NFD Helm chart, mainly new configuration values (see chart parameters for documentation).
Deprecations
gRPC API
The NodeFeature API is now GA and the legacy gRPC API has been completely removed.
Hooks
Support for hooks (deprecated in v0.12 has been removed. See the customization guide for replacements.
ResourceLabels config option
The
resourceLabelsconfiguration file option (and the corresponding-resource-labelsflag), deprecated in v0.13 were removed. Use NodeFeatureRule object's extendedResources field instead.Dynamic configuration
Dynamic runt-time reconfiguration was removed. This improves robustness and consistency as some of the configuration options did not support dynamic configuration.
Upcoming changes
The separate metric and health ports will be united behind a single port and the corresponding Helm chart values will be removed in NFD v0.18. This should be invisible to most users.
List of PRs
(Full Changelog: kubernetes-sigs/node-feature-discovery@v0.17.0-devel...v0.17.0)
v0.16.6Compare Source
What's Changed
Contributors @marquiz @elezar @ArangoGutierrez
Full Changelog: kubernetes-sigs/node-feature-discovery@v0.16.5...v0.16.6
v0.16.5Compare Source
What's Changed
Fixes an nfd-master memory leak on re-configure events when leader election is enabled. Adds parameters to configure health endpoint port.
Full Changelog: kubernetes-sigs/node-feature-discovery@v0.16.4...v0.16.5
v0.16.4Compare Source
What's Changed
This patch release contains improvements to the Helm chart, adding configurable liveness and readiness probes for all daemons and configurable revision history limit for the nfd-worker and nfd-topology-updater.
Full Changelog: kubernetes-sigs/node-feature-discovery@v0.16.3...v0.16.4
v0.16.3Compare Source
Fix detection of swap in some scenarios (#1751) and add Helm parameter to set the revisionHistoryLimit of nfd-master and nfd-gc (#1759).
Full Changelog: kubernetes-sigs/node-feature-discovery@v0.16.2...v0.16.3
v0.16.2Compare Source
What's Changed
Fixes an issue where node labels were temporarily removed on nfd-worker pod restarts.
Full Changelog: kubernetes-sigs/node-feature-discovery@v0.16.1...v0.16.2
v0.16.1Compare Source
What's Changed
Full Changelog: kubernetes-sigs/node-feature-discovery@v0.16.0...v0.16.1
v0.16.0Compare Source
Changelog
NodeFeatureGroup API
The NodeFeatureGroup custom resource was added to the NFD API. The NodeFeatureGroup API enables the creation of node groups based on features discovered by NFD. The API is an alpha feature and is disabled by default and can be enabled with the NodeFeatureGroupAPI feature gate.
See documentation for more details.
Feature gates
NFD adapted the concept of feature gates from Kubernetes to introduce and stabilize new features in a controlled way. See the documentation for more details. Two existing features (NodeFeature API and disabling label auto-prefixing) were converted into feature gates.
Deprecations
Upcoming changes
Support for hooks is deprecated since v0.12.0 and will be completely dropped in the NFD v0.17.
RDT feature labels removed
The
feature.node.kubernetes.io/cpu-rdt.*feature labels that were deprecated in NFD v0.13 were removed. RDT features are still available for use in NodeFeatureRules for custom labels.Deprecated flags and options
The autoDefaultNs config file option of nfd-master is deprecated and will be removed in NFD v0.17. Superseded by the DisableAutoPrefix feature gate (
featureGates.DisableAutoPrefixHelm parameter).The
-enable-nodefeature-apicommand line flag of nfd-master and nfd-worker and the correspondingenableNodeFeatureApiHelm chart parameter have been deprecated and will be removed in NFD v0.17. Superseded by the NodeFeature API feature gate (featureGates.NodeFeatureAPIHelm parameter).The
-crd-controllercommand line flag of nfd-master is deprecated and will be removed with the gRPC API in a future release.Miscellaneous
Network devices
Discover speed of virtual network interfaces.
DMI
Added support for detecting DMI attributes from
/sys/devices/virtual/dmi/id/. In v0.16 onlysys_vendordiscovered, available assystem.dmiid.sys_vendorfeature for use in NodeFeatureRules.Swap
Discover the availability of swap on the node. Available as
memory.swap.enabledfeature for use in NodeFeatureRules.Helm chart
Now all nodes are cleaned up (feature labels, annotations, extended resources and taints are removed) after uninstalling NFD using a post-delete hook.
The Helm chart now sets resource requests (cpu and memory) for NFD pods. Users may want to adjust these for their cluster. An option to set the pod priority class was added. See Helm chart parameters in the documentation).
Container health
A gRPC health server was added to the nfd-master, nfd-worker and nfd-topology-updater daemons. Deployments (Helm and kustomize) configure container liveness and readiness probes to use that for health checking.
List of PRs
nfd-workererroring when reading attributes from paravirtual devices (#1557)v0.15.7Compare Source
What's Changed
This patch release updates dependencies.
Full Changelog: kubernetes-sigs/node-feature-discovery@v0.15.6...v0.15.7
v0.15.6Compare Source
What's Changed
Fixes an issue where node labels were temporarily removed on nfd-worker pod restarts.
Full Changelog: kubernetes-sigs/node-feature-discovery@v0.15.5...v0.15.6
v0.15.5Compare Source
Changelog
This patch release fixes nfd-topology-updater on IPv6 clusters.
List of PRs
v0.15.4Compare Source
This patch release fixes a potential crash in nfd-master (#1644).
v0.15.3Compare Source
Changelog
This patch release fixes a critical memory leak in nfd-master, along with updating dependencies.
Full Changelog: kubernetes-sigs/node-feature-discovery@v0.15.2...v0.15.3
v0.15.2Compare Source
Changelog
This release fixes a bug in hooks and updates dependencies.
Full Changelog: kubernetes-sigs/node-feature-discovery@v0.15.1...v0.15.2
v0.15.1Compare Source
What's Changed
This patch release adds detection of
speedattribute of virtual network interfaces.List of PRs
Full Changelog: kubernetes-sigs/node-feature-discovery@v0.15.0...v0.15.1
v0.15.0Compare Source
What's new
NodeFeatureRule API extended
Annotations
NFD now supports creating node annotations with the NodeFeatureRuless. See the documentation for details.
matchName
New
matchNamefield was added to the NodeFeatureRule CRD. It can be used to match the names of features (instead of their values which is done with thematchExpressionsfield). Seedocumentation for details.
Feature files
Hidden feature files: feature files whose name start with a dot (
.) are now ignored by nfd-worker. This makes it easier to update tConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.