Bitnami package for PrestaShop

PrestaShop is a powerful open source eCommerce platform used by over 250,000 online storefronts worldwide. It is easily customizable, responsive, and includes powerful tools to drive online sales.

Overview of PrestaShop

Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.

TL;DR

helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/prestashop

Note: You need to substitute the placeholders REGISTRY_NAME and REPOSITORY_NAME with a reference to your Helm chart registry and repository.

Introduction

This chart bootstraps a PrestaShop deployment on a Kubernetes cluster using the Helm package manager.

It also packages the Bitnami MariaDB chart which is required for bootstrapping a MariaDB deployment for the database requirements of the PrestaShop application.

Bitnami charts can be used with Kubeapps for deployment and management of Helm Charts in clusters.

Prerequisites

Kubernetes 1.23+
Helm 3.8.0+
PV provisioner support in the underlying infrastructure
ReadWriteMany volumes for deployment scaling

Installing the Chart

To install the chart with the release name my-release:

helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/prestashop

Note: You need to substitute the placeholders REGISTRY_NAME and REPOSITORY_NAME with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use REGISTRY_NAME=registry-1.docker.io and REPOSITORY_NAME=bitnamicharts.

The command deploys PrestaShop on the Kubernetes cluster in the default configuration. The Parameters section lists the parameters that can be configured during installation.

Tip: List all releases using helm list

Configuration and installation details

Resource requests and limits

Bitnami charts allow setting resource requests and limits for all containers inside the chart deployment. These are inside the resources value (check parameter table). Setting requests is essential for production workloads and these should be adapted to your specific use case.

To make this process easier, the chart contains the resourcesPreset values, which automatically sets the resources section according to different presets. Check these presets in the bitnami/common chart. However, in production workloads using resourcePreset is discouraged as it may not fully adapt to your specific needs. Find more information on container resource management in the official Kubernetes documentation.

Rolling VS Immutable tags

It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.

Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.

Image

The image parameter allows specifying which image will be pulled for the chart.

Private registry

If you configure the image value to one in a private registry, you will need to specify an image pull secret.

Manually create image pull secret(s) in the namespace. See this YAML example reference. Consult your image registry’s documentation about getting the appropriate secret.
Note that the imagePullSecrets configuration value cannot currently be passed to helm using the --set parameter, so you must supply these using a values.yaml file, such as:
```
imagePullSecrets:
  - name: SECRET_NAME
```
Install the chart

Setting Pod’s affinity

This chart allows you to set your custom affinity using the affinity parameter. Find more information about Pod’s affinity in the kubernetes documentation.

As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the bitnami/common chart. To do so, set the podAffinityPreset, podAntiAffinityPreset, or nodeAffinityPreset parameters.

Host path

System compatibility

The local filesystem accessibility to a container in a pod with hostPath has been tested on OSX/MacOS with xhyve, and Linux with VirtualBox.
Windows has not been tested with the supported VM drivers. Minikube does however officially support Mounting Host Folders per pod. Or you may manually sync your container whenever host files are changed with tools like docker-sync or docker-bg-sync.

Mounting steps

The specified hostPath directory must already exist (create one if it does not).
Install the chart
```
helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT oci://REGISTRY_NAME/REPOSITORY_NAME/prestashop
```
Note
Note: You need to substitute the placeholders REGISTRY_NAME and REPOSITORY_NAME with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use REGISTRY_NAME=registry-1.docker.io and REPOSITORY_NAME=bitnamicharts.

This will mount the prestashop-data volume into the hostPath directory. The site data will be persisted if the mount path contains valid data, else the site data will be initialized at first launch.
Because the container cannot control the host machine’s directory permissions, you must set the PrestaShop file directory permissions yourself and disable or clear PrestaShop cache.

SSL

One needs to explicitly turn on SSL in the Prestashop administration panel, else a 302 redirect to http scheme is returned on any page of the site by default.

To enable SSL on all pages, follow these steps:

