changed host to example domain

README.md

@@ -76,7 +76,7 @@ First of all, you will need a Kubernetes cluster up and running. If you are not
 ```sh
 git clone https://gitlab.fabcity.hamburg/software/interfacer-swkit.git
 cd interfacer-swkit
-kubectl kustomize --enable-helm | kubectl apply -f -
+kubectl kustomize --enable-helm overlays/dev | kubectl apply -f -
 ```
 
 ## ⚙️ Development Workflow and Contributing

apps/gitea/values.yaml

@@ -17,14 +17,14 @@ ingress:
     kubernetes.io/tls-acme: "true"
     cert-manager.io/cluster-issuer: letsencrypt-http
   hosts:
-    - host: code.k8s.dev.fabcity-hamburg.de
+    - host: code.example.org
       paths:
         - path: /
           pathType: Prefix
   tls:
     - secretName: interfacer-gitea-tls
       hosts:
-        - code.k8s.dev.fabcity-hamburg.de
+        - code.example.org
 resources:
   requests:
     cpu: 100m

apps/interfacer-core/values.yaml

@@ -1,3 +1,3 @@
 ---
 gateway:
-  url: "https://gateway.k8s.dev.fabcity-hamburg.de/"
+  url: "https://gateway.example.org/"

base/cert-manager/letsencrypt.yaml

@@ -5,7 +5,7 @@ metadata:
   name: letsencrypt-http
 spec:
   acme:
-    email: hostmaster@fabcity-hamburg.de
+    email: hostmaster@example.org
     server: https://acme-v02.api.letsencrypt.org/directory
     privateKeySecretRef:
       name: letsencrypt-key
@@ -20,7 +20,7 @@ metadata:
   name: letsencrypt-http-staging
 spec:
   acme:
-    email: hostmaster@fabcity-hamburg.de
+    email: hostmaster@example.org
     server: https://acme-staging-v02.api.letsencrypt.org/directory
     privateKeySecretRef:
       name: letsencrypt-key-staging

overlays/dev/gitea/ingress.yaml

@@ -19,4 +19,4 @@ spec:
                   name: http
   tls:
     - hosts:
-        - code.k8s.dev.fabcity-hamburg.de
+        - code.example.org

overlays/dev/gitea/kustomization.yaml

@@ -10,7 +10,7 @@ namespace: gitea
 #       - op: replace
 #         path: /spec/rules
 #         value:
-#           - host: code.k8s.dev.fabcity-hamburg.de
+#           - host: code.example.org
 #             http:
 #               paths:
 #                 - path: /
@@ -21,4 +21,4 @@ namespace: gitea
 #         value:
 #           - secretName: gitea-tls
 #             hosts:
-#               - code.k8s.dev.fabcity-hamburg.de
+#               - code.example.org

overlays/prod/interfacer-core/ingress.yaml

@@ -8,7 +8,7 @@ metadata:
     cert-manager.io/cluster-issuer: letsencrypt-http
 spec:
   rules:
-    - host: hub.k8s.dev.fabcity-hamburg.de
+    - host: hub.example.org
       http:
         paths:
           - path: /
@@ -20,7 +20,7 @@ spec:
                   name: http
   tls:
     - hosts:
-        - hub.k8s.dev.fabcity-hamburg.de
+        - hub.example.org
       secretName: interfacer-core-frontend-tls
 ---
 apiVersion: networking.k8s.io/v1
@@ -32,7 +32,7 @@ metadata:
     cert-manager.io/cluster-issuer: letsencrypt-http
 spec:
   rules:
-    - host: gateway.k8s.dev.fabcity-hamburg.de
+    - host: gateway.example.org
       http:
         paths:
           - path: /
@@ -44,5 +44,5 @@ spec:
                   name: http
   tls:
     - hosts:
-        - gateway.k8s.dev.fabcity-hamburg.de
+        - gateway.example.org
       secretName: interfacer-core-gateway-tls

overlays/prod/interfacer-webpresence/ingress.yaml

@@ -8,7 +8,7 @@ metadata:
     cert-manager.io/cluster-issuer: letsencrypt-http
 spec:
   rules:
-    - host: www.k8s.dev.fabcity-hamburg.de
+    - host: www.example.org
       http:
         paths:
           - path: /
@@ -20,5 +20,5 @@ spec:
                   name: http
   tls:
     - hosts:
-        - www.k8s.dev.fabcity-hamburg.de
+        - www.example.org
       secretName: interfacer-webpresence-tls