SuiteCRM Minikube/K8에 설치

나는 suiteCRM에 새로운 것이므로 Minikube에 배포하려고합니다. 나는 K8S의 REPO에 지배 차트를 사용하고 있습니다 :SuiteCRM Minikube/K8에 설치

https://github.com/kubernetes/charts/tree/master/stable/suitecrm

나는 명령을 사용하고 있습니다 : (나는 일부 사용자 지정 값을 가지도록 values.yaml 수정 예를 들어 이메일, 사용자 이름을

helm install --name red-falcon-crm -f values.yaml stable/suitecrm

을, 암호). 매우 유용한 오류가 발생하지 않아도 설치가 성공적이지 않습니다. 해결할 수있는 호스트가 없다는 오류가 있지만 프록시를 사용하고 싶습니다.

[email protected]:~/redfalcon/gitlab/platform-setup/modules/suitecrm$ helm install --name red-falcon-crm -f values.yaml stable/suitecrm 
NAME: red-falcon-crm 
LAST DEPLOYED: Tue Oct 31 19:13:03 2017 
NAMESPACE: default 
STATUS: DEPLOYED 

RESOURCES: 
==> v1/Pod(related) 
NAME          READY STATUS    RESTARTS AGE 
red-falcon-crm-mariadb-7fb6774f5c-b5w7t 0/1 ContainerCreating 0   0s 

==> v1/Secret 
NAME      TYPE DATA AGE 
red-falcon-crm-mariadb Opaque 2  1s 
red-falcon-crm-suitecrm Opaque 2  1s 

==> v1/ConfigMap 
NAME     DATA AGE 
red-falcon-crm-mariadb 1  1s 

==> v1/PersistentVolumeClaim 
NAME        STATUS VOLUME         CAPACITY ACCESS MODES STORAGECLASS AGE 
red-falcon-crm-mariadb   Bound pvc-cf72d52d-bea1-11e7-b8a4-080027c951c6 8Gi  RWO   standard  1s 
red-falcon-crm-suitecrm-apache Pending standard         1s 
red-falcon-crm-suitecrm-suitecrm Pending standard         1s 

==> v1/Service 
NAME      TYPE   CLUSTER-IP EXTERNAL-IP PORT(S)      AGE 
red-falcon-crm-mariadb ClusterIP  10.0.0.104 <none>  3306/TCP     1s 
red-falcon-crm-suitecrm LoadBalancer 10.0.0.89 <pending> 80:32750/TCP,443:31973/TCP 1s 

==> v1beta1/Deployment 
NAME     DESIRED CURRENT UP-TO-DATE AVAILABLE AGE 
red-falcon-crm-mariadb 1  1  1   0   1s 


NOTES: 
############################################################################### 
### ERROR: You did not provide an external host in your 'helm install' call ### 
############################################################################### 

This deployment will be incomplete until you configure SuiteCRM with a resolvable 
host. To configure SuiteCRM with the URL of your service: 

1. Get the SuiteCRM URL by running: 

    NOTE: It may take a few minutes for the LoadBalancer IP to be available. 
     Watch the status with: 'kubectl get svc --namespace default -w red-falcon-crm-suitecrm' 

    export APP_HOST=$(kubectl get svc --namespace default red-falcon-crm-suitecrm --template "{{ range (index .status.loadBalancer.ingress 0) }}{{.}}{{ end }}") 
    export APP_PASSWORD=$(kubectl get secret --namespace default red-falcon-crm-suitecrm -o jsonpath="{.data.suitecrm-password}" | base64 --decode) 
    export APP_DATABASE_PASSWORD=$(kubectl get secret --namespace default red-falcon-crm-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 --decode) 

2. Complete your SuiteCRM deployment by running: 

    helm upgrade red-falcon-crm \ 
    --set suitecrmHost=$APP_HOST,suitecrmPassword=$APP_PASSWORD,mariadb.mariadbRootPassword=$APP_DATABASE_PASSWORD stable/suitecrm 

[email protected]:~/redfalcon/gitlab/platform-setup/modules/suitecrm$ kubectl get svc --namespace default -w red-falcon-crm-suitecrm 
NAME      TYPE   CLUSTER-IP EXTERNAL-IP PORT(S)      AGE 
red-falcon-crm-suitecrm LoadBalancer 10.0.0.89 <pending>  80:32750/TCP,443:31973/TCP 3m 
^[email protected]:~/redfalcon/gitlab/platform-setup/modules/suitecrm$ minikube service red-falcon-crm-suitecrm 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet... 
Waiting, endpoint for service is not ready yet...

내 Values.yaml :

## Bitnami SuiteCRM image version 
## ref: https://hub.docker.com/r/bitnami/suitecrm/tags/ 
## 
image: bitnami/suitecrm:7.9.7-r0 

## Specify a imagePullPolicy 
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images 
## 
imagePullPolicy: IfNotPresent 

## SuiteCRM host to create application URLs 
## ref: https://github.com/bitnami/bitnami-docker-suitecrm#configuration 
## 
# suitecrmHost: 

## loadBalancerIP for the SuiteCRM Service (optional, cloud specific) 
## ref: http://kubernetes.io/docs/user-guide/services/#type-loadbalancer 
## 
# suitecrmLoadBalancerIP: 

## User of the application 
## ref: https://github.com/bitnami/bitnami-docker-suitecrm#configuration 
## 
suitecrmUsername: craig 