Browse to the administration panel and log in.
Click “Shop Parameters” in the left navigation panel.
Set the option “Enable SSL” to “Yes”.
Click the “Save” button.
Set the (now enabled) option “Enable SSL on all pages” to “Yes”.
Click the “Save” button.

Persistence

The Bitnami PrestaShop image stores the PrestaShop data and configurations at the /bitnami/prestashop path of the container.

Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube. See the Parameters section to configure the PVC or to disable persistence.

Existing PersistentVolumeClaim

Create the PersistentVolume
Create the PersistentVolumeClaim
Install the chart

helm install my-release --set persistence.existingClaim=PVC_NAME oci://REGISTRY_NAME/REPOSITORY_NAME/prestashop

Note
Note: You need to substitute the placeholders REGISTRY_NAME and REPOSITORY_NAME with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use REGISTRY_NAME=registry-1.docker.io and REPOSITORY_NAME=bitnamicharts.

Parameters

Global parameters

Name	Description	Value
`global.imageRegistry`	Global Docker image registry	`""`
`global.imagePullSecrets`	Global Docker registry secret names as an array	`[]`
`global.storageClass`	Global StorageClass for Persistent Volume(s)	`""`
`global.compatibility.openshift.adaptSecurityContext`	Adapt the securityContext sections of the deployment to make them compatible with Openshift restricted-v2 SCC: remove runAsUser, runAsGroup and fsGroup and let the platform use their allowed default IDs. Possible values: auto (apply if the detected running cluster is Openshift), force (perform the adaptation always), disabled (do not perform adaptation)	`auto`

Common parameters

Name	Description	Value
`kubeVersion`	Force target Kubernetes version (using Helm capabilities if not set)	`""`
`nameOverride`	String to partially override prestashop.fullname template (will maintain the release name)	`""`
`fullnameOverride`	String to fully override prestashop.fullname template	`""`
`namespaceOverride`	String to fully override common.names.namespace	`""`
`commonAnnotations`	Common annotations to add to all PrestaShop resources (sub-charts are not considered). Evaluated as a template	`{}`
`commonLabels`	Common labels to add to all PrestaShop resources (sub-charts are not considered). Evaluated as a template	`{}`
`extraDeploy`	Array with extra yaml to deploy with the chart. Evaluated as a template	`[]`

PrestaShop parameters

