Bikramdeep Singh

## Binding I did perform some testing with `mongodbblog` sample [app](https://github.com/SUSE/scf/blob/develop/src/scf-release/src/acceptance-tests-brain/test-scripts/016_minibroker_mongodb_test.rb). Here are my observations: I was able to successfully create the app and bind `mongodb` service instance to the...

I tested again with `0.3.0` and now I can see the pod spawning for the service instance. Also, now I am able to work with the broker without `Service Catalog`....

Also, tried it for the `redis` [app](https://github.com/SUSE/scf/blob/develop/src/scf-release/src/acceptance-tests-brain/test-scripts/012_minibroker_redis_test.rb) still seem to be getting similar issues: ``` * Connected to redis-example-app.cap.bsingh.aws.howdoi.website (52.32.185.182) port 80 (#0) > PUT /hello HTTP/1.1 > Host: redis-example-app.cap.bsingh.aws.howdoi.website...

I should have been more clear while describing the issue, the `cf` client is not trying to connect to the database, but the app that is deployed. So the `curl`...

@tamalsaha Thanks for the update. I guess it should be okay. Just wanted to make sure this is on the agenda.

Based on feedback from @troytop we might have to re-scope this task to keep the two pipelines separate while figuring out a mechanism to share the pipeline codebase.

Based on recent developments, the home for `suse-buildpacks` pipeline should be:https://github.com/cloudfoundry-incubator/kubecf/tree/master/.concourse

As per @viovanov we can rename the `cf-operator-ci` repo to `kubecf-ci` and make that home for all release image related pipelines.

As discussed, broken the task in two chunks - other task is: https://github.com/cloudfoundry-incubator/kubecf/issues/601