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.

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

workflows: force a version of k3s that should fix our ci issues #99

Merged

Conversation

phlogistonjohn
Copy link
Collaborator

See: k3s-io/k3s#3704

Figuring out what to actually put on the --image option was far harder
than it seems it should have been. :-\

Signed-off-by: John Mulligan [email protected]

See: k3s-io/k3s#3704

Figuring out what to actually put on the --image option was far harder
than it seems it should have been. :-\

Signed-off-by: John Mulligan <[email protected]>
@@ -113,7 +113,7 @@ jobs:
- name: Create k3d registry
run: k3d registry create "${REG_BASE}" --port "${REG_PORT}"
- name: Create k3d cluster
run: k3d cluster create --wait --registry-use "${REGISTRY}"
run: k3d cluster create --wait --image docker.io/rancher/k3s:v1.21.5-k3s1 --registry-use "${REGISTRY}"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Instead of hardcoding to one particular patch version, would it make more sense to lock on to a Minor version?

Something like

IMAGE_TAG=$(curl --silent "https://update.k3s.io/v1-release/channels/v1.21" | egrep -o '/v[^ ]+"' | sed -E 's/\/|\"//g' | sed -E 's/\+/\-/')
k3d cluster create --wait --image docker.io/rancher/k3s:${IMAGE_TAG} --registry-use "${REGISTRY}"

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Sure, let's follow up with something like that in a follow-up pr.

@phlogistonjohn phlogistonjohn merged commit f210a8d into samba-in-kubernetes:master Sep 24, 2021
@phlogistonjohn phlogistonjohn deleted the jjm-newer-k3s branch September 24, 2021 14:16
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.

2 participants