1.4.0
Changed
-
Removed duplicate code from
Klutch, as the same logic is now sourced fromKlutchio. -
Updated image link and version for
provider-anynines.Breaking Change The
provider-anyninesimage has been updated, requiring a reapplication with the correct repository path and version.Old:
public.ecr.aws/w5n9a2g2/anynines/provider-anynines:v1.X.XNew:
public.ecr.aws/w5n9a2g2/klutch/provider-anynines:1.3.2Please 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 Clusteris nowApp ClusterandManagement Clusteris nowControl Plane Cluster. -
Renamed backend resources for bindings. Changed the namespace used for bindings on the App Clusters from
kube-bindtoklutch-bind.This change automatically applies to new bindings.
Breaking Change this change also changes the namespace of the
konnectordeployment. Please make sure that only one deployment ofkonnectoris running. Please delete the old konnector deployment by runningkubectl delete -n kube-bind deployment konnectorbefore 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
-
Create a new
ServiceAccountcalledklutch-binderin eachcluster-<xyz>namespace without an additional suffix. -
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 -
Copy the token and replace the old token in the
kubeconfigsecret within the same namespace -
Copy the content of the
kubeconfigsecret from the provider cluster tokubeconfig-<abc>secret in theklutch-bindnamespace 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.