Skip to content

hack/microvm-assets: stage assets to rustfs over IPv6 - #1122

Open
Yuan Gao (ygao-g) wants to merge 1 commit into
agent-substrate:mainfrom
ygao-g:microvm-rustfs-ipv6
Open

hack/microvm-assets: stage assets to rustfs over IPv6#1122
Yuan Gao (ygao-g) wants to merge 1 commit into
agent-substrate:mainfrom
ygao-g:microvm-rustfs-ipv6

Conversation

@ygao-g

Copy link
Copy Markdown
Collaborator

Staging the micro-VM assets fails on an IPv6-only cluster. The endpoint is built
from the rustfs ClusterIP, which there is a bare IPv6 literal, and a bare literal
is not a URL. Bracketing alone is not enough: the botocore vendored into aws-cli
2.17 has no IPv6 endpoint validator and rejects the bracketed form outright, so
the image pin moves to 2.31.0 as well. Both changes are no-ops on IPv4.

Verified on an IP_FAMILY=ipv6 kind cluster: hack/run-microvm-demo-kind.sh now
completes and the counter-microvm golden snapshot reaches Ready — a micro-VM
guest booting and checkpointing on a v6-only cluster.

Part of #246.

🤖 Generated with Claude Code

On an IPv6-only cluster the rustfs ClusterIP is a v6 literal, so the
endpoint came out as http://fd00:10:96::abcd:9000 — not a valid URL —
and micro-VM asset staging failed outright. Bracketing alone is not
enough: the botocore vendored into aws-cli 2.17.0 has no IPv6 endpoint
validator and rejects a bracketed literal too.

Bracket the literal when it contains a colon, and bump this script's
aws-cli pin. The rustfs-bucket-init Job addresses rustfs by DNS name
and is left alone, so no address family pays for a fresh in-cluster
image pull.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant