openshift-evangelists / wordpress-quickstart Goto Github PK

Standard deployment on OCP 3.7. Screenshot attached

Hello, small and maybe silly question:

How one does to give an external IP to the wordpress?
I saw the openshift documentation about editing the master-config.yaml but I'm a bit lost. For this wordpress project, where is the master-config.yaml in question? Is it the right way to do it?

My goal is simply to add a A record in my DNS provider to access the wordpress website.

This is my first try on openshift, so my question maybe stupid and I'm sorry about this.
Thanks,
Dex

Cannot start container, even after removing the healthiness check.

Events:
FirstSeen LastSeen Count From SubObjectPath Type Reason Message

3m 3m 1 default-scheduler Normal Scheduled Successfully assigned my-wordpress-site-3-6kljt to ip-10-0-89-180.ap-southeast-2.compute.internal
3m 3m 1 kubelet, ip-10-0-89-180.ap-southeast-2.compute.internal Normal SuccessfulMountVolume MountVolume.SetUp succeeded for volume "default-token-lqbqx"
1m 1m 1 kubelet, ip-10-0-89-180.ap-southeast-2.compute.internal Warning FailedMount Unable to mount volumes for pod "my-wordpress-site-3-6kljt_proj1(1d71e155-2ceb-11e8-ba54-0a147b740ca6)": timeout expired waiting for volumes to attach/mount for pod "proj1"/"my-wordpress-site-3-6kljt". list of unattached/unmounted volumes=[data]

What is structure of source repository?

what's the recommended upgrade procedure, for deploying next wp releases? performing the upgrade within wordpress, then updating the repository branch pointer?

OpenShift version 4.5.11:

Error 1:

Error "Error resolving ImageStreamTag php:7.0 in namespace openshift: unable to find latest tagged image" for field "from".

Error 2:

Generated from buildconfig-controller
26 times in the last 7 minutes
error instantiating Build from BuildConfig wordpress/my-wordpress-site2 (0): Error resolving ImageStreamTag php:7.0 in
namespace openshift: unable to find latest tagged image

Any idea how to fix it?

The deployment container is unable to unpack wordpress in /opt/app-root/src given it's owned by root and not default. The logs are spammed with this sort of thing:

tar: wp-includes/js/tinymce/plugins/textcolor/plugin.js: Cannot open: No such file or directory
tar: wp-includes: Cannot mkdir: Permission denied

This causes the deployment to fail since wordpress never becomes available.

I havent dug deeper into the why, but with the readyness probe enabled I was not able to deploy the app container (db worked fine)
Then I removed the readyness probe and deployment went through