Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deps: update dependency kubernetes-sigs/kustomize to v5 #769

Merged
merged 1 commit into from
Apr 20, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 5, 2023

Mend Renovate

This PR contains the following updates:

Package Update Change
kubernetes-sigs/kustomize major v4.5.7 -> v5.0.1

Release Notes

kubernetes-sigs/kustomize

v5.0.1

Compare Source

Bug fixes

#​5048: Fix a regression causing warning messages to be intermingled with Kustomize build output on stdout
#​5073: Revert strict decoding of Kustomization files due to regression in anchor handling

Dependencies

#​5088: Update kyaml to v0.14.1
#​5089: Update cmd/config to v0.11.1
#​5090: Update api to v0.13.2

v5.0.0

Compare Source

🎉The Kustomize team is so excited to release version 5.0! 🎉

This release is packed with exciting features and improvements. The full list is below, but here are some of our favorites:

  • kustomize localize: a brand new alpha command that localizes remote content. You’ll be able to build the localized kustomization without network access and performance delays! Please give it a try and let us know what you think in #​4996. See more details in its entry under Features below.
  • support for four new Helm fields, by popular request: additionalValuesFiles, skipTests, apiVersions and nameTemplate
  • A new sortOptions kustomization field gives you fine-grained control over resource ordering in build output
  • Significant performance improvements!

A HUGE thank you to everyone who contributed to this release! 🙇‍♀️

Breaking changes

  • #​4930: Remove deprecated alpha cfg and fn commands: kustomize fn sink, kustomize fn source, kustomize fn wrap, kustomize fn xargs, kustomize cfg annotate, kustomize cfg create-setter, kustomize cfg delete-setter, kustomize cfg delete-substitution, kustomize cfg create-substitution, kustomize cfg fmt, kustomize cfg init, kustomize cfg list-setters, kustomize cfg merge, kustomize cfg merge3, kustomize cfg set.
  • #​4983, #​4954, #​4922, #​4900, #​4885: Warning: We made major improvements to the maintainability of the URL-parsing code for remote URLs, fixing several bugs in the process. We have test coverage for backwards-compatibility with all documented supported URLs, but if you experience a regression with a remote URL, please file an issue.
    • #​4985: If you previously included .git in an AWS or Azure URL, we will no longer automatically remove that suffix. You may need to add an extra / to replace the .git for the URL to properly resolve.
    • #​4954: Drop support for using gh: as a host (e.g. gh:kubernetes-sigs/kustomize). We were unable to find any usage of or basis for this and believe it may have been targeting a custom gitconfig shorthand syntax.
  • #​4911: Drop support for a very old, legacy style of patches. patches used to be allowed to be used as an alias for patchesStrategicMerge in kustomize v3. You now have to use patchesStrategicMerge explicitly, or update to the new syntax supported by patches. See examples in the PR description of #​4911.
  • #​4731: Remove a potential build-time side-effect in ConfigMapGenerator and SecretGenerator, which loaded values from the local environment under some circumstances, breaking kustomize build's side-effect-free promise. While this behavior was never intended, we deprecated it and are announcing it as a breaking change since it existed for a long time. See also the Eschewed Features documentation.
  • #​4929: Duplicate fields in Kustomization files will now result in an error instead of them silently being ignored in an undefined order. NOTE: This was reverted in release v5.0.1.

Deprecations

  • #​4723, #​4923: We are deprecating the following kustomization fields. These fields will never be removed from the kustomize.config.k8s.io/v1beta1 Kustomization API, but they will not be included in the kustomize.config.k8s.io/v1 Kustomization API. When Kustomization v1 is available, we will announce the deprecation of the v1beta1 version. There will be at least two releases between deprecation and removal of Kustomization v1beta1 support from the kustomize CLI, and removal itself will happen in a future major version bump.
    • patchesStrategicMerge. Please use patches instead
    • patchesJson6902. Please use patches instead
    • vars. Please use replacements instead.
    • imageTags. This is an alias for images, please switch to images.
  • #​5000: The --short flag for kustomize version is deprecated.
  • #​4954: Deprecate RepoSpec git:: prefix, which is invalid. Kustomize currently strips it, but will stop doing so in a future release.

