0.6.1

Announcing the immediate availability of passbolt's official helm chart 0.6.1.

This release removes a leak of the pgpass to the stdout when installing psql.

0.6.0

Announcing the immediate availability of passbolt's official helm chart 0.6.0.

With this release comes a fix for a long time bug related with the automatic
creation of JWT keys by the chart.

A new job has been introduced named job-create-jwt that will output valid
JWT keys and store them in a Kubernetes secret.

Users with already valid JWT keys stored as base64 in their values.yaml
jwtServerPrivate and jwtServerPublic won't have to do anything special.
The new job will detect your custom JWT keys and won't update them.

Users that don't have stored any JWT key in jwtServerPrivate and
jwtServerPublic Will be blocked upgrading to 0.6.0. There are two
options for these users:

Disable JWT auth

Chances are if you have not realized about this bug means you are
not using JWT authentication at all so you can disable it by editing
your values.yaml and set passboltEnv.plain.PASSBOLT_PLUGINS_JWT_AUTHENTICATION_ENABLED to false

You can also use a --set flag:

helm upgrade RELEASE_NAME my-repo/passbolt --set passboltEnv.plain.PASSBOLT_PLUGINS_JWT_AUTHENTICATION_ENABLED=false

Force the generation of new JWT keys

Set jwtCreateKeysForced to true before upgrading to 0.6.0 version of
this chart.

Execute an upgrade as usual, this will patch your current JWT secret
with new keys.

Collect the new generated JWT key from the Kubernetes cluster and store it in
your values.yaml in jwtServerPrivate and jwtServerPublic:

For jwtServerPrivate take the output of this command and update your values.yaml

kubectl get secret RELEASE_NAME-passbolt-sec-jwt --namespace default -o jsonpath="{.data.jwt\.key}"`

For jwtServerPublic take the output of this command and update your values.yaml:

kubectl get secret RELEASE_NAME-passbolt-sec-jwt --namespace default -o jsonpath="{.data.jwt\.pem}"

Or use again a --set flag:

export JWT_PRIVATE_KEY=$(kubectl get secret RELEASE_NAME-passbolt-sec-jwt --namespace default -o jsonpath="{.data.jwt\.key}")
export JWT_PUBLIC_KEY=$(kubectl get secret RELEASE_NAME-passbolt-sec-jwt --namespace default -o jsonpath="{.data.jwt\.pem}")
helm upgrade RELEASE_NAME my-repo/passbolt --set jwtServerPrivate=$JWT_PRIVATE_KEY --set jwtServerPublic=$JWT_PUBLIC_KEY

Where RELEASE_NAME is the name of your helm release

For more information please check our changelog

0.5.0

We are happy to announce the availability of the version 0.5.0 of
the official Passbolt helm chart.
This release comes with a well requested feature: PostgreSQL support.
Users will be able to plug their external PostgreSQL instances or
use the bundled dependency in this chart.
PostgreSQL is an opt-in feature, by default Passbolt helm chart
still relies on MariaDB. However, it should be easy for users to plug
one or the other.
Thanks to all the community members for your feedback and support.

For more information please check our changelog

0.4.4

This is a small hotfix release that fixes issues reported
by the community regarding the imagePullPolicy on the
deployment resource.

For more information please check our changelog

0.4.3

This release introduces several fixes and enhancenments reported by
the community.

It introduces the possibility to inject SSL certificates as external
secrets to both the ingress object and to the passbolt container
through the tls.existingSecret. By default the chart still relies
on the autogenerated SSL certificate if not specified.

[Deprecation warning]: ingress.tls will be deprecated in future
versions in favour of the new tls{} value to specify secrets.

[Deprecation warning]: ingress.hosts will be deprecated in future
versions too, new values will be announced.

For more information please check our changelog

0.4.2

Bump 4.2.0-1-ce version

0.4.1

Adds the ability to inject extra pod labels

0.4.0

Allow injection of variables to pods to use existing K8s secrets

Breaking change: redisProxyResources defined with app.cache.redis.sentinelProxy.resources

0.3.3

Bump passbolt docker image to 4.0.2-2-ce and merged community PR

0.3.2

Passbolt v4 and support for service annotations