mirror of
https://github.com/bitnami/charts.git
synced 2026-03-06 15:10:15 +08:00
[bitnami/redmine] Release 17.2.5 updating components versions
Signed-off-by: Bitnami Containers <containers@bitnami.com>
This commit is contained in:
Bitnami Containers
@@ -1,12 +1,12 @@
|
||||
dependencies:
|
||||
- name: common
|
||||
repository: https://charts.bitnami.com/bitnami
|
||||
version: 1.11.0
|
||||
version: 1.11.1
|
||||
- name: mariadb
|
||||
repository: https://charts.bitnami.com/bitnami
|
||||
version: 9.8.1
|
||||
- name: postgresql
|
||||
repository: https://charts.bitnami.com/bitnami
|
||||
version: 10.16.2
|
||||
digest: sha256:9850c11539f2c818b1586acec2426534ba916a4375be53710d1455e78eccbc6f
|
||||
generated: "2022-02-01T17:58:49.573266+01:00"
|
||||
digest: sha256:dc59fb099ba79551712eda05d6ab6c92c2a914ee3cccce82ff86267a8fef9700
|
||||
generated: "2022-02-12T14:01:54.620871159Z"
|
||||
|
||||
@@ -16,7 +16,7 @@ dependencies:
|
||||
name: postgresql
|
||||
repository: https://charts.bitnami.com/bitnami
|
||||
version: 10.x.x
|
||||
description: A flexible project management web application.
|
||||
description: Redmine is an open source management application. It includes a tracking issue system, Gantt charts for a visual view of projects and deadlines, and supports SCM integration for version control.
|
||||
engine: gotpl
|
||||
home: https://github.com/bitnami/charts/tree/master/bitnami/redmine
|
||||
icon: https://bitnami.com/assets/stacks/redmine/img/redmine-stack-220x234.png
|
||||
@@ -36,4 +36,4 @@ name: redmine
|
||||
sources:
|
||||
- https://github.com/bitnami/bitnami-docker-redmine
|
||||
- https://www.redmine.org/
|
||||
version: 17.2.4
|
||||
version: 17.2.5
|
||||
|
||||
@@ -1,9 +1,13 @@
|
||||
<!--- app-name: Redmine -->
|
||||
<!--- app-name: ®edmine -->
|
||||
|
||||
# Redmine
|
||||
# ®edmine packaged by Bitnami
|
||||
|
||||
[Redmine](https://www.redmine.org) is a free and open source, web-based project management and issue tracking tool.
|
||||
®edmine is an open source management application. It includes a tracking issue system, Gantt charts for a visual view of projects and deadlines, and supports SCM integration for version control.
|
||||
|
||||
[Overview of ®edmine](http://www.redmine.org/)
|
||||
|
||||
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
|
||||
|
||||
## TL;DR
|
||||
|
||||
```bash
|
||||
@@ -13,9 +17,9 @@ $ helm install my-release bitnami/redmine
|
||||
|
||||
## Introduction
|
||||
|
||||
This chart bootstraps a [Redmine](https://github.com/bitnami/bitnami-docker-redmine) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
|
||||
This chart bootstraps a [®edmine](https://github.com/bitnami/bitnami-docker-redmine) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
|
||||
|
||||
It also packages the [Bitnami MariaDB chart](https://github.com/bitnami/charts/tree/master/bitnami/mariadb) and the [PostgreSQL chart](https://github.com/bitnami/charts/tree/master/bitnami/postgresql) which are required for bootstrapping a MariaDB/PostgreSQL deployment for the database requirements of the Redmine application.
|
||||
It also packages the [Bitnami MariaDB chart](https://github.com/bitnami/charts/tree/master/bitnami/mariadb) and the [PostgreSQL chart](https://github.com/bitnami/charts/tree/master/bitnami/postgresql) which are required for bootstrapping a MariaDB/PostgreSQL deployment for the database requirements of the ®edmine application.
|
||||
|
||||
Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment and management of Helm Charts in clusters. This chart has been tested to work with NGINX Ingress, cert-manager, fluentd and Prometheus on top of the [BKPR](https://kubeprod.io/).
|
||||
|
||||
@@ -34,7 +38,7 @@ To install the chart with the release name `my-release`:
|
||||
$ helm install my-release bitnami/redmine
|
||||
```
|
||||
|
||||
The command deploys Redmine on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
|
||||
The command deploys ®edmine on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
|
||||
|
||||
> **Tip**: List all releases using `helm list`
|
||||
|
||||
@@ -50,7 +54,7 @@ The command removes all the Kubernetes components associated with the chart and
|
||||
|
||||
## Using PostgreSQL instead of MariaDB
|
||||
|
||||
This chart includes the option to use a PostgreSQL database for Redmine instead of MariaDB. To use this, set the `databaseType` parameter to `postgresql`:
|
||||
This chart includes the option to use a PostgreSQL database for ®edmine instead of MariaDB. To use this, set the `databaseType` parameter to `postgresql`:
|
||||
|
||||
```
|
||||
helm install my-release bitnami/redmine --set databaseType=postgresql
|
||||
@@ -77,54 +81,54 @@ helm install my-release bitnami/redmine --set databaseType=postgresql
|
||||
| `commonLabels` | Labels to add to all deployed objects | `{}` |
|
||||
| `commonAnnotations` | Annotations to add to all deployed objects | `{}` |
|
||||
| `extraDeploy` | Array of extra objects to deploy with the release | `[]` |
|
||||
| `image.registry` | Redmine image registry | `docker.io` |
|
||||
| `image.repository` | Redmine image repository | `bitnami/redmine` |
|
||||
| `image.tag` | Redmine image tag (immutable tags are recommended) | `4.2.3-debian-10-r88` |
|
||||
| `image.pullPolicy` | Redmine image pull policy | `IfNotPresent` |
|
||||
| `image.pullSecrets` | Redmine image pull secrets | `[]` |
|
||||
| `image.registry` | ®edmine image registry | `docker.io` |
|
||||
| `image.repository` | ®edmine image repository | `bitnami/redmine` |
|
||||
| `image.tag` | ®edmine image tag (immutable tags are recommended) | `4.2.3-debian-10-r88` |
|
||||
| `image.pullPolicy` | ®edmine image pull policy | `IfNotPresent` |
|
||||
| `image.pullSecrets` | ®edmine image pull secrets | `[]` |
|
||||
| `image.debug` | Enable image debug mode | `false` |
|
||||
|
||||
|
||||
### Redmine Configuration parameters
|
||||
### ®edmine Configuration parameters
|
||||
|
||||
| Name | Description | Value |
|
||||
| ----------------------- | ---------------------------------------------------------------------- | ------------------ |
|
||||
| `redmineUsername` | Redmine username | `user` |
|
||||
| `redminePassword` | Redmine user password | `""` |
|
||||
| `redmineEmail` | Redmine user email | `user@example.com` |
|
||||
| `redmineLanguage` | Redmine default data language | `en` |
|
||||
| `redmineUsername` | ®edmine username | `user` |
|
||||
| `redminePassword` | ®edmine user password | `""` |
|
||||
| `redmineEmail` | ®edmine user email | `user@example.com` |
|
||||
| `redmineLanguage` | ®edmine default data language | `en` |
|
||||
| `customPostInitScripts` | Custom post-init.d user scripts | `{}` |
|
||||
| `smtpHost` | SMTP server host | `""` |
|
||||
| `smtpPort` | SMTP server port | `""` |
|
||||
| `smtpUser` | SMTP username | `""` |
|
||||
| `smtpPassword` | SMTP user password | `""` |
|
||||
| `smtpProtocol` | SMTP protocol | `""` |
|
||||
| `existingSecret` | Name of existing secret containing Redmine credentials | `""` |
|
||||
| `existingSecret` | Name of existing secret containing ®edmine credentials | `""` |
|
||||
| `smtpExistingSecret` | The name of an existing secret with SMTP credentials | `""` |
|
||||
| `allowEmptyPassword` | Allow the container to be started with blank passwords | `false` |
|
||||
| `command` | Override default container command (useful when using custom images) | `[]` |
|
||||
| `args` | Override default container args (useful when using custom images) | `[]` |
|
||||
| `extraEnvVars` | Array with extra environment variables to add to the Redmine container | `[]` |
|
||||
| `extraEnvVars` | Array with extra environment variables to add to the ®edmine container | `[]` |
|
||||
| `extraEnvVarsCM` | Name of existing ConfigMap containing extra env vars | `""` |
|
||||
| `extraEnvVarsSecret` | Name of existing Secret containing extra env vars | `""` |
|
||||
|
||||
|
||||
### Redmine deployment parameters
|
||||
### ®edmine deployment parameters
|
||||
|
||||
| Name | Description | Value |
|
||||
| ------------------------------------ | ----------------------------------------------------------------------------------------- | --------------- |
|
||||
| `replicaCount` | Number of Redmine replicas to deploy | `1` |
|
||||
| `updateStrategy.type` | Redmine deployment strategy type | `RollingUpdate` |
|
||||
| `replicaCount` | Number of ®edmine replicas to deploy | `1` |
|
||||
| `updateStrategy.type` | ®edmine deployment strategy type | `RollingUpdate` |
|
||||
| `schedulerName` | Alternate scheduler | `""` |
|
||||
| `serviceAccount.create` | Specifies whether a ServiceAccount should be created | `false` |
|
||||
| `serviceAccount.name` | The name of the ServiceAccount to create. Defaults to the `redmine.fullname` macro | `""` |
|
||||
| `hostAliases` | Redmine pod host aliases | `[]` |
|
||||
| `extraVolumes` | Optionally specify extra list of additional volumes for Redmine pods | `[]` |
|
||||
| `extraVolumeMounts` | Optionally specify extra list of additional volumeMounts for Redmine container(s) | `[]` |
|
||||
| `sidecars` | Add additional sidecar containers to the Redmine pod | `[]` |
|
||||
| `initContainers` | Add additional init containers to the Redmine pods | `[]` |
|
||||
| `podLabels` | Extra labels for Redmine pods | `{}` |
|
||||
| `podAnnotations` | Annotations for Redmine pods | `{}` |
|
||||
| `hostAliases` | ®edmine pod host aliases | `[]` |
|
||||
| `extraVolumes` | Optionally specify extra list of additional volumes for ®edmine pods | `[]` |
|
||||
| `extraVolumeMounts` | Optionally specify extra list of additional volumeMounts for ®edmine container(s) | `[]` |
|
||||
| `sidecars` | Add additional sidecar containers to the ®edmine pod | `[]` |
|
||||
| `initContainers` | Add additional init containers to the ®edmine pods | `[]` |
|
||||
| `podLabels` | Extra labels for ®edmine pods | `{}` |
|
||||
| `podAnnotations` | Annotations for ®edmine pods | `{}` |
|
||||
| `podAffinityPreset` | Pod affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `""` |
|
||||
| `podAntiAffinityPreset` | Pod anti-affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `soft` |
|
||||
| `nodeAffinityPreset.type` | Node affinity preset type. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `""` |
|
||||
@@ -133,13 +137,13 @@ helm install my-release bitnami/redmine --set databaseType=postgresql
|
||||
| `affinity` | Affinity for pod assignment | `{}` |
|
||||
| `nodeSelector` | Node labels for pod assignment | `{}` |
|
||||
| `tolerations` | Tolerations for pod assignment | `[]` |
|
||||
| `resources.limits` | The resources limits for the Redmine container | `{}` |
|
||||
| `resources.requests` | The requested resources for the Redmine container | `{}` |
|
||||
| `containerPort` | Redmine HTTP container port | `3000` |
|
||||
| `podSecurityContext.enabled` | Enabled Redmine pods' Security Context | `false` |
|
||||
| `podSecurityContext.fsGroup` | Set Redmine pod's Security Context fsGroup | `1001` |
|
||||
| `containerSecurityContext.enabled` | Enabled Redmine containers' Security Context | `false` |
|
||||
| `containerSecurityContext.runAsUser` | Set Redmine container's Security Context runAsUser | `1001` |
|
||||
| `resources.limits` | The resources limits for the ®edmine container | `{}` |
|
||||
| `resources.requests` | The requested resources for the ®edmine container | `{}` |
|
||||
| `containerPort` | ®edmine HTTP container port | `3000` |
|
||||
| `podSecurityContext.enabled` | Enabled ®edmine pods' Security Context | `false` |
|
||||
| `podSecurityContext.fsGroup` | Set ®edmine pod's Security Context fsGroup | `1001` |
|
||||
| `containerSecurityContext.enabled` | Enabled ®edmine containers' Security Context | `false` |
|
||||
| `containerSecurityContext.runAsUser` | Set ®edmine container's Security Context runAsUser | `1001` |
|
||||
| `livenessProbe.enabled` | Enable livenessProbe | `true` |
|
||||
| `livenessProbe.path` | Path for to check for livenessProbe | `/` |
|
||||
| `livenessProbe.initialDelaySeconds` | Initial delay seconds for livenessProbe | `300` |
|
||||
@@ -170,16 +174,16 @@ helm install my-release bitnami/redmine --set databaseType=postgresql
|
||||
|
||||
| Name | Description | Value |
|
||||
|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|--------------------------|
|
||||
| `service.type` | Redmine service type | `LoadBalancer` |
|
||||
| `service.port` | Redmine service HTTP port | `80` |
|
||||
| `service.type` | ®edmine service type | `LoadBalancer` |
|
||||
| `service.port` | ®edmine service HTTP port | `80` |
|
||||
| `service.nodePort` | Node port for HTTP | `""` |
|
||||
| `service.clusterIP` | Redmine service Cluster IP | `""` |
|
||||
| `service.loadBalancerIP` | Redmine service Load Balancer IP | `""` |
|
||||
| `service.loadBalancerSourceRanges` | Redmine service Load Balancer sources | `[]` |
|
||||
| `service.externalTrafficPolicy` | Redmine service external traffic policy | `Cluster` |
|
||||
| `service.annotations` | Additional custom annotations for Redmine service | `{}` |
|
||||
| `service.extraPorts` | Extra port to expose on Redmine service | `[]` |
|
||||
| `ingress.enabled` | Enable ingress record generation for Redmine | `false` |
|
||||
| `service.clusterIP` | ®edmine service Cluster IP | `""` |
|
||||
| `service.loadBalancerIP` | ®edmine service Load Balancer IP | `""` |
|
||||
| `service.loadBalancerSourceRanges` | ®edmine service Load Balancer sources | `[]` |
|
||||
| `service.externalTrafficPolicy` | ®edmine service external traffic policy | `Cluster` |
|
||||
| `service.annotations` | Additional custom annotations for ®edmine service | `{}` |
|
||||
| `service.extraPorts` | Extra port to expose on ®edmine service | `[]` |
|
||||
| `ingress.enabled` | Enable ingress record generation for ®edmine | `false` |
|
||||
| `ingress.selfSigned` | Create a TLS secret for this ingress record using self-signed certificates generated by Helm | `false` |
|
||||
| `ingress.className` | Set the ingressClassName which will be used for this ingress | `""` |
|
||||
| `ingress.pathType` | Ingress path type | `ImplementationSpecific` |
|
||||
@@ -217,9 +221,9 @@ helm install my-release bitnami/redmine --set databaseType=postgresql
|
||||
| `podDisruptionBudget.create` | Enable a Pod Disruption Budget creation | `false` |
|
||||
| `podDisruptionBudget.minAvailable` | Minimum number/percentage of pods that should remain scheduled | `""` |
|
||||
| `podDisruptionBudget.maxUnavailable` | Maximum number/percentage of pods that may be made unavailable | `""` |
|
||||
| `autoscaling.enabled` | Enable Horizontal POD autoscaling for Redmine | `false` |
|
||||
| `autoscaling.minReplicas` | Minimum number of Redmine replicas | `1` |
|
||||
| `autoscaling.maxReplicas` | Maximum number of Redmine replicas | `11` |
|
||||
| `autoscaling.enabled` | Enable Horizontal POD autoscaling for ®edmine | `false` |
|
||||
| `autoscaling.minReplicas` | Minimum number of ®edmine replicas | `1` |
|
||||
| `autoscaling.maxReplicas` | Maximum number of ®edmine replicas | `11` |
|
||||
| `autoscaling.targetCPU` | Target CPU utilization percentage | `50` |
|
||||
| `autoscaling.targetMemory` | Target Memory utilization percentage | `50` |
|
||||
|
||||
@@ -228,7 +232,7 @@ helm install my-release bitnami/redmine --set databaseType=postgresql
|
||||
|
||||
| Name | Description | Value |
|
||||
| ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
|
||||
| `databaseType` | Redmine database type. Allowed values: `mariadb` and `postgresql` | `mariadb` |
|
||||
| `databaseType` | ®edmine database type. Allowed values: `mariadb` and `postgresql` | `mariadb` |
|
||||
| `mariadb.enabled` | Whether to deploy a MariaDB server to satisfy the database requirements | `true` |
|
||||
| `mariadb.architecture` | MariaDB architecture. Allowed values: `standalone` or `replication` | `standalone` |
|
||||
| `mariadb.auth.rootPassword` | MariaDB root password | `""` |
|
||||
@@ -268,7 +272,7 @@ helm install my-release bitnami/redmine --set databaseType=postgresql
|
||||
| `mailReceiver.suspend` | Whether to create suspended CronJob | `true` |
|
||||
| `mailReceiver.podAnnotations` | Additional pod annotations | `{}` |
|
||||
| `mailReceiver.podLabels` | Additional pod labels | `{}` |
|
||||
| `mailReceiver.priorityClassName` | Redmine pods' priority. | `""` |
|
||||
| `mailReceiver.priorityClassName` | ®edmine pods' priority. | `""` |
|
||||
| `mailReceiver.mailProtocol` | Mail protocol to use for reading emails. Allowed values: `IMAP` and `POP3` | `IMAP` |
|
||||
| `mailReceiver.host` | Server to receive emails from | `""` |
|
||||
| `mailReceiver.port` | TCP port on the `host` | `993` |
|
||||
@@ -298,8 +302,8 @@ helm install my-release bitnami/redmine --set databaseType=postgresql
|
||||
| `mailReceiver.extraVolumeMounts` | Optionally specify extra list of additional volumeMounts for mailReceiver container | `[]` |
|
||||
| `mailReceiver.command` | Override default container command (useful when using custom images) | `["bash"]` |
|
||||
| `mailReceiver.args` | Override default container args (useful when using custom images) | `["-c","/cj/receive.sh"]` |
|
||||
| `mailReceiver.podSecurityContext.enabled` | Enabled Redmine pods' Security Context | `true` |
|
||||
| `mailReceiver.podSecurityContext.fsGroup` | Set Redmine pod's Security Context fsGroup | `1001` |
|
||||
| `mailReceiver.podSecurityContext.enabled` | Enabled ®edmine pods' Security Context | `true` |
|
||||
| `mailReceiver.podSecurityContext.fsGroup` | Set ®edmine pod's Security Context fsGroup | `1001` |
|
||||
| `mailReceiver.containerSecurityContext.enabled` | mailReceiver Container securityContext | `false` |
|
||||
| `mailReceiver.containerSecurityContext.runAsUser` | User ID for the mailReceiver container | `1001` |
|
||||
| `mailReceiver.containerSecurityContext.runAsNonRoot` | Whether to run the mailReceiver container as a non-root user | `true` |
|
||||
@@ -326,11 +330,11 @@ helm install my-release bitnami/redmine --set databaseType=postgresql
|
||||
| `certificates.customCertificate.chainSecret.name` | Name of the secret containing the certificate chain | `""` |
|
||||
| `certificates.customCertificate.chainSecret.key` | Key of the certificate chain file inside the secret | `""` |
|
||||
| `certificates.customCA` | Defines a list of secrets to import into the container trust store | `[]` |
|
||||
| `certificates.image.registry` | Redmine image registry | `docker.io` |
|
||||
| `certificates.image.repository` | Redmine image repository | `bitnami/bitnami-shell` |
|
||||
| `certificates.image.tag` | Redmine image tag (immutable tags are recommended) | `10-debian-10-r309` |
|
||||
| `certificates.image.pullPolicy` | Redmine image pull policy | `IfNotPresent` |
|
||||
| `certificates.image.pullSecrets` | Redmine image pull secrets | `[]` |
|
||||
| `certificates.image.registry` | ®edmine image registry | `docker.io` |
|
||||
| `certificates.image.repository` | ®edmine image repository | `bitnami/bitnami-shell` |
|
||||
| `certificates.image.tag` | ®edmine image tag (immutable tags are recommended) | `10-debian-10-r309` |
|
||||
| `certificates.image.pullPolicy` | ®edmine image pull policy | `IfNotPresent` |
|
||||
| `certificates.image.pullSecrets` | ®edmine image pull secrets | `[]` |
|
||||
| `certificates.extraEnvVars` | Container sidecar extra environment variables (e.g. proxy) | `[]` |
|
||||
|
||||
|
||||
@@ -342,11 +346,11 @@ helm install my-release bitnami/redmine --set databaseType=postgresql
|
||||
| `networkPolicy.ingress.enabled` | Enable network policy for Ingress Proxies | `false` |
|
||||
| `networkPolicy.ingress.namespaceSelector` | Ingress Proxy namespace selector labels. These labels will be used to identify the Ingress Proxy's namespace. | `{}` |
|
||||
| `networkPolicy.ingress.podSelector` | Ingress Proxy pods selector labels. These labels will be used to identify the Ingress Proxy pods. | `{}` |
|
||||
| `networkPolicy.ingressRules.backendOnlyAccessibleByFrontend` | Enable ingress rule that makes the backend (mariadb) only accessible by Redmine's pods. | `false` |
|
||||
| `networkPolicy.ingressRules.backendOnlyAccessibleByFrontend` | Enable ingress rule that makes the backend (mariadb) only accessible by ®edmine's pods. | `false` |
|
||||
| `networkPolicy.ingressRules.customBackendSelector` | Backend selector labels. These labels will be used to identify the backend pods. | `{}` |
|
||||
| `networkPolicy.ingressRules.accessOnlyFrom.enabled` | Enable ingress rule that makes Redmine only accessible from a particular origin | `false` |
|
||||
| `networkPolicy.ingressRules.accessOnlyFrom.namespaceSelector` | Namespace selector label that is allowed to access Redmine. This label will be used to identified the allowed namespace(s). | `{}` |
|
||||
| `networkPolicy.ingressRules.accessOnlyFrom.podSelector` | Pods selector label that is allowed to access Redmine. This label will be used to identified the allowed pod(s). | `{}` |
|
||||
| `networkPolicy.ingressRules.accessOnlyFrom.enabled` | Enable ingress rule that makes ®edmine only accessible from a particular origin | `false` |
|
||||
| `networkPolicy.ingressRules.accessOnlyFrom.namespaceSelector` | Namespace selector label that is allowed to access ®edmine. This label will be used to identified the allowed namespace(s). | `{}` |
|
||||
| `networkPolicy.ingressRules.accessOnlyFrom.podSelector` | Pods selector label that is allowed to access ®edmine. This label will be used to identified the allowed pod(s). | `{}` |
|
||||
| `networkPolicy.ingressRules.customRules` | Custom network policy ingress rule | `{}` |
|
||||
| `networkPolicy.egressRules.denyConnectionsToExternal` | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53). | `false` |
|
||||
| `networkPolicy.egressRules.customRules` | Custom network policy rule | `{}` |
|
||||
@@ -362,7 +366,7 @@ $ helm install my-release \
|
||||
bitnami/redmine
|
||||
```
|
||||
|
||||
The above command sets the Redmine administrator account username and password to `admin` and `password` respectively. Additionally, it sets the MariaDB `root` user password to `secretpassword`.
|
||||
The above command sets the ®edmine administrator account username and password to `admin` and `password` respectively. Additionally, it sets the MariaDB `root` user password to `secretpassword`.
|
||||
|
||||
> NOTE: Once this chart is deployed, it is not possible to change the application's access credentials, such as usernames or passwords, using Helm. To change these application credentials after deployment, delete any persistent volumes (PVs) used by the chart and re-deploy it, or use the application's built-in administrative tools if available.
|
||||
|
||||
@@ -384,9 +388,9 @@ Bitnami will release a new chart updating its containers if a new version of the
|
||||
|
||||
### Replicas
|
||||
|
||||
Redmine writes uploaded files to a persistent volume. By default that volume cannot be shared between pods (RWO). In such a configuration the `replicas` option must be set to `1`. If the persistent volume supports more than one writer (RWX), ie NFS, `replicas` can be greater than `1`.
|
||||
®edmine writes uploaded files to a persistent volume. By default that volume cannot be shared between pods (RWO). In such a configuration the `replicas` option must be set to `1`. If the persistent volume supports more than one writer (RWX), ie NFS, `replicas` can be greater than `1`.
|
||||
|
||||
> **Important**: When running more than one instance of Redmine they must share the same `secret_key_base` to have sessions working acreoss all instances.
|
||||
> **Important**: When running more than one instance of ®edmine they must share the same `secret_key_base` to have sessions working acreoss all instances.
|
||||
> This can be achieved by setting
|
||||
>
|
||||
> ```
|
||||
@@ -399,7 +403,7 @@ Redmine writes uploaded files to a persistent volume. By default that volume can
|
||||
|
||||
(adapted from https://github.com/bitnami/bitnami-docker-redmine)
|
||||
|
||||
On certain occasions, you may need that Redmine is available under a specific sub-URI path rather than the root. A common scenario to this problem may arise if you plan to set up your Redmine container behind a reverse proxy. To deploy your Redmine container using a certain sub-URI you just need to follow these steps:
|
||||
On certain occasions, you may need that ®edmine is available under a specific sub-URI path rather than the root. A common scenario to this problem may arise if you plan to set up your ®edmine container behind a reverse proxy. To deploy your ®edmine container using a certain sub-URI you just need to follow these steps:
|
||||
|
||||
#### Create a configmap containing an altered version of post-init.sh
|
||||
|
||||
@@ -427,7 +431,7 @@ data:
|
||||
echo 'map ActionController::Base.config.try(:relative_url_root) || "/" do' >> ${config1}
|
||||
echo 'run Rails.application' >> ${config1}
|
||||
echo 'end' >> ${config1}
|
||||
echo 'Redmine::Utils::relative_url_root = "'${SUB_URI_PATH}'"' >> ${config2}
|
||||
echo '®edmine::Utils::relative_url_root = "'${SUB_URI_PATH}'"' >> ${config2}
|
||||
|
||||
SUB_URI_PATH=$(echo ${SUB_URI_PATH} | sed -e 's|/|\\/|g')
|
||||
sed -i -e "s/\(relative_url_root\ \=\ \"\).*\(\"\)/\1${SUB_URI_PATH}\2/" ${config2}
|
||||
@@ -468,7 +472,7 @@ readinessProbe:
|
||||
|
||||
## Persistence
|
||||
|
||||
The [Bitnami Redmine](https://github.com/bitnami/bitnami-docker-redmine) image stores the Redmine data and configurations at the `/bitnami/redmine` path of the container.
|
||||
The [Bitnami ®edmine](https://github.com/bitnami/bitnami-docker-redmine) image stores the ®edmine data and configurations at the `/bitnami/redmine` path of the container.
|
||||
|
||||
Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube. The volume is created using dynamic volume provisioning. Clusters configured with NFS mounts require manually managed volumes and claims.
|
||||
|
||||
@@ -476,7 +480,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
|
||||
|
||||
### Existing PersistentVolumeClaims
|
||||
|
||||
The following example includes two PVCs, one for Redmine and another for MariaDB.
|
||||
The following example includes two PVCs, one for ®edmine and another for MariaDB.
|
||||
|
||||
1. Create the PersistentVolume
|
||||
1. Create the PersistentVolumeClaim
|
||||
@@ -577,7 +581,7 @@ See [PR#7114](https://github.com/bitnami/charts/pull/7114) for more info about t
|
||||
|
||||
### To 16.0.0
|
||||
|
||||
The [Bitnami Redmine](https://github.com/bitnami/bitnami-docker-redmine) image was refactored and now the source code is published in GitHub in the [`rootfs`](https://github.com/bitnami/bitnami-docker-redmine/tree/master/4/debian-10/rootfs) folder of the container image repository.
|
||||
The [Bitnami ®edmine](https://github.com/bitnami/bitnami-docker-redmine) image was refactored and now the source code is published in GitHub in the [`rootfs`](https://github.com/bitnami/bitnami-docker-redmine/tree/master/4/debian-10/rootfs) folder of the container image repository.
|
||||
|
||||
Upgrades from previous versions require to specify `--set volumePermissions.enabled=true` in order for all features to work properly:
|
||||
|
||||
@@ -613,7 +617,7 @@ Full compatibility is not guaranteed due to the amount of involved changes, howe
|
||||
|
||||
As a consequence, backwards compatibility from previous versions is not guaranteed during the upgrade. To upgrade to this new version `15.0.0` there are two alternatives:
|
||||
|
||||
- Install a new Redmine chart and follow the [official guide on how to backup/restore](https://www.redmine.org/projects/redmine/wiki/RedmineBackupRestore).
|
||||
- Install a new ®edmine chart and follow the [official guide on how to backup/restore](https://www.redmine.org/projects/redmine/wiki/®edmineBackupRestore).
|
||||
|
||||
- Reuse the PVC used to hold the PostgreSQL/MariaDB data on your previous release. To do so, follow the instructions below.
|
||||
|
||||
@@ -631,7 +635,7 @@ example-mariadb-0 1/1 Running 0 40s
|
||||
example-redmine-9f8c7b54d-trns2 1/1 Running 0 72s
|
||||
```
|
||||
|
||||
2. Export both MariaDB and Redmine credentials in order to provide them in the update
|
||||
2. Export both MariaDB and ®edmine credentials in order to provide them in the update
|
||||
|
||||
```console
|
||||
$ export REDMINE_PASSWORD=$(kubectl get secret --namespace default example-redmine -o jsonpath="{.data.redmine-password}" | base64 --decode)
|
||||
@@ -641,7 +645,7 @@ $ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default example-
|
||||
$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default example-mariadb -o jsonpath="{.data.mariadb-password}" | base64 --decode)
|
||||
```
|
||||
|
||||
3. Delete the Redmine deployment and delete the MariaDB statefulset. Notice the option `--cascade=false` in the latter.
|
||||
3. Delete the ®edmine deployment and delete the MariaDB statefulset. Notice the option `--cascade=false` in the latter.
|
||||
|
||||
```console
|
||||
$ kubectl delete deployment.apps/example-redmine
|
||||
@@ -729,4 +733,4 @@ Unless required by applicable law or agreed to in writing, software
|
||||
distributed under the License is distributed on an "AS IS" BASIS,
|
||||
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||||
See the License for the specific language governing permissions and
|
||||
limitations under the License.
|
||||
limitations under the License.
|
||||
@@ -37,19 +37,19 @@ commonAnnotations: {}
|
||||
##
|
||||
extraDeploy: []
|
||||
|
||||
## Bitnami Redmine image
|
||||
## Bitnami ®edmine image
|
||||
## ref: https://hub.docker.com/r/bitnami/redmine/tags/
|
||||
## @param image.registry Redmine image registry
|
||||
## @param image.repository Redmine image repository
|
||||
## @param image.tag Redmine image tag (immutable tags are recommended)
|
||||
## @param image.pullPolicy Redmine image pull policy
|
||||
## @param image.pullSecrets [array] Redmine image pull secrets
|
||||
## @param image.registry ®edmine image registry
|
||||
## @param image.repository ®edmine image repository
|
||||
## @param image.tag ®edmine image tag (immutable tags are recommended)
|
||||
## @param image.pullPolicy ®edmine image pull policy
|
||||
## @param image.pullSecrets [array] ®edmine image pull secrets
|
||||
## @param image.debug Enable image debug mode
|
||||
##
|
||||
image:
|
||||
registry: docker.io
|
||||
repository: bitnami/redmine
|
||||
tag: 4.2.3-debian-10-r88
|
||||
tag: 4.2.3-debian-10-r117
|
||||
## Specify a imagePullPolicy
|
||||
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
|
||||
## ref: https://kubernetes.io/docs/user-guide/images/#pre-pulling-images
|
||||
@@ -67,24 +67,24 @@ image:
|
||||
##
|
||||
debug: false
|
||||
|
||||
## @section Redmine Configuration parameters
|
||||
## Redmine settings based on environment variables
|
||||
## @section ®edmine Configuration parameters
|
||||
## ®edmine settings based on environment variables
|
||||
## ref: https://github.com/bitnami/bitnami-docker-redmine#environment-variables
|
||||
|
||||
## @param redmineUsername Redmine username
|
||||
## @param redmineUsername ®edmine username
|
||||
## ref: https://github.com/bitnami/bitnami-docker-redmine#configuration
|
||||
##
|
||||
redmineUsername: user
|
||||
## @param redminePassword Redmine user password
|
||||
## @param redminePassword ®edmine user password
|
||||
## Defaults to a random 10-character alphanumeric string if not set
|
||||
## ref: https://github.com/bitnami/bitnami-docker-redmine#configuration
|
||||
##
|
||||
redminePassword: ""
|
||||
## @param redmineEmail Redmine user email
|
||||
## @param redmineEmail ®edmine user email
|
||||
## ref: https://github.com/bitnami/bitnami-docker-redmine#configuration
|
||||
##
|
||||
redmineEmail: user@example.com
|
||||
## @param redmineLanguage Redmine default data language
|
||||
## @param redmineLanguage ®edmine default data language
|
||||
## ref: https://github.com/bitnami/bitnami-docker-redmine/#environment-variables
|
||||
##
|
||||
redmineLanguage: en
|
||||
@@ -113,7 +113,7 @@ smtpPort: ""
|
||||
smtpUser: ""
|
||||
smtpPassword: ""
|
||||
smtpProtocol: ""
|
||||
## @param existingSecret Name of existing secret containing Redmine credentials
|
||||
## @param existingSecret Name of existing secret containing ®edmine credentials
|
||||
## NOTE: Must contain key `redmine-password`
|
||||
## NOTE: When it's set, the `redminePassword` parameter is ignored
|
||||
##
|
||||
@@ -132,7 +132,7 @@ command: []
|
||||
## @param args Override default container args (useful when using custom images)
|
||||
##
|
||||
args: []
|
||||
## @param extraEnvVars Array with extra environment variables to add to the Redmine container
|
||||
## @param extraEnvVars Array with extra environment variables to add to the ®edmine container
|
||||
## e.g:
|
||||
##
|
||||
# extraEnvVars:
|
||||
@@ -146,13 +146,13 @@ extraEnvVarsCM: ""
|
||||
##
|
||||
extraEnvVarsSecret: ""
|
||||
|
||||
## @section Redmine deployment parameters
|
||||
## @section ®edmine deployment parameters
|
||||
|
||||
## @param replicaCount Number of Redmine replicas to deploy
|
||||
## @param replicaCount Number of ®edmine replicas to deploy
|
||||
## NOTE: ReadWriteMany PVC(s) are required if replicaCount > 1
|
||||
##
|
||||
replicaCount: 1
|
||||
## @param updateStrategy.type Redmine deployment strategy type
|
||||
## @param updateStrategy.type ®edmine deployment strategy type
|
||||
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy
|
||||
## NOTE: Set it to `Recreate` if you use a PV that cannot be mounted on multiple pods
|
||||
## e.g:
|
||||
@@ -174,17 +174,17 @@ schedulerName: ""
|
||||
serviceAccount:
|
||||
create: false
|
||||
name: ""
|
||||
## @param hostAliases [array] Redmine pod host aliases
|
||||
## @param hostAliases [array] ®edmine pod host aliases
|
||||
## https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/
|
||||
##
|
||||
hostAliases: []
|
||||
## @param extraVolumes Optionally specify extra list of additional volumes for Redmine pods
|
||||
## @param extraVolumes Optionally specify extra list of additional volumes for ®edmine pods
|
||||
##
|
||||
extraVolumes: []
|
||||
## @param extraVolumeMounts Optionally specify extra list of additional volumeMounts for Redmine container(s)
|
||||
## @param extraVolumeMounts Optionally specify extra list of additional volumeMounts for ®edmine container(s)
|
||||
##
|
||||
extraVolumeMounts: []
|
||||
## @param sidecars Add additional sidecar containers to the Redmine pod
|
||||
## @param sidecars Add additional sidecar containers to the ®edmine pod
|
||||
## e.g:
|
||||
##
|
||||
# sidecars:
|
||||
@@ -195,7 +195,7 @@ extraVolumeMounts: []
|
||||
# - name: portname
|
||||
# containerPort: 1234
|
||||
sidecars: []
|
||||
## @param initContainers Add additional init containers to the Redmine pods
|
||||
## @param initContainers Add additional init containers to the ®edmine pods
|
||||
## ref: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/
|
||||
## e.g:
|
||||
##
|
||||
@@ -205,11 +205,11 @@ sidecars: []
|
||||
# imagePullPolicy: Always
|
||||
# command: ['sh', '-c', 'copy addons from git and push to /bitnami/redmine/plugins. Should work with extraVolumeMounts and extraVolumes']
|
||||
initContainers: []
|
||||
## @param podLabels Extra labels for Redmine pods
|
||||
## @param podLabels Extra labels for ®edmine pods
|
||||
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
|
||||
##
|
||||
podLabels: {}
|
||||
## @param podAnnotations Annotations for Redmine pods
|
||||
## @param podAnnotations Annotations for ®edmine pods
|
||||
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/
|
||||
##
|
||||
podAnnotations: {}
|
||||
@@ -251,10 +251,10 @@ nodeSelector: {}
|
||||
## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
|
||||
##
|
||||
tolerations: []
|
||||
## Redmine containers' resource requests and limits
|
||||
## ®edmine containers' resource requests and limits
|
||||
## ref: https://kubernetes.io/docs/user-guide/compute-resources/
|
||||
## @param resources.limits The resources limits for the Redmine container
|
||||
## @param resources.requests [object] The requested resources for the Redmine container
|
||||
## @param resources.limits The resources limits for the ®edmine container
|
||||
## @param resources.requests [object] The requested resources for the ®edmine container
|
||||
##
|
||||
resources:
|
||||
limits: {}
|
||||
@@ -262,26 +262,26 @@ resources:
|
||||
memory: 512Mi
|
||||
cpu: 300m
|
||||
## Container ports
|
||||
## @param containerPort Redmine HTTP container port
|
||||
## @param containerPort ®edmine HTTP container port
|
||||
##
|
||||
containerPort: 3000
|
||||
## Configure Pods Security Context
|
||||
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
|
||||
## @param podSecurityContext.enabled Enabled Redmine pods' Security Context
|
||||
## @param podSecurityContext.fsGroup Set Redmine pod's Security Context fsGroup
|
||||
## @param podSecurityContext.enabled Enabled ®edmine pods' Security Context
|
||||
## @param podSecurityContext.fsGroup Set ®edmine pod's Security Context fsGroup
|
||||
##
|
||||
podSecurityContext:
|
||||
enabled: false
|
||||
fsGroup: 1001
|
||||
## Configure Container Security Context (only main container)
|
||||
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-container
|
||||
## @param containerSecurityContext.enabled Enabled Redmine containers' Security Context
|
||||
## @param containerSecurityContext.runAsUser Set Redmine container's Security Context runAsUser
|
||||
## @param containerSecurityContext.enabled Enabled ®edmine containers' Security Context
|
||||
## @param containerSecurityContext.runAsUser Set ®edmine container's Security Context runAsUser
|
||||
##
|
||||
containerSecurityContext:
|
||||
enabled: false
|
||||
runAsUser: 1001
|
||||
## Configure extra options for Redmine containers' liveness and readiness probes
|
||||
## Configure extra options for ®edmine containers' liveness and readiness probes
|
||||
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes
|
||||
## @param livenessProbe.enabled Enable livenessProbe
|
||||
## @param livenessProbe.path Path for to check for livenessProbe
|
||||
@@ -343,13 +343,13 @@ customStartupProbe: {}
|
||||
|
||||
## @section Traffic Exposure Parameters
|
||||
|
||||
## Redmine service parameters
|
||||
## ®edmine service parameters
|
||||
##
|
||||
service:
|
||||
## @param service.type Redmine service type
|
||||
## @param service.type ®edmine service type
|
||||
##
|
||||
type: LoadBalancer
|
||||
## @param service.port Redmine service HTTP port
|
||||
## @param service.port ®edmine service HTTP port
|
||||
##
|
||||
port: 80
|
||||
## Node ports to expose
|
||||
@@ -357,38 +357,38 @@ service:
|
||||
## NOTE: choose port between <30000-32767>
|
||||
##
|
||||
nodePort: ""
|
||||
## @param service.clusterIP Redmine service Cluster IP
|
||||
## @param service.clusterIP ®edmine service Cluster IP
|
||||
## e.g.:
|
||||
## clusterIP: None
|
||||
##
|
||||
clusterIP: ""
|
||||
## @param service.loadBalancerIP Redmine service Load Balancer IP
|
||||
## @param service.loadBalancerIP ®edmine service Load Balancer IP
|
||||
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-loadbalancer
|
||||
##
|
||||
loadBalancerIP: ""
|
||||
## @param service.loadBalancerSourceRanges Redmine service Load Balancer sources
|
||||
## @param service.loadBalancerSourceRanges ®edmine service Load Balancer sources
|
||||
## ref: https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service
|
||||
## e.g:
|
||||
##
|
||||
# loadBalancerSourceRanges:
|
||||
# - 10.10.10.0/24
|
||||
loadBalancerSourceRanges: []
|
||||
## @param service.externalTrafficPolicy Redmine service external traffic policy
|
||||
## @param service.externalTrafficPolicy ®edmine service external traffic policy
|
||||
## ref https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
|
||||
##
|
||||
externalTrafficPolicy: Cluster
|
||||
## @param service.annotations Additional custom annotations for Redmine service
|
||||
## @param service.annotations Additional custom annotations for ®edmine service
|
||||
##
|
||||
annotations: {}
|
||||
## @param service.extraPorts Extra port to expose on Redmine service
|
||||
## @param service.extraPorts Extra port to expose on ®edmine service
|
||||
##
|
||||
extraPorts: []
|
||||
|
||||
## Configure the ingress resource that allows you to access the Redmine installation
|
||||
## Configure the ingress resource that allows you to access the ®edmine installation
|
||||
## ref: https://kubernetes.io/docs/concepts/services-networking/ingress/
|
||||
##
|
||||
ingress:
|
||||
## @param ingress.enabled Enable ingress record generation for Redmine
|
||||
## @param ingress.enabled Enable ingress record generation for ®edmine
|
||||
##
|
||||
enabled: false
|
||||
## @param ingress.className Set the ingressClassName which will be used for this ingress
|
||||
@@ -535,7 +535,7 @@ volumePermissions:
|
||||
|
||||
## @section Other Parameters
|
||||
|
||||
## Redmine Pod Disruption Budget configuration
|
||||
## ®edmine Pod Disruption Budget configuration
|
||||
## ref: https://kubernetes.io/docs/tasks/run-application/configure-pdb/
|
||||
## @param podDisruptionBudget.create Enable a Pod Disruption Budget creation
|
||||
## @param podDisruptionBudget.minAvailable Minimum number/percentage of pods that should remain scheduled
|
||||
@@ -546,11 +546,11 @@ podDisruptionBudget:
|
||||
minAvailable: ""
|
||||
maxUnavailable: ""
|
||||
|
||||
## Redmine Autoscaling configuration
|
||||
## ®edmine Autoscaling configuration
|
||||
## ref: https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/
|
||||
## @param autoscaling.enabled Enable Horizontal POD autoscaling for Redmine
|
||||
## @param autoscaling.minReplicas Minimum number of Redmine replicas
|
||||
## @param autoscaling.maxReplicas Maximum number of Redmine replicas
|
||||
## @param autoscaling.enabled Enable Horizontal POD autoscaling for ®edmine
|
||||
## @param autoscaling.minReplicas Minimum number of ®edmine replicas
|
||||
## @param autoscaling.maxReplicas Maximum number of ®edmine replicas
|
||||
## @param autoscaling.targetCPU Target CPU utilization percentage
|
||||
## @param autoscaling.targetMemory Target Memory utilization percentage
|
||||
##
|
||||
@@ -563,7 +563,7 @@ autoscaling:
|
||||
|
||||
## @section Database Parameters
|
||||
|
||||
## @param databaseType Redmine database type. Allowed values: `mariadb` and `postgresql`
|
||||
## @param databaseType ®edmine database type. Allowed values: `mariadb` and `postgresql`
|
||||
## ref: https://github.com/bitnami/bitnami-docker-redmine/#environment-variables
|
||||
##
|
||||
databaseType: mariadb
|
||||
@@ -701,7 +701,7 @@ externalDatabase:
|
||||
## @section Mail Receiver/Cron Job Parameters
|
||||
|
||||
## Configure CronJob scheduler for receiving emails and converting them to tasks
|
||||
## ref: https://www.redmine.org/projects/redmine/wiki/RedmineReceivingEmails
|
||||
## ref: https://www.redmine.org/projects/redmine/wiki/®edmineReceivingEmails
|
||||
##
|
||||
mailReceiver:
|
||||
## @param mailReceiver.enabled Whether to enable scheduled mail-to-task CronJob
|
||||
@@ -721,7 +721,7 @@ mailReceiver:
|
||||
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
|
||||
##
|
||||
podLabels: {}
|
||||
## @param mailReceiver.priorityClassName Redmine pods' priority.
|
||||
## @param mailReceiver.priorityClassName ®edmine pods' priority.
|
||||
## ref: https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/
|
||||
##
|
||||
priorityClassName: ""
|
||||
@@ -760,7 +760,7 @@ mailReceiver:
|
||||
##
|
||||
moveOnFailure: ""
|
||||
## @param mailReceiver.unknownUserAction Action to perform is an email received from unregistered user
|
||||
## ref: https://www.redmine.org/projects/redmine/wiki/RedmineReceivingEmails
|
||||
## ref: https://www.redmine.org/projects/redmine/wiki/®edmineReceivingEmails
|
||||
##
|
||||
unknownUserAction: ignore
|
||||
## @param mailReceiver.noPermissionCheck Whether skip permission check during creating a new task
|
||||
@@ -826,8 +826,8 @@ mailReceiver:
|
||||
args: ["-c", "/cj/receive.sh"]
|
||||
## Configure Pods Security Context
|
||||
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
|
||||
## @param mailReceiver.podSecurityContext.enabled Enabled Redmine pods' Security Context
|
||||
## @param mailReceiver.podSecurityContext.fsGroup Set Redmine pod's Security Context fsGroup
|
||||
## @param mailReceiver.podSecurityContext.enabled Enabled ®edmine pods' Security Context
|
||||
## @param mailReceiver.podSecurityContext.fsGroup Set ®edmine pod's Security Context fsGroup
|
||||
##
|
||||
podSecurityContext:
|
||||
enabled: true
|
||||
@@ -940,16 +940,16 @@ certificates:
|
||||
customCA: []
|
||||
# - secret: custom-CA
|
||||
# - secret: more-custom-CAs
|
||||
## @param certificates.image.registry Redmine image registry
|
||||
## @param certificates.image.repository Redmine image repository
|
||||
## @param certificates.image.tag Redmine image tag (immutable tags are recommended)
|
||||
## @param certificates.image.pullPolicy Redmine image pull policy
|
||||
## @param certificates.image.pullSecrets [array] Redmine image pull secrets
|
||||
## @param certificates.image.registry ®edmine image registry
|
||||
## @param certificates.image.repository ®edmine image repository
|
||||
## @param certificates.image.tag ®edmine image tag (immutable tags are recommended)
|
||||
## @param certificates.image.pullPolicy ®edmine image pull policy
|
||||
## @param certificates.image.pullSecrets [array] ®edmine image pull secrets
|
||||
##
|
||||
image:
|
||||
registry: docker.io
|
||||
repository: bitnami/bitnami-shell
|
||||
tag: 10-debian-10-r309
|
||||
tag: 10-debian-10-r336
|
||||
## Specify a imagePullPolicy
|
||||
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
|
||||
## ref: https://kubernetes.io/docs/user-guide/images/#pre-pulling-images
|
||||
@@ -988,15 +988,15 @@ networkPolicy:
|
||||
## label: ingress
|
||||
##
|
||||
namespaceSelector: {}
|
||||
## @param networkPolicy.ingressRules.backendOnlyAccessibleByFrontend Enable ingress rule that makes the backend (mariadb) only accessible by Redmine's pods.
|
||||
## @param networkPolicy.ingressRules.backendOnlyAccessibleByFrontend Enable ingress rule that makes the backend (mariadb) only accessible by ®edmine's pods.
|
||||
## @param networkPolicy.ingressRules.customBackendSelector Backend selector labels. These labels will be used to identify the backend pods.
|
||||
## @param networkPolicy.ingressRules.accessOnlyFrom.enabled Enable ingress rule that makes Redmine only accessible from a particular origin
|
||||
## @param networkPolicy.ingressRules.accessOnlyFrom.namespaceSelector Namespace selector label that is allowed to access Redmine. This label will be used to identified the allowed namespace(s).
|
||||
## @param networkPolicy.ingressRules.accessOnlyFrom.podSelector Pods selector label that is allowed to access Redmine. This label will be used to identified the allowed pod(s).
|
||||
## @param networkPolicy.ingressRules.accessOnlyFrom.enabled Enable ingress rule that makes ®edmine only accessible from a particular origin
|
||||
## @param networkPolicy.ingressRules.accessOnlyFrom.namespaceSelector Namespace selector label that is allowed to access ®edmine. This label will be used to identified the allowed namespace(s).
|
||||
## @param networkPolicy.ingressRules.accessOnlyFrom.podSelector Pods selector label that is allowed to access ®edmine. This label will be used to identified the allowed pod(s).
|
||||
## @param networkPolicy.ingressRules.customRules Custom network policy ingress rule
|
||||
##
|
||||
ingressRules:
|
||||
## mariadb backend only can be accessed from Redmine
|
||||
## mariadb backend only can be accessed from ®edmine
|
||||
##
|
||||
backendOnlyAccessibleByFrontend: false
|
||||
customBackendSelector: {}
|
||||
|
||||
Reference in New Issue
Block a user