profile
viewpoint
Carlos Rodríguez Hernández carrodher @vmware / @bitnami Seville (Spain) Member of Technical Staff (MTS) at @vmware / @bitnami

helm/charts 13740

Curated applications for Kubernetes

juan131/dockerfile-best-practices 62

Best Practices writing a Dockerfile

bitnami/bitnami-docker-orangehrm 14

Bitnami Docker Image for OrangeHRM

bitnami/bitnami-docker-harbor-portal 6

Bitnami Docker Image for Harbor

bitnami-labs/healthcheck-tools 5

Set of Go tools to check different elements of your stack (SSL, SMTP, Permissions...)

bitnami/bitnami-docker-harbor-registry 2

Bitnami Docker Image for Harbor Registry

bitnami/bitnami-docker-harbor-notary-server 1

Bitnami Docker Image for Harbor Notary Server

bitnami-bot/helm-charts 1

Curated applications for Kubernetes

darioalvarez/bitnami-bootcamp-2020 1

Bitnami Bootcamp 2020 repository

Angelmmiguel/adventcode2018 0

Code solutions for the advent code of 2018

issue commentbitnami/bitnami-docker-wordpress

Support for IPv6 in Apache config

Hi, I just created an internal task to investigate this issue and if it's possible to add IPv6 in the Apache configuration. We'll update the thread when we have more info. Thanks for letting us know

anuragbhatia

comment created time in 11 days

delete branch bitnami/charts

delete branch : kwemail

delete time in 11 days

issue commentbitnami/charts

Cannot produce/consume when using load balancer for per pod service NLB in kafka

Hi, running helm install kafka -f values.yaml bitnami/kafka it is going to use the default parameters, without taking into account the specific configuration for the load balancers. There are two ways, on the first one you can take advantage of an initContainer in order to discover the IPs, in that case you need to install the chart using

helm install kafka --set externalAccess.enabled=true --set externalAccess.service.type=LoadBalancer
externalAccess.service.port=9094 --set externalAccess.autoDiscovery.enabled=true --set serviceAccount.create=true --set rbac.create=true bitnami/kafka

On the second way, you can manually specify the IPs:

helm install kafka --set externalAccess.enabled=true --set externalAccess.service.type=LoadBalancer
externalAccess.service.port=9094 --set externalAccess.service.loadBalancerIPs[0]='external-ip-1' --set 
externalAccess.service.loadBalancerIPs[1]='external-ip-2' bitnami/kafka
dsindatry

comment created time in 11 days

issue commentbitnami/charts

Postgres-ha

Hi, thanks for being keeping an eye on this. Are you able to share this env. variable across nodes and maintain it up-to-date?

rg2609

comment created time in 11 days

issue commentbitnami/charts

[bitnami/mongodb] NodePort service is created with wrong targetPort

Hi, thanks for using the Bitnami MongoDB chart and for reporting this issue. We are going to take a look trying to reproduce the issue on our side; but yes, probably there is an issue with that

sgops

comment created time in 11 days

pull request commentbitnami/charts

[bitnami/moodle] Migrate container to non-root approach

Changes in terms of code LGTM, but the helm install GH action is failing. In the logs this is the error:

WARN  ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
INFO  ==> Starting gosu... 
ln: failed to create symbolic link '/etc/cron.d/moodle': Permission denied
cron: can't open or create /var/run/crond.pid: Permission denied
Starting Apache...
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 10.244.0.7. Set the 'ServerName' directive globally to suppress this message
(13)Permission denied: AH00072: make_sock: could not bind to address [::]:80
(13)Permission denied: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs

Not sure if now you need to set some extra parameters when installing the chart (it shouldn't, but if it's the case you can do it by creating a ci folder)

marcosbc

comment created time in 11 days

push eventbitnami/bitnami-docker-harbor-adapter-trivy

Carlos Rodriguez Hernandez

commit sha eb3d0d22fd3d5b6e7f40ad660c0ecb789cd5a8df

Remove old version folder

view details

push time in 12 days

push eventbitnami/bitnami-docker-harbor-notary-signer

Carlos Rodriguez Hernandez

commit sha 9aba43d050587ca300e3cef495d452da49649839

Remove old version folder

view details

push time in 12 days

push eventbitnami/bitnami-docker-harbor-adapter-clair

Carlos Rodriguez Hernandez

commit sha 36064c147c1aec07e8971f797468a4592fb606fa

Remove old version folder

view details

push time in 12 days

push eventbitnami/bitnami-docker-harbor-notary-server

Carlos Rodriguez Hernandez

commit sha 25a40c7cdde02a1befe7e5db935b9c2f05aea9c0

Remove old version folder

view details

push time in 12 days

push eventbitnami/bitnami-docker-harbor-jobservice

Carlos Rodriguez Hernandez

commit sha c764bf786177ab1aedc6ded1847110e3c000a966

Remove old version folder

view details

push time in 12 days

push eventbitnami/bitnami-docker-harbor-registryctl

Carlos Rodriguez Hernandez

commit sha 3a0ef690f7d7fbfe17020821b4683cb2cd29054a

Remove old version folder

view details

push time in 12 days

push eventbitnami/bitnami-docker-harbor-clair

Carlos Rodriguez Hernandez

commit sha 18690df51892039f69317c79a2137c0e01408f5b

Remove old version folder

view details

push time in 12 days

push eventbitnami/bitnami-docker-harbor-registry

Carlos Rodriguez Hernandez

commit sha 4c98a86023b8f17767b6ea7152ef0b5b53b96e4e

Remove old version folder

view details

push time in 12 days

push eventbitnami/bitnami-docker-harbor-core

Carlos Rodriguez Hernandez

commit sha b4c8fa69312d2476f18293914a30a6bf9231e848

Remove old version folder

view details

push time in 12 days

push eventbitnami/bitnami-docker-harbor-portal

Carlos Rodriguez Hernandez

commit sha 96b63388ac687423f6060424d385b4f568505a8f

Remove old version folder

view details

push time in 12 days

issue commentbitnami/charts

Cannot produce/consume when using load balancer for per pod service NLB in kafka

Hi, thanks for using the bitnami kafka chart. In order to try to reproduce the issue on our side, please can you provide more info about how did you deploy the chart? Did you change any parameter by using a custom values.yaml or options via --set when installing the chart?

In the same way, there is a section in the README about how to access Kafka brokers from outside the cluster, can you take a look just in case you find something useful for your use case?

dsindatry

comment created time in 12 days

issue commentbitnami/bitnami-docker-wordpress

Support for IPv6 in Apache config

Hi, thanks for reporting this issue. In order to be able to reproduce the issue and provide more information if it is needed to implement any changes, can you please share with us the changes you are doing in the docker-compose to enable IPv6? Thanks

anuragbhatia

comment created time in 12 days

Pull request review commentbitnami/charts

[bitnami/ejbca] EJBCA Chart

+## Global Docker image parameters+## Please, note that this will override the image parameters, including dependencies, configured to use the global value+## Current available global Docker image parameters: imageRegistry and imagePullSecrets+##+# global:+#   imageRegistry: myRegistryName+#   imagePullSecrets:+#     - myRegistryKeySecretName+#   storageClass: myStorageClass++## Bitnami EJBCA image version+## ref: https://hub.docker.com/r/bitnami/ejbca/tags/+##+image:+  registry: docker.io+  repository: bitnami/ejbca+  tag: latest+  ## Specify a imagePullPolicy+  ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'+  ## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images+  ##+  pullPolicy: IfNotPresent+  ## Optionally specify an array of imagePullSecrets.+  ## Secrets must be manually created in the namespace.+  ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/+  ##+  # pullSecrets:+  #   - myRegistryKeySecretName+  ## Set to true if you would like to see extra information on logs+  ##++## String to partially override ebjca.fullname template (will maintain the release name)+##+# nameOverride:++## String to fully override ebjca.fullname template+##+# fullnameOverride:++replicaCount: 1

I would add here a comment, as the rest of parameters has their own comment this looks weird

joancafom

comment created time in 12 days

Pull request review commentbitnami/charts

[bitnami/ejbca] EJBCA Chart

