To GoodData homepage

Replies posted by IVèS

5 Replies

I
IVèSParticipating Frequently
asked in Administration

Fail to install GoodData in a Self-Hosted Kubernetes cluster

Hello all,My question has been marked as RESOLVED with the Robert Moucha answer but it is not solved at all.I’m still waiting for someone to help me.Could you please reopen this topic please?Thank you!

8
I
2 years ago
I
IVèSParticipating Frequently
asked in Administration

Fail to install GoodData in a Self-Hosted Kubernetes cluster

Hello Robert,Thank you for your help, it points out that my cluster is working well (following your advice):[root@k8s-master ~]# curl podinfo.internal.ives.fr{ "hostname": "podinfo-694f589bf6-w87k7", "version": "6.1.1", "revision": "", "color": "#34577c", "logo": "https://raw.githubusercontent.com/stefanprodan/podinfo/gh-pages/cuddle_clap.gif", "message": "greetings from podinfo v6.1.1", "goos": "linux", "goarch": "amd64", "runtime": "go1.17.8", "num_goroutine": "10", "num_cpu": "2"}[root@k8s-master ~]# curl podinfo.internal.ives.fr{ "hostname": "podinfo-694f589bf6-8lhkt", "version": "6.1.1", "revision": "", "color": "#34577c", "logo": "https://raw.githubusercontent.com/stefanprodan/podinfo/gh-pages/cuddle_clap.gif", "message": "greetings from podinfo v6.1.1", "goos": "linux", "goarch": "amd64", "runtime": "go1.17.8", "num_goroutine": "11", "num_cpu": "2"} 

8
I
2 years ago
I
IVèSParticipating Frequently
asked in Administration

Fail to install GoodData in a Self-Hosted Kubernetes cluster

To test my cluster:Verify that deployments work:[root@k8s-master ~]# kubectl run nginx --image=nginxpod/nginx created[root@k8s-master ~]# kubectl get pods -l run=nginxNAME READY STATUS RESTARTS AGEnginx 0/1 ContainerCreating 0 6s[root@k8s-master ~]# kubectl get pods -l run=nginxNAME READY STATUS RESTARTS AGEnginx 1/1 Running 0 15sVerify that remote access works via port forwarding.[root@k8s-master ~]# kubectl port-forward nginx 8081:80Forwarding from 127.0.0.1:8081 -> 80Forwarding from [::1]:8081 -> 80[... From a new terminal, `curl --head http://127.0.0.1:8081` ==> HTTP 200 ...]Handling connection for 8081Verify that you can access container logs with kubectl logs.[root@k8s-master ~]# kubectl logs nginx/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d//docker-entrypoint.sh: La

8
I
2 years ago
I
IVèSParticipating Frequently
asked in Administration

Fail to install GoodData in a Self-Hosted Kubernetes cluster

Still looking on my side, but just for information:[root@k8s-master ~]# helm install --namespace gooddata-cn --wait -f customized-values-gooddata-cn.yaml gooddata-cn gooddata/gooddata-cn --timeout 30m --debuginstall.go:178: [debug] Original chart version: ""install.go:199: [debug] CHART PATH: /root/.cache/helm/repository/gooddata-cn-1.7.0.tgzclient.go:128: [debug] creating 1 resource(s)install.go:151: [debug] CRD kopfpeerings.kopf.dev is already present. Skipping.client.go:128: [debug] creating 1 resource(s)install.go:151: [debug] CRD organizations.controllers.gooddata.com is already present. Skipping.W0329 10:19:37.631097 18516 warnings.go:70] batch/v1beta1 CronJob is deprecated in v1.21+, unavailable in v1.25+; use batch/v1 CronJobclient.go:299: [debug] Starting delete for "gooddata-cn-create-namespace" Jobclient.go:128: [debug] creating 1 resource(s)client.go:528: [debug] Watching for changes to Job gooddata-cn-create-namespace with timeout of 30m0sclient.go:556: [debug] Add/Modif

8
I
2 years ago
I
IVèSParticipating Frequently
asked in Administration

Fail to install GoodData in a Self-Hosted Kubernetes cluster

Hello :)My first issue is now solved by installing metallb.I understood that my organisation and the authentication have to be done when GDCN is installed, i’ll see these points later.I still have the issue when installing GDCN, I try to figure out why.

8
I
2 years ago
Welcome to the GoodData Community!Cookie settings