-
Notifications
You must be signed in to change notification settings - Fork 689
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
Add deployment example #4126
Add deployment example #4126
Conversation
stevesloka
commented
Oct 20, 2021
- Adds an example for running Envoy as a deployment vs a daemonset
- Updates the e2e tests to read an env var to determine if the deployment version should be run
- Enables running e2e tests for Envoy deployment on each PR build (😱)
e449db6
to
6f112c8
Compare
Codecov Report
@@ Coverage Diff @@
## main #4126 +/- ##
==========================================
- Coverage 77.78% 77.77% -0.02%
==========================================
Files 112 112
Lines 10005 10005
==========================================
- Hits 7782 7781 -1
- Misses 2040 2041 +1
Partials 183 183
|
I thought about just having the deployment version run hourly or something to pick up issues vs running on each PR. That might reduce the churn time for each iteration. |
Marking this PR stale since there has been no activity for 14 days. It will be closed if there is no activity for another 30 days. |
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.
👍 to having this as an example. It'd also be good to update examples/contour/README.md
, as well as some stuff in the docs about deployment options (e.g. https://projectcontour.io/docs/v1.19.1/deploy-options/, maybe some other pages too)
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.
LGTM, I agree with @skriss about the risk of burning all our Actions time if we have a few PRs though.
0139066
to
3dfad38
Compare
@skriss @sunjayBhatia I refactored this a bit to add some "deployment" tests. I'd like to write up some docs, but can follow that up with a new PR. |
ah @stevesloka just merged #4170 and realized there will be merge conflicts now, my apologies |
abfdf67
to
1ba7616
Compare
No worries @sunjayBhatia, all rebased! |
Marking this PR stale since there has been no activity for 14 days. It will be closed if there is no activity for another 30 days. |
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 looks pretty good, one small merge conflict to resolve. I do think de-duping the tests would be good, but maybe we can do that in a follow-up for the sake of getting this in.
metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" | ||
) | ||
|
||
func testPathConditionMatch(namespace string) { |
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.
If we wanted to get this in as-is, I'd be willing to take the follow-up to do some de-duplication here.
Signed-off-by: Steve Sloka <slokas@vmware.com>
Signed-off-by: Steve Sloka <slokas@vmware.com>
Signed-off-by: Steve Sloka <slokas@vmware.com>
Signed-off-by: Steve Sloka <slokas@vmware.com>
Signed-off-by: Steve Sloka <slokas@vmware.com>
Signed-off-by: Steve Sloka <slokas@vmware.com>
Signed-off-by: Steve Sloka <slokas@vmware.com>
Signed-off-by: Steve Sloka <slokas@vmware.com>
Signed-off-by: Steve Sloka <slokas@vmware.com>
Signed-off-by: Steve Sloka <slokas@vmware.com>
1ba7616
to
218d63a
Compare
@skriss @sunjayBhatia I think that's a good plan, merge this in and we can refactor everything around maybe. What do you think? |
Signed-off-by: Steve Sloka <slokas@vmware.com>
It works for me. I was thinking that maybe another path here would be to run the full suite of E2E's against a Deployment as part of the daily run, so we could make a decision on that and then make some subsequent revisions here. |
I'm inclined to just merge this, then I'll add it to the daily build to help validate. Just want to check in with you @sunjayBhatia if that makes sense. |
sounds good to me 👍🏽 good to get changes in and then we can refactor the CI as needed |