y-assert, y-build-nothing and split registry kustomize base#27
Merged
Conversation
almost: buildkitd needs to be proxied too
Also fixes an issue with the buildkitd service's selector
solsson
force-pushed
the
k3s-image-for-y-build
branch
from
May 25, 2020 09:31
23f2d8e to
a0ca6d1
Compare
I don't think that kube access is used, unless we switch to buildctl's kubernetes protocol.
solsson
referenced
this pull request
in Yolean/kubernetes-assert
May 25, 2020
Collaborator
Author
|
Re-scoping this PR; while the README's new CI flows are still incomplete - k3s in docker doesn't work with the buildkitd service yet - I managed to do other improvements towards automating Yolean/kubernetes-assert#13 runs in existing clusters. Most importantly it starts a workflow for running asserts: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docker Hub's autobuilds can test using
docker-compose.test.yml. It'd be great for projects that build images and/or maintain kustomize bases to be able to build test containers (as inlining scrips in docker-compose is painful, not least because of the$=$$gotcha).