forgejo-helm/forgejo-helm

Watch

Fork 24

Allow to deploy SSH Key for signing #1343

New issue

Open

opened 2025-08-19 04:15:10 +00:00 by dvonessen · 1 comment

dvonessen commented

2025-08-19 04:15:10 +00:00

Hello,

first of all, thank you for this helm chart. It helps me alot to deploy forgejo to my k8s cluster.

Since Forgejo 12 is able to use SSH keys to sign commits it would be good to allow deploy one.
I think it could be the "same" as the GPG deployment for singing.

Regards
Daniel

Hello, first of all, thank you for this helm chart. It helps me alot to deploy forgejo to my k8s cluster. Since Forgejo 12 is able to use SSH keys to sign commits it would be good to allow deploy one. I think it could be the "same" as the GPG deployment for singing. Regards Daniel

👍 5

viceice added the

labels

2025-08-19 05:05:24 +00:00

PaarthShah referenced this issue from a commit

2026-02-28 09:54:27 +00:00

feat(signing): add SSH key signing support

PaarthShah referenced this issue

2026-02-28 10:16:32 +00:00

feat: support ssh key for signing #1489

PaarthShah referenced this issue from a commit

2026-03-02 08:25:40 +00:00

feat(signing): add SSH key signing support

PaarthShah referenced this issue from a commit

2026-03-14 08:06:02 +00:00

feat(signing): add SSH key signing support

sujiba commented

2026-04-20 08:49:37 +00:00

Hi,

thanks for implementing SSH key signing support with v17. For anyone interested in how to deploy it:

values.yaml

...
signing:
  enabled: true
  ssh:
    existingSecret: 'forgejo-ssh-signing-secret'

gitea:
  config:
    repository.signing:
      FORMAT: ssh
      SIGNING_KEY: /data/git/.ssh-signing/key.pub
      SIGNING_NAME: "MY Instance"
      SIGNING_EMAIL: noreply@domain.tld
      INITIAL_COMMIT: pubkey
      DEFAULT_TRUST_MODEL: pubkey
      CRUD_ACTIONS: pubkey
      MERGES: pubkey
...

secrets.sops.yaml

---
apiVersion: v1
kind: Secret
metadata:
    name: forgejo-ssh-signing-secret
    namespace: development
stringData:
    privateKey: |
        -----BEGIN OPENSSH PRIVATE KEY-----
        adkoadijoqwidwjidw
        -----END OPENSSH PRIVATE KEY-----

The public key is automatically generated during startup. You can find both keys under /data/git/.ssh-signing/.

Hi, thanks for implementing SSH key signing support with v17. For anyone interested in how to deploy it: <details><summary>values.yaml</summary> ```yaml ... signing: enabled: true ssh: existingSecret: 'forgejo-ssh-signing-secret' gitea: config: repository.signing: FORMAT: ssh SIGNING_KEY: /data/git/.ssh-signing/key.pub SIGNING_NAME: "MY Instance" SIGNING_EMAIL: noreply@domain.tld INITIAL_COMMIT: pubkey DEFAULT_TRUST_MODEL: pubkey CRUD_ACTIONS: pubkey MERGES: pubkey ... ``` </details> <details><summary>secrets.sops.yaml</summary> ```yaml --- apiVersion: v1 kind: Secret metadata: name: forgejo-ssh-signing-secret namespace: development stringData: privateKey: | -----BEGIN OPENSSH PRIVATE KEY----- adkoadijoqwidwjidw -----END OPENSSH PRIVATE KEY----- ``` </details> The public key is automatically generated during startup. You can find both keys under `/data/git/.ssh-signing/`.

👍 1

No milestone

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

forgejo-helm/forgejo-helm#1343

No description provided.

Rows
Columns