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:
  • Custom Projection
  • Direct Secret Reference
  • Role-Based Access Control (RBAC)

The Binding Secret Generation Strategies extension is not supported.

Changelog

• [Breaking] Removed SERVICE_BINDINGS_ROOT env var, use SERVICE_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