trust-manager is the easiest way to manage trust bundles in Kubernetes and OpenShift clusters.
This prerelease version is intended as a follow up to v0.5.0-beta.0, allowing users to test the new JKS support available in trust-manager. It fixes a bug in the original implementation of the JKS feature which meant some certificates wouldn't appear in the resulting JKS file - this was addressed in #127 - special thanks to @claudiuavat1 and @hazmat345 for their debugging efforts!
Several other pull requests landed, mostly tweaking helm charts to allow for easier use.
Users can test JKS functionality using a bundle such as the following:
{
"apiVersion": "trust.cert-manager.io/v1alpha1",
"kind": "Bundle",
"metadata": {
"name": "testing"
},
"spec": {
"sources": [
{
"useDefaultCAs": true
}
],
"target": {
"additionalFormats": {
"jks": {
"key": "my-bundle.jks"
}
},
"configMap": {
"key": "mybundle.pem"
}
}
}
}What's Changed
- ⭐ Use ordered aliases when creating JKS files by @SgtCoDFish in #127
- Allow node selection based on nodeSelector, tolerations, affinities and topologySpreadConstraints (fixes #13) by @stzov in #117
- helm: make installation of default trust package optional by @siiimooon in #121
- Add descriptions for some helm chart fields by @SgtCoDFish in #126
- Formatting improvements, tests for dummy certs by @SgtCoDFish in #128
- Explicitly define resource namespaces in Helm chart by @inteon in #123
- Use boilersuite for boilerplate verification by @SgtCoDFish in #130
- Ensure unique aliases in JKS files by @SgtCoDFish in #129
- Bump version to v0.5.0-beta.1 by @SgtCoDFish in #134
New Contributors
- @stzov made their first contribution in #117
- @siiimooon made their first contribution in #121
Full Changelog: v0.5.0-beta.0...v0.5.0-beta.1