-
Notifications
You must be signed in to change notification settings - Fork 273
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
feat(k8s): add test and task support for kubernetes module type #1530
Conversation
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.
Had a few minor comments.
Also wondering if we should add a guide similar to this one https://docs.garden.io/guides/using-helm-charts for the Kubernetes module type. Or merge the two into a single generic guide. These concepts are a little complicated IMO and the Helm charts guide does a really good job of explaining them.
We might also want to show this functionality in an example project. The current kubernetes-module example only uses remote container images. (It would also showcase how to reference the deployment image under the manifests
field). We could in turn skip the redis service.
I'm fine with updating the guide in a follow-up PR but updating the example should be straightforward.
25c8d5b
to
0b0f9b6
Compare
I basically re-used the same functionality from the `helm` module type. Nice and simple. Note: We may want to revisit that schema at some point, but I figured the sane approach would be to keep it consistent for now. Closes #1529
Added integ tests for the basic failing cases for Kubernetes module tests and tasks. Also added missing imports for the getTestResult and getTaskResult handlers to the kubernetes module type.
0ac1dab
to
c5f20c4
Compare
c5f20c4
to
2f1ecc0
Compare
What this PR does / why we need it:
I basically re-used the same functionality from the
helm
module type.Nice and simple.
Note: We may want to revisit that schema at some point, but I figured
the sane approach would be to keep it consistent for now.
Which issue(s) this PR fixes:
Closes #1529