Tag: kubernetes

Posted on

k3s nodes showing not ready after initial install and config

‘kubectrl describe nodes’ is showing

reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized

for each node.

This looks like the same issue as here – I followed the quickstart guide and used the ‘--flannel-backend none' option which looks like I setup a snigle node cluster with no networking…

Following the network docs here, I changed my setup line removing the ‘none’ option and now everything is good:

curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="server" sh -s - --token [my token]
Posted on

Kubernetes: creating a hostPath PersistentVolume in a single node cluster

To create a ‘hostPath’ PersistentVolume in a single node cluster (do not use in a cluster with more than 1 node):

kind: PersistentVolume
 apiVersion: v1
 metadata:
   name: pv1
   labels:
     type: local
 spec:
   storageClassName: manual
   capacity:
     storage: 1Gi
   accessModes:
     - ReadWriteOnce
   hostPath:
     path: "/your-path-for-vol1"

If the above is pv1.yaml, apply with:

kubectl apply -f pv1.yaml

For more info, see the docs here.

Posted on

Helm install of MariaDB on bare metal Kubernetes: “mkdir: cannot create directory ‘/bitnami/mariadb/data’: Permission denied”

Installing the MariaDB chart with Helm on Kubernetes, I ran into issues with permissions on the folder that I created for the PersistentVolume:

INFO  ==> ** Starting MariaDB setup **
 INFO  ==> Validating settings in MYSQL_/MARIADB_ env vars..
 INFO  ==> Initializing mariadb database…
 mkdir: cannot create directory '/bitnami/mariadb/data': Permission denied
 INFO  ==> Stopping mariadb…

Per similar question here, if you’re manually creating or reusing a PersistentVolume for MariaDB, you need to “chown -R 1001:1001 /pv-dir” on the PV directory, as the MariaDB container runs with userid 1001 and group 1001.

Proudly powered by WordPress