Name	Description	Value
`image.registry`	PrestaShop image registry	`REGISTRY_NAME`
`image.repository`	PrestaShop image repository	`REPOSITORY_NAME/prestashop`
`image.digest`	PrestaShop image digest in the way sha256:aa…. Please note this parameter, if set, will override the tag	`""`
`image.pullPolicy`	PrestaShop image pull policy	`IfNotPresent`
`image.pullSecrets`	Specify docker-registry secret names as an array	`[]`
`image.debug`	Specify if debug logs should be enabled	`false`
`automountServiceAccountToken`	Mount Service Account token in pod	`false`
`hostAliases`	Deployment pod host aliases	`[]`
`replicaCount`	Number of PrestaShop Pods to run (requires ReadWriteMany PVC support)	`1`
`prestashopSkipInstall`	Skip PrestaShop installation wizard. Useful for migrations and restoring from SQL dump	`false`
`prestashopHost`	PrestaShop host to create application URLs (when ingress, it will be ignored)	`""`
`prestashopUsername`	User of the application	`[email protected]`
`prestashopPassword`	Application password	`""`
`prestashopEmail`	Admin email	`[email protected]`
`prestashopFirstName`	First Name	`Bitnami`
`prestashopLastName`	Last Name	`User`
`prestashopCookieCheckIP`	Whether to check the cookie’s IP address or not	`no`
`prestashopCountry`	Default country of the store	`us`
`prestashopLanguage`	Default language of the store (ISO code)	`en`
`allowEmptyPassword`	Allow DB blank passwords	`true`
`command`	Override default container command (useful when using custom images)	`[]`
`args`	Override default container args (useful when using custom images)	`[]`
`updateStrategy.type`	Update strategy - only really applicable for deployments with RWO PVs attached	`RollingUpdate`
`extraEnvVars`	An array to add extra environment variables	`[]`
`extraEnvVarsCM`	ConfigMap with extra environment variables	`""`
`extraEnvVarsSecret`	Secret with extra environment variables	`""`
`extraVolumes`	Extra volumes to add to the deployment. Requires setting `extraVolumeMounts`	`[]`
`extraVolumeMounts`	Extra volume mounts to add to the container. Normally used with `extraVolumes`	`[]`
`initContainers`	Extra init containers to add to the deployment	`[]`
`pdb.create`	Enable/disable a Pod Disruption Budget creation	`true`
`pdb.minAvailable`	Minimum number/percentage of pods that should remain scheduled	`""`
`pdb.maxUnavailable`	Maximum number/percentage of pods that may be made unavailable. Defaults to `1` if both `pdb.minAvailable` and `pdb.maxUnavailable` are empty.	`""`
`sidecars`	Extra sidecar containers to add to the deployment	`[]`
`tolerations`	Tolerations for pod assignment. Evaluated as a template.	`[]`
`priorityClassName`	PrestaShop pods’ priorityClassName	`""`
`schedulerName`	Name of the k8s scheduler (other than default)	`""`
`topologySpreadConstraints`	Topology Spread Constraints for pod assignment	`[]`
`existingSecret`	Use existing secret for the application password	`""`
`smtpHost`	SMTP host	`""`
`smtpPort`	SMTP port	`""`
`smtpUser`	SMTP user	`""`
`smtpPassword`	SMTP password	`""`
`smtpProtocol`	SMTP Protocol (options: ssl,tls, nil)	`""`
`containerPorts.http`	Sets HTTP port inside NGINX container	`8080`
`containerPorts.https`	Sets HTTPS port inside NGINX container	`8443`
`extraContainerPorts`	Optionally specify extra list of additional ports for Prestashop container(s)	`[]`
`sessionAffinity`	Control where client requests go, to the same pod or round-robin	`None`
`persistence.enabled`	Enable persistence using PVC	`true`
`persistence.storageClass`	PrestaShop Data Persistent Volume Storage Class	`""`
`persistence.accessModes`	PVC Access Mode for PrestaShop volume	`["ReadWriteOnce"]`
`persistence.size`	PVC Storage Request for PrestaShop volume	`8Gi`
`persistence.existingClaim`	An Existing PVC name	`""`
`persistence.hostPath`	If defined, the prestashop-data volume will mount to the specified hostPath	`""`
`persistence.annotations`	Persistent Volume Claim annotations	`{}`
`podAffinityPreset`	Pod affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard`	`""`
`podAntiAffinityPreset`	Pod anti-affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard`	`soft`
`nodeAffinityPreset.type`	Node affinity preset type. Ignored if `affinity` is set. Allowed values: `soft` or `hard`	`""`
`nodeAffinityPreset.key`	Node label key to match Ignored if `affinity` is set.	`""`
`nodeAffinityPreset.values`	Node label values to match. Ignored if `affinity` is set.	`[]`
`affinity`	Affinity for pod assignment	`{}`
`nodeSelector`	Node labels for pod assignment. Evaluated as a template.	`{}`
`resourcesPreset`	Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if resources is set (resources is recommended for production).	`micro`
`resources`	Set container requests and limits for different resources like CPU or memory (essential for production workloads)	`{}`
`podSecurityContext.enabled`	Enable PrestaShop pods’ Security Context	`true`
`podSecurityContext.fsGroupChangePolicy`	Set filesystem group change policy	`Always`
`podSecurityContext.sysctls`	Set kernel settings using the sysctl interface	`[]`
`podSecurityContext.supplementalGroups`	Set filesystem extra groups	`[]`
`podSecurityContext.fsGroup`	PrestaShop pods’ group ID	`1001`
`containerSecurityContext.enabled`	Enabled containers’ Security Context	`true`
`containerSecurityContext.seLinuxOptions`	Set SELinux options in container	`{}`
`containerSecurityContext.runAsUser`	Set containers’ Security Context runAsUser	`1001`
`containerSecurityContext.runAsGroup`	Set containers’ Security Context runAsGroup	`0`
`containerSecurityContext.runAsNonRoot`	Set container’s Security Context runAsNonRoot	`true`
`containerSecurityContext.privileged`	Set container’s Security Context privileged	`false`
`containerSecurityContext.readOnlyRootFilesystem`	Set container’s Security Context readOnlyRootFilesystem	`false`
`containerSecurityContext.allowPrivilegeEscalation`	Set container’s Security Context allowPrivilegeEscalation	`false`
`containerSecurityContext.capabilities.drop`	List of capabilities to be dropped	`["ALL"]`
`containerSecurityContext.seccompProfile.type`	Set container’s Security Context seccomp profile	`RuntimeDefault`
`livenessProbe.enabled`	Enable livenessProbe	`true`
`livenessProbe.initialDelaySeconds`	Initial delay seconds for livenessProbe	`600`
`livenessProbe.periodSeconds`	Period seconds for livenessProbe	`10`
`livenessProbe.timeoutSeconds`	Timeout seconds for livenessProbe	`5`
`livenessProbe.failureThreshold`	Failure threshold for livenessProbe	`6`
`livenessProbe.successThreshold`	Success threshold for livenessProbe	`1`
`readinessProbe.enabled`	Enable readinessProbe	`true`
`readinessProbe.path`	Request path for readinessProbe	`/`
`readinessProbe.initialDelaySeconds`	Initial delay seconds for readinessProbe	`30`
`readinessProbe.periodSeconds`	Period seconds for readinessProbe	`5`
`readinessProbe.timeoutSeconds`	Timeout seconds for readinessProbe	`3`
`readinessProbe.failureThreshold`	Failure threshold for readinessProbe	`6`
`readinessProbe.successThreshold`	Success threshold for readinessProbe	`1`
`startupProbe.enabled`	Enable startupProbe	`false`
`startupProbe.path`	Request path for startupProbe	`/`
`startupProbe.initialDelaySeconds`	Initial delay seconds for startupProbe	`0`
`startupProbe.periodSeconds`	Period seconds for startupProbe	`10`
`startupProbe.timeoutSeconds`	Timeout seconds for startupProbe	`3`
`startupProbe.failureThreshold`	Failure threshold for startupProbe	`60`
`startupProbe.successThreshold`	Success threshold for startupProbe	`1`
`customLivenessProbe`	Override default liveness probe	`{}`
`customReadinessProbe`	Override default readiness probe	`{}`
`customStartupProbe`	Override default startup probe	`{}`
`lifecycleHooks`	LifecycleHook to set additional configuration at startup Evaluated as a template	`{}`
`podAnnotations`	Pod annotations	`{}`
`podLabels`	Pod extra labels	`{}`
`serviceAccount.create`	Enable creation of ServiceAccount for Prestashop pod	`true`
`serviceAccount.name`	The name of the ServiceAccount to use.	`""`
`serviceAccount.automountServiceAccountToken`	Allows auto mount of ServiceAccountToken on the serviceAccount created	`false`
`serviceAccount.annotations`	Additional custom annotations for the ServiceAccount	`{}`

