[BUG] K3S 1.21.3-k3s1 - Issue with pods accessing PVCs

[stephenpope]

(Im not sure if this is an issue with K3D or an issue with the new K3S version or both of them together but I thought I'd start here ..)

What did you do

k3d cluster create -i rancher/k3s:v1.21.3-k3s1 --k3s-server-arg '--disable=traefik' --k3s-server-arg '--disable=metrics-server'
helm repo add elastic https://helm.elastic.co
helm upgrade --install elastic/elasticsearch elastic

{"type": "server", "timestamp": "2021-08-09T13:28:11,343Z", "level": "ERROR", "component": "o.e.b.ElasticsearchUncaughtExceptionHandler", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-0", "message": "uncaught exception in thread [main]", 
"stacktrace": ["org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: Unable to access 'path.data' (/usr/share/elasticsearch/data)",

What did you expect to happen

The PVCs created as part of the Helm deployment do not have the correct permissions so the pods cannot access the data on them.

I have also tried this with other charts (e.g Redis / Neo4J / RabbitMQ etc .. anything that creates PVCs) so this is nothing to do with ElastiSearch directly .. it was just one of the broken parts of our deployment.

Switching to k3s:v1.21.2-k3s1 everything is fine and behaves as it should. Is this a regression in K3S ?

Screenshots or terminal output

(See above)

Which OS & Architecture

• MacOS

Which version of k3d

• k3d version v4.4.7

Which version of docker

• Server: Docker Engine - Community
  Engine:
  Version: 20.10.7

[ChristianCiach]

This is a known bug in K3s which will be fixed in the next release. k3s-io/k3s#3704

[iwilltry42]

Hi @stephenpope , thanks for opening this issue! As @ChristianCiach pointed out (thank you!), this is a problem with k3s, which we cannot influence in k3d.
Due to this, I'll go ahead and close this issue here. Feel free to reopen if you think we can do something from our side 👍

[stephenpope]

np .. I was going to close when the next 1.21 version was out of the door, but feel free to close :)