Skip to content

Releases: upbound/provider-vault

v3.0.1

29 Sep 11:16
ccc7ff3

Choose a tag to compare

This patch release fixes the wrong API reference of ClusterProviderConfig. This will resolve the connection to the provider issue when the ClusterProviderConfig is used. Details are in #102 #103.

What's Changed

  • [Backport release-3.0] fix(apis): fix Items in ClusterProviderConfigList by @github-actions[bot] in #104

Full Changelog: v3.0.0...v3.0.1

v3.0.0

18 Sep 15:44
f44625d

Choose a tag to compare

Release v3.0.0

Caution

This release introduces breaking changes and significant internal upgrades. Please review the release notes thoroughly, make the necessary changes to your manifests, and test thoroughly before upgrading.

Before using any Crossplane v2 capabilities in the provider, we encourage you to familiarize yourself with the changes in v2.

This release introduces:

  • Compatibility with Crossplane v2
  • Support for Crossplane v2 namespace-scoped Managed Resources (MRs) alongside existing cluster-scoped MRs.
  • Upgrade to crossplane-runtime v2.0.0.
  • Upgrade to Upjet v2.0.0.
  • Removal of External Secret Store support.

Please review the breaking changes carefully before upgrading.

Namespace-scope MR Support (Crossplane v2-only)

  • New namespace-scoped MR APIs are available under the vault.m.upbound.io API group.
  • All new APIs are at version v1beta1.
  • ProviderConfig
    • ProviderConfig.vault.m.upbound.io is now namespace-scoped.
    • A new cluster-scoped ClusterProviderConfig.vault.m.upbound.io resource was added; new MRs can reference either ProviderConfig or ClusterProviderConfig via spec.providerConfigRef.kind.
    • spec.providerConfigRef defaults to ClusterProviderConfig with name default when omitted.
  • spec.writeConnectionSecretToRef and sensitive parameter refs (e.g., spec.forProvider.fooSecretRef) in namespace-scoped MRs are now local secret references (if no namespace is specified, it defaults to the MR's namespace).
  • Cross-resource references are now namespace-scoped by default, however, cross-namespace references are allowed.
  • This provider will serve both the new namespace-scoped and cluster-scoped APIs.

Note

Cluster-scoped MRs do NOT implement the above changes and continue operating as before.

Removed Features

  • External Secret Store support has been removed from all MRs (spec.publishConnectionDetailsTo is no longer available) as the feature has been removed in Crossplane v2.

Note

The removed feature is the External Secret Store, which allowed storing connection details outside the cluster (e.g., in Vault). Connection secrets for managed resources remain available for storing connection details in Kubernetes Secrets.

Other Notable Changes

  • SafeStart capability has been added (Crossplane v2-only): Controllers start once their CRD is installed.
  • Repository structure changes:
    • apis, controllers, and examples now have scoped subdirectories: cluster and namespaced.
    • Resource configurations are also scoped; updates must be applied to both where relevant.
    • Examples for namespace-scoped MRs are included.

Note

This PR duplicates most of the controller logic and apis for namespaced MRs with several namespace-specific code modified. A refactoring of types and controllers should follow-up.

Backward Compatibility Notes

  • This provider can be installed in Crossplane v1.x environments:
    • Both cluster-scoped and namespace-scoped CRDs will be installed; namespace-scoped CRDs cannot be composed in v1.x.
    • SafeStart will be disabled.
  • When upgrading from v1.x providers, review all breaking resource API changes noted above. The package itself is Crossplane v1.x compatible, but there can be resources that have API changes that need adjustment in your control plane.

Upgrade Guide

  1. Review all affected resources listed under Breaking API Changes.
  2. Update manifests to reflect renamed/removed properties.
  3. For Crossplane v2.x users:
    • Ensure secret and reference configurations align with the new namespace-scoped MR behavior.
    • Decide whether to use ProviderConfig or ClusterProviderConfig.
  4. Remove any spec.publishConnectionDetailsTo usage.
  5. Validate repository structure changes if maintaining custom resource configurations.

What's Changed

  • [main] Update go.mod dependencies [SECURITY] by @turkenf in #92
  • add basic plumbing for provider startup checks. by @jastang in #96
  • crossplane v2: introduce namespaced MRs with TF provider v5.2.1 by @erhancagirici in #100

New Contributors

Full Changelog: v2.2.0...v3.0.0

v2.2.2

21 Aug 15:35
71cc3e4

Choose a tag to compare

This release updates go mod dependencies to fix the following CVEs:

What's Changed

  • [release-2.2]: Update go.mod dependencies [SECURITY] by @turkenf in #99

Full Changelog: v2.2.1...v2.2.2

v2.2.1

25 Jun 10:54
07ceb5b

Choose a tag to compare

What's Changed

  • [release-2.2] Update go.mod dependencies [SECURITY] by @turkenf in #91

Full Changelog: v2.2.0...v2.2.1

v2.2.0

12 Jun 19:45
1258bc5

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v2.1.3...v2.2.0

v2.1.1

11 Feb 13:21
78fb20a

Choose a tag to compare

This release includes updates to the go.mod file to address security vulnerabilities.

What's Changed

Full Changelog: v2.1.0...v2.1.1

v2.1.0

23 Jan 14:32
681aa00

Choose a tag to compare

This release includes updates to the go.mod file to address security vulnerabilities.

What's Changed

  • Fix authentication configuration options by @m1so in #50
  • Remove publish-artifacts job from the CI pipeline and fix security vulnerabilities by @turkenf in #53

New Contributors

Full Changelog: v2.0.1...v2.1.0

v2.0.1

06 Jan 20:49
35de732

Choose a tag to compare

This release contains a fix about authentication configuration options.

What's Changed

  • [Backport release-2.0] Fix authentication configuration options by @github-actions in #51

New Contributors

  • @github-actions made their first contribution in #51

Full Changelog: v2.0.0...v2.0.1

v2.0.0

11 Dec 16:17
fd00fdf

Choose a tag to compare

This release contains two important changes:

  • Switching to no-fork architecture
  • Bumping the underlying provider version to: v4.4.0

What's Changed

New Contributors

Full Changelog: v1.0.0...v2.0.0

v1.0.0

24 May 18:51
f6c7b1d

Choose a tag to compare

What's Changed

  • fix: broken JSON in ProviderConfig example by @jaylevin in #34
  • fix: Rename Namespace MR to VaultNamespace by @jaylevin in #35

Breaking Changes

please check #35

Full Changelog: v0.4.0...v1.0.0