Conversation
|
So, I also hit a catch-22 while I was testing this... There was something that required me to set an endpoint, so I set "sfo2" since I noticed a piece of the database backup code which would use region to inform "create_bucket" -- I have no idea if this will work against the DigitalOcean API, I had already created the buckets, but this seemed to fit. Then I tried builder, and noticed: Maybe it would work if I was able to set an empty region, but like I said, something else had prohibited me from leaving the region value blank. Will follow up later... |
|
I also noticed, with regard to DO and kops, that having configured ingress, I still had a LoadBalancer provisioned by deis-builder, which was expected; but it never picked up the backing service and routed traffic to it. I don't know if this would have worked with the managed Kubernetes service, I assume so. Kops support for DigitalOcean is alpha, but "Limited release" managed k8s probably has this solved already. This is why as you can see I kicked builder over into NodePort mode for the purposes of this testing. I had to do this by hand; I guess that the router nodeport setting is not apparently able to be honored as well by builder in ingress mode. |
|
I have close my rp(#74) and sorted out the commit log, removed global var, and submitted a new RP. see: |
|
This was not closed on purpose... whoops – it looks like #76 is still open though, so this is fine. |
Supporting changes for teamhephy/postgres#6
Perhaps the default setting should remain as "true"?
These commits may still need to be cleaned up so they conform to the style guide...