+# EJBCA++[EJBCA](https://www.ejbca.org/) is a free software public key infrastructure certificate authority software package.++## TL;DR;++```console+$ helm repo add bitnami https://charts.bitnami.com/bitnami+$ helm install my-release bitnami/ejbca+```++## Introduction++This chart bootstraps a [EJBCA](https://www.ejbca.org/) deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.++It also packages [Bitnami MariaDB](https://github.com/bitnami/charts/tree/master/bitnami/mariadb) as the required databases for the EJBCA application.++Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment and management of Helm Charts in clusters.++## Prerequisites++- Kubernetes 1.12++- Helm 2.11+ or Helm 3.0-beta3++- PV provisioner support in the underlying infrastructure++## Installing the Chart++To install the chart with the release name `my-release`:++```console+$ helm install my-release bitnami/ejbca+```++The command deploys EJBCA 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`++## Uninstalling the Chart++To uninstall/delete the `my-release` deployment:++```console+$ helm delete my-release+```++The command removes all the Kubernetes components associated with the chart and deletes the release.++## Parameters++The following table lists the configurable parameters of the EJBCA chart and their default values.++ Parameter                                  | Description                                                                           | Default                                                      |+|-------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------------------------------------|+| `global.imageRegistry`                    | Global Docker image registry                                                          | `nil`                                                        |+| `global.imagePullSecrets`                 | Global Docker registry secret names as an array                                       | `[]` (does not add image pull secrets to deployed pods)      |+| `global.storageClass`                     | Global storage class for dynamic provisioning                                         | `nil`                                                        |++### Common & Pod-specific parameters++| Parameter                                 | Description                                                                           | Default                                                      |+|-------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------------------------------------|+| `image.registry`                          | EJBCA image registry                                                                  | `docker.io`                                                  |+| `image.repository`                        | EJBCA image name                                                                      | `bitnami/ejbca`                                              |+| `image.tag`                               | EJBCA image tag                                                                       | `{TAG_NAME}`                                                 |+| `image.pullPolicy`                        | EJBCA image pull policy                                                               | `IfNotPresent`                                               |+| `image.pullSecrets`                       | Specify docker-registry secret names as an array                                      | `[]` (does not add image pull secrets to deployed pods)      |+| `nameOverride`                            | String to partially override discourse.fullname                                       | `nil`                                                        |+| `fullnameOverride`                        | String to fully override discourse.fullname                                           | `nil`                                                        |+| `replicaCount`                            | Number of EJBCA replicas                                                              | `1`                                                          |+| `extraVolumes`                            | Array of extra volumes to be added deployment. Requires setting `extraVolumeMounts`   | `[]` (evaluated as a template)                               |+| `podAnnotations`                          | Additional pod annotations                                                            | `{}`                                                         |+| `podLabels`                               | Additional pod labels                                                                 | `{}` (evaluated as a template)                               |+| `commonLabels`                            | Labels to be added to all deployed resources                                          | `{}` (evaluated as a template)                               |+| `commonAnnotations`                       | Annotations to be added to all deployed resources                                     | `{}` (evaluated as a template)                               |+| `podSecurityContext.enabled`              | Enable security context for EJBCA pods                                                | `true`                                                       |+| `podSecurityContext.fsGroup`              | Group ID for the volumes of the pod                                                   | `1001`                                                       |+| `nodeSelector`                            | Node labels for pod assignment.                                                       | `{}` (evaluated as a template)                               |+| `tolerations`                             | Tolerations for pod assignment.                                                       | `[]` (evaluated as a template)                               |+| `affinity`                                | Affinity for pod assignment                                                           | `{}` (evaluated as a template)                               |+| `sidecars`                                | Attach additional sidecar containers to the pod                                       | `[]` (evaluated as a template)                               |+| `initContainers`                          | Additional init containers to add to the pods                                         | `[]` (evaluated as a template)                               |+| `persistence.enabled`                     | Whether to enable persistence based on Persistent Volume Claims                       | `true`                                                       |+| `persistence.storageClass`                | PVC Storage Class                                                                     | `nil`                                                        |+| `persistence.existingClaim`               | Name of an existing PVC to reuse                                                      | `nil`                                                        |+| `persistence.accessMode`                  | PVC Access Mode (RWO, ROX, RWX)                                                       | `ReadWriteOnce`                                              |+| `persistence.size`                        | Size of the PVC to request                                                            | `2Gi`                                                        |+++### Service parameters++| Parameter                                 | Description                                                                           | Default                                                      |+|-------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------------------------------------|+| `service.type`                            | Kubernetes Service type                                                               | `LoadBalancer`                                               |+| `service.port`                            | Service HTTP port                                                                     | `8080`                                                       |+| `service.httpsPort`                       | Service HTTPS port                                                                    | `8443`                                                       |+| `service.httpsTargetPort`                 | Service Target HTTPS port                                                             | `https`                                                      |+| `service.nodePorts.http`                  | Kubernetes http node port                                                             | `""`                                                         |+| `service.nodePorts.https`                 | Kubernetes https node port                                                            | `""`                                                         |+| `service.externalTrafficPolicy`           | Enable client source IP preservation                                                  | `Cluster`                                                    |+| `service.annotations`                     | Service annotations                                                                   | `{}` (evaluated as a template)                               |+| `service.loadBalancerSourceRanges`        | Restricts access for LoadBalancer (only with `service.type: LoadBalancer`)            | `[]`                                                         |+| `service.extraPorts`                      | Extra ports to expose in the service (normally used with the `sidecar` value)         | `nil`                                                        |++### EJBCA parameters++| Parameter                                 | Description                                                                           | Default                                                      |+|-------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------------------------------------|+| `ejbcaAdminUsername`                      | EJBCA administrator username                                                          | `bitnami`                                                    |+| `ejbcaAdminPassword`                      | EJBCA administrator password                                                          | _random 10 character long alphanumeric string_               |+| `existingSecret`                          | Name of an existing secret containing EJBCA admin password ('ejbca-admin-password' key) | `nil`                                                      |+| `ejbcaJavaOpts`                           | Options used to launch the WildFly server                                             | `nil`                                                        |+| `ejbcaHttpsServerHostname`                | Hostname of the server when using HTTPS                                               | `hostname`                                                   |+| `ejbcaCA.name`                            | Name of the CA EJBCA will instantiate by default                                      | `ManagementCA`                                               |+| `ejbcaCA.baseDN`                          | Base DomainName of the CA EJBCA will instantiate by default                           | `nil`                                                        |+| `ejbcaKeystoreExistingSecret`             | Existing Secret containing a Keystore to be imported by EBJCA                         | `nil`                                                        |+| `extraEnvVars`                            | An array to add extra env vars                                                        | `[]` (evaluated as a template)                               |+| `command`                                 | Custom command to override image cmd                                                  | `nil` (evaluated as a template)                              |+| `args`                                    | Custom args for the custom commad                                                     | `nil` (evaluated as a template)                              |+| `extraVolumeMounts`                       | Additional volume mounts (used along with `extraVolumes`)                             | `[]` (evaluated as a template)                               |+| `resources`                               | EJBCA container's resource requests and limits                                        | `{}`                                                         |+| `podSecurityContext.enabled`              | Enable security context for EJBCA container                                           | `true`                                                       |+| `podSecurityContext.runAsUser`            | User ID for the EJBCA container                                                       | `1001`                                                       |+| `livenessProbe.enabled`                   | Enable/disable livenessProbe                                                          | `true`                                                       |+| `livenessProbe.initialDelaySeconds`       | Delay before liveness probe is initiated                                              | `120`                                                        |+| `livenessProbe.periodSeconds`             | How often to perform the probe                                                        | `10`                                                         |+| `livenessProbe.timeoutSeconds`            | When the probe times out                                                              | `5`                                                          |+| `livenessProbe.failureThreshold`          | Minimum consecutive failures for the probe                                            | `6`                                                          |+| `livenessProbe.successThreshold`          | Minimum consecutive successes for the probe                                           | `1`                                                          |+| `readinessProbe.enabled`                  | Enable/disable readinessProbe                                                         | `true`                                                       |+| `readinessProbe.initialDelaySeconds`      | Delay before readiness probe is initiated                                             | `30`                                                         |+| `readinessProbe.periodSeconds`            | How often to perform the probe                                                        | `10`                                                         |+| `readinessProbe.timeoutSeconds`           | When the probe times out                                                              | `5`                                                          |+| `readinessProbe.failureThreshold`         | Minimum consecutive failures for the probe                                            | `6`                                                          |+| `readinessProbe.successThreshold`         | Minimum consecutive successes for the probe                                           | `1`                                                          |+| `customLivenessProbe`                     | Custom liveness probe to execute (when the main one is disabled)                      | `{}` (evaluated as a template)                               |+| `customReadinessProbe`                    | Custom readiness probe to execute (when the main one is disabled)                     | `{}` (evaluated as a template)                               |+| `extraEnvVarsCM`                          | Array to add extra configmaps                                                         | `[]`                                                         |+| `extraEnvVarsSecret`                      | Array to add extra environment from a Secret                                          | `nil`                                                        |++### Database parameters++| Parameter                                 | Description                                                                           | Default                                                      |+|-------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------------------------------------|+| `mariadb.enabled`                         | Deploy MariaDB container(s)                                                           | `true`                                                       |+| `mariadb.rootUser.password`               | MariaDB admin password                                                                | `nil`                                                        |+| `mariadb.db.name`                         | Database name to create                                                               | `bitnami_ejbca`                                              |+| `mariadb.db.user`                         | Database user to create                                                               | `bn_ejbca`                                                   |+| `mariadb.db.password`                     | Password for the database                                                             | _random 10 character long alphanumeric string_               |+| `mariadb.existingSecret`                  | Use existing secret for password details (`rootUser.password`, `db.password`, `replication.password` will be ignored and picked up from this secret) See [ref](https://github.com/bitnami/charts/tree/master/bitnami/mariadb)                                                                                         | `nil`                                                        |+| `mariadb.replication.enabled`             | MariaDB replication enabled                                                           | `false`                                                      |+| `mariadb.master.persistence.enabled`      | Enable database persistence using PVC                                                 | `true`                                                       |+| `mariadb.master.persistence.accessModes`  | Database Persistent Volume Access Modes                                               | `[ReadWriteOnce]`                                            |+| `mariadb.master.persistence.size`         | Database Persistent Volume Size                                                       | `8Gi`                                                        |+| `externalDatabase.host`                   | Host of the external database                                                         | `localhost`                                                  |+| `externalDatabase.user`                   | Existing username in the external db                                                  | `bn_ejbca`                                                   |+| `externalDatabase.password`               | Password for the above username                                                       | `nil`                                                        |+| `externalDatabase.existingSecret`         | Name of an existing secret resource containing the DB password in a 'mariadb-password' key | `nil`                                                   |+| `externalDatabase.database`               | Name of the existing database                                                         | `bitnami_ejbca`                                              |+| `externalDatabase.port`                   | Database port number                                                                  | `3306`                                                       |++The above parameters map to the env variables defined in [bitnami/ejbca](http://github.com/bitnami/bitnami-docker-ejbca). For more information please refer to the [bitnami/ejbca](http://github.com/bitnami/bitnami-docker-ejbca) image documentation.++Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,++```console+$ helm install my-release \+  --set ejbcaAdminUsername=admin,ejbcaAdminPassword=password,mariadb.db.password=secretpassword \+    bitnami/discourse+```++The above command sets the EJBCA administrator account username and password to `admin` and `password` respectively. Additionally, it sets the MariaDB `bn_ejbca` user password to `secretpassword`.++Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,++```console+$ helm install my-release -f values.yaml bitnami/ejbca+```++> **Tip**: You can use the default [values.yaml](values.yaml)++## Configuration and installation details

Inside this section, we try to avoid commands like helm install ... or helm upgrade ... because there are some places where users are installing the chart without a CLI, like marketplaces. In those cases, this section of the README is rendered in the marketplace, so if possible try to explain how to set up the replication but avoiding specific commands, you can check other READMES as an example if you want

joancafom

comment created time in 12 days

Pull request review commentbitnami/charts

[bitnami/ejbca] EJBCA Chart

+# EJBCA++[EJBCA](https://www.ejbca.org/) is a free software public key infrastructure certificate authority software package.++## TL;DR;++```console+$ helm repo add bitnami https://charts.bitnami.com/bitnami+$ helm install my-release bitnami/ejbca+```++## Introduction++This chart bootstraps a [EJBCA](https://www.ejbca.org/) deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.++It also packages [Bitnami MariaDB](https://github.com/bitnami/charts/tree/master/bitnami/mariadb) as the required databases for the EJBCA application.++Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment and management of Helm Charts in clusters.++## Prerequisites++- Kubernetes 1.12++- Helm 2.11+ or Helm 3.0-beta3++- PV provisioner support in the underlying infrastructure++## Installing the Chart++To install the chart with the release name `my-release`:++```console+$ helm install my-release bitnami/ejbca+```++The command deploys EJBCA 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`++## Uninstalling the Chart++To uninstall/delete the `my-release` deployment:++```console+$ helm delete my-release+```++The command removes all the Kubernetes components associated with the chart and deletes the release.++## Parameters++The following table lists the configurable parameters of the EJBCA chart and their default values.++ Parameter                                  | Description                                                                           | Default                                                      |+|-------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------------------------------------|+| `global.imageRegistry`                    | Global Docker image registry                                                          | `nil`                                                        |+| `global.imagePullSecrets`                 | Global Docker registry secret names as an array                                       | `[]` (does not add image pull secrets to deployed pods)      |+| `global.storageClass`                     | Global storage class for dynamic provisioning                                         | `nil`                                                        |++### Common & Pod-specific parameters++| Parameter                                 | Description                                                                           | Default                                                      |+|-------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------------------------------------|+| `image.registry`                          | EJBCA image registry                                                                  | `docker.io`                                                  |+| `image.repository`                        | EJBCA image name                                                                      | `bitnami/ejbca`                                              |+| `image.tag`                               | EJBCA image tag                                                                       | `{TAG_NAME}`                                                 |+| `image.pullPolicy`                        | EJBCA image pull policy                                                               | `IfNotPresent`                                               |+| `image.pullSecrets`                       | Specify docker-registry secret names as an array                                      | `[]` (does not add image pull secrets to deployed pods)      |+| `nameOverride`                            | String to partially override discourse.fullname                                       | `nil`                                                        |+| `fullnameOverride`                        | String to fully override discourse.fullname                                           | `nil`                                                        |+| `replicaCount`                            | Number of EJBCA replicas                                                              | `1`                                                          |+| `extraVolumes`                            | Array of extra volumes to be added deployment. Requires setting `extraVolumeMounts`   | `[]` (evaluated as a template)                               |+| `podAnnotations`                          | Additional pod annotations                                                            | `{}`                                                         |+| `podLabels`                               | Additional pod labels                                                                 | `{}` (evaluated as a template)                               |+| `commonLabels`                            | Labels to be added to all deployed resources                                          | `{}` (evaluated as a template)                               |+| `commonAnnotations`                       | Annotations to be added to all deployed resources                                     | `{}` (evaluated as a template)                               |+| `podSecurityContext.enabled`              | Enable security context for EJBCA pods                                                | `true`                                                       |+| `podSecurityContext.fsGroup`              | Group ID for the volumes of the pod                                                   | `1001`                                                       |+| `nodeSelector`                            | Node labels for pod assignment.                                                       | `{}` (evaluated as a template)                               |+| `tolerations`                             | Tolerations for pod assignment.                                                       | `[]` (evaluated as a template)                               |+| `affinity`                                | Affinity for pod assignment                                                           | `{}` (evaluated as a template)                               |+| `sidecars`                                | Attach additional sidecar containers to the pod                                       | `[]` (evaluated as a template)                               |+| `initContainers`                          | Additional init containers to add to the pods                                         | `[]` (evaluated as a template)                               |+| `persistence.enabled`                     | Whether to enable persistence based on Persistent Volume Claims                       | `true`                                                       |+| `persistence.storageClass`                | PVC Storage Class                                                                     | `nil`                                                        |+| `persistence.existingClaim`               | Name of an existing PVC to reuse                                                      | `nil`                                                        |+| `persistence.accessMode`                  | PVC Access Mode (RWO, ROX, RWX)                                                       | `ReadWriteOnce`                                              |+| `persistence.size`                        | Size of the PVC to request                                                            | `2Gi`                                                        |+

