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 update
Deploy SF Interoperator using helm
helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.23.3 interoperator interoperator-charts/interoperator
NOTE: 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 update
Helm 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/interoperator
Refer detailed upgrade docs for more info.