feat(ci): Add a matrix style test for different versions of k8s & helm #418
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.
What
While trying to reproduce #416, I made a GitHub Actions matrix job that allows us to install to do an e2e style deployment of our helm charts. We aren't providing an actual auth token or API key currently, so it will just fail to connect, but we can use this to validate that chart versions install properly along with the CRDs. If we do find a case that can re-create #416, this will also help serve as a regression test in the future.
How
Created a GitHub action that allows for
workflow_dispatch
, so we can test any of our helm chart versions. I chose the latest 4 versions of helm as well as k8s to test against using a kind clusterBreaking Changes
No, this is an internal tool for testing.