As a frequent user of ingress, I agree that portability isn't useful in practice and that requirement is a hindrance on ingress evolution. A lot of work has been put into CRDs, yet parts of the community push for a "portable" ingress. With all the one-off features/settings, users will inevitably make substantial changes to their ingress object - might as well use CRDs with clear specs. The alternative is annotation hell or associated configmaps.
I've heard some say they want to be able to list out all external addresses exposed from the cluster, but that can be solved with a new resource more akin to endpoints.
This is highly unreasonable. If I'm hosting large files, you bet I'm going to require the public to create an account so I can protect my quality of service for others. They're not restricting who can create accounts... they're not requiring a payment...
I purchased a $350 dresser from Overstock a few weeks ago. It arrived with ~10 pieces in ruins or had large visual defects. After giving Overstock a call, they sent out a box of replacement parts; however, they sent it to the wrong address. After another call, we finally got the parts. Of course, one of the replacement parts is also defective...
Same experience with Overstock when I bought a table. Three months and several frustrations later, I got the table and they offered me a 10% discount on my next furniture order. Needless to say, I'll never shop there again.
However, when my wife bought a chair on Wayfair, we didn't have any issues. I'd definitely do it again. It all depends on who you buy from.
Who would want this Amazon product for every light switch, remote control, and thermostat? No, most buyers will probably just buy one for a household. In that case, I agree that a regular tablet would suffice.
My point was that you have a remote control already; you don't use a tablet instead of that, just for use as a remote control. In a similar way, a tablet might be overkill for a 'home assistant', and the Amazon Echo seems designed to address that.
Not if you use a low TTL. And no, I'd rather not have my traffic run or even terminate through every intelligence agency on the planet, even if that means accepting a few drops in the timeframe it takes to propagate.
... hence the lose-lose scenario. Having a low TTL just makes it your client's problem. If you want to be paranoid about the government, you can still use an L4 load balancer such as the one offered by GCP.
Run your infrastructure however you want. This setup would never fly for a real organization.
> - docker itself constantly ships with a lot of bugs. To this day (we are on docker 1.12.6), we constantly have problems with the docker daemon hanging or becoming unresponsive. I'm not sure if k8s can do much about this, but I feel like it should since we don't directly control docker.
To be fair, sometimes these problems are due to the kernel. Specifically, the infamous unregister_netdevice ref count issue (https://github.com/docker/docker/issues/5618) has been around for years. One of the comments from a kubernetes dev says they're bypassing the cause and don't see it in GKE production.