Unnecessary blank line

joancafom

comment created time in 12 days

Pull request review commentbitnami/charts

[bitnami/ejbca] EJBCA Chart

+## Global Docker image parameters+## Please, note that this will override the image parameters, including dependencies, configured to use the global value+## Current available global Docker image parameters: imageRegistry and imagePullSecrets+##+# global:+#   imageRegistry: myRegistryName+#   imagePullSecrets:+#     - myRegistryKeySecretName+#   storageClass: myStorageClass++## Bitnami EJBCA image version+## ref: https://hub.docker.com/r/bitnami/ejbca/tags/+##+image:+  registry: docker.io+  repository: bitnami/ejbca+  tag: latest

We need to ensure that this is updated by the pipeline

joancafom

comment created time in 12 days

Pull request review commentbitnami/charts

[bitnami/ejbca] EJBCA Chart

+dependencies:+- name: mariadb+  repository: https://charts.bitnami.com/bitnami+  version: 7.5.2

The latest version is 7.6.1, maybe you want to run helm dep update again

joancafom

comment created time in 12 days

issue commentbitnami/bitnami-docker-redis

Failed run redis in k8s if "redis" DNS name resolved to something else

It seems there is some difference when deploying the manifests using redis vs redis-svc in terms of the environment variable that k8s set: Screenshot 2020-07-01 at 18 13 53 On the left side there are the variables in a deployment with service name redis, while on the right side the service name was redis-svc, you can see that the REDIS_PORT variable obtain different values, as well as other env. variables were also renamed.

In the Bitnami chart (although it is a statefulset instead of a deployment), we are setting the REDIS_PORT env. variable in the container:

            - name: REDIS_PORT
              value: {{ .Values.redisPort | quote }}

in your case, it should be enough by setting:

      containers:
        - image: "bitnami/redis:6.0.5"
          name: redis
          env:
+           - name: REDIS_PORT
+             value: "6379"
            - name: REDIS_PASSWORD
              valueFrom:
                secretKeyRef:
                  name: redis-redis-pass
                  key: redisPassword
Panoptik

comment created time in 13 days

issue commentbitnami/bitnami-docker-redis

Failed run redis in k8s if "redis" DNS name resolved to something else

Ok, thanks I am taking a look at the issue as I was able to reproduce it.

Replacing

 kind: Service
 metadata:
   name: redis-svc

by

 kind: Service
 metadata:
   name: redis

(basically removing the -svc suffix), the deployment is failing with this error:

 15:40:19.06 INFO  ==> ** Starting Redis **
*** FATAL CONFIG FILE ERROR (Redis 6.0.5) ***
Reading the configuration file, at line 92
>>> 'port tcp://10.108.226.199:6379'
argument couldn't be parsed into an integer

The source of the issue seems to be in the libredis.sh file:

        debug "Setting Redis config file..."
        redis_conf_set port "$REDIS_PORT"

I added more debug here by creating my own image and I found the following:

  • When using name: redis-svc, the env. variable REDIS_PORT is set to 6379
  • But when using name: redis, the env. variable REDIS_PORT is set to tcp://10.108.226.199:6379, that is not a valid value in the config file and produce the error (argument couldn't be parsed into an integer)

This is just an update, I will continue investigating the issue.

Panoptik

comment created time in 13 days

issue commentbitnami/bitnami-docker-redis

Failed run redis in k8s if "redis" DNS name resolved to something else

Hi, I am sorry but I don't fully understand how are you deploying Redis. Are you using the Bitnami Helm chart (helm install redis bitnami/redis) or are you creating your own k8s manifest using the bitnami container image (bitnami/redis:6.0.5)?

Panoptik

comment created time in 13 days

delete branch bitnami/charts

delete branch : rabbitIngressSecret

delete time in 13 days

issue commentbitnami/charts

[RabbitMQ] Unable to set existingSecret for ingress.tls

Hi, thanks for open this issue. I just created a PR (attached to this issue) that should solve the issue, feel free to take a look. Once reviewed and merged, the issue will be automatically closed.

farlop

comment created time in 13 days

push eventbitnami/charts

Carlos Rodriguez Hernandez

commit sha 8f31eb63b8d7ccdf66ab6cde0adf6a18dac712f1

Add parameter to the README

view details

push time in 13 days

PR opened bitnami/charts

[bitnami/rabbitmq] Use existingSecret for ingress TLS

Description of the change

Add the possibility to use existing secrets for ingress TLS and not only the one named based on hostname

Applicable issues

<!-- Enter any applicable Issues here (You can reference an issue using #) -->

  • fixes #2974

Checklist <!-- [Place an '[X]' (no spaces) in all applicable fields. Please remove unrelated fields.] -->

  • [X] Chart version bumped in Chart.yaml according to semver.
  • [X] Variables are documented in the README.md
  • [X] Title of the PR starts with chart name (e.g. [bitnami/chart])
  • [X] If the chart contains a values-production.yaml apart from values.yaml, ensure that you implement the changes in both files
+17 -2

0 comment

5 changed files

pr created time in 13 days

create barnchbitnami/charts

branch : rabbitIngressSecret

created branch time in 13 days

push eventbitnami/charts

Igor Zubkov

commit sha 36a663607aa4929a294bf547da583ce2edc64ec8

Fix typos (#2983)

view details

push time in 13 days

PR merged bitnami/charts

Fix typos
+3 -3

1 comment

1 changed file

biow0lf

pr closed time in 13 days

pull request commentbitnami/charts

Fix typos

Thanks for the fix!

biow0lf

comment created time in 13 days

issue commentbitnami/charts

Any way to add notification channels / alerts into the grafana chart?

Hi,

In order to try to reproduce the issue on our side, please, can you provide more information about the specific parameters you used to deploy the chart? Mainly what are the custom values you used such as parameters, config files, etc

Apart from that, once deployed the chart, what method are you using to recreate Grafana?

alextes

comment created time in 14 days

issue commentbitnami/bitnami-docker-sonarqube

configuring sonar.properties

Hi all, we just released a new version with the possibility of specifying different sonarqube properties via an environment variable.

You can set the SONARQUBE_PROPERTIES env. variable that is a comma separated list of properties to be set in the sonar.properties file, i.e my.sonar.property1=property_value,my.sonar.property2=property_value. By default this variable is empty.

As a functional example, I added the following to the docker-compose.yaml:

environment:
  ...
  - SONARQUBE_PROPERTIES=sonar.jdbc.maxWait=4000,sonar.jdbc.minIdle=3

deploying the docker-compose with the above env. variable and comparing it with another installation without the env. variable those are the differences in the sonar.properties:

66c68
- #sonar.jdbc.minIdle=2
+ sonar.jdbc.minIdle = 3
71c73
- #sonar.jdbc.maxWait=5000
+ sonar.jdbc.maxWait = 4000

The properties set in the env. variable are applied to the file.

You can find those changes from the following tags:

  • 7-debian-10, 7.9.3-debian-10-r89, 7, 7.9.3, latest
  • 8-debian-10, 8.3.1-debian-10-r31, 8, 8.3.1
bdito

comment created time in 14 days

delete branch bitnami/charts

delete branch : psqlharemoveingress

delete time in 14 days

issue commentbitnami/charts

[bitnami/jenkins] User and password aren't set properly

It seems the issue is that you are using a parameter that is not valid :--set jenkinsUsername=admin the real parameter is --set jenkinsUser=admin. We are using jenkinsUser everywhere in the docs (README.md) except in an example code-block that I just fixed in this commit: c9a01cb22534bc48c3f791d0454e3053554a06b8

Using jenkinsUser this is the result:

$ helm install jenkins2 --set jenkinsUser=admin,jenkinsPassword=password bitnami/jenkins
NAME: jenkins2
LAST DEPLOYED: Mon Jun 29 16:29:35 2020
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
** Please be patient while the chart is being deployed **

1. Get the Jenkins URL by running:

** Please ensure an external IP is associated to the jenkins2 service before proceeding **
** Watch the status using: kubectl get svc --namespace default -w jenkins2 **

  export SERVICE_IP=$(kubectl get svc --namespace default jenkins2 --template "{{ range (index .status.loadBalancer.ingress 0) }}{{.}}{{ end }}")
  echo "Jenkins URL: http://$SERVICE_IP/"

2. Login with the following credentials

  echo Username: admin
  echo Password: $(kubectl get secret --namespace default jenkins2 -o jsonpath="{.data.jenkins-password}" | base64 --decode)

$ echo Username: admin
Username: admin

$ echo Password: $(kubectl get secret --namespace default jenkins2 -o jsonpath="{.data.jenkins-password}" | base64 --decode)
Password: password

according to the above notes and the result of the echos, the values are property set.

Accessing to the pod everything seems to be properly set:

$ kubectl get pods
NAME                        READY   STATUS    RESTARTS   AGE
jenkins2-5ccf7685b5-khp4m   1/1     Running   0          3m45s

$ kubectl exec -it jenkins2-5ccf7685b5-khp4m /bin/bash
  $ cat /opt/bitnami/jenkins/jenkins_home/users/users.xml
  <?xml version='1.1' encoding='UTF-8'?>
  <hudson.model.UserIdMapper>
    <version>1</version>
    <idToDirectoryNameMap class="concurrent-hash-map">
      <entry>
        <string>admin</string>
        <string>admin_1233489618902837442</string>
      </entry>
    </idToDirectoryNameMap>
  </hudson.model.UserIdMapper>

  $ env | grep JENKINS_
  JENKINS_USERNAME=admin
  JENKINS_PASSWORD=password

Can you confirm if using jenkinsUser and jenkinsPassword are you able to set access by using your custom values?

misterstrickland

comment created time in 15 days

push eventbitnami/charts

Carlos Rodriguez Hernandez

commit sha c9a01cb22534bc48c3f791d0454e3053554a06b8

[bitnami/jenkins] Fix typo in README (jenkinsUsername -> jenkinsUser)

view details

push time in 15 days

push eventbitnami/bitnami-docker-spring-cloud-dataflow

Alexey Zhokhov

commit sha d3f58a35b48a650975f11b7f5199b14b31133590

Added ability to pass JAVA_OPTS to java -jar cmd

view details

Alexey Zhokhov

commit sha 39fd0d2892c21314bfac02208257feb8e353c54a

Move JAVA_OPTS to __run_flags.

view details

Carlos Rodríguez Hernández

commit sha 222986a33888fb3362262ffc37d6c8750092e1b3

Merge pull request #1 from donbeave/master Added ability to pass JAVA_OPTS to java -jar cmd

view details

push time in 15 days

PR merged bitnami/bitnami-docker-spring-cloud-dataflow

Added ability to pass JAVA_OPTS to java -jar cmd

Description of the change

This env will add the ability to pass custom parameters to the Java app, like changing log level or setting Xmx or garbage collector.

+4 -1

1 comment

2 changed files

donbeave

pr closed time in 15 days

pull request commentbitnami/bitnami-docker-spring-cloud-dataflow

Added ability to pass JAVA_OPTS to java -jar cmd

We need to do some changes in our automation to release those changes, so probably a new commit appears sometime before merging the PR

donbeave

comment created time in 15 days

issue commentbitnami/charts

Postgres-ha

Hi, at this moment there are different charts implementing HPA: spring-cloud-dataflow, spark, nginx, thanos or kong.

For example, in the case of kong, this is the template and here you can find the values.

rg2609

comment created time in 15 days

issue commentbitnami/charts

Helm - PostgreSQL | How to enable PostGIS extension?

Hi, there are several ways to configure the password, you can use for example a secret, on this way the password is not going appear in the repository in plain text. In the same way, instead of modifying the values.yaml you can also set the parameters directly in the install command, i.e helm install --set postgresqlPassword=my_app

Those are the different options to configure the password:

 ## PostgreSQL admin password (used when `postgresqlUsername` is not `postgres`)
 ## ref: https://github.com/bitnami/bitnami-docker-postgresql/blob/master/README.md#creating-a-database-user-on-first-run (see note!)
 postgresqlPostgresPassword:

 ## PostgreSQL user (has superuser privileges if username is `postgres`)
 ## ref: https://github.com/bitnami/bitnami-docker-postgresql/blob/master/README.md#setting-the-root-password-on-first-run
 postgresqlUsername: postgres

 ## PostgreSQL password
 ## ref: https://github.com/bitnami/bitnami-docker-postgresql/blob/master/README.md#setting-the-root-password-on-first-run
 ##
 postgresqlPassword:

 ## PostgreSQL password using existing secret
 existingSecret: secret

 ## Mount PostgreSQL secret as a file instead of passing environment variable
 usePasswordFile: false
mabdelfattah

comment created time in 15 days

push eventbitnami/charts

Joseph Ball

commit sha 760be6522f2053d817cd555217d5313a0905635f

[bitnami/dokuwiki] Inject certificates into image (#2942) Add a certificate authority and tls certificate into the image. Pulls from kubernetes secret using a sidecar init container. Signed-off-by: Joseph Ball <joseph.ball@packetsolutions.io>

view details

push time in 15 days

PR merged bitnami/charts

[bitnami/dokuwiki] Inject certificates into image

Description of the change

Add a certificate authority into the redmine image. Pulls CA from kubernetes secret using a sidecar init container.

Benefits

  • Allows LDAP authentication using LDAPS to servers with an internal certificate.
  • Adds a snakeoil certificate to the container. Used can be used for TLS sessions to the ingress.
  • Allows injection of custom user certificate into image.

Possible drawbacks

None

Applicable issues

None

Additional information

Readme has not been fully aligned. Can create an additional commit to realign the table if required.

Checklist <!-- [Place an '[X]' (no spaces) in all applicable fields. Please remove unrelated fields.] -->

  • [X] Chart version bumped in Chart.yaml according to semver.
  • [X] Variables are documented in the README.md
  • [X] Title of the PR starts with chart name (e.g. [bitnami/chart])
  • [X] If the chart contains a values-production.yaml apart from values.yaml, ensure that you implement the changes in both files
+222 -1

0 comment

5 changed files

ballj

pr closed time in 15 days

push eventbitnami/charts

Maxence Boutet

commit sha 26f323e021ff38e7f2132fe24d8f564b383ea8cf

Add redis.topologySpreadConstraints (#2951) Co-authored-by: Maxence Boutet <maxenceboutet@oulook.com>

view details

push time in 15 days

PR merged bitnami/charts

[bitnami/redis-cluster] Add pod topology spread constraints

<!-- Before you open the request please review the following guidelines and tips to help it be more easily integrated:

  • Describe the scope of your change - i.e. what the change does.
  • Describe any known limitations with your change.
  • Please run any tests or examples that can exercise your modified code.

Thank you for contributing! We will try to test and integrate the change as soon as we can, but be aware we have many GitHub repositories to manage and can't immediately respond to every request. There is no need to bump or check in on a pull request (it will clutter the discussion of the request).

Also don't be worried if the request is closed or not integrated sometimes the priorities of Bitnami might not match the priorities of the pull request. Don't fret, the open source community thrives on forks and GitHub makes it easy to keep your changes in a forked repo. -->

Description of the change

Add redis.topologySpreadConstraints to values.yaml

Benefits

Allow to specify topologySpreadConstraints for controlling the spreading of pods across topology keys.

Possible drawbacks

None

Applicable issues

None

Additional information

None

Checklist <!-- [Place an '[X]' (no spaces) in all applicable fields. Please remove unrelated fields.] -->

  • [X] Chart version bumped in Chart.yaml according to semver.
  • [X] Variables are documented in the README.md
  • [X] Title of the PR starts with chart name (e.g. [bitnami/chart])
  • [X] If the chart contains a values-production.yaml apart from values.yaml, ensure that you implement the changes in both files

:warning: Keep in mind that if you want to make changes to the kubeapps chart, please implement them in the kubeapps repository. This is only a synchronized mirror.

+15 -1

0 comment

5 changed files

mboutet

pr closed time in 15 days

issue commentbitnami/charts

Postgres-ha

Hi, thanks for the suggestion, at this moment we are working on different fixes/improvements for the postgresql(-ha) charts, but the one you are suggesting was not in our short term improvements list. I think it's a good feature to be added to the chart if you want to contribute with the required changes we are happy to help and review the PR.

rg2609

comment created time in 18 days

delete branch bitnami/charts

delete branch : prom-op/externalUrl

delete time in 18 days

delete branch bitnami/charts

delete branch : ct

delete time in 18 days

delete branch bitnami/charts

delete branch : redis-cluster-extra-init-containers

delete time in 18 days

delete branch bitnami/charts

delete branch : javsalgar-patch-1

delete time in 18 days

delete branch bitnami/charts

delete branch : phpmyadmin-nonroot

delete time in 18 days

delete branch bitnami/charts

delete branch : elasticsearch-fix-port-reference

delete time in 18 days

delete branch bitnami/charts

delete branch : kafkafixlivenessreadiness

delete time in 18 days

delete branch bitnami/charts

delete branch : harborpullsecrets

delete time in 18 days

delete branch bitnami/charts

delete branch : fixharborUpgrade

delete time in 18 days

delete branch bitnami/charts

delete branch : node-storageclass

delete time in 18 days

delete branch bitnami/charts

delete branch : carrodher-patch-1

delete time in 18 days

delete branch bitnami/charts

delete branch : harbortrivyfix

delete time in 18 days

issue commentbitnami/charts

bitnami/contour 1.0.0 chart - envoy container fails to launch healthy

Hi, I am trying to reproduce the error, but in my case I am not able to see the same issue:

  • Installing the chart without extra parameters:
$ helm install contour bitnami/contour
NAME: contour
LAST DEPLOYED: Thu Jun 25 17:12:04 2020
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
1. Get Contours's load balancer IP/hostname:

     NOTE: It may take a few minutes for this to become available.

     You can watch the status by running:

         $ kubectl get svc contour --namespace default -w

     Once 'EXTERNAL-IP' is no longer '<pending>':

         $ kubectl describe svc contour --namespace default | grep Ingress | awk '{print $3}'

2. Configure DNS records corresponding to Kubernetes ingress resources to point to the load balancer IP/hostname found in step 1
  • Check all the resources:
$ kubectl get all
NAME                                  READY   STATUS      RESTARTS   AGE
pod/contour-contour-5db47c985-7hnb2   1/1     Running     0          4m25s
pod/contour-contour-5db47c985-p7jfd   1/1     Running     0          4m25s
pod/contour-contour-certgen-znx7c     0/1     Completed   0          4m25s
pod/contour-envoy-6h5ll               2/2     Running     0          4m25s

NAME                    TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)                      AGE
service/contour         ClusterIP      10.100.43.5      <none>        8001/TCP                     4m25s
service/contour-envoy   LoadBalancer   10.107.140.191   <pending>     80:30388/TCP,443:31657/TCP   4m25s
service/kubernetes      ClusterIP      10.96.0.1        <none>        443/TCP                      5m12s

NAME                           DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
daemonset.apps/contour-envoy   1         1         1       1            1           <none>          4m25s

NAME                              READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/contour-contour   2/2     2            2           4m25s

NAME                                        DESIRED   CURRENT   READY   AGE
replicaset.apps/contour-contour-5db47c985   2         2         2       4m25s

NAME                                COMPLETIONS   DURATION   AGE
job.batch/contour-contour-certgen   1/1           12s        4m25s
  • Envoy & Shutdown-manager logs:
$ kubectl logs -f contour-envoy-6h5ll envoy
[2020-06-25 15:12:27.043][1][info][main] [source/server/server.cc:255] initializing epoch 0 (hot restart version=11.104)
[2020-06-25 15:12:27.043][1][info][main] [source/server/server.cc:257] statically linked extensions:
...
[2020-06-25 15:12:35.749][1][info][upstream] [source/server/lds_api.cc:76] lds: add/update listener 'stats-health'
[2020-06-25 15:12:35.749][1][info][config] [source/server/listener_manager_impl.cc:725] all dependencies initialized. starting workers

$ kubectl logs -f contour-envoy-6h5ll shutdown-manager
time="2020-06-25T15:12:22Z" level=info msg="started envoy shutdown manager" context=shutdown-manager

In order to try to find the source of the issue, are you facing the same issue running just helm install (like I did) instead of helm upgrade [more options]?

geota

comment created time in 19 days

issue commentbitnami/bitnami-docker-couchdb

CouchDB server doesn't start.

Yes, you can see the different configuration options in this section of the README: https://github.com/bitnami/bitnami-docker-couchdb#configuration

thomascenni

comment created time in 20 days

issue closedbitnami/bitnami-docker-couchdb

CouchDB server doesn't start.

Description

CouchDB server doesn't start.

Steps to reproduce the issue:

docker run --name couchdb bitnami/couchdb:latest

Describe the results you received:

I receive the following error: couchdb 22:41:43.03 INFO ==> ** Starting CouchDB setup ** couchdb 22:41:43.07 INFO ==> Initializing CouchDB... couchdb 22:41:43.07 INFO ==> Updating '/opt/bitnami/couchdb/etc/default.d/10-bitnami.ini' based on user configuration... /opt/bitnami/scripts/libcouchdb.sh: line 178: 3: value is required

Describe the results you expected:

I expected the server to start normally.

Version

  • Output of docker version:
Client: Docker Engine - Community
 Version:           19.03.5
 API version:       1.40
 Go version:        go1.12.12
 Git commit:        633a0ea
 Built:             Wed Nov 13 07:22:34 2019
 OS/Arch:           darwin/amd64
 Experimental:      false

Additional environment details (AWS, VirtualBox, Docker for MAC, physical, etc.): Docker for Mac on macOS Sierra 10.12.6

closed time in 20 days

thomascenni

issue commentbitnami/bitnami-docker-couchdb

CouchDB server doesn't start.

Hi,

the new version was released in this commit fa04921ade3a69fd41bbcce1a75d579dd70dee95, now the environment variable has a default value so you can execute docker run bitnami/couchdb without extra arguments and it should work.

If you are using latest or another rolling tag like 3.1.0, please ensure the new version is pulled:

$ docker run bitnami/couchdb:latest
Unable to find image 'bitnami/couchdb:latest' locally
latest: Pulling from bitnami/couchdb
20b41457e783: Pull complete
df0a44c882d2: Pull complete
50f489f30371: Pull complete
55ac83aa9866: Pull complete
a2dd1484ab7d: Pull complete
fffd384d26bc: Pull complete
b0d84d510d54: Pull complete
5ed55421fcb2: Pull complete
6aff6b711004: Pull complete
f29ec6c473cf: Pull complete
Digest: sha256:241f39a6c15335e69783f74de555347179941f4ee64a71e3e41654f13c930ffa
Status: Downloaded newer image for bitnami/couchdb:latest
couchdb 12:07:54.61
couchdb 12:07:54.61 Welcome to the Bitnami couchdb container
couchdb 12:07:54.61 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-couchdb
couchdb 12:07:54.61 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-couchdb/issues
couchdb 12:07:54.62
couchdb 12:07:54.62 INFO  ==> ** Starting CouchDB setup **
couchdb 12:07:54.62 WARN  ==> You set the environment variable COUCHDB_PASSWORD=couchdb. This is the default value when bootstrapping CouchDB and should not be used in production environments.
couchdb 12:07:54.63 INFO  ==> Initializing CouchDB...
couchdb 12:07:54.63 INFO  ==> Updating '/opt/bitnami/couchdb/etc/default.d/10-bitnami.ini' based on user configuration...
couchdb 12:07:54.66 INFO  ==> Updating '/opt/bitnami/couchdb/etc/vm.args' based on user configuration...
couchdb 12:07:54.66 INFO  ==> Deploying CouchDB from scratch
couchdb 12:07:54.66 INFO  ==> Starting CouchDB in background...
couchdb 12:07:55.67 INFO  ==> Creating initial databases...
couchdb 12:07:55.78 INFO  ==> Stopping CouchDB...

couchdb 12:07:57.29 INFO  ==> ** CouchDB setup finished! **
couchdb 12:07:57.29 INFO  ==> ** Starting CouchDB **
[info] 2020-06-24T12:07:57.874602Z couchdb@127.0.0.1 <0.240.0> -------- Preflight check: Asserting Admin Account

[info] 2020-06-24T12:07:57.876339Z couchdb@127.0.0.1 <0.240.0> -------- Apache CouchDB 3.1.0 is starting.

[info] 2020-06-24T12:07:57.876412Z couchdb@127.0.0.1 <0.241.0> -------- Starting couch_sup
[info] 2020-06-24T12:07:57.913370Z couchdb@127.0.0.1 <0.240.0> -------- Apache CouchDB has started. Time to relax.

[notice] 2020-06-24T12:07:57.919219Z couchdb@127.0.0.1 <0.273.0> -------- rexi_server : started servers
[notice] 2020-06-24T12:07:57.920205Z couchdb@127.0.0.1 <0.277.0> -------- rexi_buffer : started servers
[notice] 2020-06-24T12:07:57.955896Z couchdb@127.0.0.1 <0.307.0> -------- mem3_reshard_dbdoc start init()
[notice] 2020-06-24T12:07:57.958362Z couchdb@127.0.0.1 <0.309.0> -------- mem3_reshard start init()
[notice] 2020-06-24T12:07:57.958441Z couchdb@127.0.0.1 <0.310.0> -------- mem3_reshard db monitor <0.310.0> starting
[notice] 2020-06-24T12:07:57.959715Z couchdb@127.0.0.1 <0.309.0> -------- mem3_reshard starting reloading jobs
[notice] 2020-06-24T12:07:57.959825Z couchdb@127.0.0.1 <0.309.0> -------- mem3_reshard finished reloading jobs
[notice] 2020-06-24T12:08:02.983221Z couchdb@127.0.0.1 <0.361.0> -------- couch_replicator_clustering : cluster stable
[notice] 2020-06-24T12:08:02.985338Z couchdb@127.0.0.1 <0.380.0> -------- Started replicator db changes listener <0.501.0>
[info] 2020-06-24T12:08:02.985671Z couchdb@127.0.0.1 <0.503.0> -------- open_result error {not_found,no_db_file} for _replicator
[notice] 2020-06-24T12:08:03.028074Z couchdb@127.0.0.1 <0.501.0> -------- creating replicator ddoc <<"shards/80000000-ffffffff/_replicator.1593000475">>
[notice] 2020-06-24T12:08:12.920204Z couchdb@127.0.0.1 <0.273.0> -------- rexi_server : cluster stable
[notice] 2020-06-24T12:08:12.920260Z couchdb@127.0.0.1 <0.277.0> -------- rexi_buffer : cluster stable
thomascenni

comment created time in 20 days

delete branch bitnami/charts

delete branch : mongoshard

delete time in 20 days

push eventbitnami/charts

Carlos Rodríguez Hernández

commit sha d1ca0595ff1be6658fc712a164273943ad9c4a06

Update CONTRIBUTING.md (#2914) * Update CONTRIBUTING.md * Update CONTRIBUTING.md * Update CONTRIBUTING.md

view details

push time in 20 days

push eventbitnami/charts

Carlos Rodríguez Hernández

commit sha 67b6a82e6b36e3969a1208210e68d5f33002804a

Update CONTRIBUTING.md

view details

push time in 20 days

push eventbitnami/charts

Carlos Rodríguez Hernández

commit sha 93874564ef99e70fa8b7d2da9897f80a150edf0d

Update CONTRIBUTING.md

view details

push time in 20 days

PR opened bitnami/charts

Reviewers
Update CONTRIBUTING.md

Description of the change

Update CONTRIBUTING.MD reflecting recent changes in the PR workflow

+4 -5

0 comment

1 changed file

pr created time in 20 days

create barnchbitnami/charts

branch : carrodher-patch-1

created branch time in 20 days

issue commentbitnami/bitnami-docker-couchdb

CouchDB server doesn't start.

Hi, thanks for reporting the issue. I am able to reproduce it and I just created an internal task to fix it in the next release.

The source of the issue is that the COUCHDB_PASSWORD environment variable is needed, as you can see in the docker-compose.yaml we are setting it:

  couchdb:
    image: docker.io/bitnami/couchdb:3-debian-10
    environment:
      - COUCHDB_PASSWORD=couchdb

that is not translated to the docker run execution, so we are going to set this default value in the container logic. In the meantime, you can set this environment variable:

$ docker run --name couchdb -e 'COUCHDB_PASSWORD=couchdb' bitnami/couchdb:latest

Once released the new version with the fix, it won't be necessary to use this workaround.

thomascenni

comment created time in 20 days

push eventbitnami/charts

Joseph Ball

commit sha 64e1ab51711278d2493857f136d5d6be81704503

[bitnami/redmine] Move certificate.extraEnvVars to certificate.image (#2907) * [bitnami/redmine] Add certificate documentation to readme * Add blank-lines surrounding code blocks and titles Co-authored-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>

view details

push time in 20 days

PR merged bitnami/charts

[bitnami/redmine] Move certificate.extraEnvVars to certificate.image

Description of the change

The change moves one of the certificate image variables to the correct location in the values file. Additionally it adds documentation on how to add user certificates into the readme.

Benefits

Everything that relates to the init container image is now in the correct hierarchy.

Possible drawbacks

If someone has already started using the feature (only added a couple of days ago) then it will require them to move the variable to the new location.

Applicable issues

N/A

Additional information

N/A

Checklist <!-- [Place an '[X]' (no spaces) in all applicable fields. Please remove unrelated fields.] -->

  • [X] Chart version bumped in Chart.yaml according to semver.
  • [X] Variables are documented in the README.md
  • [X] Title of the PR starts with chart name (e.g. [bitnami/chart])
  • [X] If the chart contains a values-production.yaml apart from values.yaml, ensure that you implement the changes in both files
+37 -3

2 comments

2 changed files

ballj

pr closed time in 20 days

push eventballj/helm-charts-bitnami

Carlos Rodríguez Hernández

commit sha 73f162f0df7eb6d8388ed1fd05f18e429f5a1327

Add blank-lines surrounding code blocks and titles

view details

push time in 21 days

pull request commentbitnami/charts

[bitnami/redmine] Move certificate.extraEnvVars to certificate.image

Hi, thanks for your contribution. The documentation changes look good to me, but we are used to isolating the image block to the parameters related to pulling the image itself:

  image:
    registry: docker.io
    repository: bitnami/apache-exporter
    tag: 0.8.0-debian-10-r76
    pullPolicy: IfNotPresent
    ## Optionally specify an array of imagePullSecrets.
    ## Secrets must be manually created in the namespace.
    ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
    ##
    # pullSecrets:
    #   - myRegistryKeySecretName

for example https://github.com/bitnami/charts/blob/master/bitnami/wordpress/values.yaml#L444

Then the extra environments variable parameters are defined at a different level, usually in relation with the container itself and the rest of parameters: https://github.com/bitnami/charts/blob/master/bitnami/wordpress/values.yaml#L142

ballj

comment created time in 21 days

issue commentbitnami/bitnami-docker-rabbitmq

Support rabbitmq 3.8.4 for bitnami docker images

There are several tags pointing to the same image:

3.8-debian-10, 3.8.5-debian-10-r14, 3.8, 3.8.5, latest

In the above list there are two types of tags:

  • Rolling tags (3.8-debian-10, 3.8, 3.8.5, latest): Those tags are always pointing to the most recent image. Bitnami publishes a daily tag mainly updating the OS packages, but also it can contain other changes. This tag is released in a daily basis using the -rXX suffix and the rest of the tags point to this one, so they are updated on a daily basis.
  • Immutable tags (3.8.5-debian-10-r14): On the other hand, the -rXX tag is immutable, this tag with a specific number is released one day and it is not updated anymore.

If you are using containers in a production environment, Bitnami recommends using immutable tags. This ensures that your deployment is not affected if a new revision inadvertently breaks existing functionality. But you need to be aware of new versions or security patches, you can subscribe to project updates by watching the bitnami/rabbitmq GitHub repo.

You can find more info about rolling tags VS immutable tags in our docs: https://docs.bitnami.com/tutorials/understand-rolling-tags-containers/

chukka

comment created time in 21 days

pull request commentbitnami/bitnami-docker-minio

Enable to specify default bucket policy for MINIO_DEFAULT_BUCKETS

Changes should be included in the following tags: 2020-debian-10, 2020.6.22-debian-10-r1, 2020, 2020.6.22, latest

adnoh

comment created time in 22 days

push eventbitnami/bitnami-docker-minio

adnoh

commit sha 00315e25ce3896d58976c632a7f1d07e41007906

Enable to specify default bucket policy for MINIO_DEFAULT_BUCKETS (#8) * Enable to specify default bucket policy for MINIO_DEFAULT_BUCKETS Enables you to specify a policy for the newly created MINIO_DEFAULT_BUCKETS like: MINIO_DEFAULT_BUCKETS=mynewpubrw:public,mynewro:download,normalbucket,..... * Fix indentation and first condition * Change variable name following conventions Co-authored-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>

view details

push time in 22 days

PR merged bitnami/bitnami-docker-minio

Enable to specify default bucket policy for MINIO_DEFAULT_BUCKETS

Description of the change

Enables you to specify a policy for the newly created MINIO_DEFAULT_BUCKETS like: MINIO_DEFAULT_BUCKETS=mynewpubrw:public,mynewro:download,normalbucket,.....

Benefits

Create eg a public bucket on initialisation

Possible drawbacks

None. "Normal" definitions will still work

Applicable issues / Additional information /

+9 -4

1 comment

1 changed file

adnoh

pr closed time in 22 days

pull request commentbitnami/bitnami-docker-minio

Enable to specify default bucket policy for MINIO_DEFAULT_BUCKETS

I just send a new commit changing the variable name to follow some internal conventions like avoid generic names and start with lower case

adnoh

comment created time in 22 days

push eventadnoh/bitnami-docker-minio

Carlos Rodríguez Hernández

commit sha 419da0b62927644202a1384ebc5f2af09f7928be

Change variable name following conventions

view details

push time in 22 days

push eventbitnami/charts

Joseph Ball

commit sha 4d5d0e135a2c01bf11fb0315097aa338910bf079

[bitnami/redmine] Fix deployment secret when using mariadb.existingSecret (#2893) * [bitnami/redmine] Fix deployment secret when using mariadb.existingSecret Use the correct secret for the mariadb database if the user has specified an existingSecret in the mariadb chart. Signed-off-by: Joseph Ball <joseph.ball@packetsolutions.io> * [bitnami/redmine] Update components versions Signed-off-by: Bitnami Containers <containers@bitnami.com> Co-authored-by: Bitnami Containers <containers@bitnami.com>

view details

push time in 22 days

PR merged bitnami/charts

[bitnami/redmine] Fix deployment secret when using mariadb.existingSecret

Description of the change

If the user has specified a secret as part of the mariadb chart, then the redmine application will use that secret.

Benefits

Uses the correct secret if specified.

Possible drawbacks

N/A

Applicable issues

N/A

Additional information

N/A

Checklist <!-- [Place an '[X]' (no spaces) in all applicable fields. Please remove unrelated fields.] -->

  • [X] Chart version bumped in Chart.yaml according to semver.
  • [X] Variables are documented in the README.md
  • [X] Title of the PR starts with chart name (e.g. [bitnami/chart])
  • [X] If the chart contains a values-production.yaml apart from values.yaml, ensure that you implement the changes in both files
+16 -7

2 comments

5 changed files

ballj

pr closed time in 22 days

issue commentbitnami/charts

[bitnami/mongodb] MongoDB primary pod restart fails to connect to mongodb-secondary

Hi, the work is still in progress, when the PR was created we can link the PR with this issue

ganchandrasekaran

comment created time in 22 days

issue commentbitnami/charts

Use helm install failed

At the end the issue is that with the default options, the random password is stored in the PV then when you uninstall the deployment with helm delete the PV/PVCs are not deleted. So the second installation generates a new random password different from the first one that is still present in the PV so there is a conflict between the new password and the previous one.

This is not a specific issue related to the MariaDB chart; we are thinking of a solution/clarification for this topic.

dommgifer

comment created time in 22 days

pull request commentbitnami/charts

[bitnami/dotnet-core-kestrel] New Chart

Hi, we are happy to help to make this chart works with the Bitnami image that you can find in GitHub and DockerHub repositories. Please, feel free to reach us regarding any issue you have deploying the chart with this image. If you think there is something we should implement in the image on our side, please, don't hesitate to let us know.

shankarmohannamakkal

comment created time in 22 days

push eventadnoh/bitnami-docker-minio

Carlos Rodríguez Hernández

commit sha 8884af4e7094e75f26fd71f965e53e984640283c

Fix indentation and first condition

view details

push time in 22 days

push eventbitnami/charts

vincedmg

commit sha 2d8b47cbabed122d1a7dad222ac6cc51731de5fe

[bitnami/zookeeper] add schedulerName option (#2872) * add schedulerName option * fulfill requirements git * Bump minor version * [bitnami/zookeeper] Update components versions Signed-off-by: Bitnami Containers <containers@bitnami.com> Co-authored-by: Carlos Rodríguez Hernández <carlosrh@vmware.com> Co-authored-by: Bitnami Containers <containers@bitnami.com>

view details

push time in 25 days

PR merged bitnami/charts

[bitnami/zookeeper] add schedulerName option

<!-- Before you open the request please review the following guidelines and tips to help it be more easily integrated:

  • Describe the scope of your change - i.e. what the change does.
  • Describe any known limitations with your change.
  • Please run any tests or examples that can exercise your modified code.

Thank you for contributing! We will try to test and integrate the change as soon as we can, but be aware we have many GitHub repositories to manage and can't immediately respond to every request. There is no need to bump or check in on a pull request (it will clutter the discussion of the request).

Also don't be worried if the request is closed or not integrated sometimes the priorities of Bitnami might not match the priorities of the pull request. Don't fret, the open source community thrives on forks and GitHub makes it easy to keep your changes in a forked repo. -->

Description of the change

Allow to specify a scheduler for pods managed by the statefulset

Benefits

Allow on-premise or custom persistence storage solution to work (like portworx) which come with his own kubernetes scheduler

Possible drawbacks

N/A

Applicable issues

  • Fixes #2874

Additional information

Checklist <!-- [Place an '[X]' (no spaces) in all applicable fields. Please remove unrelated fields.] -->

  • [x] Chart version bumped in Chart.yaml according to semver.
  • [x] Variables are documented in the README.md
  • [x] Title of the PR starts with chart name (e.g. [bitnami/chart])
  • [x] If the chart contains a values-production.yaml apart from values.yaml, ensure that you implement the changes in both files

:warning: Keep in mind that if you want to make changes to the kubeapps chart, please implement them in the kubeapps repository. This is only a synchronized mirror.

+17 -3

1 comment

5 changed files

vDMG

pr closed time in 25 days

issue closedbitnami/charts

[bitnami/zookeeper] allow possibilty to give a schedulerName to pod spec

Which chart: bitnami/zookeeper

Is your feature request related to a problem? Please describe. I would like, and it may be useful for a lot of person to give a schedulerName, especially for on-premise kubernetes storage solution (aka portworx) Describe the solution you'd like

https://github.com/bitnami/charts/pull/2872

Describe alternatives you've considered N/A Additional context N/A

closed time in 25 days

vDMG

issue commentbitnami/charts

"connection refused" issue in postgresql-ha

Hi @sergeyshaykhullin, I created this issue as a separate issue, it seems the error in the original post:

Error opening connection to database (postgresql://postgres:PASSWORD_REMOVED@127.0.0.1:5432/postgres?sslmode=disable): dial tcp 127.0.0.1:5432: connect: connection refused"

is unrelated to the one you're facing:

could not translate host name "pg-ha-postgresql-ha-postgresql-0.pg-ha-postgresql-ha-postgresql-headless.i4llhv1ea14hcp1rvnxfhfu4p3.svc.cluster.local" to address: Name or service not known

In this case, please can you provide more information in order to try to reproduce the issue? For example:

  • Are you using any custom parameters or modifications in the values.yaml?
  • Is it the first installation or is it an upgrade?
  • Is it a deployment from scratch or did you install it previously without removing the PV/PVC?

This information is really useful to try to reproduce the issue on our side.

carrodher

comment created time in 25 days

issue openedbitnami/charts

"connection refused" issue in postgresql-ha

@carrodher I am getting same issue

Version

Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-20T12:52:00Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}                                                                                                                    Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-20T12:43:34Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"} 

Logs (INVERTED)

2020-06-18 20:11:43 | time="2020-06-18T17:11:43Z" level=error msg="Error opening connection to database (postgresql://postgres:PASSWORD_REMOVED@127.0.0.1:5432/postgres?sslmode=disable): dial tcp 127.0.0.1:5432: connect: connection refused" source="postgres_exporter.go:1474"
-- | --
  |   | 2020-06-18 20:11:40 | time="2020-06-18T17:11:40Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:11:38 | time="2020-06-18T17:11:38Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:11:37 | time="2020-06-18T17:11:37Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:11:19 | [2020-06-18 17:11:19] [HINT] check that this node is part of a repmgr cluster
  |   | 2020-06-18 20:11:19 | [2020-06-18 17:11:19] [DETAIL] repmgr extension is available but not installed in database "repmgr"
  |   | 2020-06-18 20:11:19 | [2020-06-18 17:11:19] [ERROR] repmgr extension not found on this node
  |   | 2020-06-18 20:11:19 | [2020-06-18 17:11:19] [NOTICE] repmgrd (repmgrd 5.1.0) starting up
  |   | 2020-06-18 20:11:19 | postgresql-repmgr 17:11:19.34 INFO  ==> ** Starting repmgrd **
  |   | 2020-06-18 20:11:19 | postgresql 17:11:19.10 INFO  ==> Starting PostgreSQL in background...
  |   | 2020-06-18 20:11:19 |  
  |   | 2020-06-18 20:11:19 | postgresql-repmgr 17:11:19.02 INFO  ==> ** PostgreSQL with Replication Manager setup finished! **
  |   | 2020-06-18 20:11:19 | postgresql 17:11:19.01 INFO  ==> Stopping PostgreSQL...
  |   | 2020-06-18 20:11:19 | postgresql 17:11:19.00 INFO  ==> Deploying PostgreSQL with persisted data...
  |   | 2020-06-18 20:11:18 | postgresql 17:11:18.93 INFO  ==> Custom configuration /opt/bitnami/postgresql/conf/pg_hba.conf detected
  |   | 2020-06-18 20:11:18 | postgresql 17:11:18.93 INFO  ==> Custom configuration /opt/bitnami/postgresql/conf/postgresql.conf detected
  |   | 2020-06-18 20:11:18 | postgresql 17:11:18.92 INFO  ==> Cleaning stale /bitnami/postgresql/data/postmaster.pid file
  |   | 2020-06-18 20:11:18 | postgresql 17:11:18.92 INFO  ==> Initializing PostgreSQL database...
  |   | 2020-06-18 20:11:18 | repmgr 17:11:18.92 INFO  ==> Initializing Repmgr...
  |   | 2020-06-18 20:11:18 | repmgr 17:11:18.91 INFO  ==> Preparing repmgr configuration...
  |   | 2020-06-18 20:11:18 | postgresql 17:11:18.84 INFO  ==> postgresql.conf file not detected. Generating it...
  |   | 2020-06-18 20:11:18 | repmgr 17:11:18.83 INFO  ==> Preparing PostgreSQL configuration...
  |   | 2020-06-18 20:11:18 | repmgr 17:11:18.67 INFO  ==> There are no nodes with primary role. Assuming the primary role...
  |   | 2020-06-18 20:11:18 | repmgr 17:11:18.56 INFO  ==> Querying all partner nodes for common upstream node...
  |   | 2020-06-18 20:11:18 | postgresql 17:11:18.55 INFO  ==> Validating settings in POSTGRESQL_* env vars..
  |   | 2020-06-18 20:11:18 | repmgr 17:11:18.55 INFO  ==> Validating settings in REPMGR_* env vars...
  |   | 2020-06-18 20:11:18 | postgresql-repmgr 17:11:18.47 INFO  ==> ** Starting PostgreSQL with Replication Manager setup **
  |   | 2020-06-18 20:11:18 | postgresql-repmgr 17:11:18.46
  |   | 2020-06-18 20:11:18 | postgresql-repmgr 17:11:18.46 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-postgresql-repmgr/issues
  |   | 2020-06-18 20:11:18 | postgresql-repmgr 17:11:18.46 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-postgresql-repmgr
  |   | 2020-06-18 20:11:18 | postgresql-repmgr 17:11:18.45 Welcome to the Bitnami postgresql-repmgr container
  |   | 2020-06-18 20:11:18 | postgresql-repmgr 17:11:18.45
  |   | 2020-06-18 20:11:13 | time="2020-06-18T17:11:13Z" level=error msg="Error opening connection to database (postgresql://postgres:PASSWORD_REMOVED@127.0.0.1:5432/postgres?sslmode=disable): dial tcp 127.0.0.1:5432: connect: connection refused" source="postgres_exporter.go:1474"
  |   | 2020-06-18 20:11:10 | time="2020-06-18T17:11:10Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:11:08 | time="2020-06-18T17:11:08Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:11:07 | time="2020-06-18T17:11:07Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:10:43 | time="2020-06-18T17:10:43Z" level=error msg="Error opening connection to database (postgresql://postgres:PASSWORD_REMOVED@127.0.0.1:5432/postgres?sslmode=disable): dial tcp 127.0.0.1:5432: connect: connection refused" source="postgres_exporter.go:1474"
  |   | 2020-06-18 20:10:40 | time="2020-06-18T17:10:40Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:10:38 | time="2020-06-18T17:10:38Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:10:37 | time="2020-06-18T17:10:37Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:10:13 | time="2020-06-18T17:10:13Z" level=error msg="Error opening connection to database (postgresql://postgres:PASSWORD_REMOVED@127.0.0.1:5432/postgres?sslmode=disable): dial tcp 127.0.0.1:5432: connect: connection refused" source="postgres_exporter.go:1474"
  |   | 2020-06-18 20:10:10 | time="2020-06-18T17:10:10Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:10:08 | time="2020-06-18T17:10:08Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:10:07 | time="2020-06-18T17:10:07Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:09:43 | time="2020-06-18T17:09:43Z" level=error msg="Error opening connection to database (postgresql://postgres:PASSWORD_REMOVED@127.0.0.1:5432/postgres?sslmode=disable): dial tcp 127.0.0.1:5432: connect: connection refused" source="postgres_exporter.go:1474"
  |   | 2020-06-18 20:09:40 | time="2020-06-18T17:09:40Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:09:38 | time="2020-06-18T17:09:38Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:09:37 | time="2020-06-18T17:09:37Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:09:13 | time="2020-06-18T17:09:13Z" level=error msg="Error opening connection to database (postgresql://postgres:PASSWORD_REMOVED@127.0.0.1:5432/postgres?sslmode=disable): dial tcp 127.0.0.1:5432: connect: connection refused" source="postgres_exporter.go:1474"
  |   | 2020-06-18 20:09:10 | time="2020-06-18T17:09:10Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:09:08 | time="2020-06-18T17:09:08Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:09:07 | time="2020-06-18T17:09:07Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:08:43 | time="2020-06-18T17:08:43Z" level=error msg="Error opening connection to database (postgresql://postgres:PASSWORD_REMOVED@127.0.0.1:5432/postgres?sslmode=disable): dial tcp 127.0.0.1:5432: connect: connection refused" source="postgres_exporter.go:1474"
  |   | 2020-06-18 20:08:40 | time="2020-06-18T17:08:40Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:08:38 | time="2020-06-18T17:08:38Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:08:37 | time="2020-06-18T17:08:37Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:08:29 | [2020-06-18 17:08:29] [HINT] check that this node is part of a repmgr cluster
  |   | 2020-06-18 20:08:29 | [2020-06-18 17:08:29] [DETAIL] repmgr extension is available but not installed in database "repmgr"
  |   | 2020-06-18 20:08:29 | [2020-06-18 17:08:29] [ERROR] repmgr extension not found on this node
  |   | 2020-06-18 20:08:29 | [2020-06-18 17:08:29] [NOTICE] repmgrd (repmgrd 5.1.0) starting up
  |   | 2020-06-18 20:08:29 | postgresql-repmgr 17:08:29.35 INFO  ==> ** Starting repmgrd **
  |   | 2020-06-18 20:08:29 | postgresql 17:08:29.09 INFO  ==> Starting PostgreSQL in background...
  |   | 2020-06-18 20:08:28 | postgresql-repmgr 17:08:28.99 INFO  ==> ** PostgreSQL with Replication Manager setup finished! **
  |   | 2020-06-18 20:08:28 |  
  |   | 2020-06-18 20:08:28 | postgresql 17:08:28.98 INFO  ==> Stopping PostgreSQL...
  |   | 2020-06-18 20:08:28 | postgresql 17:08:28.97 INFO  ==> Deploying PostgreSQL with persisted data...
  |   | 2020-06-18 20:08:28 | postgresql 17:08:28.89 INFO  ==> Custom configuration /opt/bitnami/postgresql/conf/pg_hba.conf detected
  |   | 2020-06-18 20:08:28 | postgresql 17:08:28.89 INFO  ==> Custom configuration /opt/bitnami/postgresql/conf/postgresql.conf detected
  |   | 2020-06-18 20:08:28 | postgresql 17:08:28.88 INFO  ==> Cleaning stale /bitnami/postgresql/data/postmaster.pid file
  |   | 2020-06-18 20:08:28 | postgresql 17:08:28.88 INFO  ==> Initializing PostgreSQL database...
  |   | 2020-06-18 20:08:28 | repmgr 17:08:28.88 INFO  ==> Initializing Repmgr...
  |   | 2020-06-18 20:08:28 | repmgr 17:08:28.87 INFO  ==> Preparing repmgr configuration...
  |   | 2020-06-18 20:08:28 | postgresql 17:08:28.80 INFO  ==> postgresql.conf file not detected. Generating it...
  |   | 2020-06-18 20:08:28 | repmgr 17:08:28.79 INFO  ==> Preparing PostgreSQL configuration...
  |   | 2020-06-18 20:08:28 | repmgr 17:08:28.55 INFO  ==> There are no nodes with primary role. Assuming the primary role...
  |   | 2020-06-18 20:08:28 | repmgr 17:08:28.50 INFO  ==> Querying all partner nodes for common upstream node...
  |   | 2020-06-18 20:08:28 | postgresql 17:08:28.49 INFO  ==> Validating settings in POSTGRESQL_* env vars..
  |   | 2020-06-18 20:08:28 | repmgr 17:08:28.49 INFO  ==> Validating settings in REPMGR_* env vars...
  |   | 2020-06-18 20:08:28 | postgresql-repmgr 17:08:28.42 INFO  ==> ** Starting PostgreSQL with Replication Manager setup **
  |   | 2020-06-18 20:08:28 | postgresql-repmgr 17:08:28.41
  |   | 2020-06-18 20:08:28 | postgresql-repmgr 17:08:28.41 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-postgresql-repmgr/issues
  |   | 2020-06-18 20:08:28 | postgresql-repmgr 17:08:28.40 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-postgresql-repmgr
  |   | 2020-06-18 20:08:28 | postgresql-repmgr 17:08:28.40 Welcome to the Bitnami postgresql-repmgr container
  |   | 2020-06-18 20:08:28 | postgresql-repmgr 17:08:28.40
  |   | 2020-06-18 20:08:13 | time="2020-06-18T17:08:13Z" level=error msg="Error opening connection to database (postgresql://postgres:PASSWORD_REMOVED@127.0.0.1:5432/postgres?sslmode=disable): dial tcp 127.0.0.1:5432: connect: connection refused" source="postgres_exporter.go:1474"
  |   | 2020-06-18 20:08:10 | time="2020-06-18T17:08:10Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:08:08 | time="2020-06-18T17:08:08Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:08:07 | time="2020-06-18T17:08:07Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:07:43 | time="2020-06-18T17:07:43Z" level=error msg="Error opening connection to database (postgresql://postgres:PASSWORD_REMOVED@127.0.0.1:5432/postgres?sslmode=disable): dial tcp 127.0.0.1:5432: connect: connection refused" source="postgres_exporter.go:1474"
  |   | 2020-06-18 20:07:40 | time="2020-06-18T17:07:40Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:07:38 | time="2020-06-18T17:07:38Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:07:37 | time="2020-06-18T17:07:37Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:07:13 | time="2020-06-18T17:07:13Z" level=error msg="Error opening connection to database (postgresql://postgres:PASSWORD_REMOVED@127.0.0.1:5432/postgres?sslmode=disable): dial tcp 127.0.0.1:5432: connect: connection refused" source="postgres_exporter.go:1474"
  |   | 2020-06-18 20:07:10 | time="2020-06-18T17:07:10Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:07:08 | time="2020-06-18T17:07:08Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:07:07 | time="2020-06-18T17:07:07Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
  |   | 2020-06-18 20:07:04 | [2020-06-18 17:07:04] [HINT] check that this node is part of a repmgr cluster
  |   | 2020-06-18 20:07:04 | [2020-06-18 17:07:04] [DETAIL] repmgr extension is available but not installed in database "repmgr"
  |   | 2020-06-18 20:07:04 | [2020-06-18 17:07:04] [ERROR] repmgr extension not found on this node
  |   | 2020-06-18 20:07:04 | [2020-06-18 17:07:04] [NOTICE] repmgrd (repmgrd 5.1.0) starting up
  |   | 2020-06-18 20:07:04 | postgresql-repmgr 17:07:04.42 INFO  ==> ** Starting repmgrd **
  |   | 2020-06-18 20:07:04 | postgresql 17:07:04.08 INFO  ==> Starting PostgreSQL in background...
  |   | 2020-06-18 20:07:03 |  
  |   | 2020-06-18 20:07:03 | postgresql-repmgr 17:07:03.96 INFO  ==> ** PostgreSQL with Replication Manager setup finished! **
  |   | 2020-06-18 20:07:03 | postgresql 17:07:03.95 INFO  ==> Stopping PostgreSQL...
  |   | 2020-06-18 20:07:03 | postgresql 17:07:03.93 INFO  ==> Deploying PostgreSQL with persisted data...
  |   | 2020-06-18 20:07:03 | postgresql 17:07:03.84 INFO  ==> Custom configuration /opt/bitnami/postgresql/conf/pg_hba.conf detected
  |   | 2020-06-18 20:07:03 | postgresql 17:07:03.84 INFO  ==> Custom configuration /opt/bitnami/postgresql/conf/postgresql.conf detected
  |   | 2020-06-18 20:07:03 | postgresql 17:07:03.83 INFO  ==> Cleaning stale /bitnami/postgresql/data/postmaster.pid file
  |   | 2020-06-18 20:07:03 | postgresql 17:07:03.83 INFO  ==> Initializing PostgreSQL database...
  |   | 2020-06-18 20:07:03 | repmgr 17:07:03.82 INFO  ==> Initializing Repmgr...
  |   | 2020-06-18 20:07:03 | repmgr 17:07:03.82 INFO  ==> Preparing repmgr configuration...
  |   | 2020-06-18 20:07:03 | postgresql 17:07:03.75 INFO  ==> postgresql.conf file not detected. Generating it...
  |   | 2020-06-18 20:07:03 | repmgr 17:07:03.74 INFO  ==> Preparing PostgreSQL configuration...
  |   | 2020-06-18 20:07:03 | repmgr 17:07:03.60 INFO  ==> There are no nodes with primary role. Assuming the primary role...
  |   | 2020-06-18 20:07:03 | repmgr 17:07:03.54 INFO  ==> Querying all partner nodes for common upstream node...
  |   | 2020-06-18 20:07:03 | postgresql 17:07:03.53 INFO  ==> Validating settings in POSTGRESQL_* env vars..
  |   | 2020-06-18 20:07:03 | repmgr 17:07:03.53 INFO  ==> Validating settings in REPMGR_* env vars...
  |   | 2020-06-18 20:07:03 | postgresql-repmgr 17:07:03.43 INFO  ==> ** Starting PostgreSQL with Replication Manager setup **
  |   | 2020-06-18 20:07:03 | postgresql-repmgr 17:07:03.41
  |   | 2020-06-18 20:07:03 | postgresql-repmgr 17:07:03.41 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-postgresql-repmgr/issues
  |   | 2020-06-18 20:07:03 | postgresql-repmgr 17:07:03.40 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-postgresql-repmgr
  |   | 2020-06-18 20:07:03 | postgresql-repmgr 17:07:03.39 Welcome to the Bitnami postgresql-repmgr container
  |   | 2020-06-18 20:07:03 | postgresql-repmgr 17:07:03.39


Originally posted by @sergeyshaykhullin in https://github.com/bitnami/charts/issues/2499#issuecomment-646184958

created time in 25 days

issue commentbitnami/charts

[bitnami/zookeeper] allow possibilty to give a schedulerName to pod spec

Hi, thanks for your changes. I just reviewed the PR and launched it in our CI/CD system. Once merged the PR this issue should be automatically closed

vDMG

comment created time in 25 days

push eventvDMG/charts-1

Bitnami Containers

commit sha 35f691a99e7e1d4741ae1838da70e4ac94b4d430

[bitnami/prometheus-operator] Release 0.20.5 updating components versions Signed-off-by: Bitnami Containers <containers@bitnami.com>

view details

Andres Martinez Gotor

commit sha 4cff6ba8b0013b6dc368a1e7986c393e8447e75b

[multiple charts] Update hidden properties in the different JSON schemas (#2871) * Update hidden properties in the different JSON schemas * Add missing paths

view details

Miguel Ángel Cabrera Miñagorri

commit sha c3e9463005440719ff2d14b591ce708865ff0670

[bitnami/prometheus-operator] Fix pod affinity (#2803) * [bitnami/prometheus-operator] Add labels when using podAntiAffinity * Fix indentation * Fix indentation

view details

Bitnami Containers

commit sha 8c6ee29fbf936e333643b87c8b4540b18860ae32

[bitnami/logstash] Release 0.4.2 updating components versions Signed-off-by: Bitnami Containers <containers@bitnami.com>

view details

Bitnami Containers

commit sha 980544e66f99869237a34a95c501f4265ff98967

[bitnami/ghost] Release 10.0.11 updating components versions Signed-off-by: Bitnami Containers <containers@bitnami.com>

view details

Bitnami Containers

commit sha ded951963f5a5b561036228ee46b6d70fee7a64c

[bitnami/prometheus-operator] Release 0.20.7 updating components versions Signed-off-by: Bitnami Containers <containers@bitnami.com>

view details

Bitnami Containers

commit sha 5d94a2001d944e8235cec6bf90d64dfc366cd8f1

[bitnami/elasticsearch] Release 12.3.6 updating components versions Signed-off-by: Bitnami Containers <containers@bitnami.com>

view details

Bitnami Containers

commit sha 74adf29dea92f987faf05017cce901ee627dd6b0

[bitnami/wordpress] Release 9.3.13 updating components versions Signed-off-by: Bitnami Containers <containers@bitnami.com>

view details

c3-anuraagnalluri

commit sha 6452a6ecc72e49fa40923f62445873b80a3909ae

[bitnami/zookeeper] Configure max session timeout as standard env var… (#2847) * [bitnami/zookeeper] Configure max session timeout as standard env var in helm chart * merge master and update chart version * merge master and update chart version * [bitnami/zookeeper] Update components versions Signed-off-by: Bitnami Containers <containers@bitnami.com> Co-authored-by: Marcos Bjoerkelund <marcos@bitnami.com> Co-authored-by: Bitnami Containers <containers@bitnami.com>

view details

Bitnami Containers

commit sha 0fbec7ec2788b1721854fd3153bff75d681cf84c

[bitnami/apache] Release 7.3.18 updating components versions Signed-off-by: Bitnami Containers <containers@bitnami.com>

view details

Bitnami Containers

commit sha 4ce55fad597cdcc9515367ec64e54d48fb190385

[bitnami/nginx] Release 6.0.1 updating components versions Signed-off-by: Bitnami Containers <containers@bitnami.com>

view details

Bitnami Containers

commit sha f00032a6a91022528bec7bbd8d5ab4b80c9a0b6f

[bitnami/redis] Release 10.7.3 updating components versions Signed-off-by: Bitnami Containers <containers@bitnami.com>

view details

Bitnami Containers

commit sha 67ffee540499832ecc9a302d8ede134a61e17d98

[bitnami/redmine] Release 14.2.1 updating components versions Signed-off-by: Bitnami Containers <containers@bitnami.com>

view details

Bitnami Containers

commit sha 6001277a42e2b41e93e91118cc88c16d12aafaed

[bitnami/ghost] Release 10.0.12 updating components versions Signed-off-by: Bitnami Containers <containers@bitnami.com>

view details

Bitnami Containers

commit sha 399dbb058bbdb29156660ffe53f852bc2d6742c4

[bitnami/kibana] Release 5.2.5 updating components versions Signed-off-by: Bitnami Containers <containers@bitnami.com>

view details

Bitnami Containers

commit sha f9cb0102f1e03d9ee7f09dbb65e9d7cdc25f84fe

[bitnami/postgresql] Release 8.10.6 updating components versions Signed-off-by: Bitnami Containers <containers@bitnami.com>

view details

Bitnami Containers

commit sha 0c306ed0afd702b0adf3f1a148593c82c61f617e

[bitnami/drupal] Release 7.0.2 updating components versions Signed-off-by: Bitnami Containers <containers@bitnami.com>

view details

Bitnami Containers

commit sha cad55a635d8c8fc558189dec9c5eda0e30585db3

[bitnami/mariadb] Release 7.5.2 updating components versions Signed-off-by: Bitnami Containers <containers@bitnami.com>

view details

Bitnami Containers

commit sha a8a06f849cdf8123fb4e68aa3bc1cfc1fadf628f

[bitnami/pytorch] Release 1.3.17 updating components versions Signed-off-by: Bitnami Containers <containers@bitnami.com>

view details

Bitnami Containers

commit sha e84a85aed105601b6beed564f0df6068d06dad0a

[bitnami/joomla] Release 7.1.19 updating components versions Signed-off-by: Bitnami Containers <containers@bitnami.com>

view details

push time in 25 days

push eventvDMG/charts-1

Carlos Rodríguez Hernández

commit sha 642c47793471a3bb7336601142709e245eb8e520

Bump minor version

view details

push time in 25 days

push eventbitnami/charts

Andres Martinez Gotor

commit sha 4cff6ba8b0013b6dc368a1e7986c393e8447e75b

[multiple charts] Update hidden properties in the different JSON schemas (#2871) * Update hidden properties in the different JSON schemas * Add missing paths

view details

push time in a month

PR merged bitnami/charts

[multiple charts] Update hidden properties in the different JSON schemas

<!-- Before you open the request please review the following guidelines and tips to help it be more easily integrated:

  • Describe the scope of your change - i.e. what the change does.
  • Describe any known limitations with your change.
  • Please run any tests or examples that can exercise your modified code.

Thank you for contributing! We will try to test and integrate the change as soon as we can, but be aware we have many GitHub repositories to manage and can't immediately respond to every request. There is no need to bump or check in on a pull request (it will clutter the discussion of the request).

Also don't be worried if the request is closed or not integrated sometimes the priorities of Bitnami might not match the priorities of the pull request. Don't fret, the open source community thrives on forks and GitHub makes it easy to keep your changes in a forked repo. -->

Description of the change

With the latest update of Kubeapps, the format to hide elements in the form has changed:

  • When hidden is an object, the keys are now value and path.
  • All the paths are JSON paths, which means that instead of using . it should use /. For example: mariadb.enabled -> mariadb/enabled.

This PR updates all the existing JSON schemas to use the new format.

<!-- If there's anything else that's important and relevant to your pull request, mention that information here.-->

Checklist <!-- [Place an '[X]' (no spaces) in all applicable fields. Please remove unrelated fields.] --> - [ ] Chart version bumped in Chart.yaml according to semver.

  • [X] Variables are documented in the README.md - [ ] Title of the PR starts with chart name (e.g. [bitnami/chart])
  • [X] If the chart contains a values-production.yaml apart from values.yaml, ensure that you implement the changes in both files

:warning: Keep in mind that if you want to make changes to the kubeapps chart, please implement them in the kubeapps repository. This is only a synchronized mirror.

+120 -120

0 comment

14 changed files

andresmgot

pr closed time in a month

issue commentbitnami/charts

[bitnami/postgresql] How to enable ssl and external access through ingress

Hi, yes, at this moment it is not the best approach. We are working on adding SSL support directly to the container image used in this chart, so this issue should be solved soon. With the new approach, it will be possible to handle SSL directly using the default image and some parameters in the chart, as we are already doing in other Bitnami charts. Those changes are going to be applied to the PostgreSQL and PostgreSQL HA charts. We will update this thread once releases, stay tuned.

In the meantime, it seems there is a PGSSLROOTCERT env. variable to change the root dir of the certificates, maybe you can mount the certificates in a different place and use this variable. It is something I didn't test, just checked the official docs:

  • https://www.postgresql.org/docs/9.3/libpq-envars.html
  • https://www.postgresql.org/docs/9.3/libpq-connect.html#LIBPQ-CONNECT-SSLROOTCERT But in the end, this is another workaround like the one you used to make it works with a 2-steps process; so I think the definitive solution is going to be part of the new release I previously mentioned.
hussainsaify

comment created time in a month

issue commentbitnami/charts

MongoDB primary pod restart fails to connect to mongodb-secondary

Hi, I was reviewing our internal backlog and there is a task to improve the behavior in this kind of use case. At this moment there is a teammate working on that, so probably in the next days/week, there is a new release of MongoDB chart fixing this issue by using a new approach.

I just added a link to this issue in the task just to be taken into account. Thanks again for letting us know. I am setting the on-hold label to prevent our stale bot from closing this issue while we're working on it.

ganchandrasekaran

comment created time in a month

more