kitchen: Remove config.yml ConfigMap generator

The `config.yml` document for *kitchen* contains several "secret" values
(e.g. passwords to Nextcloud, MQTT, etc.).  We don't want to commit
these to the Git repository, of course, but as long as Kustomize expects
to find the `config.yml` file, we won't be able to manage the
application with Argo CD.  Ultimately, *kitchen* needs to be modified to
be able to read secrets separately from config, but until then, we will
have to avoid managing `config.yml` with Kustomize.

kitchen/kitchen.yaml

@@ -4,18 +4,6 @@ kind: Namespace
 metadata:
   name: kitchen
 
----
-apiVersion: v1
-kind: ConfigMap
-metadata:
-  labels:
-    app.kubernetes.io/name: kitchen
-    app.kubernetes.io/instance: kitchen
-    app.kubernetes.io/component: kitchen
-    app.kubernetes.io/part-of: kitchen
-  name: kitchen
-  namespace: kitchen
-
 ---
 apiVersion: apps/v1
 kind: Deployment
@@ -66,6 +54,7 @@ spec:
       - name: config
         configMap:
           name: kitchen
+          optional: true
       - name: tzinfo
         hostPath:
           path: /usr/share/zoneinfo

kitchen/kustomization.yaml

@@ -9,13 +9,6 @@ resources:
 - kitchen.yaml
 - secrets.yaml
 
-configMapGenerator:
-- name: kitchen
-  namespace: kitchen
-  behavior: merge
-  files:
-  - config.yaml
-
 patches:
 - patch: |-
     apiVersion: apps/v1