helm | Easy server and cluster automation

You don't need to unpack the charts/*.tgz file. If they're in that directory (and still packed up) then Helm will use them to run the deployment. Helm won't contact the external chart repository on its own, only when you run the helm dependency commands.

After you run helm dep up your filesystem layout should look like

You can use any templating constructs you want inside the template files. A file can include (or generate) multiple YAML files (or none); if it's more than one you need to make sure each begins with the --- YAML start-of-document marker.

If you wanted to generate multiple Deployments based on values, for example, you can specify

serviceName is not the recent representation. Changing it to service/name fixed problem.

helm status will show you the state of a release. This also contains the notes.txt output.

Helm offers the ability to specify the output format of the helm status command (doc). So by running:

The chart exposes two parameters that allow you to choose the StorageClass you want to use for your PVC(s) (otherwise it will use the 'default' one):

• configsvr.persistence.storageClass
• shardsvr.persistence.storageClass

Find more information in the Parameters section of the README.md

So basically you need to install the chart setting these parameters accordingly.

Bitnami Engineer here,

The app's files are now inside the /opt/bitnami/wordpress directory. We recently updated all our WordPress cloud solutions to have the same directory structure. However, it seems that you have a previous version of the solution deployed in the cloud our you used the Bitnami installer in your server.

The easiest way to migrate your data from your current server to the k8s deployment is by using the All in One WP Migration plugin. The plugin takes care of saving all the necessary data so you just need to recover that data in the new deployment. You won't need to copy any other file from the deployment when using this plugin.

Posting this as a community wiki, feel free to edit and expand it for better experience.

As David Maze and Lucia pointed out in comments, services are accessible by their IPs and URLs based on service names.

This part is covered and well explained in official kubenetes documentation DNS for services and pods

That's not from Helm, that's a Kubernetes error. This chart does not support clean upgrades or your values are not matching what you had before. If you can take the downtime, delete the offending deployment and let Helm recreate it. Otherwise you have to look up the right dance of orphan deletes and whatnot.

You can use $ to get to the root scope. So instead of .type you can use $.type. Here you used $type, that is why it's showing undefined (undefined variable "$type", rather it would be $.type.