Traffic Exposure Parameters

Name	Description	Value
`service.type`	Kubernetes Service type	`LoadBalancer`
`service.ports.http`	Service HTTP port	`80`
`service.ports.https`	Service HTTPS port	`443`
`service.clusterIP`	Service Cluster IP	`""`
`service.loadBalancerSourceRanges`	Control hosts connecting to “LoadBalancer” only	`[]`
`service.loadBalancerIP`	Load balancerIP for the PrestaShop Service (optional, cloud specific)	`""`
`service.nodePorts.http`	Kubernetes HTTP node port	`""`
`service.nodePorts.https`	Kubernetes HTTPS node port	`""`
`service.externalTrafficPolicy`	Enable client source IP preservation	`Cluster`
`service.extraPorts`	Extra ports to expose (normally used with the `sidecar` value)	`[]`
`service.annotations`	Additional custom annotations for PrestaShop service	`{}`
`service.sessionAffinity`	Session Affinity for Kubernetes service, can be “None” or “ClientIP”	`None`
`service.sessionAffinityConfig`	Additional settings for the sessionAffinity	`{}`
`ingress.enabled`	Enable ingress controller resource	`false`
`ingress.pathType`	Ingress path type	`ImplementationSpecific`
`ingress.apiVersion`	Override API Version (automatically detected if not set)	`""`
`ingress.ingressClassName`	IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)	`""`
`ingress.hostname`	Default host for the ingress resource	`prestashop.local`
`ingress.path`	Default path for the ingress resource*’ in order to use this	`/`
`ingress.annotations`	Additional annotations for the Ingress resource. To enable certificate autogeneration, place here your cert-manager annotations.	`{}`
`ingress.tls`	Create TLS Secret	`false`
`ingress.extraHosts`	The list of additional hostnames to be covered with this ingress record.	`[]`
`ingress.extraPaths`	Any additional arbitrary paths that may need to be added to the ingress under the main host.	`[]`
`ingress.extraTls`	The tls configuration for additional hostnames to be covered with this ingress record.	`[]`
`ingress.secrets`	If you’re providing your own certificates, please use this to add the certificates as secrets	`[]`
`ingress.extraRules`	Additional rules to be covered with this ingress record	`[]`

