kubernetes-pvc

问题 I'm creating a Kubernetes PVC and a Deploy that uses it. In the yaml it is specified that uid and gid must be 1000. But when deployed the volume is mounted with different IDs so I have no write access on it. How can I specify effectively uid and gid for a PVC? PVC yaml: --- apiVersion: v1 kind: PersistentVolumeClaim metadata: name: jmdlcbdata annotations: pv.beta.kubernetes.io/gid: "1000" volume.beta.kubernetes.io/mount-options: "uid=1000,gid=1000" volume.beta.kubernetes.io/storage-class:

问题 I have a DaemonSet that creates flink task manager pods, one per each node. Nodes Say I have two nodes node-A node-B Pods the daemonSet would create pod-A on node-A pod-B on node-B Persistent Volume Claim I am on AKS and want to use azure-disk for Persistent Storage According to the docs : [https://docs.microsoft.com/en-us/azure/aks/azure-disks-dynamic-pv ] an azure disk can be associated on to single node say I create pvc-A for pv-A attached to node-A pvc-B for pv-B attached to node-B

问题 I have a DaemonSet that creates flink task manager pods, one per each node. Nodes Say I have two nodes node-A node-B Pods the daemonSet would create pod-A on node-A pod-B on node-B Persistent Volume Claim I am on AKS and want to use azure-disk for Persistent Storage According to the docs : [https://docs.microsoft.com/en-us/azure/aks/azure-disks-dynamic-pv ] an azure disk can be associated on to single node say I create pvc-A for pv-A attached to node-A pvc-B for pv-B attached to node-B

问题 Situation: - users A, B, C, D - team 1: user A, user B - team 2: user C, user D Desired: - each user has private volume - each team has a shared volume --> users in team can see shared volume - some users, based on permission, can see both shared volumes Searched for quite some time now, do not see a solution in the Docs. Ideas: - Use Namespaces! problem --> can no longer see shared volume of other Namespace 回答1: This is an example of how you would do it. You can use namespaces for the