search

replicatedhq / troubleshoot

Preflight Checks and Support Bundles Framework for Kubernetes Applications
https://troubleshoot.sh
Apache License 2.0
539 stars 92 forks source link

chore(deps): bump the security group with 12 updates #1565

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps the security group with 12 updates:

Package From To
github.com/spf13/cobra 1.8.0 1.8.1
github.com/vmware-tanzu/velero 1.13.2 1.14.0
k8s.io/api 0.30.1 0.30.2
k8s.io/apiextensions-apiserver 0.30.1 0.30.2
k8s.io/apimachinery 0.30.1 0.30.2
k8s.io/apiserver 0.30.1 0.30.2
k8s.io/cli-runtime 0.30.1 0.30.2
k8s.io/client-go 0.30.1 0.30.2
k8s.io/klog/v2 2.120.1 2.130.0
helm.sh/helm/v3 3.15.1 3.15.2
k8s.io/kubelet 0.30.1 0.30.2
k8s.io/metrics 0.30.1 0.30.2

Updates github.com/spf13/cobra from 1.8.0 to 1.8.1

Release notes

Sourced from github.com/spf13/cobra's releases.

v1.8.1

✨ Features

🐛 Bug fixes

🔧 Maintenance

🧪 Testing & CI/CD

✏️ Documentation

... (truncated)

Commits


Updates github.com/vmware-tanzu/velero from 1.13.2 to 1.14.0

Release notes

Sourced from github.com/vmware-tanzu/velero's releases.

v1.14.0-rc.3

v1.14

Download

https://github.com/vmware-tanzu/velero/releases/tag/v1.14.0

Container Image

velero/velero:v1.14.0

Documentation

https://velero.io/docs/v1.14/

Upgrading

https://velero.io/docs/v1.14/upgrade-to-1.14/

Highlights

The maintenance work for kopia/restic backup repositories is run in jobs

Since velero started using kopia as the approach for filesystem-level backup/restore, we've noticed an issue when velero connects to the kopia backup repositories and performs maintenance, it sometimes consumes excessive memory that can cause the velero pod to get OOM Killed. To mitigate this issue, the maintenance work will be moved out of velero pod to a separate kubernetes job, and the user will be able to specify the resource request in "velero install".

Volume Policies are extended to support more actions to handle volumes

In an earlier release, a flexible volume policy was introduced to skip certain volumes from a backup. In v1.14 we've made enhancement to this policy to allow the user to set how the volumes should be backed up. The user will be able to set "fs-backup" or "snapshot" as value of “action" in the policy and velero will backup the volumes accordingly. This enhancement allows the user to achieve a fine-grained control like "opt-in/out" without having to update the target workload. For more details please refer to https://velero.io/docs/v1.14/resource-filtering/#supported-volumepolicy-actions

Node Selection for Data Movement Backup

In velero the data movement flow relies on datamover pods, and these pods may take substantial resources and keep running for a long time. In v1.14, the user will be able to create a configmap to define the eligible nodes on which the datamover pods are launched. For more details refer to https://velero.io/docs/v1.14/data-movement-backup-node-selection/

VolumeInfo metadata for restored volumes

In v1.13, we introduced volumeinfo metadata for backup to help velero CLI and downstream adopter understand how velero handles each volume during backup. In v1.14, similar metadata will be persisted for each restore. velero CLI is also updated to bring more info in the output of "velero restore describe".

"Finalizing" phase is introduced to restores

The "Finalizing" phase is added to the state transition flow to restore, which helps us fix several issues: The labels added to PVs will be restored after the data in the PV is restored via volumesnapshotter. The post restore hook will be executed after datamovement is finished.

Certificate-based authentication support for Azure

Besides the service principal with secret(password)-based authentication, Velero introduces the new support for service principal with certificate-based authentication in v1.14.0. This approach enables you to adopt a phishing resistant authentication by using conditional access policies, which better protects Azure resources and is the recommended way by Azure.

Runtime and dependencies

  • Golang runtime: v1.22.2
  • kopia: v0.17.0

Limitations/Known issues

  • For the external BackupItemAction plugins that take snapshots for PVs, such as vsphere plugin. If the plugin checks the value of the field "snapshotVolumes" in the backup spec as a criteria for snapshot, the settings in the volume policy will not take effect. For example, if the "snapshotVolumes" is set to False in the backup spec, but a volume meets the condition in the volume policy for "snapshot" action, because the plugin will not check the settings in the volume policy, the plugin will not take snapshot for the volume. For more details please refer to #7818

Breaking changes

  • CSI plugin has been merged into velero repo in v1.14 release. It will be installed by default as an internal plugin, and should not be installed via "–plugins " parameter in "velero install" command.
  • The default resource requests and limitations for node agent are removed in v1.14, to make the node agent pods have the QoS class of "BestEffort", more details please refer to #7391
  • There's a change in namespace filtering behavior during backup: In v1.14, when the includedNamespaces/excludedNamespaces fields are not set and the labelSelector/OrLabelSelectors are set in the backup spec, the backup will only include the namespaces which contain the resources that match the label selectors, while in previous releases all namespaces will be included in the backup with such settings. More details refer to #7105
  • Patching the PV in the "Finalizing" state may cause the restore to be in "PartiallyFailed" state when the PV is blocked in "Pending" state, while in the previous release the restore may end up being in "Complete" state. For more details refer to #7866

