Skip to content
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.

Correctly set image pull policy during k8s install #3948

Merged
merged 2 commits into from
Sep 29, 2022

Conversation

paladin-devops
Copy link
Contributor

After converting to Helm for the server installation, as well as adding runner install, the configuration for k8s for the image pull policy was not updated to be set for a Helm install. This PR fixes that and closes #3866.

Copy link
Member

@briancain briancain left a comment

Choose a reason for hiding this comment

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

Looks good to me!

brian@ubuntu:waypoint-tetris λ waypoint install -accept-tos -platform=kubernetes -k8s-server-image="localhost:5000/waypoint:dev" -k8s-pull-policy="Always"                                                                                          ±[main]
⚠️ Kind cluster detected!

Installing Waypoint to a Kind cluster requires that the cluster has
LoadBalancer capabilities (such as metallb). If Kind isn't configured
in this way, then the install may hang. If this happens, please delete
all the Waypoint resources and try again.
✓ Service "waypoint" is ready
✓ Server bootstrap complete!
✓ Waypoint server installed with Helm!
...
...
...

brian@ubuntu:waypoint-tetris λ kubectl get pod/waypoint-server-0 -o yaml | grep -i pullPolicy                                                                                                                                                       ±[main]
    imagePullPolicy: Always

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CLI: waypoint install does not respect k8s-pull-policy flag
2 participants