This repository has been archived by the owner on Mar 19, 2024. It is now read-only.
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.
Add conformance testing workflow for GitHub Actions #139
Add conformance testing workflow for GitHub Actions #139
Changes from 12 commits
6fd25a8
43e63a7
e3e0afb
385dbde
3009a6b
58820e8
2c70bd4
6d1404a
b8845de
7192c57
56c41f9
5a7b79f
cc16f7d
7070ab7
1cec51c
a3724a3
f60a6a0
d68ec4a
54771c2
45c165f
e72ecf2
d965fa5
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will run at midnight UTC every day
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This allows us to kick off runs manually in the repo Actions tab if we choose
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be triggered manually on specific branches/PRs, or only on
main
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep yep. Here's the blogpost I initially read about it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to run using the
main
branch of consul-k8s for now because of some fixes that haven't been released yet. Once those fixes are released, we can drop this installation from a clone.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This uses my fork + branch of the gateway-api repo from kubernetes-sigs/gateway-api#1080.
Hoping that merges in the next week or so and we can update this to use
kubernetes-sigs/gateway-api@master
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated to match the
default
step inDockerfile
. I don't think there's a reason to be on an older version, but can pin this if we generally prefer keeping it pinned.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Turns out kind runs out of CPU before all of the conformance testing resources can spin up. There's no easy option for increasing the size of the runner today. It sounds like the consul team is running into similar issues that we may need to figure out in the future if/when upstream adds more deployments.