Thank you for your post!! it kicked me in the right direction for making a similar setup.
I've run in a few challenges:
You are missing the storage class name in the Volume Claim description.
Also, the volume claim got stuck in a weird "pending" loop. I tracked the error was specifying the volume name. (last line on the volume claim)
I did not use the cloudsql proxy since I have my cloud sql instances with private internal IP so wordpress can use the ip directly.
There's one thing I could not fix yet... Wordpress can't write the wp-content mounted folder, I know it must be a permissions problem. The fix could be to extend the default wordpress docker image and run a chown there, but I thought I would ask you, maybe you have a clever idea!!
Thanks again!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hello!
Thank you for your post!! it kicked me in the right direction for making a similar setup.
I've run in a few challenges:
You are missing the storage class name in the Volume Claim description.
Also, the volume claim got stuck in a weird "pending" loop. I tracked the error was specifying the volume name. (last line on the volume claim)
I did not use the cloudsql proxy since I have my cloud sql instances with private internal IP so wordpress can use the ip directly.
There's one thing I could not fix yet... Wordpress can't write the wp-content mounted folder, I know it must be a permissions problem. The fix could be to extend the default wordpress docker image and run a chown there, but I thought I would ask you, maybe you have a clever idea!!
Thanks again!