Enable SSH clone #72
Labels
No Label
has
backport
in progress
invalid
kind
breaking
kind
bug
kind
build
kind
dependency
kind
deployment
kind
docs
kind
enhancement
kind
feature
kind
lint
kind
proposal
kind
question
kind
refactor
kind
security
kind
testing
kind
translation
kind
ui
need
backport
priority
critical
priority
low
priority
maybe
priority
medium
reviewed
duplicate
reviewed
invalid
reviewed
wontfix
skip-changelog
status
blocked
status
needs-feedback
status
needs-reviews
status
wip
upstream
gitea
upstream
other
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/helm-chart#72
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'm fairly new to kubernetes, but I'm not seeing an option to enable using git-over-SSH to clone/push/pull/etc. Am I missing something? Is it intentionally missing? If so, is there a way I can enable it?
I don't really understand. You can clone via https/ssh by default.
The only problem would be that your clone url won't be correct.
You can nodePort the ssh port. You can use ingress and a load balancer, there are many options.
Please see https://docs.gitea.io/en-us/config-cheat-sheet/ for configuration of SSH_PORT, SSH_DOMAIN and SSH_LISTEN_PORT.
You can configure those values in:
As I said, I'm new to Kubernetes. This is my
values.yaml
file, with sensitive information changed to[REDACTED]
. I haveingress-nginx
set up, and Gitea and Drone are both automatically available through it.With these settings, Gitea starts but is not accessible via SSH. If I enable any one of the commented-out SSH settings, the pod fails to start with status
CrashLoopBackOff
.The reason why I asked if SSH was enabled by default is because the helm ingress.yaml file seems to only reference HTTP and not SSH.
Is there any other direction you can give? I'm not sure if the issue lies in the Gitea configuration, the helm chart, or my own inexperience.
Yeah, ingress is not able to forward ssh ports. You'll need to use a load balancer.
I'm using metallb for this task. You'll need to add something like this to your ssh service in your gitea values:
Okay, I'm not sure what happened, but I had to
helm uninstall
andhelm install
again to get the change totype: LoadBalancer
to actually take. It created a new DigitalOcean load balancer different from the one used for HTTP(S), with a different IP, so I copied the port mappings over to the preexisting one and git seems to be working now. ?♂️I suppose this means that my issue is resolved, but maybe something can be added to the README to indicate that
type: LoadBalancer
is needed to access SSH externally?I will extend the readme in the next few days
#80 was merged including some hints for load balancers