Skip to content

Releases: SAP/crossplane-provider-cloudfoundry

v0.3.3

29 Sep 14:38
ffab0af

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.3.2...v0.3.3

v0.3.2

06 Aug 14:32
53bc2b6

Choose a tag to compare

What's Changed

  • docs: refer to actual fields in ServiceInstance CRD by @johanngoltz in #70
  • chore: enable advanced CodeQL to enable manual trigger by @Lasserich in #84
  • chore: improve field descriptor documentation by @Lasserich in #88
  • docs: added CRD browser link to README.md by @sk31337 in #92
  • feat: enhance ServiceCredentialBinding for Rotation by @Noel-Ch in #89
  • feat: add enhanced validation rules by @dattito in #97
  • feat: make docker image updatable for apps by @dattito in #96
  • chore: remove potential confidential data from ServiceInstance spec by @dattito in #98

New Contributors

Full Changelog: v0.3.1...v0.3.2

v0.3.1

16 Jun 11:49
56bd5d9

Choose a tag to compare

What's Changed

  • chore: updating go-cfclient version by @gergely-szabo-sap in #9
  • fix: Setup controller for providerconfig by @dwlou in #59
  • Fix: resolve space name reference only when provided by @dwlou in #60
  • fix(typo): maintainer contact mail in provider package reference by @maximiliantech in #62
  • Add support for nested values in secret data by @dwlou in #71

New Contributors

Full Changelog: v0.3.0...v0.3.1

v0.3.0

14 May 10:07
6584a91

Choose a tag to compare

What's Changed

Migration Notes

Note: changing any of these steps, especially the installation of the providers will severely mess up your setup. Be absolutely sure to check every time before doing any kubectl commands that these resources in fact have the apiGroup that you want to modify.

Full Changelog: https://github.com/SAP/crossplane-provider-cloudfoundry/commits/v0.3.0

Migration Steps:

These steps are applicable if you are using the SAP inner-source provider (version v2.2.5 or earlier) and you want to migrate the existing custom resources to use this provider:

  1. Copy manifests of the existing resources to your local machine
kubectl get Organization,Space,App,Orgmembers,Route,ServiceInstance,ServiceKey,Spacemembers,ProviderConfig,Domain -o yaml | yq 'del(.. | .status?)' > legacy-cf-resources.yaml
  1. Pause reconciliation of all resources via annotation (Synced = False)
kubectl annotate Organization,Space,App,Orgmembers,Route,ServiceInstance,ServiceKey,Spacemembers,ProviderConfig,Domain --all=true crossplane.io/paused="true"
  1. (manually) Modify the manifests on your local machine from step 1, according to resource-specific migration guide in the CRD browser. (Note: migration guides are available only internally at SAP )
  2. Install New Provider Version (Github.com v0.3.0) in your cluster.
  3. Apply the modified manifests of the new version, e.g.,
kubectl apply -f modified-legacy-cf-resources.yaml
  1. Ensure that the newly applied resources are synced.
  2. Remove the finalizers of the paused legacy resources (!!! Make sure these are your old resources !!! e.g. kubectl describe <Resource> has to include API Version: cloudfoundry.btp.orchestrate.cloud.sap/v1alpha1)
for resource in $(kubectl get Organization,Space,App,Orgmembers,Route,ServiceInstance,ServiceKey,Spacemembers,ProviderConfig,Domain -o name); do
  kubectl patch $resource --type merge -p '{"metadata":{"finalizers":[]}}'
done
  1. Delete legacy resources
kubectl delete Organization,Space,App,Orgmembers,Route,ServiceInstance,ServiceKey,Spacemembers,ProviderConfig,Domain --all
  1. Delete legacy provider version