Hi Community -
When we decided to build the Data Center helm charts, we knew that one of the added benefits was that we could make incremental improvements more frequently. We’re excited to share the latest fixes that we’ve made. Below you can find a list of features and changes.
Features and changes to the Data Center helm charts
-
You can define a custom schedulerName for the application StatefulSet.
-
You can define securityContext on the container and pod level. Use any settings that are available for the securityContext setting in the Kubernetes API.
-
You can configure the ingress.class annotation for the Ingress object. This is helpful if you're using multiple ingress controllers within your cluster.
-
StatefulSet pods are restarted in case there's a change to the ConfigMaps so that new changes are picked up.
-
All products are updated to their latest available LTS versions.
Features and changes to the Bitbucket Data Center helm charts
-
We’ve added support for Smart Mirrors and Mirror Farms. You can now deploy Bitbucket Data Center helm charts in mirror mode. It will be connected to a defined upstream to enable you to create a scalable mirroring deployment.
-
You can set the context path, which allows you to access the application through a path, such as https://mydomain.com/bitbucket. This feature is already available in the Jira Software and Confluence Data Center helm charts.
Features and changes to the Jira Software Data Center helm charts
You can find a complete changelog in the Helm chart repository.
Compatibility
There are no breaking changes in this release. If you are interested in what will change in the next major version, read the following document.
Installation
To install a new deployment, follow the installation documentation.
Upgrade
To upgrade the existing stack, follow the upgrade documentation.
Let us know if you have any questions in the comments below. We’ve also updated our documentation to reflect these updates.
0 comments