Repository navigation
docker: merged Gateways and cert-manager, as qemu - #36
Merged
Merged
Conversation
On macOS docker is the provider for the local dev clusters that qemu provisions on Linux, and the workloads converged on them need both: a second Gateway next to ystack's on the single node's 80/443, and certificates from y-cluster-ca (webhooks, a wildcard Gateway certificate). Without them a docker cluster on Apple Silicon had a Gateway whose ServiceLB pod stayed Pending, and a buckety-controller install that uses cert-manager TLS failed to apply. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
solsson
pushed a commit
to Yolean/ystack
that referenced
this pull request
Oct 12, 2026
The one change (Yolean/y-cluster#36) is in the docker provisioner: it now installs cert-manager with y-cluster's CA issuer, and enables Envoy Gateway's mergeGateways, as the qemu provisioner already does. A docker cluster (the macOS dev setup) can then run a second Gateway next to ystack's on the node's 80/443 and apply workloads that take certificates from y-cluster's CA. Both happen at provision time, so an existing docker cluster gets them only when re-provisioned. qemu and the other provisioners are unchanged. sha256 computed from the downloaded assets and identical to the release's y-cluster_v0.7.2_checksums.txt. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
solsson
added a commit
that referenced
this pull request
Oct 15, 2026
docker: merged Gateways and cert-manager, as qemu
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The two Gateway resources (both still exist):
Before the fix: Envoy Gateway's default is one proxy, with its own LoadBalancer Service, per Gateway. On a single-node k3s cluster each LoadBalancer Service has to bind the node's own ports 80/443, and only one can hold a port.
After the fix (mergeGateways: true): both Gateways share one proxy, envoy-y-cluster-…, with a single Service on 80 and 443. It tells their routes apart by hostname. Both Gateways show PROGRAMMED True at 172.17.0.2.