1. ホーム
  2. 質問と答え
  3. SuiteCRM Minikube/K8sにインストール

SuiteCRM Minikube/K8sにインストール

2017-11-01 12 views
2

私はsuiteCRMの新しいです。私はMinikubeに展開しようとしています。私はK8Sレポで舵チャートを使用しています：SuiteCRM Minikube/K8sにインストール

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

私はコマンドを使用しています：

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

私はいくつかのカスタム値（例えば、電子メール、ユーザ名を持つようにvalues.yamlを変更し、パスワード）。私は非常に有用なエラーを得ていないのに、インストールは成功しません。私は解決可能なホストを持っていないということについて間違いを犯しますが、私は代理することを望んでいました。

[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

+0

こんにちは、あなたのvalues.ymlファイルを共有できますか？ –

+0

@JavierSalmeron - 問題ありません。元の投稿に追加し、PIIデータを削除しました。 – mornindew

答えて

1

私は決してヘルムチャートを得られませんでしたが、私は回避策を見つけました。伝統的なkubctrlを介してインストールするとうまくいきました。私は問題が正しくsuitecrmホストを設定していないとしなければならないと思います

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

出典

2017-11-02 04:09:43 mornindew

1

：私は、ここに提供される方法を使用していました。 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

関連する問題

 関連する問題