Marco Franssen
a1b19dd215
*64585baFix formatting issues introduced with #152 *0dac0dbImprove Spire Chart documentation *f709ed9Bump actions/checkout from 3.4.0 to 3.5.0 *faef439Bump helm/chart-testing-action from 2.3.1 to 2.4.0 *ae62dd1Bump spire version to 1.6.1 *02fda80Add Artifact Hub badge to README.md *901e670Disable default Tornjak deployment (#153) *05d0f47Introduction of Tornjak to SPIRE Server helm charts (#144) *b25dc77Test fixing the tests (#148) *b4be9edAdd maturity tag (#138) *d4fd2ceExtract the namespace override test out of the old lockdown test. (#145) *4f85802Update lockdown test to test the production example *04a1305Fork the lockdown test to two tests as it is doing the work of 2 (#134) *64d0107Resolve issue in prod example on volume mount (#143) *5b6708bRemove @dennisgove from CODEOWNERS (#140) *a516caaRemove k8s 1.21 from test matrix + small syntax error fix (#133) *811a2f6Add option to enable federation on spire-server (#97) Signed-off-by: Marco Franssen <[email protected]>
Note
: All the helm charts in this repo are beta. We encourage you to try them out and contribute. The API may change as we move towards a production ready release.
SPIFFE Helm Charts
A suite of Helm Charts for standardized installations of SPIRE components in Kubernetes environments.
Add Helm repository
helm repo add spiffe https://spiffe.github.io/helm-charts/
helm repo update
Dependencies and Version Compatibility
Unless otherwise noted in an application chart README, the following dependencies will follow these prescribed version compatibility rules.
| Dependency | Supported Versions |
|---|---|
| SPIRE | 1.5.3+, 1.6.x |
| Helm | 3.x |
For Kubernetes we will officially try to support the last 3 versions as described in k8s versioning.
Contributing
Before contributing ensure to check our CONTRIBUTING guidelines.
LICENSE
This project is licensed under Apache License, Version 2.0.
Reporting a Vulnerability
Vulnerabilities can be reported by sending an email to [email protected]. A confirmation email will be sent to acknowledge the report within 72 hours. A second acknowledgement will be sent within 7 days when the vulnerability has been positively or negatively confirmed.