We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The Gitea Operator doesn't support cloning with SSH. Even if you can configure the SSH Settings, the container port will never be exposed
SSH is needed for Lab 6.3 Authentication
Possible solution is to use the Bitnam Gitea chart
helm repo add bitnami https://charts.bitnami.com/bitnami
helm upgrade -i gitea bitnami/gitea -f values.yaml
values.yalm
image: registry: docker.io repository: bitnami/gitea tag: 1.19.0-debian-11-r2 adminUsername: acend-admin adminPassword: "" adminEmail: [email protected] appName: gitea runMode: prod exposeSSH: true rootURL: <url> containerPorts: http: 3000 ssh: 2222 persistence: enabled: true accessModes: - ReadWriteOnce size: 4Gi podSecurityContext: enabled: false containerSecurityContext: enabled: false service: type: LoadBalancer ports: http: 80 ssh: 2222 ingress: enabled: true hostname: <url> annotations: kubernetes.io/tls-acme: "true" route.openshift.io/termination: edge #tls: true postgresql: enabled: true primary: podSecurityContext: enabled: false containerSecurityContext: enabled: false
And then create a DNS entry for ssh. which points to the external Load Balancer record
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The Gitea Operator doesn't support cloning with SSH.
Even if you can configure the SSH Settings, the container port will never be exposed
SSH is needed for Lab 6.3 Authentication
Possible solution is to use the Bitnam Gitea chart
helm repo add bitnami https://charts.bitnami.com/bitnami
helm upgrade -i gitea bitnami/gitea -f values.yaml
values.yalm
And then create a DNS entry for ssh. which points to the external Load Balancer record
The text was updated successfully, but these errors were encountered: