Log for
電訊台
apiVersion: v1
kind: Service
metadata:
name: dsm
namespace: legacy
spec:
ports:
- protocol: TCP
port: 443
targetPort: 443
name: web-https
- protocol: TCP
port: 5000
targetPort: 5000
name: dsm-http
- protocol: TCP
port: 5001
targetPort: 5001
name: dsm-https
externalIPs:
- 192.168.42.69
---
apiVersion: v1
kind: Endpoints
metadata:
name: dsm
namespace: legacy
subsets:
- addresses:
- ip: 192.168.42.69
ports:
-
port: 5000
name: dsm-http
-
port: 5001
name: dsm-https
-
port: 443
name: web-https
---
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
name: dsm
namespace: legacy
annotations:
nginx.ingress.kubernetes.io/backend-protocol: https
nginx.ingress.kubernetes.io/proxy-body-size: "100m"
spec:
rules:
- host: dsm.stevefan1999.me
http:
paths:
- path: /photo
backend:
serviceName: dsm
servicePort: 443
- path: /
backend:
serviceName: dsm
servicePort: 5001damn, can't believe it worked pretty well
just got my dsm covered by cloudflare, dns update triggered by external-dns, then nginx-ingress handled the rest...
this is a much better solution with my manual traefik redirection
even video station worked, but i doubt it is not
jun's loader is not a secret
it is not docker dsm i think?
So I thought it's Docker DSM because you integrated it into K8S
no, but i had enabled traffic forwarding to my DSM
/https?/ socket with service load balancer, and i need to rewrite some subpath to cover 443 case
but still i can use docker and run k3s if i want
oh and btw ddsm is deprecated right? synology want you to use vdsm instead
我用external ceph, 一切connectivity正式
@licson yeah you right, i should just use minio instead
lemme see if i can make the minio docker image to work in synology, hopefully it will work out of the box