-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add install instructions for various K8s vendors/distributions #33
Comments
Any particular word of advice for openshift? |
@adrianog Well these are the commands that you would need to run on openshift? Do you foresee that they would run as is on an openshift kubernetes cluster? kubectl create -f https://raw.githubusercontent.com/hasura/gitkube/master/manifests/gitkube-setup.yaml This command will create k8s objects in the $ kubectl --namespace kube-system expose deployment gitkubed --type=LoadBalancer --name=gitkubed This command will expose the deployment on a public IP. If you can do these 2 things, things should work for you. If you can try them out, please let us know if it works or doesn't and then we can add docs for how to on openshift! |
Trying to setup gitkube with minikube, but while creating the remote, I am getting this error: |
Sorted, It was Kubernetes version issue. |
@disha94 which version did you have the issue with and which issue fixed it for you? We have docs/minikube.md where we can mention this. |
@tirumaraiselvan So I think it was from my side, gitkube support is only after v1.8.7 of kubernetes and I had a older version (1.8.0) in my minikube. Upgrading the kubernetes version in minikube fixed the problem. |
In README
|
@sunfmin https://storage.googleapis.com/gitkube/gitkube-setup-stable.yaml was not publicly accessible. I have added the correct permissions. Can you try again? |
@arvi3411301 Yes it works. I tried gitkube successfully on my local Docker for desktop kubernetes. It works great. |
I am seeing these errors.. Error from server (BadRequest): error when creating "https://storage.googleapis.com/gitkube/gitkube-setup-stable.yaml": ClusterRoleBinding in version "v1" cannot be handled as a ClusterRoleBinding: no kind "ClusterRoleBinding" is registered for version "rbac.authorization.k8s.io/v1" unable to recognize "https://storage.googleapis.com/gitkube/gitkube-setup-stable.yaml": no matches for apiextensions.k8s.io/, Kind=CustomResourceDefinition |
@mandarku Could you please specify additional details like which Kubernetes version, which provider (if any), etc. You may want to open a new issue just for this. |
kubectl version I read above gitkube is supported 1.8 onwards? |
@mandarku Yes, as the error suggest your K8s version does not have the APIs like ClusterRoleBinding or CustomResourceDefinition (or have it in a different api group). Hence, gitkube works only 1.8+ |
Hi, I have executed both command
but even after that I get error when I do gitkube --version Error message: I am running Kubernetes on Amazon EKS Please let me what is wrong with my installation. Add output for get svc command I see gitkubed service through my get SVC command but when I run git clone command I get git: command not found error. |
Hello.
Let me know where I made mistake or just check it on microk8s. Regards |
Finally I solved the problem by updating file gitkube-setup-stable.yaml to new k8s api. Let's check my commit #121
Regards |
Hi @easyenglishcoding can you explain how to apply your solution? |
Gitkube runs on most Kubernetes distributions/vendors as per the install instructions in README. But in some cases, there may be more configuration required to correctly setup for e.g. exposing the gitkubed service may require configuring a Loadbalancer manually.
We need to document the instructions (docs/install.md) covering various vendors like GKE, Rancher, kops based installations, etc. In most cases, the instructions should be default instructions as provided in the README and in other cases the additional steps should be mentioned.
Please use this issue to mention any distribution which is not covered by the installation instructions.
The text was updated successfully, but these errors were encountered: