Release notes

v0.8.1

Release Date: November 15, 2022

  • libssl3 has been updated to 3.0.2-0ubuntu1.7 to resolve CVE-2022-3786.
  • libssl3 has been updated to 3.0.2-0ubuntu1.7 to resolve CVE-2022-3602.

v0.8.0

Release Date: October 11, 2022

v0.7.1

Release Date: July 12, 2022

  • Services Toolkit now integrates with Amazon RDS using the ACK Operator. See Consuming AWS RDS on Tanzu Application Platform with AWS Controllers for Kubernetes (ACK).

  • Services Toolkit now integrates with Amazon RDS by using Crossplane. See Consuming AWS RDS on Tanzu Application Platform with Crossplane.

  • New ClusterInstanceClass supports service instance abstraction. It is available using tanzu service classes list in v0.3.0 of the Services plug-in for Tanzu CLI.

  • You can now use the InstanceQuery API to discover claimable resources. It is available using tanzu service claimable list --class CLASS in v0.3.0 of the Services plug-in for Tanzu CLI.

  • ResourceClaims no longer mutate service resources with an annotation to mark a claimed resource. Instead it uses Kubernetes Leases.

  • ResourceClaims no longer require the update permission when adding new service resources to Tanzu Application Platform.

  • ResourceClaims now aggregate on ClusterRoles for service resources with the standard servicebinding.io/controller: "true" label from the Service Binding specification for Kubernetes This label is recommended over the existing resourceclaims.services.apps.tanzu.vmware.com/controller: "true" label, although the old label continues to work as expected.

  • Performance enhancements to ResourceClaim controller tracker.

  • All Services Toolkit components now conform to Tanzu Application Platform logging standards.

  • Deprecation warning: tanzu service types list and tanzu service instances list commands are now deprecated. These commands are hidden from help text but remain functional if invoked. VMware intends to support these commands for either two additional minor releases (v0.6.0 of the CLI plug-in) or after one year (2023-07-12), whichever comes later. VMware recommends using tanzu service class and tanzu service claimable commands in place of tanzu service type and tanzu service instance from now on.

Bug Fixes

  • ResourceClaims no longer overwrite existing secrets on cross namespace claims.
  • Fix ResourceClaims incorrectly logging resource requests as part of tracking.
  • ResourceClaims .status.ClaimedResourceRef.Namespace is now set for same namespace claims.

v0.6.0

Release Date: April 12, 2022

  • Introduced default aggregating ClusterRoles for Tanzu Application Platform’s App Editors, App Viewers, and App Operators.
  • The ResourceClaim and ResourceClaimPolicy CRD category resourceclaims was removed to avoid clashes with the ResourceClaim resource plural.
  • Fixed kubectl table output of ResourceClaimPolicy.
  • All Services Toolkit pods now adhere to Restricted Pod Security Standards.
  • Services plug-in for Tanzu CLI v0.2.0 includes the following changes:
    • Allows the management of ResourceClaims using tanzu service claims <list/get/create/delete>.
    • Alpha Warnings are now output to stderr instead of stdout.

v0.5.1

Release Date: March 3, 2022

  • Fixed a race condition issue that might lead to a failure of the services-toolkit controller manager when a new ResourceClaim is being created whilst another is being deleted.
  • Fixed an issue that caused kapp-controller to unnecessarily reconcile continuously.
  • Services plug-in for Tanzu CLI at v0.1.2 now supports interactions with GCP clusters.

v0.5.0

Release Date: January 11, 2022

  • Resource Claims now support cross namespace claiming by using ResourceClaimPolicy objects.
  • Resource Claims are now exclusive. Multiple ResourceClaim objects can not claim a single service resource.
  • Services Toolkit, specifically Resource Claims, now depends on at least v0.5.0 of carvel-secretgen-controller in GitHub.
  • Do not block claim deletion when it can not find GVR.

Breaking changes

  • Rename ClusterServiceResource to ClusterResource

  • Move ClusterResource, ClusterExampleUsage and ResourceClaim to services.apps.tanzu.vmware.com APIGroup

  • Move DownstreamClusterLink, UpstreamClusterLink, APIExportRoleBinding, APIResourceImport and ClusterAPIGroupImport to projection.apiresources.multicluster.x-tanzu.vmware.com APIGroup

  • Move ClusterResourceExportMonitor, ClusterResourceImportMonitor, ResourceExportMonitorBinding, ResourceImportMonitorBinding, SecretExport and SecretImport to replication.apiresources.multicluster.x-tanzu.vmware.com APIGroup

  • Add the label prefix replication.apiresources.multicluster.x-tanzu.vmware.com for the monitored-resource-* labels of ClusterResourceExportMonitor and ClusterResourceImportMonitor

  • Rename the Resource Claims finalizer from claim.services.apps.tanzu.vmware.com/finalizer to resourceclaims.services.apps.tanzu.vmware.com/finalizer. Existing ResourceClaims must be updated to remove the old finalizer to be deleted.

  • Rename the Resource Claims aggregation ClusterRole label from services.apps.tanzu.vmware.com/aggregate-to-resource-claims: "true" to resourceclaims.services.apps.tanzu.vmware.com/controller: "true". Existing aggregated roles must be updated to have the new label.

  • Edit all deployment resources naming to use services-toolkit rather than the outdated scp-toolkit.

check-circle-line exclamation-circle-line close-line
Scroll to top icon