Repository navigation
update: add support for 'imagePullSecrets' propagation by root helm chart - #2191
Conversation
|
|
✅ Deploy Preview for kubernetes-sigs-nfd ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Welcome @heyvister1! |
|
Hi @heyvister1. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
e1ff13c to
9771b94
Compare
|
/lgtm can you please update |
|
LGTM label has been added. DetailsGit tree hash: bd701be73e52cd1fb44e3b3c89a9b22e7acbf7a5 |
9771b94 to
155d929
Compare
d0ae92d to
2fde4d8
Compare
9b9d9ad to
210393f
Compare
|
@adrianchiris PTAL |
|
|
||
| | Name | Type | Default | Description | | ||
| |---------------------------------------------|---------|----------------------------------|----------------------------------------------------------------------------------------------------------------------------| | ||
| | `global.imagePullSecrets` | array | [] | In case global `imagePullSecrets` are used, their values will be appended, when local `.Values.imagePullSecrets` are not specified. Local values take precedence over global values. | |
There was a problem hiding this comment.
i find the description hard to understand.
suggested reword:
An optional list of references to secrets with the same meaning as imagePullSecrets. If imagePullSecrets is specified, it takes precedence over global.imagePullSecrets
210393f to
fa457bd
Compare
fa457bd to
8dff365
Compare
8dff365 to
23adbbf
Compare
…hart, in case nfd serves as sub-chart Signed-off-by: Ido Heyvi
marquiz
left a comment
There was a problem hiding this comment.
Even better 😊 Thank you @adrianchiris for sharp-eyed review
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adrianchiris, heyvister1, marquiz The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Thanks @adrianchiris. Why prow ignored your lgtm 😞 |
|
LGTM label has been added. DetailsGit tree hash: d18ab7c45ceffa840a5c1b9935ace74b96cd6d63 |
…270) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [node-feature-discovery](https://github.com/kubernetes-sigs/node-feature-discovery) | minor | `v0.17.3` → `0.18.3` | --- ### Release Notes--- ### Configuration 📅 **Schedule**: (UTC) - 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. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). Co-authored-by: Renovate Botkubernetes-sigs/node-feature-discovery (node-feature-discovery)
### [`v0.18.3`](https://github.com/kubernetes-sigs/node-feature-discovery/releases/tag/v0.18.3) [Compare Source](kubernetes-sigs/node-feature-discovery@v0.18.2...v0.18.3) #### What's Changed This patch release adds support for ppc64le and s390x architectures by providing official NFD container images for them. It also fixes the "test" subcommand of kubectl-nfd plugin. **Full Changelog**: <kubernetes-sigs/node-feature-discovery@v0.18.2...v0.18.3> ### [`v0.18.2`](https://github.com/kubernetes-sigs/node-feature-discovery/releases/tag/v0.18.2) [Compare Source](kubernetes-sigs/node-feature-discovery@v0.18.1...v0.18.2) This patch release fixes the /metrics endpoint of nfd-topology-updater ([#2343](kubernetes-sigs/node-feature-discovery#2343)). ### [`v0.18.1`](https://github.com/kubernetes-sigs/node-feature-discovery/releases/tag/v0.18.1) [Compare Source](kubernetes-sigs/node-feature-discovery@v0.18.0...v0.18.1) This patch release fixes the deployment of PodMonitor object when prometheus-operator metrics collection is enabled. ### [`v0.18.0`](https://github.com/kubernetes-sigs/node-feature-discovery/releases/tag/v0.18.0) [Compare Source](kubernetes-sigs/node-feature-discovery@v0.17.4...v0.18.0) #### Changelog ##### Image compatibility (EXPERIMENTAL) The image compatibility related features introduced in [v0.17](https://github.com/kubernetes-sigs/node-feature-discovery/releases/v0.17.0) have been improved and enhanced. Major new feature is the `nfd export` command. See the [documentation](https://kubernetes-sigs.github.io/node-feature-discovery/v0.18/usage/image-compatibility.html) for more details ##### Helm The Helm chart is now served from the registry.k8s.io OCI registry at registry.k8s.io/nfd/charts/node-feature-discovery. One liner installation with ```bash helm install -n node-feature-discovery nfd oci://registry.k8s.io/nfd/charts/node-feature-discovery --version 0.18.0 --create-namespace ``` > \[!IMPORTANT] > The legacy Helm repository at <https://kubernetes-sigs.github.io/node-feature-discovery/charts> is still available, but will be deprecated and stop getting updated in a future release. Users are encouraged to migrate to the OCI registry. The release contains numerous small improvements and fixes to the Helm chart and its documentation, including: - Configurable DNS policy ([#2025](kubernetes-sigs/node-feature-discovery#2025)) - Configurable PodDisruptionBudget ([#2148](kubernetes-sigs/node-feature-discovery#2148)) - Configurable UpdateStrategy for nfd-worker ([#2157](kubernetes-sigs/node-feature-discovery#2157)) - Global `global.imagePullSecrets` parameter ([#2191](kubernetes-sigs/node-feature-discovery#2191)) - Fix for running with OwnerReferencesPermissionEnforcement validating webhook enabled ([#2006](kubernetes-sigs/node-feature-discovery#2006)) - Post-delete hook: option to disable ([#2076](kubernetes-sigs/node-feature-discovery#2076)) and configurable image pull secret ([#2082](kubernetes-sigs/node-feature-discovery#2082)) ##### Deprecations The deprecated `autoDefaultNs` configuration parameter of nfd-master was removed. Toleration for the deprecated `node-role.kubernetes.io/master:NoSchedule` taint and affinity to the deprecated `node-role.kubernetes.io/master` label have been removed from the default nfd-master deployment manifests. If you still need these, they need to be explicitly added to the deployment (`master.tolerations` and `master.affinity` in the Helm chart). > \[!IMPORTANT] > In v0.18.0 the DisableAutoPrefix feature is still alpha and disabled by default. NFD adds `feature.node.kubernetes.io/` prefix to all unprefixed label, annotation and extended resource names. When DisableAutoPrefix is enabled (will be default in a future release), NFD will not add the default prefix automatilly (and add unprefixed names, verbatim). Users are stronglycencouraged to start using fully qualified names (with the prefix) for allccustom labels, annotations and extended resources. ##### Miscellaneous ##### Scalability The release contains improvements and fixes to NFD scalability in larger clusters. ##### NodeFeatureRules ##### Label templating The label templates in NodeFeatureRules now support [sprig](https://masterminds.github.io/sprig/) functions, greatly enhancing their flexibility. ##### New comparison operators New comparison operators `Ge`, `Le` and `GeLe` were added ([#2085](kubernetes-sigs/node-feature-discovery#2085)). ##### Type field in MatchExpressions New `Type` field was added to `MatchExpressions`, allowing to specify the type of the value being compared ([#2096](kubernetes-sigs/node-feature-discovery#2096)). Currently supported types are empty value (the default) and `version`. Use of `version` type enables version-aware comparisons. ##### CPU features Support for new CPUID flags were added, including AMXCOMPLEX, AMXTRANSPOSE and AMXTF32. ##### Memory features NFD now detects availability of hugepages and reports them as `memory-hugepages.enabled` and `hugepages-`features ([#2056](kubernetes-sigs/node-feature-discovery#2056)). ##### Network features Detection of the MTU of network devices was added ([#2044](kubernetes-sigs/node-feature-discovery#2044)). ##### Metrics and health endpoints The gRPC health endpoint was replaced by an HTTP healthz endpoint in all NFD daemons. In addition, both the metrics and healthz endpoints are now served on the same port (configurable with `--port`, default 8080). [**Full Changelog**](kubernetes-sigs/node-feature-discovery@v0.18.0-devel...v0.18.0) ### [`v0.17.4`](https://github.com/kubernetes-sigs/node-feature-discovery/releases/tag/v0.17.4) [Compare Source](kubernetes-sigs/node-feature-discovery@v0.17.3...v0.17.4) #### What's Changed This release updates dependencies. **Full Changelog**: <kubernetes-sigs/node-feature-discovery@v0.17.3...v0.17.4> Reviewed-on: https://codeberg.org/blake-hamm/bhamm-lab/pulls/270
nfd serves as sub-chart in our project, and we would like to propagate
imagePullSecretscontent in rootvalues.yamlto nfd sub-chart. Therefore I have added.Values.global.imagePullSecretsand created a helper helm func to update accordingly.