# Deploying bitnami/wordpress

**URL:** <https://forums.k8slens.dev/t/deploying-bitnami-wordpress/572>\
**Category:** All about k0s\
**Created:** [June 14, 2023, 5:42pm UTC](https://forums.k8slens.dev/t/deploying-bitnami-wordpress/572 "2023-06-14T17:42:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mwoodpatrick](https://forums.k8slens.dev/user_avatar/forums.k8slens.dev/mwoodpatrick/32/188_2.png) [@mwoodpatrick](https://forums.k8slens.dev/u/mwoodpatrick)\
**Post date:** [June 14, 2023, 5:42pm UTC](https://forums.k8slens.dev/t/deploying-bitnami-wordpress/572/1 "2023-06-14T17:42:56Z")

</div>

Anyone have any pointers on the right way to deploy bitnami/wordpress on a k0s cluster

---

<div class="post-metadata">

**Author:** ![juanluisvaladas](https://forums.k8slens.dev/letter_avatar_proxy/v4/letter/j/e79b87/32.png) [@juanluisvaladas](https://forums.k8slens.dev/u/juanluisvaladas)\
**Post date:** [June 15, 2023, 8:18am UTC](https://forums.k8slens.dev/t/deploying-bitnami-wordpress/572/2 "2023-06-15T08:18:22Z")

</div>

Hi @mwoodpatrick,  
K0s deploys a vanilla kubernetes so it’s the same as with any other kubernetes distribution.

Checking the bitnami documentation, I see [there is a guide for minikube](https://docs.bitnami.com/kubernetes/get-started-kubernetes/) so it’s pretty much the same with these few differences:

The first 3 steps are installing minikube, so skip them.

Steps 4 and 5 are installing helm, deploying bitnami and redis, you should be able to run this as is. Or if you want to use a GUI you can use you can do it with [Lens](https://k8slens.dev/). The steps are basically the same except you don’t need to install helm.

Step 6 uses the kubernetes dashboard which we don’t have, you can obtain the same information using [Lens](https://k8slens.dev/) or if you don’t want a GUI, use the CLI.

Step 7 is uninstalling, you can do it with helm CLI or lens, depending on what you did on steps 4 and 5.

---

<div class="post-metadata">

**Author:** ![mwoodpatrick](https://forums.k8slens.dev/user_avatar/forums.k8slens.dev/mwoodpatrick/32/188_2.png) [@mwoodpatrick](https://forums.k8slens.dev/u/mwoodpatrick)\
**Post date:** [June 15, 2023, 10:34am UTC](https://forums.k8slens.dev/t/deploying-bitnami-wordpress/572/3 "2023-06-15T10:34:14Z")

</div>

Many thanks for the response its much appreciated.

I do have Helm installed and running on my cluster and did try to install WordPress using:

> helm install bitnami/wordpress --generate-name

The install is pending and if I look at the pvc’s I see they are pending:

```auto
> kubectl get pvc
> NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
> data-wordpress-1686763442-mariadb-0 Pending 16h
> wordpress-1686763442 Pending 16h

```

Uninstalling that helm release and running:

> helm show values bitnami/wordpress|less

I realized that the issue was that Helm did not know what storage class to use for the PVC so after running:

> helm install bitnami/wordpress --generate-name --set serviceType=NodePort --set global.storageClass=openebs-hostpath

The chart did deploy and I was able to access the logs for the WordPress pod showing the app was running. The only item still pending:

```auto
> kubectl get all -A|grep -i pend
> default service/wordpress-1686823545 LoadBalancer 10.110.100.38 <pending> 80:31856/TCP,443:31155/TCP 107s

```

WordPress service. I was able to access the WordPress app using port forward:

> kubectl port-forward deployment.apps/wordpress-1686823545 :8080

And was able to login to WordPress and update the plugins.

I need to try and figure out why the service is still pending. If anyone has any pointers on how to do this I would appreciate some pointers

---

<div class="post-metadata">

**Author:** ![mwoodpatrick](https://forums.k8slens.dev/user_avatar/forums.k8slens.dev/mwoodpatrick/32/188_2.png) [@mwoodpatrick](https://forums.k8slens.dev/u/mwoodpatrick)\
**Post date:** [June 15, 2023, 12:48pm UTC](https://forums.k8slens.dev/t/deploying-bitnami-wordpress/572/4 "2023-06-15T12:48:12Z")

</div>

Is there a way to get: [WSL-2 system dependencies · Issue #2755 · k0sproject/k0s (github.com)](https://github.com/k0sproject/k0s/issues/2755) reopened? I’m having problems getting loadbalancers to come out of pending state on wsl-2 and “k0s sysinfo” is reporting erroneous info on WSL-2. I updated this issue with the problems I’m seeing with load balancers on WSL-2