search

fabric8io / gofabric8

CLI used when working with fabric8 running on Kubernetes or OpenShift
https://fabric8.io/
Apache License 2.0
147 stars 72 forks source link

installing fabric8 on kubernetes cluster #563

Open akshaysaxena16 opened 7 years ago

akshaysaxena16 commented 7 years ago

https://github.com/fabric8io/gofabric8

i was following this link to install fabric8 on kubernetes , but after running this command(gofabric8 deploy) i got this error. i was using google compute engine and also done the ingress rule for 80 and 443 port. if anyone can help

Waiting for External LoadBalancer IP Address for service nginx-ingress in namespace nginx-ingress. This may take a few minutes.If you are running your own ingress controller please run deploy again passing the --ingress=false flag

alexfons commented 7 years ago

I faced the same problem then I try gofabric8 deploy -y --ingress=false and get other error

Loading fabric8 releases from maven repository:https://repo1.maven.org/maven2/ Deploying package: platform version: 2.4.24

Cannot get platform template to deploy. error: error unmarshaling JSON: json: cannot unmarshal string into Go value of type v1.Template

have you already find a solution for this?

silently9527 commented 7 years ago

have you already find a solution for this? i also faced it! please tell me

robertjwozniak commented 7 years ago

Any solution for that? I'm having the same issue!

rawlingsj commented 7 years ago

could you try using the latest gofabric8 (currently 0.4.152) and 

gofabric8 deploy --legacy=true -y

please? I wonder if recent changes to support a new major fabric8 release have crept in and affected deploying the current version.

alexfons commented 7 years ago

Using
gofabric8 deploy --legacy=true -y it's deployed de cluster and the fabric8 services, I can chek them on the k8s dashboard, but I not able to access fabric8 dashboard, when I type gofabric8 console I got an URL that does not work and some erros

Opening URL http://fabric8.default.34.201.9.74.nip.io /usr/bin/xdg-open: 771: /usr/bin/xdg-open: www-browser: not found /usr/bin/xdg-open: 771: /usr/bin/xdg-open: links2: not found /usr/bin/xdg-open: 771: /usr/bin/xdg-open: elinks: not found /usr/bin/xdg-open: 771: /usr/bin/xdg-open: links: not found /usr/bin/xdg-open: 771: /usr/bin/xdg-open: lynx: not found /usr/bin/xdg-open: 771: /usr/bin/xdg-open: w3m: not found xdg-open: no method available for opening 'http://fabric8.default.34.201.9.74.nip.io'

when I try to access the URL I get

502 Bad Gateway nginx/1.11.4

alexfons commented 7 years ago

I was able to solve this by redeploing everything

kubectl delete deployment --all kubectl delete rc --all kubectl delete rs --all kubectl delete service -l provider=fabric8 kubectl delete secret -l provider=fabric8 kubectl delete ingress --all kubectl delete configmap --all kubectl delete sa --all kubectl delete deployment Ingress --namespace=fabric8-system

gofabric8 deploy --legacy=true --pv=false -y

alexfons commented 7 years ago

when I try to access the URL I get getting this erro again

502 Bad Gateway nginx/1.11.4

ivanknow commented 7 years ago

woooow man! this issues is happening to me too god save us

alexfons commented 7 years ago

I found some others guys facing this on https://github.com/fabric8io/fabric8/issues/6933

silently9527 commented 7 years ago

Hi, I am trying to setup fabric8 on a one node k8 cluster. Upon executing the command gofabric8 deploy --pv=false -y -d monkeyk.com --namespace=fabric8 the console hangs.

execute command gofabric8 validate

Validating your Kubernetes installation at https://192.168.8.201:6443 in namespace default

Service account...............................................................✘ serviceaccounts "fabric8" not found Console.......................................................................✘ deployments.extensions "fabric8" not found Jenkinshift Service...........................................................✘ services "jenkinshift" not found PersistentVolumeClaims........................................................✔ ConfigMaps....................................................................✔

[root@k8s-master ~]#kubectl get pods --all-namespaces

NAMESPACE NAME READY STATUS RESTARTS AGE fabric8-system ingress-nginx-3912307751-1hq78 1/1 Running 0 57m fabric8 configmapcontroller-3014251921-6nz5v 1/1 Running 0 1h fabric8 exposecontroller-2721663720-712pd 1/1 Running 0 57m fabric8 fabric8-3154273818-4fxk9 2/2 Running 0 57m fabric8 fabric8-docker-registry-2820431470-g4sgv 1/1 Running 0 1h fabric8 fabric8-forge-871551670-59wvt 1/1 Running 0 1h fabric8 gogs-3450696057-p00h6 1/1 Running 0 57m fabric8 jenkins-341579423-j9c4m 1/1 Running 0 1h fabric8 nexus-2305045875-b6q0t 1/1 Running 0 1h kube-system etcd-k8s-master 1/1 Running 0 1h kube-system kube-apiserver-k8s-master 1/1 Running 0 1h kube-system kube-controller-manager-k8s-master 1/1 Running 0 1h kube-system kube-dns-2425271678-v7tk9 3/3 Running 0 1h kube-system kube-flannel-ds-mj8gk 2/2 Running 2 1h kube-system kube-flannel-ds-smc6m 2/2 Running 0 1h kube-system kube-proxy-qw8lw 1/1 Running 0 1h kube-system kube-proxy-z094w 1/1 Running 0 1h kube-system kube-scheduler-k8s-master 1/1 Running 0 1h

