Skip to main content

1.4.0

· 2 min read

Changed

  • Removed duplicate code from Klutch, as the same logic is now sourced from Klutchio.

  • Updated image link and version for provider-anynines.

    Breaking Change The provider-anynines image has been updated, requiring a reapplication with the correct repository path and version.

    Old: public.ecr.aws/w5n9a2g2/anynines/provider-anynines:v1.X.X

    New: public.ecr.aws/w5n9a2g2/klutch/provider-anynines:1.3.2

    Please reapply using the following command:

    kubectl apply -f https://raw.githubusercontent.com/anynines/klutchio/refs/heads/main/crossplane-api/deploy/provider-anynines.yaml
  • Updated naming conventions. Consumer Cluster is now App Cluster and Management Cluster is now Control Plane Cluster.

  • Renamed backend resources for bindings. Changed the namespace used for bindings on the App Clusters from kube-bind to klutch-bind.

    This change automatically applies to new bindings.

    Breaking Change this change also changes the namespace of the konnector deployment. Please make sure that only one deployment of konnector is running. Please delete the old konnector deployment by running

    kubectl delete -n kube-bind deployment konnector

    before creating any new bindings. Creating a new binding will deploy the konnector to the new namespace.

    Breaking Change The service account created on the provider cluster, and all role bindings have been updated. In order to migrate please

    1. Create a new ServiceAccount called klutch-binder in each cluster-<xyz> namespace without an additional suffix.

    2. Create a new secret to hold the servic account token in the same namespace:

      apiVersion: v1
      data:
      kind: Secret
      metadata:
      annotations:
      kubernetes.io/service-account.name: klutch-binder
      kubernetes.io/service-account.uid: <service account UID>
      name: klutch-binder
      namespace: cluster-<xyz>
      type: kubernetes.io/service-account-token
    3. Copy the token and replace the old token in the kubeconfig secret within the same namespace

    4. Copy the content of the kubeconfig secret from the provider cluster to kubeconfig-<abc> secret in the klutch-bind namespace in the App Cluster.

  • Replace native patch&transform patching in compositions with composite functions

Added

  • Experimental support for exposing a9s data services via TCP proxy. This can be opted in to by using the composition a9s-service-binding-proxy. Installation of a8s service guard is required.