-
Notifications
You must be signed in to change notification settings - Fork 78
Conversation
d29e544
to
be7a67f
Compare
45162c4
to
8911303
Compare
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.
Looking good so far.
Also removed unused ServiceAccount
- Also added some new Makefile targets - Switched for an alpine image for the Drone build
7301a30
to
bd0b16d
Compare
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!
charts/access/email/Chart.yaml
Outdated
# This is the chart version. This version number should be incremented each time you make changes | ||
# to the chart and its templates, including the app version. | ||
# Versions are expected to follow Semantic Versioning (https://semver.org/) | ||
version: 0.1.0 |
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.
I'd like for this to hit 1.0.0 before we release to customers. It doesn't (and probably shouldn't) be there yet in this PR though.
64ecd39
to
2f97af2
Compare
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
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.
Additionally, commented out chart version to indicate it's not ready yet
Build fails without a valid version in Chart.yaml, so I updated it to 1.0.0 (the chart won't change anyways, only a build will be added)
We might want to consider more detailed tests in the future to avoid this
This change adds a Helm chart for
access-plugin-email
and it'll serve as a base for the rest of the plugins.Part of #439
TODO:
values.yaml
added by the default templateMake it possible to use secrets and configmaps where it's applicable (but also keep string input where it makes sense)helm unittest
values.schema.json
to help validating values.Testing done
I've tested the chart in a local minikube environment, I'll also test it under EKS once the images are available on ECR.
I've also added some unit tests using the third party plugin vbehar/helm3-unittest (we are already using it in gravitational/teleport).
Deployment
Deployment of the helm chart is going to be in a separate pull request.