And as per above output everything is working fine.

Would you please suggest where can be the problem?

max6cn commented 7 years ago

I am able to deploy on a single node Kubernetes cluster and have access to the dashboard. Bellow are some obvious bugs that have been fixed but still occurs to me:

Not working: Waiting for pipeline, almost same as fabric8io/fabric8-platform#78

agounaris commented 6 years ago

I face the same issues, permissions and dns problems on legacy and when I try the version 4...

NAME READY STATUS RESTARTS AGE auth-869b9cc55-jd587 0/1 Running 0 1m auth-db-6867ff9c97-zsr74 0/1 CrashLoopBackOff 5 4m che-starter-57b47f6b5f-m2wqn 1/1 Running 0 4m configmapcontroller-59b4c5566d-qsdch 1/1 Running 0 4m docker-registry-574854f68c-w5cxr 1/1 Running 0 4m exposecontroller-8b85857bd-jkp9d 1/1 Running 0 3m fabric8-69f98f5db8-rl5dd 0/1 Terminating 0 1m fabric8-75b4449c5c-zpjzk 1/1 Running 0 55s forge-65c4cb64cc-t2msn 1/1 Running 0 1m init-tenant-76c4cbcdc7-2zzc5 0/1 Running 1 59s init-tenant-db-5f4f746966-58j5c 0/1 CrashLoopBackOff 5 4m keycloak-7776dccc6d-whvqv 0/1 Terminating 0 3m keycloak-db-7868894fd-k867h 0/1 CrashLoopBackOff 4 4m wit-78cf9d974-b4vnk 0/1 Running 1 57s wit-7bd7658fdd-zdp62 0/1 Terminating 0 1m wit-db-784d5848cb-hw6pj 0/1 CrashLoopBackOff 2 57s

With all the errors related to

Warning Unhealthy 1s (x5 over 1m) kubelet, minikube Readiness probe failed: Get http://172.17.0.17:8089/api/status: dial tcp 172.17.0.17:8089: getsockopt: connection refused

alfie-far commented 6 years ago

I am trying to use the commands mentioned here to install fabric8 on my local kubernetes but I get a prompt saying: Waiting for External LoadBalancer IP Address for service nginx-ingress in namespace nginx-ingress. This may take a few minutes.If you are running your own ingress controller please run deploy again passing the --ingress=false flag.

and halts.

jaseemabid commented 6 years ago

@amin-RFarzin gofabric8 is abandoned. See https://github.com/fabric8io/gofabric8/issues/380#issuecomment-391269847

ctientcheu commented 6 years ago

Can we get support on this? I have been trying to deploy the fabric8 plaform on GKE now for the last 4 days and no matter the options on the deploy command I get the following errors

NAME READY STATUS RESTARTS AGE auth-65cf86bbb4-mgqt5 0/1 CrashLoopBackOff 7 9m auth-db-77cc7868cd-vmq75 0/1 CrashLoopBackOff 6 9m che-starter-56579b55d-s24xk 1/1 Running 0 9m configmapcontroller-6c4fc5568f-jl2dq 1/1 Running 0 9m docker-registry-56f8dc66db-hr749 1/1 Running 0 9m exposecontroller-564d8fcd55-tw6td 1/1 Running 0 9m fabric8-694998ddb8-hnds2 0/1 CrashLoopBackOff 6 9m forge-56fbbf9b7b-5xnwx 1/1 Running 0 9m init-tenant-75f4d89d6-c48qf 0/1 CrashLoopBackOff 7 9m init-tenant-db-8b7b5856c-tvvmv 0/1 CrashLoopBackOff 6 9m keycloak-84c6cc698b-glcm9 0/1 Running 4 9m keycloak-db-59b8b4f645-vr8th 0/1 CrashLoopBackOff 6 9m wit-7bb7888d88-vbd6l 0/1 Running 7 9m wit-db-6756b4ccf7-qr9tf 0/1 CrashLoopBackOff 6 9m

jaseemabid commented 6 years ago

@ctientcheu gofabric8 is an abandoned project. See my previous comment.

fcmfcm01 commented 6 years ago

if you are using kubernetes for deploy , try to add security context for "gogs" deployment , here are some code slice:

template:
    metadata:
      annotations:
        configmap.fabric8.io/update-on-change: gogs
        fabric8.io/git-branch: release-v2.2.311
        fabric8.io/git-commit: 2b9f7ce19493fe6d18392ac4f4be16f5e1a76fa3
        fabric8.io/iconUrl: https://cdn.rawgit.com/fabric8io/fabric8-devops/master/gogs/src/main/fabric8/icon.png
        fabric8.io/metrics-path: dashboard/file/kubernetes-pods.json/?var-project=gogs&var-version=2.2.311
      creationTimestamp: null
      labels:
        group: io.fabric8.devops.apps
        project: gogs
        provider: fabric8
        version: 2.2.311
    spec:
      securityContext:
        runAsUser: 1000
        fsGroup: 2000
      containers:
      - env:
        - name: GOGS_SERVER__ROOT_URL