Database parameters

Name	Description	Value
`mariadb.enabled`	Whether to deploy a mariadb server to satisfy the applications database requirements	`true`
`mariadb.architecture`	MariaDB architecture. Allowed values: `standalone` or `replication`	`standalone`
`mariadb.auth.rootPassword`	Password for the MariaDB `root` user	`""`
`mariadb.auth.database`	Database name to create	`bitnami_prestashop`
`mariadb.auth.username`	Database user to create	`bn_prestashop`
`mariadb.auth.password`	Password for the database	`""`
`mariadb.primary.persistence.enabled`	Enable database persistence using PVC	`true`
`mariadb.primary.persistence.storageClass`	MariaDB primary persistent volume storage Class	`""`
`mariadb.primary.persistence.accessModes`	Database Persistent Volume Access Modes	`["ReadWriteOnce"]`
`mariadb.primary.persistence.size`	Database Persistent Volume Size	`8Gi`
`mariadb.primary.persistence.hostPath`	Set path in case you want to use local host path volumes (not recommended in production)	`""`
`mariadb.primary.persistence.existingClaim`	Name of an existing `PersistentVolumeClaim` for MariaDB primary replicas	`""`
`mariadb.primary.resourcesPreset`	Set container resources according to one common preset (allowed values: none, nano, small, medium, large, xlarge, 2xlarge). This is ignored if primary.resources is set (primary.resources is recommended for production).	`micro`
`mariadb.primary.resources`	Set container requests and limits for different resources like CPU or memory (essential for production workloads)	`{}`
`externalDatabase.host`	Host of the existing database	`""`
`externalDatabase.port`	Port of the existing database	`3306`
`externalDatabase.user`	Existing username in the existing database	`bn_prestashop`
`externalDatabase.password`	Password for the above username	`""`
`externalDatabase.database`	Name of the existing database	`bitnami_prestashop`
`externalDatabase.existingSecret`	Name of an existing secret resource containing the DB password	`""`

Volume Permissions parameters

Name	Description	Value
`volumePermissions.enabled`	Enable init container that changes volume permissions in the data directory (for cases where the default k8s `runAsUser` and `fsUser` values do not work)	`false`
`volumePermissions.image.registry`	Init container volume-permissions image registry	`REGISTRY_NAME`
`volumePermissions.image.repository`	Init container volume-permissions image repository	`REPOSITORY_NAME/os-shell`
`volumePermissions.image.digest`	Init container volume-permissions image digest in the way sha256:aa…. Please note this parameter, if set, will override the tag	`""`
`volumePermissions.image.pullPolicy`	Init container volume-permissions image pull policy	`IfNotPresent`
`volumePermissions.image.pullSecrets`	Specify docker-registry secret names as an array	`[]`
`volumePermissions.resourcesPreset`	Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if volumePermissions.resources is set (volumePermissions.resources is recommended for production).	`nano`
`volumePermissions.resources`	Set container requests and limits for different resources like CPU or memory (essential for production workloads)	`{}`

Metrics parameters

Name	Description	Value
`metrics.enabled`	Start a side-car prometheus exporter	`false`
`metrics.image.registry`	Apache exporter image registry	`REGISTRY_NAME`
`metrics.image.repository`	Apache exporter image repository	`REPOSITORY_NAME/apache-exporter`
`metrics.image.digest`	Apache exporter image digest in the way sha256:aa…. Please note this parameter, if set, will override the tag	`""`
`metrics.image.pullPolicy`	Apache exporter image pull policy	`IfNotPresent`
`metrics.image.pullSecrets`	Specify docker-registry secret names as an array	`[]`
`metrics.resourcesPreset`	Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if metrics.resources is set (metrics.resources is recommended for production).	`nano`
`metrics.resources`	Set container requests and limits for different resources like CPU or memory (essential for production workloads)	`{}`
`metrics.podAnnotations`	Metrics exporter pod annotations	`{}`

Certificate injection parameters

Name	Description	Value
`certificates.customCertificate.certificateSecret`	Secret containing the certificate and key to add	`""`
`certificates.customCertificate.chainSecret.name`	Name of the secret containing the certificate chain	`""`
`certificates.customCertificate.chainSecret.key`	Key of the certificate chain file inside the secret	`""`
`certificates.customCertificate.certificateLocation`	Location in the container to store the certificate	`/etc/ssl/certs/ssl-cert-snakeoil.pem`
`certificates.customCertificate.keyLocation`	Location in the container to store the private key	`/etc/ssl/private/ssl-cert-snakeoil.key`
`certificates.customCertificate.chainLocation`	Location in the container to store the certificate chain	`/etc/ssl/certs/mychain.pem`
`certificates.customCAs`	Defines a list of secrets to import into the container trust store	`[]`
`certificates.command`	Override default container command (useful when using custom images)	`[]`
`certificates.args`	Override default container args (useful when using custom images)	`[]`
`certificates.extraEnvVars`	Container sidecar extra environment variables	`[]`
`certificates.extraEnvVarsCM`	ConfigMap with extra environment variables	`""`
`certificates.extraEnvVarsSecret`	Secret with extra environment variables	`""`
`certificates.image.registry`	Container sidecar registry	`REGISTRY_NAME`
`certificates.image.repository`	Container sidecar image repository	`REPOSITORY_NAME/os-shell`
`certificates.image.digest`	Container sidecar image digest in the way sha256:aa…. Please note this parameter, if set, will override the tag	`""`
`certificates.image.pullPolicy`	Container sidecar image pull policy	`IfNotPresent`
`certificates.image.pullSecrets`	Container sidecar image pull secrets	`[]`

NetworkPolicy parameters

Name	Description	Value
`networkPolicy.enabled`	Specifies whether a NetworkPolicy should be created	`true`
`networkPolicy.allowExternal`	Don’t require server label for connections	`true`
`networkPolicy.allowExternalEgress`	Allow the pod to access any range of port and all destinations.	`true`
`networkPolicy.extraIngress`	Add extra ingress rules to the NetworkPolicy	`[]`
`networkPolicy.extraEgress`	Add extra ingress rules to the NetworkPolicy	`[]`
`networkPolicy.ingressNSMatchLabels`	Labels to match to allow traffic from other namespaces	`{}`
`networkPolicy.ingressNSPodMatchLabels`	Pod labels to match to allow traffic from other namespaces	`{}`

The above parameters map to the env variables defined in bitnami/prestashop. For more information please refer to the bitnami/prestashop image documentation.

Note
:

For PrestaShop to function correctly, you should specify the prestashopHost parameter to specify the FQDN (recommended) or the public IP address of the PrestaShop service.

Optionally, you can specify the prestashopLoadBalancerIP parameter to assign a reserved IP address to the PrestaShop service of the chart. However please note that this feature is only available on a few cloud providers (f.e. GKE).

To reserve a public IP address on GKE:
$ gcloud compute addresses create prestashop-public-ip
The reserved IP address can be associated to the PrestaShop service by specifying it as the value of the prestashopLoadBalancerIP parameter while installing the chart.

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

helm install my-release \
  --set prestashopUsername=admin,prestashopPassword=password,mariadb.auth.rootPassword=secretpassword \
    oci://REGISTRY_NAME/REPOSITORY_NAME/prestashop

Note: You need to substitute the placeholders REGISTRY_NAME and REPOSITORY_NAME with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use REGISTRY_NAME=registry-1.docker.io and REPOSITORY_NAME=bitnamicharts.

The above command sets the PrestaShop administrator account username and password to admin and password respectively. Additionally, it sets the MariaDB root user password to secretpassword.

NOTE: Once this chart is deployed, it is not possible to change the application’s access credentials, such as usernames or passwords, using Helm. To change these application credentials after deployment, delete any persistent volumes (PVs) used by the chart and re-deploy it, or use the application’s built-in administrative tools if available.

Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,

helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/prestashop

Note: You need to substitute the placeholders REGISTRY_NAME and REPOSITORY_NAME with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use REGISTRY_NAME=registry-1.docker.io and REPOSITORY_NAME=bitnamicharts. Tip: You can use the default values.yaml

Troubleshooting

Find more information about how to deal with common errors related to Bitnami’s Helm charts in this troubleshooting guide.

Upgrading

To 21.0.0

This major bump changes the following security defaults:

resourcesPreset is changed from none to the minimum size working in our test suites (NOTE: resourcesPreset is not meant for production usage, but resources adapted to your use case).
global.compatibility.openshift.adaptSecurityContext is changed from disabled to auto.
The networkPolicy section has been normalized amongst all Bitnami charts. Compared to the previous approach, the values section has been simplified (check the Parameters section) and now it set to enabled=true by default. Egress traffic is allowed by default and ingress traffic is allowed by all pods but only to the ports set in containerPorts and extraContainerPorts.

This could potentially break any customization or init scripts used in your deployment. If this is the case, change the default values to the previous ones.

Also, this major release bumps the MariaDB chart version to 18.x.x; no major issues are expected during the upgrade.

To 20.0.0

This major release bumps the MariaDB version to 11.2. No major issues are expected during the upgrade.

To 19.0.0

This major release bumps the MariaDB version to 11.1. No major issues are expected during the upgrade.

To 18.0.0

This major release bumps the MariaDB version to 11.0. Follow the upstream instructions for upgrading from MariaDB 10.11 to 11.0. No major issues are expected during the upgrade.

To 17.0.0

This major release bumps the MariaDB version to 10.11. Follow the upstream instructions for upgrading from MariaDB 10.6 to 10.11. No major issues are expected during the upgrade.

To 15.0.0

This major release bumps the MariaDB version to 10.6. Follow the upstream instructions for upgrading from MariaDB 10.5 to 10.6. No major issues are expected during the upgrade.

To 14.0.0

This major release renames several values in this chart and adds missing features, in order to be inline with the rest of assets in the Bitnami charts repository.

Affected values:

service.port was deprecated. We recommend using service.ports.http instead.
service.httpsPort was deprecated. We recommend using service.ports.https instead.

Additionally updates the MariaDB subchart to it newest major, 10.0.0, which contains similar changes. Check MariaDB Upgrading Notes for more information.

To 13.0.0

This version standardizes the way of defining Ingress rules. When configuring a single hostname for the Ingress rule, set the ingress.hostname value. When defining more than one, set the ingress.extraHosts array. Apart from this case, no issues are expected to appear when upgrading.

To 12.0.0

On November 13, 2020, Helm v2 support was formally finished, this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.

What changes were introduced in this major version?

Previous versions of this Helm Chart use apiVersion: v1 (installable by both Helm 2 and 3), this Helm Chart was updated to apiVersion: v2 (installable by Helm 3 only). Here you can find more information about the apiVersion field.
Move dependency information from the requirements.yaml to the Chart.yaml
After running helm dependency update, a Chart.lock file is generated containing the same structure used in the previous requirements.lock
The different fields present in the Chart.yaml file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts

