Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions base/transmission/service.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3,10 +3,19 @@ kind: Service
metadata:
name: transmission
spec:
type: LoadBalancer

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

When using type: LoadBalancer for a BitTorrent service like Transmission, it is highly recommended to set externalTrafficPolicy: Local. This preserves the client's source IP address, which is essential for peer connectivity, DHT performance, and adhering to tracker requirements.

Security Note: Changing the service type to LoadBalancer exposes the Web UI (port 9091) to the network. Please ensure that RPC authentication is enabled in your Transmission configuration to prevent unauthorized access.

  type: LoadBalancer
  externalTrafficPolicy: Local

ports:
- port: 9091
protocol: TCP
targetPort: 9091
name: webui
- name: torrent-tcp
protocol: TCP
port: 51413
targetPort: 51413
- name: torrent-udp
protocol: UDP
port: 51413
targetPort: 51413
selector:
run: transmission
9 changes: 9 additions & 0 deletions install_armhf.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -172,9 +172,18 @@ spec:
port: 9091
protocol: TCP
targetPort: 9091
- name: torrent-tcp

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

Kubernetes requires all ports in a Service to be named when multiple ports are defined. The first port (9091) is missing a name in this manifest, which will cause a validation error (e.g., spec.ports[0].name: Required value) during deployment.

It appears that the update-manifests.sh script did not correctly propagate the name: webui field from the base service definition. Please ensure the generated manifests are correctly synchronized.

    name: webui
  - name: torrent-tcp

port: 51413
protocol: TCP
targetPort: 51413
- name: torrent-udp
port: 51413
protocol: UDP
targetPort: 51413
selector:
app: htpc
run: transmission
type: LoadBalancer
---
apiVersion: v1
kind: Service
Expand Down
9 changes: 9 additions & 0 deletions install_x86_64.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -172,9 +172,18 @@ spec:
port: 9091
protocol: TCP
targetPort: 9091
- name: torrent-tcp

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

Kubernetes requires all ports in a Service to be named when multiple ports are defined. The first port (9091) is missing a name in this manifest, which will cause a validation error (e.g., spec.ports[0].name: Required value) during deployment.

It appears that the update-manifests.sh script did not correctly propagate the name: webui field from the base service definition. Please ensure the generated manifests are correctly synchronized.

    name: webui
  - name: torrent-tcp

port: 51413
protocol: TCP
targetPort: 51413
- name: torrent-udp
port: 51413
protocol: UDP
targetPort: 51413
selector:
app: htpc
run: transmission
type: LoadBalancer
---
apiVersion: v1
kind: Service
Expand Down
Loading