Episode 05 nfs server client provioner is deprecated about kubernetes-101 HOT 5 OPEN

Just a note for anyone doing this in August 2022 -

The resolution/workaround listed by @Kiollpt in Issue 30 is valid for kubernetes 1.24. Note the change of IPAddress required for set nfs.server=x.x.x.x

$ helm repo add nfs-subdir-external-provisioner https://kubernetes-sigs.github.io/nfs-subdir-external-provisioner/
$ helm install nfs-subdir-external-provisioner nfs-subdir-external-provisioner/nfs-subdir-external-provisioner \
    --set nfs.server=x.x.x.x \
    --set nfs.path=/exported/path

from kubernetes-101.

But this will render the video outdated?

Yeah, that's the nature of video content.

Luckily, this change can be made in here, and also I'll make sure to change it in the book too—and that way people can still get to the right directions here and in the book content after they try the video example and see it fail :D

from kubernetes-101.

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

from kubernetes-101.

This issue is no longer marked for closure.

from kubernetes-101.

Hello,

I follow a Linode's article to set up a Rook NFS solution at chapter 5 and I was able to deploy Drupal with three replicas.

In drupal.yml, I used:

storageClassName: rook-nfs-share1

Looks like rook-nfs-share1 was deployed using sc.yml

from kubernetes-101.