shadowsocks / shadowsocks/shadowsocks-rust

shadowsocks on kubernetes with traefik ingress

Open
#1,067 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
10.9k
Forks
1.5k
Avg merge
4d 15h
Merged PRs (30d)
5

Description

Hello,

So I deployed shadowsocks-rust on kubernetes thanks to the manifest (big up to @realies).

First, let's start with what is working:

  • Using local port forward kubectl port-forward pod/shadowsocks-rust-6ff96bd5dc-qnppw 8388:8388

And then routing my traffic to 127.0.0.1:8388 works!

However, when trying to connect using a domain name pointing to my Traefik ingress, it doesn't work.

Here is my ingress definition:

apiVersion: traefik.containo.us/v1alpha1
kind: IngressRouteTCP
metadata:
  name: shadowsocks-rust
spec:
  entryPoints:
    - websecure
  routes:
    - kind: Rule
      match: HostSNI(`*`)
      services:
        - name: shadowsocks-rust
          port: 8388   <--- I use 8388 instead of the default 80 
  tls:
    certResolver: le

And websecure refers to this Traefik conf:

--entrypoints.websecure.address=:8443/tcp

Any idea on how to tell traefik to correctly route my sslocal traffic to shadowsocks-rust running in k8s, directly? (without having to kubectl port-forward)

Thanks a lot!
Screenshot from 2022-12-22 13-14-19

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the k8s manifest linked in the issue and compare its service configuration with the Traefik IngressRouteTCP definition and websecure entrypoint. Reproduce the working kubectl port-forward path, then test the domain route. Done means shadowsocks-rust traffic works through the Traefik endpoint without port forwarding, with the required configuration documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, rust
Domain
infrastructure, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.