Releases: vmware-tanzu/servicebinding
Release v0.7.0
Service Bindings for Kubernetes implements the Service Binding Specification for Kubernetes v1.0.
This is a preview release for developers to gain a familiarity with the core specification concepts.
This implementation provides support for:
- Provisioned Service
- Workload Projection
- Service Binding
- Direct Secret Reference
- Role-Based Access Control (RBAC)
The following are not implemented:
- Workload Resource Mapping
- Extensions including:
Equivalent capabilities from the v1.0.0-rc3 (servicebinding.io/v1alpha3) version of the spec are also supported. There are no significant API or runtime changes between v1alpha3 and v1beta1 versions.
Samples
Samples provide an overview of the features available with Service Bindings, including:
- Spring PetClinic with MySQL
- Controlled Resource
- Overridden Type and Provider
- Provisioned Service
- Multiple Bindings
Changelog
- [Feature] Add TAP aggregate roles (#228)
- [Feature] Support ServiceBinding.io/v1beta1 (#227)
- [Feature] Use RFC-3339 in log time stamp (#224)
Install/Upgrade
kapp is recommended to install/upgrade the Service Bindings CRDs and operator.
If upgrading from a release not installed with kapp, first remove the current install.
Then deploy Service Bindings:
kapp deploy -a service-bindings -f https://github.com/vmware-labs/service-bindings/releases/download/v0.7.0/service-bindings-0.7.0yaml
If you are unable to use kapp, service-bindings-0.7.0.yaml can be applied via tools like kubectl, but it will be harder to uninstall and upgrade.
Advanced installs
For users who need to install into an air-gapped cluster, or wish to limit their dependence on public image registries, an imgpkg bundle is available. For this install flow Carvel kapp, imgpkg and kbld are required.
Download the bundle to a location that has access to your image registry and cluster:
curl -L https://github.com/vmware-labs/service-bindings/releases/download/v0.7.0/service-bindings-bundle-0.7.0.tar -o service-bindings-bundle-0.7.0.tar
Relocate the bundle's images to your registry:
imgpkg copy --tar service-bindings-bundle-0.7.0.tar --to-repo <your-image-repository>
Pull the config files from the bundle:
mkdir bundle
imgpkg pull --bundle <your-image-repository> --output bundle
Finally, deploy Service Binding to your cluster:
kapp deploy -a service-bindings -f <(kbld -f ./bundle/config/service-bindings.yaml -f ./bundle/.imgpkg/images.yml)
The Carvel docs have more information about deploying to air-gapped environments.
kapp-controller managed installs
Preview support for kapp-controller with a Package definition in the service-bindings-package-0.7.0.yaml asset. Please see the Carvel docs for how to install a package on a cluster.
Uninstall
To remove service bindings from your cluster:
kapp delete -a service-bindings
Release v0.6.1
Service Bindings for Kubernetes implements the Service Binding Specification for Kubernetes. We are tracking changes to the spec as it approaches a stable release (currently targeting RC3). Backwards and forwards compatibility should not be expected for alpha versioned resources.
This is a preview release for developers to gain a familiarity with the core specification concepts. Neither the specification, nor implementation are stable.
This implementation provides support for:
- Provisioned Service
- Workload Projection
- Service Binding
- Direct Secret Reference
- Role-Based Access Control (RBAC)
The following are not supported: - Workload Resource Mapping
- Extensions including:
- Binding Secret Generation Strategies
Samples
Samples provide an overview of the features available with Service Bindings, including:
- Spring PetClinic with MySQL
- Controlled Resource
- Overridden Type and Provider
- Provisioned Service
- Multiple Bindings
Changelog
- [Fix] Clean redeploys with kapp (#208)
- [Fix] ServiceBinding reconciliation fails on k8s v1.22+ (#216)
Install/Upgrade
kapp is recommended to install/upgrade the Service Bindings CRDs and operator.
If upgrading from a release not installed with kapp, first remove the current install.
Then deploy Service Bindings:
kapp deploy -a service-bindings -f https://github.com/vmware-labs/service-bindings/releases/download/v0.6.1/service-bindings-0.6.1.yaml
If you are unable to use kapp, service-bindings-0.6.1.yaml can be applied via tools like kubectl, but it will be harder to uninstall and upgrade.
Advanced installs
For users who need to install into an air-gapped cluster, or wish to limit their dependence on public image registries, an imgpkg bundle is available. For this install flow Carvel kapp, imgpkg and kbld are required.
Download the bundle to a location that has access to your image registry and cluster:
curl -L https://github.com/vmware-labs/service-bindings/releases/download/v0.6.1/service-bindings-bundle-0.6.1.tar -o service-bindings-bundle-0.6.1.tar
Relocate the bundle's images to your registry:
imgpkg copy --tar service-bindings-bundle-0.6.1.tar --to-repo <your-image-repository>
Pull the config files from the bundle:
mkdir bundle
imgpkg pull --bundle <your-image-repository> --output bundle
Finally, deploy Service Binding to your cluster:
kapp deploy -a service-bindings -f <(kbld -f ./bundle/config/service-bindings.yaml -f ./bundle/.imgpkg/images.yml)
The Carvel docs have more information about deploying to air-gapped environments.
kapp-controller managed installs
Preview support for kapp-controller with a Package definition in the service-bindings-package-0.6.1.yaml asset. Please see the Carvel docs for how to install a package on a cluster.
Uninstall
To remove service bindings from your cluster:
kapp delete -a service-bindings
Release v0.6.0
Service Bindings for Kubernetes implements the Service Binding Specification for Kubernetes. We are tracking changes to the spec as it approaches a stable release (currently targeting pre-RC3). Backwards and forwards compatibility should not be expected for alpha versioned resources.
This is a preview release for developers to gain a familiarity with the core specification concepts. Neither the specification, nor implementation are stable.
This implementation provides support for:
- Provisioned Service
- Workload Projection
- Service Binding
- Direct Secret Reference
- Role-Based Access Control (RBAC)
The following are not supported:
- Workload Resource Mapping
- Extensions including:
Samples
Samples provide an overview of the features available with Service Bindings, including:
- Spring PetClinic with MySQL
- Controlled Resource
- Overridden Type and Provider
- Provisioned Service
- Multiple Bindings
Changelog
- [Fix] Fixed error reporting when service is not matched (#191)
Install/Upgrade
kapp is recommended to install/upgrade the Service Bindings CRDs and operator.
If upgrading from a release not installed with kapp, first remove the current install.
Then deploy Service Bindings:
kapp deploy -a service-bindings -f https://github.com/vmware-labs/service-bindings/releases/download/v0.6.0/service-bindings-0.6.0.yamlIf you are unable to use kapp, service-bindings-0.6.0.yaml can be applied via tools like kubectl, but it will be harder to uninstall and upgrade.
Advanced installs
For users who need to install into an air-gapped cluster, or wish to limit their dependence on public image registries, an imgpkg bundle is available. For this install flow Carvel kapp, imgpkg and kbld are required.
Download the bundle to a location that has access to your image registry and cluster:
curl -L https://github.com/vmware-labs/service-bindings/releases/download/v0.6.0/service-bindings-bundle-0.6.0.tar -o service-bindings-bundle-0.6.0.tarRelocate the bundle's images to your registry:
imgpkg copy --tar service-bindings-bundle-0.6.0.tar --to-repo <your-image-repository>Pull the config files from the bundle:
mkdir bundle
imgpkg pull --bundle <your-image-repository> --output bundleFinally, deploy Service Binding to your cluster:
kapp deploy -a service-bindings -f <(kbld -f ./bundle/service-bindings.yml -f ./bundle/.imgpkg/images.yml)The Carvel docs have more information about deploying to air-gapped environments.
kapp-controller managed installs
Preview support for kapp-controller with a Package definition in the service-bindings-package-0.6.0.yaml asset. Please see the Carvel docs for how to install a package on a cluster.
Uninstall
To remove service bindings from your cluster:
kapp delete -a service-bindings
Release v0.5.0
Service Bindings for Kubernetes implements the Service Binding Specification for Kubernetes. We are tracking changes to the spec as it approaches a stable release (currently targeting pre-RC3). Backwards and forwards compatibility should not be expected for alpha versioned resources.
This is a preview release for developers to gain a familiarity with the core specification concepts. Neither the specification, nor implementation are stable.
This implementation provides support for:
- Provisioned Service
- Workload Projection
- Service Binding
- Direct Secret Reference
- Role-Based Access Control (RBAC)
The following are not supported:
- Workload Resource Mapping
- Extensions including:
Samples
Samples provide an overview of the features available with Service Bindings, including:
- Spring PetClinic with MySQL
- Controlled Resource
- Overridden Type and Provider
- Provisioned Service
- Multiple Bindings
Changelog
- [Breaking] Change apiVersion from
service.binding/v1alpha2toservicebindings.io/v1alpha3(#173 #169) - [Feature] Carvel packaging with image pull secret (#176)
Install/Upgrade
kapp is recommended to install/upgrade the Service Bindings CRDs and operator.
If upgrading from a release not installed with kapp, first remove the current install.
Then deploy Service Bindings:
kapp deploy -a service-bindings -f https://github.com/vmware-labs/service-bindings/releases/download/v0.5.0/service-bindings-0.5.0.yamlIf you are unable to use kapp, service-bindings-0.5.0.yaml can be applied via tools like kubectl, but it will be harder to uninstall and upgrade.
Advanced installs
For users who need to install into an air-gapped cluster, or wish to limit their dependence on public image registries, an imgpkg bundle is available. For this install flow Carvel kapp, imgpkg and kbld are required.
Download the bundle to a location that has access to your image registry and cluster:
curl -L https://github.com/vmware-labs/service-bindings/releases/download/v0.5.0/service-bindings-bundle-0.5.0.tar -o service-bindings-bundle-0.5.0.tarRelocate the bundle's images to your registry:
imgpkg copy --tar service-bindings-bundle-0.5.0.tar --to-repo <your-image-repository>Pull the config files from the bundle:
mkdir bundle
imgpkg pull --bundle <your-image-repository> --output bundleFinally, deploy Service Binding to your cluster:
kapp deploy -a service-bindings -f <(kbld -f ./bundle/service-bindings.yml -f ./bundle/.imgpkg/images.yml)The Carvel docs have more information about deploying to air-gapped environments.
kapp-controller managed installs
Preview support for kapp-controller with a Package definition in the service-bindings-package-0.5.0.yaml asset. Please see the Carvel docs for how to install a package on a cluster.
Uninstall
To remove service bindings from your cluster:
kapp delete -a service-bindings
Release v0.4.0
Service Bindings for Kubernetes implements the Service Binding Specification for Kubernetes. We are tracking changes to the spec as it approaches a stable release (currently targeting RC2++). Backwards and forwards compatibility should not be expected for alpha versioned resources.
This is a preview release for developers to gain a familiarity with the core specification concepts. Neither the specification, nor implementation are stable.
This implementation provides support for:
- Provisioned Service
- Application Projection
- Service Binding
- Direct Secret Reference
- Role-Based Access Control (RBAC)
The following are not supported:
- Application Resource Mapping
- Extensions including:
Samples
Samples provide an overview of the features available with Service Bindings, including:
- Spring PetClinic with MySQL
- Controlled Resource
- Overridden Type and Provider
- Provisioned Service
- Multiple Bindings
Changelog
- [Breaking] Drop Custom Projection support (#123)
- [Breaking] Drop Mappings support (#134)
- [Breaking] Drop specifying containers by index (#158)
- [Feature] Offer Carvel kapp-controller Package and imgpkg Bundle for offline or managed installs (#160)
- [Feature] Use metav1.Conditions on status (#159)
- [Bug fix] Eliminated a condition where a resource could get stuck in an update-loop (#131)
- [Maintenance] updated dependencies to their latest stable versions
Install/Upgrade
kapp is recommended to install/upgrade the Service Bindings CRDs and operator.
If upgrading from a release not installed with kapp, first remove the current install.
Then deploy Service Bindings:
kapp deploy -a service-bindings -f https://github.com/vmware-labs/service-bindings/releases/download/v0.4.0/service-bindings-0.4.0.yamlIf you are unable to use kapp, service-bindings-0.4.0.yaml can be applied via tools like kubectl, but it will be harder to uninstall and upgrade.
Advanced installs
For users who need to install into an air-gapped cluster, or wish to limit their dependence on public image registries, an imgpkg bundle is available. For this install flow Carvel kapp, imgpkg and kbld are required.
Download the bundle to a location that has access to your image registry and cluster:
curl -L https://github.com/vmware-labs/service-bindings/releases/download/v0.4.0/service-bindings-bundle-0.4.0.tar -o service-bindings-bundle-0.4.0.tarRelocate the bundle's images to your registry:
imgpkg copy --tar service-bindings-bundle-0.4.0.tar --to-repo <your-image-repository>Pull the config files from the bundle:
mkdir bundle
imgpkg pull --bundle <your-image-repository> --output bundleFinally, deploy Service Binding to your cluster:
kapp deploy -a service-bindings -f <(kbld -f ./bundle/service-bindings.yml -f ./bundle/.imgpkg/images.yml)The Carvel docs have more information about deploying to air-gapped environments.
kapp-controller managed installs
Preview support for kapp-controller with a Package definition in the service-bindings-package-0.4.0.yaml asset. Please see the Carvel docs for how to install a package on a cluster.
Uninstall
To remove service bindings from your cluster:
kapp delete -a service-bindings
Release v0.3.0
Service Bindings for Kubernetes implements the Service Binding Specification for Kubernetes. We are tracking changes to the spec as it approaches a stable release (currently targeting RC2++). Backwards and forwards compatibility should not be expected for alpha versioned resources.
This is a preview release for developers to gain a familiarity with the core specification concepts. Neither the specification, nor implementation are stable.
This implementation provides support for:
- Provisioned Service
- Application Projection
- Service Binding
- Extensions including:
The Binding Secret Generation Strategies extension is not supported.
Changelog
- [Breaking] Removed
SERVICE_BINDINGS_ROOTenv var, useSERVICE_BINDING_ROOT(#61) - [Feature] Allow binding directly from secrets (#64)
- [Feature] Add label to ProvisionedService CRD to aid discovery (#80)
- [Bug fix] Cleanup injected values based on annotations and ServiceBindingProjection (#77)
- [Bug partial fix]Multi-ServiceBindings for a single application (#75)
- [Maintenance] updated dependencies to their latest stable versions
Install/Upgrade
kapp is recommended to install/upgrade the Service Bindings CRDs and operator.
If upgrading from a release not installed with kapp, first remove the current install.
Then deploy Service Bindings:
kapp deploy -a service-bindings -f https://github.com/vmware-labs/service-bindings/releases/download/v0.3.0/service-bindings-0.3.0.yaml
If you are unable to use kapp, service-bindings-core-0.3.0.yaml can be applied via tools like kubectl, but it will be harder to uninstall and upgrade.
Uninstall
To remove service bindings from your cluster:
kapp delete -a service-bindings
Release v0.2.1
This is the second release (amended) of the Service Bindings for Kubernetes project. It is an implementation of the Service Binding Specification for Kubernetes (1.0.0-rc2). This is a preview release for developers to gain a familiarity with the core specification concepts. Neither the specification, nor implementation are stable.
Notable Changes
The SERVICE_BINDINGS_ROOTenv var is deprecated in favor of SERVICE_BINDING_ROOT. Both values are supported in this release, however, SERVICE_BINDINGS_ROOT will be removed in a future release.
A typo in the spec, caused the name of the variable to be ambiguous. It is now uniformly defined as SERVICE_BINDING_ROOT.
Install/Upgrade
kapp is recommended to install/upgrade the Service Bindings CRDs and operator.
If upgrading from a release not installed with kapp, first remove the current install.
Then deploy Service Bindings:
kapp deploy -a service-bindings -f https://github.com/vmware-labs/service-bindings/releases/download/v0.2.1/service-bindings-0.2.1.yaml
If you are unable to use kapp, service-bindings-core-0.2.1.yaml can be applied via tools like kubectl, but it will be harder to uninstall and upgrade.
Uninstall
To remove service bindings from your cluster:
kapp delete -a service-bindings
Release v0.2.0
This is the second release of the Service Bindings for Kubernetes project.
It is an implementation of the Service Binding Specification for Kubernetes (1.0.0-rc2).
This is a preview release for developers to gain a familiarity with the core specification concepts.
Neither the specification, nor implementation are stable.
Notable Changes
- added support for the Custom Projection specification extension
- four new samples that each demonstrate different service binding capabilities
- refined status conditions to better reflect service binding nomenclature
- fixed an issue that could cause reconciliation errors when editing a
ServiceBindingresource - fixed an issue with long resource names exceeding the 63 character limit
- increased test coverage from ~3% to ~90%
Upgrade
If upgrading, delete all existing ServiceBindings and then remove the previous install:
kubectl delete servicebindings.service.binding --all --all-namespaces
kubectl delete -f https://github.com/vmware-labs/service-bindings/releases/download/v0.1.0/service-bindings-0.1.0.yaml
Then continue with the install instructions.
Install
To install the Service Bindings CRD and operator, apply the release yaml:
kubectl apply -f https://github.com/vmware-labs/service-bindings/releases/download/v0.2.0/service-bindings-0.2.0.yaml
Uninstall
To remove service bindings from your cluster:
kubectl delete servicebindings.service.binding --all --all-namespaces
kubectl delete -f https://github.com/vmware-labs/service-bindings/releases/download/v0.2.0/service-bindings-0.2.0.yaml
Release v0.1.0
This is the first release of the Service Bindings for Kubernetes project. It is an implementation of the Service Binding Specification for Kubernetes (1.0.0-rc2). This is a preview release for developers to gain a familiarity with the core specification concepts. Neither the specification, nor implementation are stable.
To install the Service Bindings CRD and operator, apply the release yaml:
kubectl apply -f https://github.com/vmware-labs/service-bindings/releases/download/v0.1.0/service-bindings-0.1.0.yaml