Closed Coolfeather2 closed 6 years ago
Looks like I’ll have to bring up a testing cluster and run through the setup again. I don’t see any recent changes in the Kubernetes API that would break these YAMLs... my current stable deployment is on v1.7.2 and it looks like the most recent version is v1.8.2. I tend to stay on one version for a while as the cluster upgrade procedure is still a crapshoot. Will try to spin it up this weekend.
I'll be happy to give you access to the gke project for testing - contact me at Coolfeather.o@gmail.com or discord: Nathan (Coolfeather2)#9831
okay, this is strange - set it up in a new project and it works fine o.O only difference is there is two clusters compared to one
Still happy to allow you to access the project that has the issue in it
Also instead of opening a new issue, how do I use it without the wordpress CMS - just wanted a LEMP stack
It's kind of purpose-built for WordPress. But if you have to take out the CMS then you could modify wp/wp-wd-Deployment.yaml
and remove the wp
container.
tried re-setting up k8s-lemp by following https://github.com/daxio/k8s-lemp/blob/master/USAGE.md exactly and resulting in this error on the nginx cluster/pod:
but the service exists: as well as the service account: