Releases: cloudfoundry/service-fabrik-broker
Interoperator Release v0.22.1
Bug fixes
- Removed dependency of cert in mTLS disabled quota app (#1572)
Supported K8S Version
- v1.20.x
- v1.21.x
- v1.22.x
How to deploy Interoperator
Interoperator requires helm version >= 3.0.0, and is not supported by helm 2.
To add service fabrik interoperator helm chart repo
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateDeploy SF Interoperator using helm
helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.22.1 interoperator interoperator-charts/interoperatorNOTE: cluster.host should be within the 63 character limit.
Deploy SFClusters, SFServices and SFPlans and Register with Interoperator
Please create sfcluster CRs and add reference to secret which contains the its kubeconfig.
For multi-cluster support, all corresponding sfcluster CRs need to be created and their kubeconfig needs to be supplied in the corresponding secret.
Please note that sfcluster, sfservice and sfplans need to be deployed in the same namespace where SF is deployed (default is interoperator).
Upgrade from the earlier releases(special handling, downtime if any)
To add service fabrik interoperator helm chart repo if not already added
# Assuming the repo name is chosen as interoperator-charts
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateHelm upgrade should take care of upgrading to the latest release.
# Assuming current helm release name is interoperator
helm --namespace interoperator upgrade -i --wait --set cluster.host=sf.ingress.< clusterdomain > --version 0.22.1 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.22.0
New features/Bug fixes
- Added SAP XRS registration support for broker & quota applications (#1505)
- Added mTLS support in quota applications (#1505)
- Documentation improvements (#1495)
- Security updates (#1516, #1481)
Supported K8S Version
- v1.22.x
- v1.21.x
- v1.20.x
How to deploy Interoperator
Interoperator requires helm version >= 3.0.0, and is not supported by helm 2.
To add service fabrik interoperator helm chart repo
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateDeploy SF Interoperator using helm
helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.22.0 interoperator interoperator-charts/interoperatorNOTE: cluster.host should be within the 63 character limit.
Deploy SFClusters, SFServices and SFPlans and Register with Interoperator
Please create sfcluster CRs and add reference to secret which contains the its kubeconfig.
For multi-cluster support, all corresponding sfcluster CRs need to be created and their kubeconfig needs to be supplied in the corresponding secret.
Please note that sfcluster, sfservice and sfplans need to be deployed in the same namespace where SF is deployed (default is interoperator).
Upgrade from the earlier releases(special handling, downtime if any)
To add service fabrik interoperator helm chart repo if not already added
# Assuming the repo name is chosen as interoperator-charts
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateHelm upgrade should take care of upgrading to the latest release.
# Assuming current helm release name is interoperator
helm --namespace interoperator upgrade -i --wait --set cluster.host=sf.ingress.< clusterdomain > --version 0.22.0 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.21.0
New features/Bug fixes
- Added mTLS support for quota application (#1494)
- Improved multi-cluster-deployer controller performance (#1498)
- Documentation improvements (#1490, #1489, #1430, #1332)
Supported K8S Version
- 1.22.x
- 1.21.x
- 1.20.x
How to deploy Interoperator
Interoperator requires helm version >= 3.0.0, and is not supported by helm 2.
To add service fabrik interoperator helm chart repo
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateDeploy SF Interoperator using helm
helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.21.0 interoperator interoperator-charts/interoperatorNOTE: cluster.host should be within the 63 character limit.
Deploy SFClusters, SFServices and SFPlans and Register with Interoperator
Please create sfcluster CRs and add reference to secret which contains the its kubeconfig.
For multi-cluster support, all corresponding sfcluster CRs need to be created and their kubeconfig needs to be supplied in the corresponding secret.
Please note that sfcluster, sfservice and sfplans need to be deployed in the same namespace where SF is deployed (default is interoperator).
Upgrade from the earlier releases(special handling, downtime if any)
It is recommended to upgrade Interoperator release to latest before moving to Kubernetes v1.22.x. The helm upgrade from versions earlier than v0.19.0 to latest breaks in Kubernetes v1.22.x. This is due to the helms' handling of deprecated Kubernetes APIs.
To add service fabrik interoperator helm chart repo if not already added
# Assuming the repo name is chosen as interoperator-charts
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateHelm upgrade should take care of upgrading to the latest release.
# Assuming current helm release name is interoperator
helm --namespace interoperator upgrade -i --wait --set cluster.host=sf.ingress.< clusterdomain > --version 0.21.0 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.20.0
New features/Bug fixes
- Added support for rotation of SFCluster Kubeconfig (#1482)
Supported K8S Version
- v1.20.x
- v1.21.x
- v1.22.x
How to deploy Interoperator
Interoperator requires helm version >= 3.0.0, and is not supported by helm 2.
To add service fabrik interoperator helm chart repo
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateDeploy SF Interoperator using helm
helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.20.0 interoperator interoperator-charts/interoperatorNOTE: cluster.host should be within the 63 character limit.
Deploy SFClusters, SFServices and SFPlans and Register with Interoperator
Please create sfcluster CRs and add reference to secret which contains the its kubeconfig.
For multi-cluster support, all corresponding sfcluster CRs need to be created and their kubeconfig needs to be supplied in the corresponding secret.
Please note that sfcluster, sfservice and sfplans need to be deployed in the same namespace where SF is deployed (default is interoperator).
Upgrade from the earlier releases(special handling, downtime if any)
It is recommended to upgrade Interoperator release to v0.20.0 before moving to Kubernetes v1.22.x. The helm upgrade from versions earlier than v0.19.0 to v0.20.0 breaks in Kubernetes v1.22.x. This is due to the helms' handling of deprecated Kubernetes APIs.
To add service fabrik interoperator helm chart repo if not already added
# Assuming the repo name is chosen as interoperator-charts
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateHelm upgrade should take care of upgrading to the latest release.
# Assuming current helm release name is interoperator
helm --namespace interoperator upgrade -i --wait --set cluster.host=sf.ingress.< clusterdomain > --version 0.20.0 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.19.0
New features/Bug fixes
- Added support for K8s v1.22 (#1472). Interoperator drops support of K8s v1.18.x and below.
- Provided mTLS auth for Interoperator broker (#1464)
- Bug fixes (#1463)
Supported K8S Version
- v1.20.x
- v1.21.x
- v1.22.x
How to deploy Interoperator
Interoperator requires helm version >= 3.0.0, and is not supported by helm 2.
To add service fabrik interoperator helm chart repo
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateDeploy SF Interoperator using helm
helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.19.0 interoperator interoperator-charts/interoperatorNOTE: cluster.host should be within the 63 character limit.
Deploy SFClusters, SFServices and SFPlans and Register with Interoperator
Please create sfcluster CRs and add reference to secret which contains the its kubeconfig.
For multi-cluster support, all corresponding sfcluster CRs need to be created and their kubeconfig needs to be supplied in the corresponding secret.
Please note that sfcluster, sfservice and sfplans need to be deployed in the same namespace where SF is deployed (default is interoperator).
Upgrade from the earlier releases(special handling, downtime if any)
It is recommended to upgrade Interoperator release to v0.19.0 before moving to Kubernetes v1.22.x. The helm upgrade from earlier version to v0.19.0 breaks in Kubernetes v1.22.x. This is due to the helms' handling of deprecated Kubernetes APIs.
To add service fabrik interoperator helm chart repo if not already added
# Assuming the repo name is chosen as interoperator-charts
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateHelm upgrade should take care of upgrading to the latest release.
# Assuming current helm release name is interoperator
helm --namespace interoperator upgrade -i --wait --set cluster.host=sf.ingress.< clusterdomain > --version 0.19.0 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.18.0
New features/Bug fixes
- Inhibited updation of up-to-date instances when AutoUpdateInstances is enabled in sfplan (#1459)
- Added support for custom metadata in catalog (#1455)
- Bug fixes (#1443, #1444, #1445)
- Security updates (#1442)
Supported K8S Version
- v1.18.x
- v1.19.x
- v1.20.x
How to deploy Interoperator
Interoperator requires helm version >= 3.0.0, and is not supported by helm 2.
To add service fabrik interoperator helm chart repo
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateDeploy SF Interoperator using helm
helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.18.0 interoperator interoperator-charts/interoperatorNOTE: cluster.host should be within the 63 character limit.
Deploy SFClusters, SFServices and SFPlans and Register with Interoperator
Please create sfcluster CRs and add reference to secret which contains the its kubeconfig.
For multi-cluster support, all corresponding sfcluster CRs need to be created and their kubeconfig needs to be supplied in the corresponding secret.
Please note that sfcluster, sfservice and sfplans need to be deployed in the same namespace where SF is deployed (default is interoperator).
Upgrade from the earlier releases(special handling, downtime if any)
To add service fabrik interoperator helm chart repo if not already added
# Assuming the repo name is chosen as interoperator-charts
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateHelm upgrade should take care of upgrading to the latest release.
# Assuming current helm release name is interoperator
helm --namespace interoperator upgrade -i --wait --set cluster.host=sf.ingress.< clusterdomain > --version 0.18.0 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.17.1
New features/Bug fixes
- Added support for allow_context_updates (#1417)
- Bug fixes (#1426, #1434)
- Security updates (#1435, #1433, #1427)
Supported K8S Version
- v1.18.x
- v1.19.x
- v1.20.x
How to deploy Interoperator
Interoperator requires helm version >= 3.0.0, and is not supported by helm 2.
To add service fabrik interoperator helm chart repo
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateDeploy SF Interoperator using helm
helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.17.1 interoperator interoperator-charts/interoperatorNOTE: cluster.host should be within the 63 character limit.
Deploy SFClusters, SFServices and SFPlans and Register with Interoperator
Please create sfcluster CRs and add reference to secret which contains the its kubeconfig.
For multi-cluster support, all corresponding sfcluster CRs need to be created and their kubeconfig needs to be supplied in the corresponding secret.
Please note that sfcluster, sfservice and sfplans need to be deployed in the same namespace where SF is deployed (default is interoperator).
Upgrade from the earlier releases(special handling, downtime if any)
To add service fabrik interoperator helm chart repo if not already added
# Assuming the repo name is chosen as interoperator-charts
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateHelm upgrade should take care of upgrading to the latest release.
# Assuming current helm release name is interoperator
helm --namespace interoperator upgrade -i --wait --set cluster.host=sf.ingress.< clusterdomain > --version 0.17.1 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.17.0
New features/Bug fixes
- Enhanced error response during provisioning failures (#1345)
- Added HorizontalPodAutoscaling(HPA) support for interoperator (#1399)
- Added metric for service binding state (#1358)
- Quota App checks for new SFPlans and SFServices in regular intervals (#1404)
- Documentation on Fluent Bit configuration (#1375)
- Upgraded Node.js version to v16.8 (#1413)
Supported K8S Version
- v1.20.x
- v1.19.x
- v1.18.x
How to deploy Interoperator
Interoperator requires helm version >= 3.0.0, and is not supported by helm 2.
To add service fabrik interoperator helm chart repo
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateDeploy SF Interoperator using helm
helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.17.0 interoperator interoperator-charts/interoperatorNOTE: cluster.host should be within the 63 character limit.
Deploy SFClusters, SFServices and SFPlans and Register with Interoperator
Please create sfcluster CRs and add reference to secret which contains the its kubeconfig.
For multi-cluster support, all corresponding sfcluster CRs need to be created and their kubeconfig needs to be supplied in the corresponding secret.
Please note that sfcluster, sfservice and sfplans need to be deployed in the same namespace where SF is deployed (default is interoperator).
Upgrade from the earlier releases(special handling, downtime if any)
To add service fabrik interoperator helm chart repo if not already added
# Assuming the repo name is chosen as interoperator-charts
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateHelm upgrade should take care of upgrading to the latest release.
# Assuming current helm release name is interoperator
helm --namespace interoperator upgrade -i --wait --set cluster.host=sf.ingress.< clusterdomain > --version 0.17.0 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.16.0
New features/Bug fixes
- Restricts off-boarding the SFCluster when there are active service instances (#1308)
- Added metric for cluster status (#1338)
- Improvements in quota checks and logging (#1346, #1328)
- Documentation improvements (#1299, #1325, #1309, #1315)
- Upgraded Node.js version to v16.3 (#1344)
- Fixed adding empty maintainance_info in SFPlans (#1324)
- Minor bug fixes (#1323, #1286, #1308)
Supported K8S Version
- v1.18.x
- v1.19.x
- v1.20.x
How to deploy Interoperator
Interoperator requires helm version >= 3.0.0, and is not supported by helm 2.
To add service fabrik interoperator helm chart repo
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateDeploy SF Interoperator using helm
helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.16.0 interoperator interoperator-charts/interoperatorNOTE: cluster.host should be within the 63 character limit.
Deploy SFClusters, SFServices and SFPlans and Register with Interoperator
Please create sfcluster CRs and add reference to secret which contains the its kubeconfig.
For multi-cluster support, all corresponding sfcluster CRs need to be created and their kubeconfig needs to be supplied in the corresponding secret.
Please note that sfcluster, sfservice and sfplans need to be deployed in the same namespace where SF is deployed (default is interoperator).
Upgrade from the earlier releases(special handling, downtime if any)
To add service fabrik interoperator helm chart repo if not already added
# Assuming the repo name is chosen as interoperator-charts
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateHelm upgrade should take care of upgrading to the latest release.
# Assuming current helm release name is interoperator
helm --namespace interoperator upgrade -i --wait --set cluster.host=sf.ingress.< clusterdomain > --version 0.16.0 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.15.0
New features/Bug fixes
- Support for asynchronous Service Bindings #1310
- Support for osb version
2.16(#1307, #1311, #1273, #1300, #1298, #1294 ) - Cleanup timed out Bindings #1311
- Minor bug fixes #1300
Supported K8S Version
- v1.17.x
- v1.18.x
- v1.19.x
- v1.20.x
How to deploy Interoperator
Interoperator requires helm version >= 3.0.0, and is not supported by helm 2.
To add service fabrik interoperator helm chart repo
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateDeploy SF Interoperator using helm
helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.15.0 interoperator interoperator-charts/interoperatorNOTE: cluster.host should be within the 63 character limit.
Deploy SFClusters, SFServices and SFPlans and Register with Interoperator
Please create sfcluster CRs and add reference to secret which contains the its kubeconfig.
For multi-cluster support, all corresponding sfcluster CRs need to be created and their kubeconfig needs to be supplied in the corresponding secret.
Please note that sfcluster, sfservice and sfplans need to be deployed in the same namespace where SF is deployed (default is interoperator).
Upgrade from the earlier releases(special handling, downtime if any)
To add service fabrik interoperator helm chart repo if not already added
# Assuming the repo name is chosen as interoperator-charts
helm repo add interoperator-charts https://cloudfoundry-incubator.github.io/service-fabrik-broker/helm-charts
helm repo updateHelm upgrade should take care of upgrading to the latest release.
# Assuming current helm release name is interoperator
helm --namespace interoperator upgrade -i --wait --set cluster.host=sf.ingress.< clusterdomain > --version 0.15.0 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.