-
Notifications
You must be signed in to change notification settings - Fork 25
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
Nightly "production like" testing #213
Labels
Comments
TristanHoladay
added a commit
that referenced
this issue
Apr 3, 2024
## Description Add EKS setup for deploying and testing uds-core. ## Related Issue related to #213 ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Other (security config, docs update, etc) ## Checklist before merging - [ ] Test, docs, adr added or updated as needed - [ ] [Contributor Guide Steps](https://github.com/defenseunicorns/uds-template-capability/blob/main/CONTRIBUTING.md)(https://github.com/defenseunicorns/uds-template-capability/blob/main/CONTRIBUTING.md#submitting-a-pull-request) followed --------- Co-authored-by: zamaz <71521611+zachariahmiller@users.noreply.github.com>
rjferguson21
pushed a commit
that referenced
this issue
Jul 11, 2024
## Description Add EKS setup for deploying and testing uds-core. ## Related Issue related to #213 ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Other (security config, docs update, etc) ## Checklist before merging - [ ] Test, docs, adr added or updated as needed - [ ] [Contributor Guide Steps](https://github.com/defenseunicorns/uds-template-capability/blob/main/CONTRIBUTING.md)(https://github.com/defenseunicorns/uds-template-capability/blob/main/CONTRIBUTING.md#submitting-a-pull-request) followed --------- Co-authored-by: zamaz <71521611+zachariahmiller@users.noreply.github.com>
Scoping the remaining work here:
It may make sense to split out this work into multiple issues as each of these sub-bullets are probably issue-sized in themselves. |
Intending to break this out into more bite sized tickets. Likely each of the above bullet points will be its own ticket. |
This was referenced Sep 5, 2024
Closing as the linked tickets provide more consumable chunks here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is your feature request related to a problem? Please describe.
Currently uds-core has CI smoke testing on k3d, with a "dev" setup (single replicas, single node, minimal external dependencies). When I deploy to my RKE2 or EKS cluster I don't have a good example of an HA setup and low confidence that has been tested before I deploy in my environment.
Describe the solution you'd like
Nightly CI tests against k8s distros, suggest targeting rke2 and eks, with a "production" bundle configuration used for CI testing only (not published).
Beyond just the basic deploy it would also be good to add more full e2e testing as part of this nightly deploy.
Describe alternatives you've considered
End users should have staging environments to test the deploy before they move to prod so this in theory isn't a high risk, but I think it's very valuable for us to test before cutting releases rather than relying on end users to test for us.
We could also run the testing on every PR, but that is likely not desirable since it slows down the fast feedback on PRs.
Additional context
We know of end users interested in RKE2 and EKS so that is part of the rationale for targeting those distros.
We also don't want to reproduce any testing that should be done upstream, so we likely should stick to cross-application functionality (i.e. hitting istio virtual services, SSO logic, etc).
The text was updated successfully, but these errors were encountered: