Releases: cloudfoundry/service-fabrik-broker
Interoperator Release v0.27.1
New features/Bug fixes
- Dependency upgrades (#2055, #2038, #2030, #2023, #1978, #2013, #2010)
- Fixed intermittent problem with service instance update flow (#2060)
- Added support for namespace label propagation to sister clusters during instance creation (#2060)
- Better handling of sfplan update events (#2037)
- Resolved inconclusive error message for json schema validation of service instance parameters (#2035)
Supported K8S Version
- v1.25.x
- v1.26.x
- v1.27.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.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.27.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.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.27.1 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.27.0
New features/Bug fixes
- Support kubeconfig rotation of clusters for Gardener users (#1982, #1998)
- Dependency upgrades (#1986)
- Fixed static check issues (#1994)
- Documentation improvements (#1844, #1684, #1665)
Supported K8S Version
- v1.25.x
- v1.26.x
- v1.27.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.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.27.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.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.27.0 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.26.0
New features/Bug fixes
3ff9572: Updating broker/Interoperator docker image versions:0.26.0
7ffd7d4: Remove unused watch events in metrics controller (#1926)
b0e1e99: update logs
8b6569f: fix and reset service instance count in sfcluster (#1914)
e5a889f: updated k8s library versions (#1913)
fd972c0: Bump k8s api and client-go to 0.25.13
0253c2d: bump apimachinery from 0.25.3 to 0.25.13 (#1905)
c55cb6b: Update npm version
388930b: update expressjwt package
3ead45e: update go package to 1.21
1c3bbd7: Fix logging error in sfservicebindingmetrics (#1899)
7fe18ba: Adding Unit Tests for Metrics Controller (#1897)
14581f4: Alicloud increase max_key options for list operation
d81d018: [Metering] During plan update send start event after stop event (#1890)
1083db3: [IOP] Updating doc for new metrics controllers (#1889)
Supported K8S Version
- v1.24.x
- v1.25.x
- v1.26.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.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.26.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.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.26.0 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.25.1
New features/Bug fixes
Added new instances and binding metrics (#1847)
Fixed static check issues (#1850)
Supported K8S Version
- v1.23.x
- v1.24.x
- v1.25.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.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.25.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.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.25.1 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.24.0
New features/Bug fixes
Added support for custom namespace labels (#1823)
Logging parameters are made configurable (#1785)
Securely storing quota regions credentials (#1810)
Fixed service type as ClusterIP (#1762)
Dependency upgrades (#1812)
Removed unused Lerna library (#1793)
Supported K8S Version
- v1.23.x
- v1.24.x
- v1.25.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.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.24.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.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.24.0 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.23.4
New features/Bug fixes
Supported K8S Version
- v1.21.x
- v1.22.x
- v1.23.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.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.23.4 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.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.23.4 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.23.3
New features/Bug fixes
Supported K8S Version
- v1.21.x
- v1.22.x
- v1.23.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.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.23.3 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.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.23.3 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.23.2
New features/Bug fixes
- Logging enhancements (#1629, #1630)
- Use uncached client to list pods/nodes (#1630)
- Improved customisation in dashboard url template (#1603)
- Dependency upgrades(#1604)
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.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.23.2 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.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.23.2 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.23.1
New features/Bug fixes
- Fixed issues with off-boarding of sfplan when no active instances are present (#1598)
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.23.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)
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.23.1 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.
Interoperator Release v0.23.0
New features/Bug fixes
- Restricts off-boarding of sfplan when there are active service instances (#1532)
- Better handling of failed orphan binding (#1534)
- Dependency upgrades (#1549, #1550, #1551, #1552, #1554, #1555, #1556, #1557, #1558, #1559, #1560, #1561, #1562, #1563, #1564, #1569, #1587, #1590, #1591)
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.23.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.23.0 interoperator interoperator-charts/interoperatorRefer detailed upgrade docs for more info.