## Application password 
## Defaults to a random 10-character alphanumeric string if not set 
## ref: https://github.com/bitnami/bitnami-docker-suitecrm#configuration 
## 
suitecrmPassword: <hadmypasswordhere> 

## Admin email 
## ref: https://github.com/bitnami/bitnami-docker-suitecrm#configuration 
## 
suitecrmEmail: <hadmyemail>@gmail.com 

## Lastname 
## ref: https://github.com/bitnami/bitnami-docker-suitecrm#configuration 
## 
suitecrmLastName: <hadmylastname> 

## SMTP mail delivery configuration 
## ref: https://github.com/bitnami/bitnami-docker-suitecrm/#smtp-configuration 
## 
# suitecrmSmtpHost: 
# suitecrmSmtpPort: 
# suitecrmSmtpUser: 
# suitecrmSmtpPassword: 
# suitecrmSmtpProtocol: 

## 
## MariaDB chart configuration 
## 
mariadb: 
    ## MariaDB admin password 
    ## ref: https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#setting-the-root-password-on-first-run 
    ## 
    mariadbRootPassword: <hadMyPasswordHere> 

    ## Enable persistence using Persistent Volume Claims 
    ## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/ 
    ## 
    persistence: 
    enabled: true 
    ## mariadb data Persistent Volume Storage Class 
    ## If defined, storageClassName: <storageClass> 
    ## If set to "-", storageClassName: "", which disables dynamic provisioning 
    ## If undefined (the default) or set to null, no storageClassName spec is 
    ## set, choosing the default provisioner. (gp2 on AWS, standard on 
    ## GKE, AWS & OpenStack) 
    ## 
    # storageClass: "-" 
    accessMode: ReadWriteOnce 
    size: 8Gi 

## Kubernetes configuration 
## For minikube, set this to NodePort, elsewhere use LoadBalancer 
## 
serviceType: LoadBalancer 

## Enable persistence using Persistent Volume Claims 
## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/ 
## 
persistence: 
    enabled: true 
    apache: 
    ## apache data Persistent Volume Storage Class 
    ## If defined, storageClassName: <storageClass> 
    ## If set to "-", storageClassName: "", which disables dynamic provisioning 
    ## If undefined (the default) or set to null, no storageClassName spec is 
    ## set, choosing the default provisioner. (gp2 on AWS, standard on 
    ## GKE, AWS & OpenStack) 
    ## 
    # storageClass: "-" 
    accessMode: ReadWriteOnce 
    size: 1Gi 
    suitecrm: 
    ## suitecrm data Persistent Volume Storage Class 
    ## If defined, storageClassName: <storageClass> 
    ## If set to "-", storageClassName: "", which disables dynamic provisioning 
    ## If undefined (the default) or set to null, no storageClassName spec is 
    ## set, choosing the default provisioner. (gp2 on AWS, standard on 
    ## GKE, AWS & OpenStack) 
    ## 
    # storageClass: "-" 
    accessMode: ReadWriteOnce 
    size: 8Gi 

## Configure resource requests and limits 
## ref: http://kubernetes.io/docs/user-guide/compute-resources/ 
## 
resources: {} 
    # requests: 
    # memory: 512Mi 
    # cpu: 300m

내가 (minikube 대시 보드를 통해) 실행중인 서비스의 로그를 볼 않았다. 실제로 많이 사용하지는 않지만 CRM 환경 준비에 매달리는 것 같습니다. 그것은 결코 그것을 넘어서는 것이 아닙니다. ...

 nami INFO Initializing apache 
apache INFO ==> Patching httpoxy... 
nami INFO apache successfully initialized 
nami INFO Initializing php 
nami INFO php successfully initialized 
nami INFO Initializing suitecrm 
suitecr INFO Preparing webserver environment... 
suitecr INFO Preparing PHP environment... 
suitecr INFO Preparing suitecrm environment...

서비스 끝점은 절대로 준비가되지 않았으며 배포를 완료 한 것으로 보이지 않습니다. 어떤 도움을 주시면 감사하겠습니다.

출처

2017-11-01 mornindew

안녕하세요, 사용자의 values.yml 파일을 공유 할 수 있습니까? –

@JavierSalmeron - 문제 없음. 원래 게시물에 추가하고 PII 데이터를 제거했습니다. – mornindew

작업 할 차트를 얻지 못했지만 해결 방법을 찾았습니다. 전통적인 kubctrl을 통해 설치하면 정상적으로 작동합니다. 나는 문제가 올바르게 suitecrm 호스트를 설정하지 않는과 관련이있다 생각

https://github.com/bitnami/bitnami-docker-suitecrm

출처

2017-11-02 04:09:43 mornindew

: 여기에서 제공하는 방법을 사용했다. LoadBalancer를 사용하도록 구성되었지만 minikube를 사용할 때 helm이 표시하는 명령과 다른 명령으로 APP_HOST 변수를 수동으로 설정해야합니다. 이것이 내가 작동하게 한 것입니다.

helm install --name red-falcon-crm -f values.yaml stable/suitecrm 
export APP_HOST=$(minikube ip):$(kubectl get svc red-falcon-crm-suitecrm --template "{{ (index .spec.ports 0).nodePort }}") 
helm upgrade red-falcon-crm --set suitecrmHost=$APP_HOST -f values.yaml stable/suitecrm

출처

2017-11-15 11:06:58

답변

관련 문제