K3s-cluster/traefik/1-traefik-external/service.yaml
Tanguy Herbron 0a41373688 feat(ingress): Add additional traefik for internal only access
A new traefik deployment has been added, and two ingressclasses have been set for the new instance, as well as the previous one. This allows the network to be split in two, one for external access and another for internal access. Each traefik deployment is connected to a loadbalancer requesting the IP necessary for each type of access.
2022-11-20 03:38:22 +01:00

37 lines
927 B
YAML

---
# Source: traefik/templates/service.yaml
apiVersion: v1
kind: List
metadata:
name: traefik-external
items:
- apiVersion: v1
kind: Service
metadata:
name: traefik-external
labels:
app.kubernetes.io/name: traefik-external
helm.sh/chart: traefik-10.24.2
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/instance: traefik
annotations:
spec:
type: LoadBalancer
loadBalancerIP: 10.19.66.247
selector:
app.kubernetes.io/name: traefik
app.kubernetes.io/instance: traefik
ports:
- port: 25565
name: minecrafttcp
targetPort: "minecrafttcp"
protocol: TCP
- port: 80 # Change port here to accomodate for internal only services
name: web
targetPort: "web"
protocol: TCP
- port: 443
name: websecure
targetPort: "websecure"
protocol: TCP