Move the CI to GHA - Githubissues

ory / k8s

Kubernetes Helm Charts for the ORY ecosystem.

https://k8s.ory.sh/helm

Apache License 2.0

336 stars 259 forks source link

Move the CI to GHA #467

Closed Demonsthere closed 2 years ago

Demonsthere commented 2 years ago

Preflight checklist

[X] I could not find a solution in the existing issues, docs, nor discussions.
[X] I agree to follow this project's Code of Conduct.
[X] I have read and am following this repository's Contribution Guidelines.
[ ] This issue affects my Ory Cloud project.
[ ] I have joined the Ory Community Slack.
[ ] I am signed up to the Ory Security Patch Newsletter.

Describe your problem

Currently most of the Ory repositories are using GithubActions for CI and release procedures. This repo has not yet been migrated

Describe your ideal solution

All pipeline functionalities are migrated to GHA
Each chart has its own pipeline for testing/upgrading/releasing
Path filtering is used to only run required actions
Deprecated elements (like kind) are upgraded or replaced with alternatives (like k3d)

Workarounds or alternatives

no

Version

yes

Additional Context

No response

Demonsthere commented 2 years ago

Followups:

[x] Add secrets to GHA
[x] Make a release with the new CI
[x] Restore upgrade tests -> https://github.com/ory/k8s/issues/480
[x] Run CI on changes in the hack/values.yaml files
[x] Run CI on changes to the CI definitions