google cloud platform - Kubernetes not claiming persistent volume - "failed due to PersistentVolumeClaim is not bound: "task-pv-claim", which is unexpected." -


i'm not sure why persistent volume not being claimed, or steps take further diagnose this?

should claim size match volume size? should volume size match gcp volume size?

this difficult test , figure out...

my goal here able create wordpress instance single replica long support rolling deployments....

output of kubectl pods:

name                         ready     status    restarts   age wordpress-1546832918-mz4rt   0/3       pending   0          47m wordpress-1546832918-p0s1s   0/3       pending   0          47m

output of kubectl describe pods:

...truncated... events:   firstseen lastseen    count              subobjectpath   type        reason          message   --------- --------    -----   ----            -------------   --------    ------          -------   47m       3s      168 default-scheduler       warning     failedscheduling    [schedulerpredicates failed due persistentvolumeclaim not bound: "task-pv-claim", unexpected., schedulerpredicates failed due persistentvolumeclaim not bound: "task-pv-claim", unexpected.]

output of kubectl pvc:

name            status    volume    capacity   accessmodes   storageclass   age task-pv-claim   pending                                      manual         4h

output of kubectl pv:

name      capacity   accessmodes   reclaimpolicy   status      claim     storageclass   reason    age pv0001    10gi       rwx           retain          available             manual                   4h

production.yaml

apiversion: extensions/v1beta1 kind: deployment metadata:   name: wordpress   labels:     app: wordpress spec:   replicas: 2   selector:     matchlabels:       app: wordpress   template:     metadata:       labels:         app: wordpress     spec:       terminationgraceperiodseconds: 30       containers:         - image: eu.gcr.io/abcxyz/wordpress:deploy-1502807720           name: wordpress           imagepullpolicy: "always"           env:             - name: wordpress_host               value: localhost             - name: wordpress_db_username               valuefrom:                 secretkeyref:                   name: cloudsql-db-credentials                   key: username           volumemounts:             - name: wordpress-persistent-storage               mountpath: /var/www/html         - image: eu.gcr.io/abcxyz/nginx:deploy-1502807720           name: nginx           imagepullpolicy: "always"           ports:             - containerport: 80               name: nginx           volumemounts:             - name: wordpress-persistent-storage               mountpath: /var/www/html               readonly: true         - image: gcr.io/cloudsql-docker/gce-proxy:1.09           name: cloudsql-proxy           command: ["/cloud_sql_proxy", "--dir=/cloudsql",                     "-instances=abcxyz:europe-west1:wordpressdb2=tcp:3306",                     "-credential_file=/secrets/cloudsql/credentials.json"]           volumemounts:             - name: cloudsql-instance-credentials               mountpath: /secrets/cloudsql               readonly: true             - name: ssl-certs               mountpath: /etc/ssl/certs             - name: cloudsql               mountpath: /cloudsql       volumes:         - name: wordpress-persistent-storage           persistentvolumeclaim:             claimname: "task-pv-claim"         - name: cloudsql-instance-credentials           secret:             secretname: cloudsql-instance-credentials         - name: ssl-certs           hostpath:             path: /etc/ssl/certs         - name: cloudsql           emptydir:

pvolume.yaml

apiversion: "v1" kind: "persistentvolume" metadata:   name: "pv0001"  spec:   storageclassname: manual   capacity:     storage: "10gi"    accessmodes:     - "readwritemany"   gcepersistentdisk:      fstype: "ext4"      pdname: "wordpress-disk"

pvolumeclaim.yaml

kind: persistentvolumeclaim apiversion: v1 metadata:   name: task-pv-claim spec:   storageclassname: manual   accessmodes:     - readwriteonce   resources:     requests:       storage: 3gi

the spec.accessmodes of persistent volume claim has match in persistent volume. try change both of them same value.

if didn't work, can add spec.selector definition persistent volume claim definition, updating match persistent volume metadata.labels this:

apiversion: "v1" kind: "persistentvolume" metadata:   name: "pv0001"    labels:     name: "pv0001" # can long matches selector in pvc spec:   ...  ---- kind: persistentvolumeclaim apiversion: v1 metadata:   name: task-pv-claim spec:   storageclassname: manual   accessmodes:     - readwriteonce   resources:     requests:       storage: 3gi   selector:     matchlabels:       name: "pv0001"

the spec.selector serves filter ensure pv specified labels matched.


Comments

Post a Comment

Popular posts from this blog

PHP and MySQL WP -

i trying accomplish 2 things here code. writing php directly wp page using insert php plugin. 1) query mysql database , return results 1 column 4 columns. 2) make each result own hyperlink directs user new wp page runs new query on page. i able query show results , turn results dynamic hyperlink, cannot formatting down. right returns result 1 column. here have: [insert_php] $servername = "localhost"; $username = "login"; //edited privacy $password = "password"; //edited privacy $database = "database"; //edited privacy // create connection $conn = new mysqli($servername, $username, $password, $database); // check connection if ($conn->connect_error) { die("connection failed: " . $conn->connect_error); } echo "connected successfully"; //get results database $result = mysqli_query($conn,"select mine mines order mine"); $all_property = array(); //declare array saving property //showing proper...
Read more

android - InAppBilling registering BroadcastReceiver in AndroidManifest -

i'm implementing inapp billing in android app. works well, however, i'm trying decouple broadcast receiver activity manifest. suggestion in android's trivialdrive sample: // important: dynamically register broadcast messages updated purchases. // register receiver here instead of <receiver> in manifest // because call getpurchases() @ startup, therefore can ignore // broadcasts sent while app isn't running. // note: registering listener in activity bad idea, done here // because sample. regardless, receiver must registered after // iabhelper setup, before first call getpurchases(). currently there's class extends broadcastreceiver : public class iabbroadcastreceiver extends broadcastreceiver { /** * intent action receiver should filter for. */ public static final string action = "com.android.vending.billing.purchases_updated"; private final iabbroadcastlistener mlistener; public iabbroadcastreceiver(iabbroadcastlistener listener) { m...
Read more

go - golang pprof for c library code -

i have been trying profile golang application pprof, seems details of c code(linked static library) missed in output result. flame graph from frame graph can see c code time consuming reported within "runtime._externalcode", no details @ all. , sure static library compiled debug enable. so there way make pprof details(like stack trace) of 3rd party c code? or there other golang profiling tool this?
Read more