Features

Bug Fixes/performance improvements

  • #​4863: Fix RepoSpec query extraction
  • #​4985: Remove forced .git suffix in RepoSpec
    • Arbitrary git servers that do not follow the .git directory naming convention can now be used with Kustomize.
    • The .git suffix no longer incorrectly appears in origin annotations in some cases.
  • #​4791, #​4944, #​4809: Significant performance improvements from refactoring metadata handling in the api and kyaml modules
  • #​4789: Replacements now throw errors on invalid targets
  • #​4890: Fix null value handling when applying strategic merge patches. A null in the patch is a deletion directive, but a null in the target should be preserved.
  • #​4654: The working directory of exec KRM-style functions is now the kustomization root that called it. This fixes a bug where KRM exec function executables were looked up incorrectly in base/overlay contexts.
  • #​4751, #​4805: When using labels.includeTemplates, create template/metadata if not present.
  • #​4834: Respect options.disableNameSuffixHash in configmap and secret generator in overlays
  • #​4919: Allow overriding of name suffix transformer default configuration
  • #​4895: Name references to local-only objects are now correctly resolved before the objects are removed from the set to be printed.

Dependencies

  • #​4877: Update minimum Go version to Go 1.19
  • #​4830: Update kyaml's dependency swag to v0.22.3
  • #​4960: Update sigs.k8s.io/yaml to v1.3.0
  • #​4965: Bump k8s.io/kube-openapi to remove archived dependency
  • #​4889: All module net and text dependent package CVE-2022-41717 and CVE-2022-32149 vulnerabilities
  • #​4970: Replace github/pkg/errors with sigs.k8s.io/kustomize/kyaml/errors

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Vienna, 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. View repository job log here.

@codecov
Copy link

codecov bot commented Feb 5, 2023

Codecov Report

Merging #769 (63491a0) into main (4c96e98) will decrease coverage by 0.08%.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #769      +/-   ##
==========================================
- Coverage   59.02%   58.94%   -0.08%     
==========================================
  Files         128      128              
  Lines       10040    10040              
==========================================
- Hits         5926     5918       -8     
- Misses       3897     3902       +5     
- Partials      217      220       +3     

see 3 files with indirect coverage changes

Flag Coverage Δ
certificate-operator 64.15% <ø> (ø)
component-tests 59.92% <ø> (ø)
lifecycle-operator 78.24% <ø> (ø)
metrics-operator 77.57% <ø> (ø)
scheduler 21.75% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@thschue thschue added the on hold Do not merge yet label Feb 7, 2023
@renovate renovate bot force-pushed the renovate/kubernetes-sigs-kustomize-5.x branch from 491eedf to 0eb0e60 Compare March 3, 2023 13:29
@netlify
Copy link

netlify bot commented Mar 3, 2023

Deploy Preview for keptn-lifecycle-toolkit ready!

Name Link
🔨 Latest commit b138b9a
🔍 Latest deploy log https://app.netlify.com/sites/keptn-lifecycle-toolkit/deploys/6413a61a79d6990007dcc733
😎 Deploy Preview https://deploy-preview-769--keptn-lifecycle-toolkit.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@sonarcloud
Copy link

sonarcloud bot commented Mar 17, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

Signed-off-by: Renovate Bot <bot@renovateapp.com>
@renovate renovate bot force-pushed the renovate/kubernetes-sigs-kustomize-5.x branch from 7e53568 to 63491a0 Compare April 17, 2023 09:16
@sonarcloud
Copy link

sonarcloud bot commented Apr 17, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@mowies mowies merged commit 33107ac into main Apr 20, 2023
@mowies mowies deleted the renovate/kubernetes-sigs-kustomize-5.x branch April 20, 2023 11:01
@keptn-bot keptn-bot mentioned this pull request Apr 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants