kubernetes persistent volume ReadWriteOnly(RWO) does not work for nfs -


there,

according doc:

readwriteonce – volume can mounted read-write single node

i created pv based on nfs:

apiversion: v1 kind: persistentvolume metadata:   name: tspv01 spec:   capacity:     storage: 15gi   accessmodes:     - readwriteonce   persistentvolumereclaimpolicy: recycle   nfs:     path: /gpfs/fs01/shared/prod/democluster01/dashdb/gamestop/spv01     server: 169.55.11.79

a pvc pv:

kind: persistentvolumeclaim apiversion: v1 metadata:   name: sclaim spec:   accessmodes:     - readwriteonce   resources:     requests:       storage: 15gi

after create pvc bind pv:

root@hydra-cdsdev-dal09-0001:~/testscript# kubectl pvc name      status    volume    capacity   accessmodes   age sclaim    bound     tspv01    15gi       rwo           4m

then created 2 pods using same pvc:

pod1:

kind: pod apiversion: v1 metadata:   name: mypodshared1   labels:     name: frontendhttp spec:   containers:     - name: myfrontend       image: nginx       ports:         - containerport: 80           name: "http-server"       volumemounts:       - mountpath: "/usr/share/nginx/html"         name: mypd   volumes:     - name: mypd       persistentvolumeclaim:        claimname: sclaim

pod2:

kind: pod apiversion: v1 metadata:   name: mypodshared2   labels:     name: frontendhttp spec:   containers:     - name: myfrontend       image: nginx       ports:         - containerport: 80           name: "http-server"       volumemounts:       - mountpath: "/usr/share/nginx/html"         name: mypd   volumes:     - name: mypd       persistentvolumeclaim:        claimname: sclaim

after create 2 pods, assigned 2 different nodes. , can exec container, , can read&write in nfs mounted folder.

root@hydra-cdsdev-dal09-0001:~/testscript# kubectl pod -o wide name                        ready     status              restarts   age       ip            node mypodshared1                1/1       running             0          18s       172.17.52.7   169.45.189.108 mypodshared2                1/1       running             0          36s       172.17.83.9   169.45.189.116

anybody know why happened?

the accessmodes dependent upon storage provider. nfs don't different, hostpath should use modes correctly.

see following table various options: http://kubernetes.io/docs/user-guide/persistent-volumes/#access-modes


Comments

Post a Comment

Popular posts from this blog

aws api gateway - SerializationException in posting new Records via Dynamodb Proxy Service in API -

i getting "__type": "com.amazon.coral.service#serializationexception" as reply in postman & in test console in api gateway trying post record directly dynamodb using api proxy services.. referring aws article - https://aws.amazon.com/blogs/compute/using-amazon-api-gateway-as-a-proxy-for-dynamodb/ here's mapping { "tablename": "tablenamegoeshere", "item": { "id" : "$context.requestid" "eventname" : "$input.path('$.eventname')", "timestamp" : $input.path('$.timestamp'), "answers": "$util.parsejson($input.path('$.answers'))" } } update: did asked ... , worked if try add array of json objects gives me above same error - here's trying now. please - couldnt find on google well #set($inputroot = $input.path('$')) { "tablename": "answer", "item": {
Read more

asp.net - Problems sending emails from forum -

i have been redesigning site has message board, has been written guy looked after site. it has few problems , written in .asp , uses .mdb files database. you can see whole thing here . feel free post if helps, test thing have set using original files , new database. the basic problem when posts message, supposed email sent them, have posted it. when replies, originator supposed message, replier has been posted. i’d have thought @ point in process there should script/file in postmessage.asp? the postmessage.asp page below. <% option explicit %> <!-- #include virtual="common/adovbs.inc" --> <html> <head> <meta http-equiv="content-type" content="text/html; charset=windows-1252"> <meta name="generator" content="microsoft frontpage 4.0"> <meta name="progid" content="frontpage.editor.document"> <title>new page 2</title> <base target="_self"
Read more