Releases: vmware-tanzu/servicebinding
Release v0.9.4
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
What's Changed
- fix: Add SecurityContextConstraints to enable running in restricted environments by @odinnordico in #297 #299
Full Changelog: v0.9.3...v0.9.4
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-tanzu/servicebinding/releases/download/v0.9.4/service-bindings-0.9.4.yaml
If you are unable to use kapp
, service-bindings-0.9.4.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-tanzu/servicebinding/releases/download/v0.9.4/service-bindings-bundle-0.9.4.tar -o service-bindings-bundle-0.9.4.tar
Relocate the bundle's images to your registry:
imgpkg copy --tar service-bindings-bundle-0.9.4.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.9.3.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.9.3
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
What's Changed
- fix: Update securityContext config in deployment to enable running in restricted environments by @odinnordico in #292
- ci: Update carvel-dev setup action by @odinnordico in #295
Full Changelog: v0.9.2...v0.9.3
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-tanzu/servicebinding/releases/download/v0.9.3/service-bindings-0.9.3.yaml
If you are unable to use kapp
, service-bindings-0.9.3.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-tanzu/servicebinding/releases/download/v0.9.3/service-bindings-bundle-0.9.3.tar -o service-bindings-bundle-0.9.3.tar
Relocate the bundle's images to your registry:
imgpkg copy --tar service-bindings-bundle-0.9.3.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.9.3.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.9.2
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
What's Changed
- chore: version updated to snapshot after release cut by @anibmurthy in #256
- chore: Bump github.com/emicklei/go-restful from 2.9.5+incompatible to 2.16.0+incompatible by @dependabot in #260
- chore: Bump go.uber.org/zap from 1.23.0 to 1.24.0 by @dependabot in #258
- chore: Update ko base image by @anibmurthy in #261
- chore: Add k8s version 1.26.0 to CI test pipeline by @anibmurthy in #262
- chore: Bump github.com/aws/aws-sdk-go from 1.31.12 to 1.34.0 by @dependabot in #263
- chore: Bump github.com/prometheus/client_golang from 1.9.0 to 1.11.1 by @dependabot in #264
- chore: Bump golang.org/x/text from 0.3.4 to 0.3.8 by @dependabot in #265
- chore: Modules updated to address cves by @anibmurthy in #267
- chore: Bump golang.org/x/net from 0.0.0-20220722155237-a158d28d115b to 0.7.0 by @dependabot in #266
- chore: add Github Token to CI step to avoid running into rate limiting by @anibmurthy in #268
- chore: Updated ko base image to run-jammy-tiny:0.1.44 by @anibmurthy in #269
- chore: updated ko base image to run-jammy-static:0.0.28 by @anibmurthy in #270
- chore: Moving to ghcr repository for packaging by @anibmurthy in #271
- build: Fix for multiple kapp changes by @rashedkvm in #274
- chore: Bump github.com/stretchr/testify from 1.8.1 to 1.8.2 by @dependabot in #272
- Dependency version bumped by @rashedkvm in #275
- chore: Bump actions/setup-go from 3 to 4 by @dependabot in #273
- chore: Bump k8s.io/api from 0.20.0-alpha.2 to 0.20.16-rc.0 by @dependabot in #277
- chore: updated ko base image to run-jammy-static:0.0.49 by @anibmurthy in #282
- chore: Bump github.com/stretchr/testify from 1.8.2 to 1.8.4 by @dependabot in #280
Full Changelog: v0.9.0...v0.9.2
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-tanzu/servicebinding/releases/download/v0.9.2/service-bindings-0.9.2.yaml
If you are unable to use kapp
, service-bindings-0.9.2.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-tanzu/servicebinding/releases/download/v0.9.2/service-bindings-bundle-0.9.2.tar -o service-bindings-bundle-0.9.2.tar
Relocate the bundle's images to your registry:
imgpkg copy --tar service-bindings-bundle-0.9.2.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.9.2.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.9.1
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
What's Changed
- chore: Bump github.com/emicklei/go-restful from 2.9.5+incompatible to 2.16.0+incompatible by @dependabot in #260
- chore: Bump go.uber.org/zap from 1.23.0 to 1.24.0 by @dependabot in #258
- chore: Add k8s version 1.26.0 to CI test pipeline by @anibmurthy in #262
- chore: Bump github.com/aws/aws-sdk-go from 1.31.12 to 1.34.0 by @dependabot in #263
- chore: Bump github.com/prometheus/client_golang from 1.9.0 to 1.11.1 by @dependabot in #264
- chore: Bump golang.org/x/text from 0.3.4 to 0.3.8 by @dependabot in #265
- chore: Modules updated to address cves by @anibmurthy in #267
- chore: Bump golang.org/x/net from 0.0.0-20220722155237-a158d28d115b to 0.7.0 by @dependabot in #266
- chore: updated ko base image to run-jammy-static:0.0.28 by @anibmurthy in #270
- chore: Moving to ghcr repository for packaging by @anibmurthy in #271
Full Changelog: v0.9.0...v0.9.1
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-tanzu/servicebinding/releases/download/v0.9.1/service-bindings-0.9.1.yaml
If you are unable to use kapp
, service-bindings-0.9.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-tanzu/servicebinding/releases/download/v0.9.1/service-bindings-bundle-0.9.1.tar -o service-bindings-bundle-0.9.1.tar
Relocate the bundle's images to your registry:
imgpkg copy --tar service-bindings-bundle-0.9.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.9.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.8.2
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
What's Changed
- chore: Bump github.com/emicklei/go-restful from 2.9.5+incompatible to 2.16.0+incompatible by @dependabot in #260
- chore: Bump go.uber.org/zap from 1.23.0 to 1.24.0 by @dependabot in #258
- chore: Bump github.com/aws/aws-sdk-go from 1.31.12 to 1.34.0 by @dependabot in #263
- chore: Bump github.com/prometheus/client_golang from 1.9.0 to 1.11.1 by @dependabot in #264
- chore: Bump golang.org/x/text from 0.3.4 to 0.3.8 by @dependabot in #265
- chore: Modules updated to address cves by @anibmurthy in #267
- chore: Bump golang.org/x/net from 0.0.0-20220722155237-a158d28d115b to 0.7.0 by @dependabot in #266
- chore: updated ko base image to run-jammy-static:0.0.28 by @anibmurthy in #270
- chore: Moving to ghcr repository for packaging by @anibmurthy in #271
Full Changelog: v0.8.1...v0.8.2
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-tanzu/servicebinding/releases/download/v0.8.2/service-bindings-0.8.2.yaml
If you are unable to use kapp
, service-bindings-0.8.2.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-tanzu/servicebinding/releases/download/v0.8.2/service-bindings-bundle-0.8.2.tar -o service-bindings-bundle-0.8.2.tar
Relocate the bundle's images to your registry:
imgpkg copy --tar service-bindings-bundle-0.8.2.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.8.2.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.9.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
What's Changed
- chore: Bump github.com/google/go-cmp from 0.5.8 to 0.5.9 by @dependabot in #250
- Updates matrix with k8s version 1.25.2 by @shaheerkootteeri in #251
- chore: add inclusive terminology scan and error fixes (test) by @anibmurthy in #253
- chore: Bump github.com/stretchr/testify from 1.8.0 to 1.8.1 by @dependabot in #252
- chore: ko updated to digest reference; release candidate by @anibmurthy in #255
New Contributors
- @shaheerkootteeri made their first contribution in #251
- @anibmurthy made their first contribution in #253
Full Changelog: v0.8.0...v0.9.0
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-tanzu/servicebinding/releases/download/v0.9.0/service-bindings-0.9.0.yaml
If you are unable to use kapp
, service-bindings-0.9.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-tanzu/servicebinding/releases/download/v0.9.0/service-bindings-bundle-0.9.0.tar -o service-bindings-bundle-0.9.0.tar
Relocate the bundle's images to your registry:
imgpkg copy --tar service-bindings-bundle-0.9.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.9.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.8.1
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
What's Changed
- Use updated Paketo Base image that has fix for OpenSSL 3 High Vulnerabilities mentioned on OpenSSL Website
Full Changelog: v0.8.0...v0.8.1
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-tanzu/servicebinding/releases/download/v0.8.1/service-bindings-0.8.1.yaml
If you are unable to use kapp
, service-bindings-0.8.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-tanzu/servicebinding/releases/download/v0.8.1/service-bindings-bundle-0.8.1.tar -o service-bindings-bundle-0.8.1.tar
Relocate the bundle's images to your registry:
imgpkg copy --tar service-bindings-bundle-0.8.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.8.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.8.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
What's Changed
- chore: Bump github.com/stretchr/testify from 1.7.2 to 1.7.4 by @dependabot in #241
- chore: Bump github.com/stretchr/testify from 1.7.4 to 1.7.5 by @dependabot in #242
- chore: Bump github.com/stretchr/testify from 1.7.5 to 1.8.0 by @dependabot in #243
- Upgrade GO version to 1.18 by @rashedkvm in #245
- chore: Bump go.uber.org/zap from 1.21.0 to 1.22.0 by @dependabot in #244
- Update k8s matrix with k8s v1.24+ by @rashedkvm in #246
- chore: Bump go.uber.org/zap from 1.22.0 to 1.23.0 by @dependabot in #248
- Updating base image to paketobuildpacks/run-jammy-tiny by @rashedkvm in #249
Full Changelog: v0.7.2...v0.8.0
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-tanzu/servicebinding/releases/download/v0.8.0/service-bindings-0.8.0.yaml
If you are unable to use kapp
, service-bindings-0.8.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-tanzu/servicebinding/releases/download/v0.8.0/service-bindings-bundle-0.8.0.tar -o service-bindings-bundle-0.8.0.tar
Relocate the bundle's images to your registry:
imgpkg copy --tar service-bindings-bundle-0.8.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.8.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.7.2
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
What's Changed
- Bump github.com/stretchr/testify from 1.7.0 to 1.7.1 by @dependabot in #231
- Fixed troubleshooting documentation by @odinnordico in #202
- Bump codecov/codecov-action from 2 to 3 by @dependabot in #232
- Bump github.com/google/go-cmp from 0.5.7 to 0.5.8 by @dependabot in #233
- Switch petclinic image to ghcr by @scothis in #234
- chore: cve-fix gopkg.in/yaml.v3 by @rashedkvm in #235
- chore: cve-fix gopkg.in/yaml.v3 by @rashedkvm in #236
- Bump github.com/stretchr/testify from 1.7.1 to 1.7.2 by @dependabot in #237
- New ClusterRole
service-binding-provisioned-service
, updated label selectors by @rashedkvm in #239 - Updated test k8s-matrix by @rashedkvm in #240
Full Changelog: v0.7.1...v0.7.2
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-tanzu/servicebinding/releases/download/v0.7.2/service-bindings-0.7.2.yaml
If you are unable to use kapp
, service-bindings-0.7.2.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-tanzu/servicebinding/releases/download/v0.7.2/service-bindings-bundle-0.7.2.tar -o service-bindings-bundle-0.7.2.tar
Relocate the bundle's images to your registry:
imgpkg copy --tar service-bindings-bundle-0.7.2.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.2.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.7.1
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
- [Fixed] Resource pluralization for postgres (#230)
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-tanzu/servicebinding/releases/download/v0.7.1/service-bindings-0.7.1.yaml
If you are unable to use kapp
, service-bindings-0.7.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-tanzu/servicebinding/releases/download/v0.7.1/service-bindings-bundle-0.7.1.tar -o service-bindings-bundle-0.7.1.tar
Relocate the bundle's images to your registry:
imgpkg copy --tar service-bindings-bundle-0.7.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.7.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