You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 6, 2022. It is now read-only.
However, the ServiceClass is not removed from the service-catalog.
This command will always list the ServiceClass.
oc get serviceclass | grep fh-sync-server
fh-sync-server ServiceClass.v1alpha1.servicecatalog.k8s.io
Is this expected behavior?
I can work around this by manually deleting the ServiceClass, and then the catalog no longer includes it. e.g. oc delete serviceclass fh-sync-server
But this seems like an unnecessary step. Should the service catalog keep up to date with new and removed ServiceClasses that each broker has?
The text was updated successfully, but these errors were encountered:
@david-martin This is related to the broker refresh interval, which we are working on now: #1086
Currently there is a single refresh interval for all brokers, which is a property of the controller-manager binary. You would eventually see the desired change, but not immediately upon updating the broker's services. The API described in #1086 will allow configuration of this interval on a per-broker period, and allow the user to trigger relisting the broker manually.
For reproducing this, I'm using an example with the template-service-broker in OpenShift.
I can add a new template to the
openshift
namespace for the template-server-broker to pick upCalling directly to the broker responds with our SerivceClass included
After some time (<5m), the serviceclass appears in openshift too
This is expected.
If I remove the template, the template-service-broker picks up on this.
Calling directly to the broker no longer includes a ServiceClass.
This is also expected.
However, the ServiceClass is not removed from the service-catalog.
This command will always list the ServiceClass.
Is this expected behavior?
I can work around this by manually deleting the ServiceClass, and then the catalog no longer includes it. e.g.
oc delete serviceclass fh-sync-server
But this seems like an unnecessary step. Should the service catalog keep up to date with new and removed ServiceClasses that each broker has?
The text was updated successfully, but these errors were encountered: