An emptyDir volume is first created when a Pod is assigned to a node, and exists as long as that Pod is running on that node. As the name says, the emptyDir volume is initially empty. All containers in the Pod can read and write the same files in the emptyDir volume, though that volume can be mounted at the same or different paths in each container. When a Pod is removed from a node for any reason, the data in the emptyDir is deleted permanently.

https://kubernetes.io/docs/concepts/storage/volumes/#emptydir

Super useful for a number of reasons.

Requirements

• Create a Helm chart that successfully deploys a simple MariaDB instance onto Porter. Add this Helm chart to the /addons folder.
• Add form.yaml which renders input options on the frontend. You can use Bitnami's values.schema.json as a starting point, but it may not be essential to support all of these input parameters.

Description

The use-regex annotation is expected to be either "true" or "false" by the ingress controller.

I'm able to successfully set the annotation in the browser, but cannot do so using the CLI with a values.yaml file such as:

ingress:
  annotations:
    nginx.ingress.kubernetes.io/use-regex: "true"
...

The following error message is printed:

Error: Upgrade failed: template: web/templates/ingress.yaml:48:21: executing "web/templates/ingress.yaml" at <eq $v "null">: error calling eq: incompatible types for comparison

It seems like "true" is being coerced into a bool and failing here according to the above error.

Location

• Browser
• CLI
• API

Steps to reproduce

1. Set ingress.annotations["nginx.ingress.kubernetes.io/use-regex"] = "true"
2. Run porter update config --app=my-app --values=values.yaml

Additional details

Setting ingress.annotations["nginx.ingress.kubernetes.io/use-regex"] = true fails at the ingress controller both locally and in the browser with the following message:

Error: Upgrade failed: unable to decode "": json: cannot unmarshal bool into Go struct field ObjectMeta.metadata.annotations of type string