Skip to content
This repository has been archived by the owner on Nov 2, 2023. It is now read-only.

Delay in state propagation of ATP from OCI to ServiceInstance #24

Open
lake-of-dreams opened this issue Feb 11, 2020 · 2 comments
Open

Comments

@lake-of-dreams
Copy link
Member

It was observed while both creating and deleting ServiceInstances for ATP that their is a random delay for state propagation to the ServiceInstance from actual state of ATP in OCI. The behaviour is intermittent but should be addressed.

While create - The ATP might already have provisioned in OCI - but the Status on ServiceInstance will still be Provisioning for as long as 4-5 minutes after the ATP might have provisioned.

Similarly while delete - the Status on ServiceInstance will still be Terminating even after the ATP is terminated

@ashokkkannan
Copy link
Contributor

Each time the oci-service-broker is polled for the status we go to the oci service and get the current status. The delay you are seeing is from the service-catalog. They are polling the oci-service-broker with an exponential back-off. Please tweak the service-catalog configuration to change this polling time to reduce the delay. For example, if you change the below value to 20s then the service-catalog will pool oci-service-broker for status at least once every 20s.
https://github.com/kubernetes-sigs/service-catalog/blob/master/charts/catalog/values.yaml#L70

@jayasheelankumar
Copy link
Member

@lake-of-dreams Please let us know if we can close this issue?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants