pvc | Python vSphere Client with a dialog interface

with the hope that due to the Retain policy, the new pods (i.e. their PVCs would bind to the existing PVs (and data wouldn't get lost)

It is explicitly written in the documentation that this is not what happens. the PVs are not available for another PVC after delete of a PVC.

the PersistentVolume still exists and the volume is considered "released". But it is not yet available for another claim because the previous claimant's data remains on the volume.

Kubernetes 1.20 stopped propagating selfLink.
There is a workaround available, but it does not always work.

After the lines

You can do it like this: First Loop over your JSON object

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.

Solved by manually creating PVC and PV specifying existing EFS directory, storage class, nfs endpoint

Right - the admin console is listening on 127.0.0.1. This is not the outside world interface. This is "localhost".

You have two choices here. You can start Keycloak with a command line argument like:

the issue is that you are using the node affinity while creating the PV.

Which think something like you say inform to Kubernetes my disk will attach to this type of node. Due to affinity your disk or PV is attached to one type of specific node only.

when you are deploying the workload or deployment (POD) it's not getting schedule on that specific node and your POD is not getting that PV or PVC.

to resolve this issue

make sure both POD and PVC schedule at same node add the node affinity to deployment also so POD schedule on that node.

or else

Remove the node affinity rule from PV and create a new PV and PVC and use it.

here is the place where you have mentioned the node affinity rule

For the ELK stack to work you need all three PersistentVolumeClaim's to be bound as I recall. Instead of creating 1 30 GB of PV create 3 of the same size with the claims and then re-install. Other nodes have unmet dependincies.

Also please do not handle the volumes by hand. There are guidelines to deploy dynamic volums. Use OpenEBS for example. That way you wont need to worry about the pvc's. After giving the pv's if anything happens write again with your cluster installation process.

I was wrong obviously, in this particular problem, filesystems and cgroups take role and the main problem of this is an old problem. From 5.2.1 to 8.0.0. Reinstall the chart by pulling the chart. Edit values file and definitely change the container version. It should be fine or create another error log stack.

NFS turns on root_squash mode by default which functionally disables uid 0 on clients as a superuser (maps those requests to some other UID/GID, usually 65534). You can disable this in your mount options, or use something other than NFS. I would recommend the latter, NFS is bad.