feat: Add network configuration to k3d config to work with lower MTU …#74
Conversation
github-actions
Bot
added
include-in-release-notes
enhancement
There was a problem hiding this comment.
Pull request overview
Adds an explicit Docker network to the k3d cluster config so the cluster can be attached to a custom network (e.g., one created with a lower MTU) instead of relying on the default.
Changes:
- Set
network: k3d-glueops-netink3d-config.yaml.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| @@ -2,6 +2,7 @@ apiVersion: k3d.io/v1alpha5 | |||
| kind: Simple | |||
| metadata: | |||
| name: captain | |||
There was a problem hiding this comment.
network: k3d-glueops-net introduces an external dependency on a pre-existing Docker network (and, per the PR intent, one configured with a lower MTU). To avoid confusing setup failures or silently running with the wrong MTU, add an inline comment here (and/or ensure the setup docs reference it) stating that this network must be created with the desired MTU before running k3d cluster create --config.
| name: captain | |
| name: captain | |
| # This Docker network must be created ahead of time with the desired MTU | |
| # before running `k3d cluster create --config`. |
…networks