RedHatOfficial / openemr-kube

OpenShift/Kube deployment info for OpenEMR (https://www.open-emr.org/)
11 stars 13 forks source link

MySQL deployment error in Openshift.com free-tier #29

Open ryannix123 opened 4 years ago

ryannix123 commented 4 years ago

Hi!

I'm trying to deploy OpenEMR-Kube in the free-tier at OpenShift.com but I ran into some errors. I was able to deploy on OKD 3.11 just fine, but I'm sure Openshift.com is probably newer.

The first error had to do with the size of the deployment: Error from server (Forbidden): error when creating "artifacts/mysql/databasevolume-persistentvolumeclaim.yaml": persistentvolumeclaims "databasevolume" is forbidden: minimum storage usage per PersistentVolumeClaim is 1Gi, but request is 100Mi

I did correct the YAML file and increased the size, but now I'm receiving this error which is a little more cryptic:

error: unable to recognize "artifacts/mysql/deployment.yaml": no matches for kind "Deployment" in version "extensions/v1beta1"

jeffcpullen commented 4 years ago

This appears to be two issues and the first one is closed with your #31 PR.

I'm assuming the second issue is still open, right @ryannix123 ?

TheCranston commented 3 years ago

Has there been any progress on the second issue: error: unable to recognize "artifacts/mysql/deployment.yaml": no matches for kind "Deployment" in version "extensions/v1beta1" I'm getting the same thing on a rancher based cluster running the install like kubectl apply -f artifacts/mysql/

TheCranston commented 3 years ago

I did some googling and arrived at this solution:

diff --git a/artifacts/mysql/deployment.yaml b/artifacts/mysql/deployment.yaml index 53b86e4..7106257 100644 --- a/artifacts/mysql/deployment.yaml +++ b/artifacts/mysql/deployment.yaml @@ -1,4 +1,4 @@ -apiVersion: extensions/v1beta1 +apiVersion: apps/v1 kind: Deployment metadata: annotations: @@ -10,6 +10,9 @@ metadata: name: mysql spec: replicas: 1 + selector: + matchLabels: + io.kompose.service: mysql strategy: type: Recreate template:

kubectl applies the yaml files now. still not working, but at least the database is setup and running.

ryannix123 commented 3 years ago

@TheCranston @jeffcpullen I actually work for Red Hat now, so I'll pick this project back up once I get a 4.7 cluster going.