Peter Fern
Peter Fern
As it currently stands, without wildcard namespaces, Fargate-backed clusters are basically unusable: 1. Fargate Profiles take considerable time to create and delete. 2. Fargate Profiles cannot be modified, so new...
Is there not some way to at least get this working, even if it doesn't perform optimally? I tried bumping the version conditionals from `703` to `704`, but all that...
Oh right, ugly. Thanks for the links.
I suspect I'm not alone in this, so I'd like to add my use-case. My employer is a mix of technical and non-technical staff. I would dearly love to be...
Same here when deploying to production: ruby-1.9.3-p0 activeadmin-0.3.4 rails-3.1.3 rake-0.9.2.2
The PR is a bit messy (merge commits and 6407711 should not be included here), but it would also solve #2442. I'll try to find some time to test against...
> I am open to supporting multiple node peers per speaker (in which case the name "node peer" wouldn't make sense anymore...), however I'd like to see a solid UX...
> I'm reluctant to allow specifying multiple autodiscovery configs when the implementation doesn't support it Of course, I wasn't suggesting that the spec be changed without being backed by an...
Correct me if I'm wrong, but without `add-path` support, aren't we in a situation where there is actually no load-balancing done when `externalTrafficPolicy: Local` is specified? Because MetalLB only announces...
> I should add, and maybe this is the source of confusion: in BGP mode, each speaker is only advertising itself as a nexthop, it's not attempting to advertise the...