All Changes

... (truncated)

Commits
  • 2fc6300 Merge pull request #7860 from blackpiglet/update_e2e_for_1_14
  • 200f16e Merge branch 'release-1.14' into update_e2e_for_1_14
  • 0d36572 Merge pull request #7876 from reasonerjt/update-release-note-1.14
  • 08fea6e Merge branch 'release-1.14' into update-release-note-1.14
  • d20bd16 Skip parallel files upload and download test for Restic case.
  • bf778c7 Merge pull request #7875 from reasonerjt/fix-restore-crash-1.14
  • a650059 Update release note of 1.14
  • f61c8b9 Add checks for csisnapshot for vol_info population
  • 2136679 Merge pull request #7852 from reasonerjt/fix-7849-1.14
  • f6367ca Use PVC to track the CSI snapshot in restore
  • Additional commits viewable in compare view


Updates k8s.io/api from 0.30.1 to 0.30.2

Commits


Updates k8s.io/apiextensions-apiserver from 0.30.1 to 0.30.2

Commits
  • 2d2addc Update dependencies to v0.30.2 tag
  • 803669d Merge pull request #124676cici37/automated-cherry-pick-of-#124675
  • 5e9c693 Adding the feature gates to fix cost for VAP and webhook matchConditions.
  • See full diff in compare view


Updates k8s.io/apimachinery from 0.30.1 to 0.30.2

Commits


Updates k8s.io/apiserver from 0.30.1 to 0.30.2

Commits
  • 3b2ed79 Update dependencies to v0.30.2 tag
  • 7a3db50 Merge pull request #124676cici37/automated-cherry-pick-of-#124675
  • a30c80f Merge pull request #124802seantywork/automated-cherry-pick-of-#124662
  • 1ce5268 Updated & added visibility to apiserver x509 test certificates expiring this ...
  • e025ab4 Adding the feature gates to fix cost for VAP and webhook matchConditions.
  • See full diff in compare view


Updates k8s.io/cli-runtime from 0.30.1 to 0.30.2

Commits


Updates k8s.io/client-go from 0.30.1 to 0.30.2

Commits


Updates k8s.io/klog/v2 from 2.120.1 to 2.130.0

Release notes

Sourced from k8s.io/klog/v2's releases.

Prepare klog release for Kubernetes v1.31 (Take 1)

What's Changed

New Contributors

Full Changelog: https://github.com/kubernetes/klog/compare/v2.120.1...v2.130.0

Commits
  • 16c7d26 Merge pull request #401 from pohly/ktesting-warning-delay
  • cd24012 ktesting: tone down warning about leaked test goroutine
  • 2ee202a Merge pull request #404 from 1978629634/fsync-freelock
  • 79575d8 Do not acquire lock for file.Sync() fsync call
  • 7af45d6 Merge pull request #406 from pohly/linter
  • d008cfe examples: fix linter warning
  • ab53041 Merge pull request #402 from pohly/linter-issues
  • ff7c070 build: fix some linter warnings
  • 569bb3c Merge pull request #399 from jsoref/spelling-corporation
  • 200f43e chore(*): fix spelling of Intel Corporation
  • See full diff in compare view


Updates helm.sh/helm/v3 from 3.15.1 to 3.15.2

Release notes

Sourced from helm.sh/helm/v3's releases.

Helm v3.15.2 is a security (patch) release. Users are strongly recommended to update to this release.

The community keeps growing, and we'd love to see you there!

  • Join the discussion in Kubernetes Slack:
    • for questions and just to hang out
    • for discussing PRs, code, and bugs
  • Hang out at the Public Developer Call: Thursday, 9:30 Pacific via Zoom
  • Test, debug, and contribute charts: ArtifactHub/packages

Installation and Upgrading

Download Helm v3.15.2. The common platform binaries are here:

This release was signed with 672C 657B E06B 4B30 969C 4A57 4614 49C2 5E36 B98E and can be found at @​mattfarina keybase account. Please use the attached signatures for verifying this release using gpg.

The Quickstart Guide will get you going from there. For upgrade instructions or detailed installation notes, check the install guide. You can also use a script to install on any system with bash.

What's Next

  • 3.15.3 will contain only bug fixes and be released on July 10, 2024.
  • 3.16.0 is the next feature release and will be on September 11, 2024.

Changelog

  • fix: wrong cli description 1a500d5625419a524fdae4b33de351cc4f58ec35 (yyzxw)
  • fix typo in load_plugins.go 70b225c9abc014cfeb73f7c9f506b0e73e912b61 (yxxhero)
  • fix docs of DeployedAll b3640f196a2cf77136ab01295bffe76fa184991d (Daniel Strobusch)
  • Bump github.com/docker/docker 46e2ba0341d43e19493b2f90c86126da8ad8a64e (dependabot[bot])
  • bump oras minor version fb311d331f66f7f9153b5d0c7aa07a77bc9528ca (Austin Abro)
  • feat(load.go): add warning on requirements.lock 23552a7de6f45aacec47bc2bfe70de02b9d7ab70 (Aaron U'Ren)
Commits


Updates k8s.io/kubelet from 0.30.1 to 0.30.2

Commits


Updates k8s.io/metrics from 0.30.1 to 0.30.2

Commits


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions