Releases: crossplane-contrib/provider-kubernetes
v1.1.0
What's New
- Added
SafeStartcapability for Crossplane v2 - Added support for authenticating with AWS Web Identity Credentials in EKS. #405
- Fixed an issue with watches for namespaced
ObjectMRs.
What's Changed
- Bump uptest to v2 by @sergenyalcin in #395
- Remove xpkg.upbound.io references in README by @bobh66 in #397
- fix(owners): set correct mail-address by @haarchri in #402
- Bump dependencies by @sergenyalcin in #403
- feat: add SafeStart capability by @erhancagirici in #401
- fix watches for Namespaced Objects by @binarycode in #391
- Update codeowners by @sergenyalcin in #406
- feat(aws): implement AWSWebIdentityCredentials by @haarchri in #405
New Contributors
- @binarycode made their first contribution in #391
Full Changelog: v1.0.0...v1.1.0
v1.0.0
Release v1.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
kubernetes.m.crossplane.ioAPI group. - All new APIs are at version
v1beta1. - ProviderConfig
ProviderConfig.kubernetes.m.crossplane.iois now namespace-scoped.- A new cluster-scoped
ClusterProviderConfig.kubernetes.m.crossplane.ioresource was added; new MRs can reference eitherProviderConfigorClusterProviderConfigviaspec.providerConfigRef.kind. spec.providerConfigRefdefaults toClusterProviderConfigwith namedefaultwhen omitted.
spec.writeConnectionSecretToRefand 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.publishConnectionDetailsTois 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, andexamplesnow have scoped subdirectories:clusterandnamespaced.- 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.xenvironments:- Both cluster-scoped and namespace-scoped CRDs will be installed; namespace-scoped CRDs cannot be composed in
v1.x. SafeStartwill be disabled.
- Both cluster-scoped and namespace-scoped CRDs will be installed; namespace-scoped CRDs cannot be composed in
- When upgrading from
v1.xproviders, review all breaking resource API changes noted above. The package itself is Crossplanev1.xcompatible, but there can be resources that have API changes that need adjustment in your control plane.
Upgrade Guide
- Review all affected resources listed under Breaking API Changes.
- Update manifests to reflect renamed/removed properties.
- For Crossplane
v2.xusers:- Ensure secret and reference configurations align with the new namespace-scoped MR behavior.
- Decide whether to use
ProviderConfigorClusterProviderConfig.
- Remove any
spec.publishConnectionDetailsTousage. - Validate repository structure changes if maintaining custom resource configurations.
What's Changed
- build: pass robot token credentials to publishing to mirror registry by @jbw976 in #368
- Mark Objects as deterministic external name by @Kidswiss in #367
- add basic plumbing for provider startup checks. by @jastang in #374
- crossplane v2: namespaced MRs by @erhancagirici in #380
- Update go version to 1.24.6 [Security] by @turkenf in #382
New Contributors
Full Changelog: v0.18.0...v1.0.0
v0.18.0
v0.17.1
What's Changed
- Add go.cachedir and go.mod.cachedir to Makefile by @turkenf in #339
- Integrate reusable workflow for provider package publishing by @turkenf in #341
- feat: update go to 1.22.8 by @AbrohamLincoln in #310
- Bump golang.org/x/crypto to v0.33.0 by @turkenf in #351
- Fixes an issue when enable-server-side-apply and sanitize-secrets are turned on by @ravilr in #350
- Remove unused backport workflows by @turkenf in #352
New Contributors
- @turkenf made their first contribution in #339
- @AbrohamLincoln made their first contribution in #310
Full Changelog: v0.17.0...v0.17.1
v0.17.0
What's Changed
- doc: add v0.16.0 package new address by @Mathges in #312
- Update go.mod dependencies [SECURITY] by @sergenyalcin in #328
- Add DesiredStateChanged event filter to filter out status updates by @ravilr in #329
- Update go version to 1.22.12 [SECURITY] by @sergenyalcin in #336
- [Backport release-0.17] Add go.cachedir and go.mod.cachedir to Makefile by @github-actions in #340
New Contributors
Full Changelog: v0.16.3...v0.17.0
v0.16.3
This release includes updates to the go.mod file to address security vulnerabilities.
What's Changed
- (release-0.16): Update go version to 1.22.12 [SECURITY] by @sergenyalcin in #335
Full Changelog: v0.16.2...v0.16.3
v0.15.3
This release includes updates to the go.mod file to address security vulnerabilities.
What's Changed
- (release-0.15): Update go version to 1.22.12 [SECURITY] by @sergenyalcin in #334
Full Changelog: v0.15.2...v0.15.3
v0.14.4
This release includes updates to the go.mod file to address security vulnerabilities.
What's Changed
- (release-0.14): Update go version to 1.22.12 [SECURITY] by @sergenyalcin in #333
Full Changelog: v0.14.3...v0.14.4
v0.16.2
This release updates golang.org/x/net to v0.33.0 to fix CVE-2024-45338
What's Changed
- (release-0.16): Update go.mod dependencies [SECURITY] by @sergenyalcin in #327
Full Changelog: v0.16.1...v0.16.2
v0.16.1
This release includes updates to the go.mod file to address security vulnerabilities.
What's Changed
- (release-0.16): Update go.mod dependencies [SECURITY] by @sergenyalcin in #324
Full Changelog: v0.16.0...v0.16.1