search

weaveworks / gitopssets-controller

Manages the GitOpsSet CRDs.
Apache License 2.0
9 stars 5 forks source link

Bump github.com/weaveworks/cluster-controller from 1.4.1 to 1.6.0 #167

Closed dependabot[bot] closed 10 months ago

dependabot[bot] commented 10 months ago

Bumps github.com/weaveworks/cluster-controller from 1.4.1 to 1.6.0.

Release notes

Sourced from github.com/weaveworks/cluster-controller's releases.

v1.6.0

What's Changed

GitopsClusters are now validated, with the requirement to have either a .spec.capiClusterRef or .spec.secretRef.

Invalid GitopsClusters are blocked by the Kubernetes CRD validation mechanism.

This may cause existing GitopsCluster resources to be invalid.

Full Changelog: https://github.com/weaveworks/cluster-controller/compare/v1.5.5...v1.6.0

v1.5.5

What's Changed

When a GitopsCluster references a secret rather than a CAPI cluster, the status message will be updated to reflect this.

Full Changelog: https://github.com/weaveworks/cluster-controller/compare/v1.5.4...v1.5.5

v1.5.4

What's Changed

GitopsCluster resources can now be annotated to indicate that they do not need the finalizer to block removal of a cluster while the secret exists.

This functionality exists to prevent leaving high-privilege Secrets around in the cluster, but it can cause problems with automated cascading deletion.

Adding an annotation clusters.gitops.weave.works/no-secret-finalizer with any value to the GitopsCluster will enable this.

Full Changelog: https://github.com/weaveworks/cluster-controller/compare/v1.5.3...v1.5.4

v1.5.3

What's Changed

This is just a dependencies update to avoid security issues.

New Contributors

Full Changelog: https://github.com/weaveworks/cluster-controller/compare/v1.5.2...v1.5.3

v1.5.2

What's Changed

Full Changelog: https://github.com/weaveworks/cluster-controller/compare/v1.5.1...v1.5.2

... (truncated)

Commits
  • 1d0c71d Validate CRD Spec fields (#83)
  • 829b7bc ci: Added weekly check of GitHub Actions dependencies
  • 61fbfdc ci: Bump actions versions and pin them to SHAs
  • 9fb4a67 Merge pull request #81 from weaveworks/add-status-message
  • 3d177d3 Add status message when referencing secrets.
  • 8d9b882 Merge pull request #79 from weaveworks/move-constant-to-api
  • 4a424eb Expose the no-secret-finalizer Annotation name
  • c4afe68 Merge pull request #78 from weaveworks/allow-secret-retention
  • b19afc5 Allow removal when referenced secret exists.
  • de46e39 Merge pull request #77 from weaveworks/bump-deps
  • Additional commits viewable in compare view


Dependabot compatibility score

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 this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)