It's too hard
- Dominant language
- Go
- Stars
- 3.8k
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
I don't know how else to put it - setting up gitkube is way too hard, please make it easier.
In the install guide
```
kubectl create -f https://storage.googleapis.com/gitkube/gitkube-setup-stable.yaml
```
this yaml still causes errors, even though this seems to have been merged https://github.com/hasura/gitkube/commit/416c8d708be79df3f504279d2ab671f634565a5d
```
$ kubectl --namespace kube-system expose deployment gitkubed --type=LoadBalancer --name=gitkubed
```
LoadBalancers cost at least $10/month. Those who are using gitkube are probably looking for low-cost options. I recommend using ingress or nodeport here.
There are namespace concerns. Gitkub seems like a good candidate for using the kube-system namespace but sometimes apps need to live in different namespaces. Is that possible?
`gitkube.sh` doesn't mention a cli anywhere. If there is a cli, then why are all these manual steps required?
Contributor guide
Research direction
Start with the install guide, gitkube-setup-stable.yaml, and gitkube.sh, then reproduce the documented kubectl commands and their errors. Review the concerns about LoadBalancer cost, ingress or NodePort, namespace selection, and the CLI workflow. Done should mean a clearer, working installation path with the requested deployment and namespace options documented or supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, kubernetes
- Domain
- cli, devops, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100