Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Distributing Cloud Foundry sidecars with buildpacks

Distributing Cloud Foundry sidecars with buildpacks

Until recently a running Cloud Foundry app container only ran and monitored a single process, but now we can run additional sidecar processes. In this deck we look at packaging the sidecar software in a buildpack.

Walk thru is at https://gist.github.com/drnic/28ba8d0dc8e91bfdc47e53916d6cdb56

Cb2b768a5e546b24052ea03334e43676?s=128

Dr Nic Williams

June 19, 2019
Tweet

Transcript

  1. Title Text Body Level One Body Level Two Body Level

    Three Body Level Four Body Level Five Distributing sidecars with Buildpacks CF CAB meeting June 2019 Dr Nic Williams @drnic
  2. None
  3. Sidecars ./app ./config-server -p 5555

  4. Sidecars ./app etcd grpc-proxy start etcd etcd etcd

  5. Sidecars nginx [--port 8080] ./app --port 8081

  6. via cf push ./app ./config-server -p 5555 ./config-server uploaded by

    dev How to separate concerns?
  7. Who? ./app etcd grpc-proxy start etcd cli curated by etcd

    team Who to distribute etcd sidecar?
  8. Buildpack ./app etcd proxy etcd service team own etcd Distribute

    sidecar via buildpack Ɏ app team etcd service team
  9. etcdproxy sidecar buildpack command: start_etcdproxy.sh

  10. Install etcd cli New "singles" buildpack Walk thru @drnic Package

    etcd cli Ɲ $ Run etcd proxy as sidecar ɑ Using CF Dev + local etcd server