Filled all placeholders

Author: nicholasdille

120_kubernetes/30_ingress/infrastructure-as-code.yaml

@@ -0,0 +1,39 @@
+---
+apiVersion: externaldns.k8s.io/v1alpha1
+kind: DNSEndpoint
+metadata:
+  name: traefik-dashboard
+spec:
+  endpoints:
+  - dnsName: traefik.seat0.inmylab.de
+    recordTTL: 300
+    recordType: A
+    targets:
+    - lb.seat0.inmylab.de
+---
+apiVersion: cert-manager.io/v1
+kind: Certificate
+metadata:
+  name: traefik-dashboard
+spec:
+  secretName: traefik-dashboard
+  issuerRef:
+    name: letsencrypt-prod
+    kind: ClusterIssuer
+  dnsNames:
+  - traefik.seat0.inmylab.de
+---
+apiVersion: traefik.io/v1alpha1
+kind: IngressRoute
+metadata:
+  name: traefik-dashboard
+spec:
+  entryPoints:
+  - http
+  routes:
+  - match: Host(`traefik.seat0.inmylab.de`)
+    kind: Rule
+    services:
+    - name: traefik-dashboard
+      port: 80
+      strategy: RoundRobin

120_kubernetes/30_ingress/ingressroute.yaml

@@ -25,4 +25,4 @@ spec:
     services:
     - name: traefik-dashboard
       port: 80
-      strategy: RoundRobin
+      strategy: RoundRobin

120_kubernetes/30_ingress/slides.md

@@ -2,15 +2,7 @@
 
 Responsible for routing requests to pods [](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/)
 
-Maintains rules for matching hosts and paths
-
-XXX
-
----
-
-## Ingress resource
-
-Ingress [](https://kubernetes.io/docs/concepts/services-networking/ingress/) defines rule to match requests and how to route them
+### Ingress resource
 
 ```
 apiVersion: networking.k8s.io/v1
@@ -30,7 +22,9 @@ spec:
             port:
               number: 5678
 ```
-<!-- .element: style="float: right; width: 22em;" -->
+<!-- .element: style="float: right; width: 20em;" -->
+
+Ingress [](https://kubernetes.io/docs/concepts/services-networking/ingress/) defines rule to match requests and how to route them
 
 ### Request matching
 
@@ -80,17 +74,17 @@ Manage access automatically - as code
 
 ### Concepts
 
-`external-dns` manages DNS records pointing to ingress controller
+`external-dns` manages DNS records pointing to ingress controller [](https://doc.crds.dev/github.com/kubernetes-sigs/external-dns)
 
-`cert-manager` maintains certificates for TLS termination
+`cert-manager` maintains certificates for TLS termination [](https://doc.crds.dev/github.com/cert-manager/cert-manager)
 
-Flexible ingress controllers offer important features, e.g. `traefik`` [](https://traefik.io/traefik/) among others
+Flexible ingress controllers offer important features, e.g. `traefik` [](https://traefik.io/traefik/) among others
 
 ### Outlook
 
 `Ingress` resource: focused on HTTP(S), annotations [](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/) for advanced features
 
-Solved by custom resources, e.g. `IngressRoute` in traefik
+Solved by custom resources, e.g. `IngressRoute` in traefik [](https://doc.crds.dev/github.com/traefik/traefik)
 
 ---
 

2023-10-11_heise-Kubernetes-verstehen.html

@@ -140,8 +140,8 @@
 
 - <span class="fa-li"><i class="fa-duotone fa-tags"></i></span> Labels provide context and select resources
 - <span class="fa-li"><i class="fa-duotone fa-arrows-spin"></i></span> Pod lifecycle is managed my multiple resources
-- <span class="fa-li"><i class="fa-duotone fa-chart-network"></i></span> XXX Architecture
-- <span class="fa-li"><i class="fa-duotone fa-handshake-simple"></i></span> XXX Communication
+- <span class="fa-li"><i class="fa-duotone fa-chart-network"></i></span> Kubernetes architecture allows for highly available setups
+- <span class="fa-li"><i class="fa-duotone fa-handshake-simple"></i></span> The Kubernetes API server is **the** central component
 - <span class="fa-li"><i class="fa-duotone fa-dungeon"></i></span> Ingress controllers provide access to services
 
 <!-- .element: class="fa-ul" style="line-height: 1.5em;" -->