search

cloudfoundry-incubator / kubecf

Cloud Foundry on Kubernetes
Apache License 2.0
115 stars 62 forks source link

Auto-register the Eirini Persi Broker when Eirini is enabled #1079

Open andreas-kupries opened 4 years ago

andreas-kupries commented 4 years ago

Describe the bug

Currently, when Eirini is enabled, the eirini-persi-broker is started, but not registered as broker with the newly-deployed CF. See https://github.com/cloudfoundry-incubator/kubecf/issues/819#issuecomment-649841863 (Step 6.i) for the operations needed to be done manually at the moment.

To Reproduce

Deploy kubecf with eirini enabled, then check with cf service-brokers that the eirini-persi-broker is not listed.

Expected behavior

If possible, have the broker register itself with CF when the CF api has become available. I suspect that this requires some kind of post-start script which waits for the CF api first, and then drives it. Or a job/task which repeats until it succeeds.

mudler commented 4 years ago

This is a dup of #839

mudler commented 4 years ago

I think we can have a quarksjob with the wait-for annotation in the pod, but not sure if that would be enough. But at least in this way we don't have to retry until it succeeds

mudler commented 4 years ago

JFYI the setup is now documented here: ~https://kubecf.suse.dev/docs/tutorials/eirini_persi/~ edit: https://kubecf.io/docs/tutorials/eirini_persi/