forgejo-next: try8.next.forgejo.org redirect #501

Closed
GhostPLACEHOLDER wants to merge 0 commits from refs/pull/67/headc5f2121903f2f5fd6e77de47e3715c935fc278eb into mainb7623d4bc2060d7314b1fa148acb2e859c9894df
First-time contributor
Closes infrastructure/k8s-cluster#66
Author
First-time contributor

Something along these lines? 9f200623a8..9730996fa1

Something along these lines? https://code.forgejo.org/infrastructure/k8s-cluster/compare/9f200623a8aa0c3b6469763579b728293e10491f..9730996fa1241232a17f90bbe1da30f0cc2b3abe
Author
First-time contributor

@viceice would that work? 🤔

I'm still fuzzy on what an Ingress is, I'll read more about it.

@viceice would that work? 🤔 I'm still fuzzy on what an Ingress is, I'll read more about it.
Author
First-time contributor

I got the fact that IngressRoute which normally reverse proxy to an existing service will rely on an internal service because all it needs to do is redirect somewhere else and not actually reverse proxy anything. In the same way the crawler blocker does.

    - match: Host(`try.next.forgejo.org`)
      kind: Rule
      priority: 1000
      services:
        - name: noop@internal
          kind: TraefikService
      middlewares:
        - name: forgejo-try-redirect
I got the fact that `IngressRoute` which normally reverse proxy to an existing service will rely on an internal service because all it needs to do is redirect somewhere else and not actually reverse proxy anything. In the same way the crawler blocker does. ```yaml - match: Host(`try.next.forgejo.org`) kind: Rule priority: 1000 services: - name: noop@internal kind: TraefikService middlewares: - name: forgejo-try-redirect ```
root closed this pull request 2025-05-29 20:27:18 +00:00
Some checks failed
build / lint (push) Has been cancelled
build / lint (pull_request) Has been cancelled

Pull request closed

Sign in to join this conversation.
No description provided.