Interoperator Release v0.14.0

New features/Bug fixes

• Fix container names in helm chart #1291
• Propagate response from operator on Bind failure #1289
• Update nodejs dependencie #1290
• Deploy Operator-api and quota app only if they are enabled #1141
• Fix metrics scrape in sister cluster #1141
• Make pod resources configurable per deployment #1141
• Fix connection issues causing mcd failures #1141
• Adding checks for concurrent operations #1262
• Get Endpoints for instance and binding #1239
• Rename the provisioner deployment #1280

Supported K8S Version

• v1.17
• v1.18
• v1.19

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 update

Deploy SF Interoperator using helm

helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.14.0 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)

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 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.14.0 interoperator interoperator-charts/interoperator

Refer detailed upgrade docs for more info.

Interoperator Release v0.13.0

New features/Bug fixes since v0.12.0

• Added multiple region support for quota #126
• Primary cluster id made configurable instead of hard coded value #1236
• Fix mismatched schema fields in SFPlan #1247
• Lazy Replication of SFService and SFPlan #1261
• Migrating to yarn berry #1193
• Update nodejs dependencies #1203 #1160 #1276
• Introduce multiple workers for replicators #1270
• Fix staticcheck failures (#1208)

Supported K8S Version

• v1.17.x
• v1.18.x
• v1.19.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 update

Deploy SF Interoperator using helm

helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.13.0 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)

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 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.13.0 interoperator interoperator-charts/interoperator

Refer detailed upgrade docs for more info.

Interoperator Release v0.12.3

New features/Bug fixes

744b30b: Updating broker/Interoperator docker image versions:0.12.3
5fd13cf: Merge pull request #1265 from cloudfoundry-incubator/revert-1238-provisioner
0014c28: Revert Rename the provisioner deployment (#1238)
0c30827: Merge pull request #1248 from cloudfoundry-incubator/anoopjb-patch-1
f8da4a2: Remove --force option from upgrade instructions

Supported K8S Version

• v1.17.x
• v1.17.x
• v1.17.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 update

Deploy SF Interoperator using helm

helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.12.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)

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 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.12.3 interoperator interoperator-charts/interoperator

Refer detailed upgrade docs for more info.

Interoperator Release v0.12.2

New features/Bug fixes

1838586: Updating broker/Interoperator docker image versions:0.12.2
9aaa417: Merge pull request #1247 from cloudfoundry-incubator/Fix-Schema
ea61727: Fixing test
b154432: Fix interoperator schema
ebf19d2: Rename the provisioner deployment (#1238)
8b8403f: reading primary cluster id from the configmap instead of hardcoded value (#1236)
502acc4: Update Lerna badge with Yarn in Readme.md (#1244)
83b9db4: Update README.md (#1243)

Supported K8S Version

• v1.17.x
• v1.17.x
• v1.17.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 update

Deploy SF Interoperator using helm

helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.12.2 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)

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 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.12.2 interoperator interoperator-charts/interoperator

Refer detailed upgrade docs for more info.

Interoperator Release v0.12.1

New features/Bug fixes

83dce79: Updating broker/Interoperator docker image versions:0.12.1
89658c3: Merge pull request #1207 from anujbansal16/master
5ac8479: Fixing source not available issue on coveralls (#1221)
2d5edad: distributing external deps across modules and migrating to yarn berry (#1193)
ab92408: Fix staticcheck failures (#1208)
212e1fd: Update Node version in Broker Dockerfile (#1203)
a65c5e5: Updated sfplan crds for mismatched schema property
1a99423: Add URL and HTTP Method to HttpClient error log (#1199)
cf029a7: Delete scheduled backup improvements (#1183)
d663c71: Updating dockerode from 2.2.10 to 3.2.1 (#1160)

Supported K8S Version

• v1.17.x
• v1.17.x
• v1.17.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 update

Deploy SF Interoperator using helm

helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.12.1 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)

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 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.12.1 interoperator interoperator-charts/interoperator

Refer detailed upgrade docs for more info.

Interoperator Release v0.12.0

New features/Bug fixes

• Replace Request with Axios in HTTP Clients (#1111)
• Update nodejs dependencies (#1139, #1153, #1142, #1122)
• Update golang dependencies (#1121)
• Interoperator Improvements (#1126)
• Adding middleware for injecting plan in the request (#1097)
• Update Dependencies of Interoperator (#1084)
  • Update client-go to v0.18.8
  • BREAKING CHANGE for consumers of generated clients
  • Refer k8s 0.18 release notes

Supported K8S Version

• v1.17.x
• v1.18.x
• v1.19.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 update

Deploy SF Interoperator using helm

helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.12.0 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)

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 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.12.0 interoperator interoperator-charts/interoperator

Refer detailed upgrade docs for more info.

Interoperator Release v0.11.2

New features/Bug fixes

• Support uppercase instance ids (#1098)
• Add validations for context parameters (#1098)

Supported K8S Version

• v1.16
• v1.17
• v1.18

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 update

Deploy SF Interoperator using helm

helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.11.2 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)

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 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.11.2 interoperator interoperator-charts/interoperator

Refer detailed upgrade docs for more info.

Interoperator Release v0.11.1

New features/Bug fixes

• [Bug] Fix state getting lost on parallel requests (#1083)

Supported K8S Version

• v1.16
• v1.17
• v1.18

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 update

Deploy SF Interoperator using helm

helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.11.1 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)

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 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.11.1 interoperator interoperator-charts/interoperator

Refer detailed upgrade docs for more info.

Interoperator Release v0.11.0

New features/Bug fixes

• Adding some custom metrics (#983)
  • Documentation
• Multi-AZ and High availability for Interoperator (#1042, #1030)
  • Documentation
• Introducing operator-apis application (#989, #1051)
  • Documentation
• Ensure credentials are stored as Secrets (#1049)
• Dependency Upgrades(#1033, #1023, #1021, #1020)
• [Bug] Fix NS replication when NS sepration is disabled (#1011)
• [Bug] Fix older version of provisioner getting replicated(#1019)

Supported K8S Version

• v1.16
• v1.17
• v1.18

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 update

Deploy SF Interoperator using helm

helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.11.0 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)

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 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.11.0 interoperator interoperator-charts/interoperator

Refer detailed upgrade docs for more info.

Interoperator Release v0.10.0

New features/Bug fixes since 0.9.0

• Fix upgrade failure due to CRDs ApiVersion change (#1013)
• Fix delete failures, when delete is triggered before provisioning is complete (#1001)
• Remove default scheduler from the k8s build (#1000)
• Add some custom metrics (#983)
• Remove org based quota check (#982)
• Update CRDs ApiVersion from crd.v1beta1.apiextensions.k8s.io to crd.v1.apiextensions.k8s.io (#913)
• Replicate imagePull secrets in Mutlicluster Deployer to sister clusters (#988)

Supported K8S Version

• v1.16.x
• v1.17.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 update

Deploy SF Interoperator using helm

helm install --set cluster.host=sf.ingress.< clusterdomain > --namespace interoperator --version 0.10.0 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)

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 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.10.0 interoperator interoperator-charts/interoperator

Refer detailed upgrade docs for more info.