Considerations when upgrading to this version

If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn’t face any issues
If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn’t support Helm v2 anymore
If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the official Helm documentation about migrating from Helm v2 to v3

Useful links

To 11.0.0

MariaDB dependency version was bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check MariaDB Upgrading Notes for more information.

To upgrade to 11.0.0, you have two alternatives:

Install a new Prestashop chart, and migrate your Prestashop site using backup/restore using any Backup and Restore tool from Prestashop marketplace.
Reuse the PVC used to hold the MariaDB data on your previous release. To do so, follow the instructions below (the following example assumes that the release name is prestashop):

Obtain the credentials and the name of the PVC used to hold the MariaDB data on your current release:

export PRESTASHOP_PASSWORD=$(kubectl get secret --namespace default prestashop -o jsonpath="{.data.prestashop-password}" | base64 -d)
export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default prestashop-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
export MARIADB_PASSWORD=$(kubectl get secret --namespace default prestashop-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
export MARIADB_PVC=$(kubectl get pvc -l app.kubernetes.io/instance=prestashop,app.kubernetes.io/name=mariadb,app.kubernetes.io/component=primary -o jsonpath="{.items[0].metadata.name}")

Upgrade your release (maintaining the version) disabling MariaDB and scaling Prestashop replicas to 0:

helm upgrade prestashop oci://REGISTRY_NAME/REPOSITORY_NAME/prestashop --set prestashopPassword=$PRESTASHOP_PASSWORD --set replicaCount=0 --set mariadb.enabled=false --version 10.0.0

Note: You need to substitute the placeholders REGISTRY_NAME and REPOSITORY_NAME with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use REGISTRY_NAME=registry-1.docker.io and REPOSITORY_NAME=bitnamicharts.

Finally, upgrade you release to 11.0.0 reusing the existing PVC, and enabling back MariaDB:

helm upgrade prestashop oci://REGISTRY_NAME/REPOSITORY_NAME/prestashop --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set prestashopPassword=$PRESTASHOP_PASSWORD

Note: You need to substitute the placeholders REGISTRY_NAME and REPOSITORY_NAME with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use REGISTRY_NAME=registry-1.docker.io and REPOSITORY_NAME=bitnamicharts.

You should see the lines below in MariaDB container logs:

$ kubectl logs $(kubectl get pods -l app.kubernetes.io/instance=prestashop,app.kubernetes.io/name=mariadb,app.kubernetes.io/component=primary -o jsonpath="{.items[0].metadata.name}")
...
mariadb 12:13:24.98 INFO  ==> Using persisted data
mariadb 12:13:25.01 INFO  ==> Running mysql_upgrade
...

To 10.0.0

The Bitnami PrestaShop image was updated to support and enable the “non-root” user approach

If you want to continue to run the container image as the root user, you need to set podSecurityContext.enabled=false and containerSecurity.context.enabled=false.

This upgrade also adapts the chart to the latest Bitnami good practices. Check the Parameters section for more information.

To 9.0.0

Helm performs a lookup for the object based on its group (apps), version (v1), and kind (Deployment). Also known as its GroupVersionKind, or GVK. Changing the GVK is considered a compatibility breaker from Kubernetes’ point of view, so you cannot “upgrade” those objects to the new GVK in-place. Earlier versions of Helm 3 did not perform the lookup correctly which has since been fixed to match the spec.

In https://github.com/helm/charts/pull/17308 the apiVersion of the deployment resources was updated to apps/v1 in tune with the api’s deprecated, resulting in compatibility breakage.

This major version signifies this change.

To 3.0.0

Backwards compatibility is not guaranteed unless you modify the labels used on the chart’s deployments. Use the workaround below to upgrade from versions previous to 3.0.0. The following example assumes that the release name is prestashop:

kubectl patch deployment prestashop-prestashop --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
kubectl delete statefulset prestashop-mariadb --cascade=false

License

Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.