Ben Snyder

> thanks for the PR! i think that this issue on the bud repo still needs to be resolved: > > [roots/bud#387](https://github.com/roots/bud/issues/387) I've applied a workaround that should work fine...

> can you please revert the changes made with `sort-package-json`? bud configuration was at the top intentionally for ease of use Moved it back to the top for you

Totally understand. Here's my view for @kellymears and @QWp6t -- Yarn v3 with `nodeLinker: node-modules` and WITHOUT zero-installs ref: .gitignore ````sh .pnp.* .yarn/* !.yarn/patches !.yarn/plugins !.yarn/releases !.yarn/sdks !.yarn/versions ```` ......

I'm glad to lend insight as I have worked with Yarn v3 extensively with the patching capability (its awesome) and with CI caching. Will reply tonight. Edit: also, Yarn v2...

Thanks @Coly010! Sure I will get that in the works and post back here when ready.

Here is my working configuration with environment variables (just replaced my company with ACME) Please note I deploy with `docker swarm init` on a single host ```yaml version: '3' services:...

> Thanks for suggesting this @benpsnyder! I'll admit that this does look very cool, and I'm glad you got it working on your setup. > > > > The thing...

This issue with zone.js is also where I am stuck when using the `--bun` option. I tweeted @brandonroberts on this as well though I am almost sure he's seen this...

I faced this when I did an AKS-to-AKS setup. I realized `--service-type LoadBalancer` was `PENDING` however I just got done setting up peering between vNets, and I should be able...

Not fixed in `v1.13.0` either ```bash cilium install --version=1.13.0 --helm-auto-gen-values cilium-helm-values-install.yaml \ --helm-set ipam.mode=cluster-pool \ --helm-set ipam.operator.clusterPoolIPv4PodCIDRList="10.252.0.0/15" \ --helm-set tunnel="geneve" \ --helm-set ipv4NativeRoutingCIDR="10.252.0.0/15" \ --helm-set bgpControlPlane.enabled=true \ --helm-set k8s.requireIPv4PodCIDR=true \...