Skip to content
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

Jump to bottom

ci: fix flaky e2e tests by colocating registry & hccm #687

Merged
merged 1 commit into from
Jul 8, 2024
Merged

ci: fix flaky e2e tests by colocating registry & hccm #687

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
4 changes: 4 additions & 0 deletions skaffold.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,10 @@ manifests:
chartPath: chart
setValues:
networking.enabled: true
# Pulling the containers from other nodes requires working network routes, but HCCM set these up.
# We circumvent this by co-locating the registry & HCCM, so it's always a local pull.
affinity.podAffinity.requiredDuringSchedulingIgnoredDuringExecution[0].topologyKey: "kubernetes.io/hostname"
affinity.podAffinity.requiredDuringSchedulingIgnoredDuringExecution[0].labelSelector.matchLabels.app: docker-registry

profiles:
# Clusters with Robot Servers do not support the native Routing functionality right now.
Expand Down
Loading