Skip to content

feat: Add network configuration to k3d config to work with lower MTU … #74

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
venkatamutyala merged 1 commit into from
Apr 26, 2026
Merged

feat: Add network configuration to k3d config to work with lower MTU … #74

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions k3d-config.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@ apiVersion: k3d.io/v1alpha5
kind: Simple
metadata:
name: captain

Copilot AI Apr 26, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Suggested change
name: captain
name: captain
# This Docker network must be created ahead of time with the desired MTU
# before running `k3d cluster create --config`.

Copilot uses AI. Check for mistakes.
network: k3d-glueops-net
servers: 1
agents: 6
kubeAPI: # same as `--api-port myhost.my.domain:6443` (where the name would resolve to 127.0.0.1)
Expand Down
Loading