Merge pull request #453 from epinio/docs/kubed-reflector

Docs/kubed reflector

Author: dcharles525

docs/explanations/advanced.md

@@ -78,15 +78,11 @@ The Epinio API server runs on the cluster.
 It's reached using Kubernetes resources like
 Deployments, Services,  Ingresses and Secrets.
 
-### Kubed
+### Reflector
 
-[Kubed documentation](https://github.com/kubeops/kubed)
+[Relector documentation](https://github.com/emberstack/kubernetes-reflector)
 
-Epinio installs Kubed to keep secrets, needed in more than one namespace, synchronized.
-For example, the image pull secret is needed in every application namespace
-so that Kubernetes can pull the built application images from the [Container Registry](#container-registry).
-
-Kubed makes sure that if the source secret changes, the copies change too.
+Reflector is a Kubernetes addon designed to monitor changes to resources (secrets and configmaps) and reflect changes to mirror resources in the same or other namespaces.
 
 ### Minio
 

docs/howtos/customization/setup_routing_secrets.md

@@ -55,22 +55,6 @@ Use them only where absolutely necessary with everything else keeping to the aut
 The secret is used whenever a requested application route matches the wildcard pattern.
 This reduces the number of Secrets needing creation.
 
-1. You can automate distribution of routing secrets by using a component like Kubed.
-Kubed can automatically copy secrets between namespaces based on annotations.
-Kubed is a component of Epinio so is available.
-As an example,
-
-   1. Place a new routing secret `RS` into the namespace `epinio`.
-
-   1. Annotate the secret with
-
-      `kubed.appscode.com/sync="app.kubernetes.io/component=epinio-namespace"`
-
-   1. Kubed now distributes `RS` to all namespaces which have the label `app.kubernetes.io/component=epinio-namespace`.
-   These are all the namespaces under Epinio's control.
-
-   For a more limited distribution it's possible to add custom labels to the
-   desired namespaces and add matching annotations on the relevant Secrets.
-
-   The distribution automatically includes all new namespaces
-   matching whatever criteria are in place.
+1. You can automate distribution of routing secrets by using a component like [Reflector](https://github.com/emberstack/kubernetes-reflector).
+Reflector can automatically copy secrets between namespaces based on annotations.
+Reflector is a component of Epinio so is available.

docs/installation/install_epinio.md

@@ -9,7 +9,7 @@ keywords: [epinio, kubernetes, k8s, installation, install]
 ## Introduction
 
 Epinio is installed from a single Helm chart.
-This also installs [`Kubed`](#kubed), [`MinIO`](#s3-storage), [`Dex`](#dex) and a [container registry](#container-registry) in your Kubernetes cluster.
+This also installs Reflector, [`MinIO`](#s3-storage), [`Dex`](#dex) and a [container registry](#container-registry) in your Kubernetes cluster.
 You can disable the installation of these additional "sub" charts by changing the settings as described in their sections below.
 
 ## Prerequisites
@@ -230,12 +230,6 @@ There exists examples within the `values.yaml` file under the `server.stagingWor
 
 The configurations under `server.stagingWorkloads` gets mapped to the build script ConfigMaps which is then processed by the Epinio Server when builds are kicked off.  These specifications are supplied to the newly created staging jobs.
 
-### Kubed
-
-Kubed is installed as a subchart when `.Values.kubed.enabled` is `true` (default).
-If you already have `kubed`, you can skip installation by setting
-the helm value `.Values.kubed.enabled` to `false`.
-
 ### S3 storage
 
 Epinio uses an S3 compatible storage to store the application source code.
@@ -283,8 +277,20 @@ to point to the desired container registry.
 
 ### Breaking Changes & Migrations
 
+#### 1.13.7 to 1.13.8
+Epinio **1.13.8** switches from using kubed to use [reflector](https://github.com/emberstack/kubernetes-reflector) for syncing ConfigMaps and Secrets across namespaces.  This change occured due to kubed being deprecated and unmaintained.
+
+If you are upgrading from **1.13.7** or earlier to **1.13.8** or later, you must manually uninstall kubed from your cluster after the upgrade is complete.
+
+You can view the changes made in the following files: 
+- [registry-secret.yaml](https://github.com/epinio/helm-charts/blob/main/chart/epinio/templates/registry-secret.yaml)
+- [certificate.yaml](https://github.com/epinio/helm-charts/blob/main/chart/epinio/templates/certificate.yaml)
+- [values.yaml](https://github.com/epinio/helm-charts/blob/main/chart/epinio/values.yaml)
+
+By default the all of the namespaces are allowed but the reflector can be customized based on your deployment style. If you were not customizing kubed previously, no action is needed other than uninstalling kubed.
+
 #### 1.12 to 1.13
 
 Epinio 1.13 rehomes configurations for the staging workloads to a more Kubernetes-standardized format that supports a larger variety of configs.  These are no longer configured via ENV variables on the Epinio Server or through CLI flags but rather read from an in-cluster ConfigMap at staging time.
 
-Documentation has been udpated for both the [Epinio Server](https://github.com/epinio/epinio?tab=readme-ov-file#112-to-113) and the [Epinio Helm Chart](https://github.com/epinio/helm-charts/tree/main/chart/epinio#112-to-113).  These READMEs go into detail describing the changes to the environment variables, CLI flags, and changes to the `values.yaml` interface.  Please refer to these before upgrading to **1.13**.
+Documentation has been updated for both the [Epinio Server](https://github.com/epinio/epinio?tab=readme-ov-file#112-to-113) and the [Epinio Helm Chart](https://github.com/epinio/helm-charts/tree/main/chart/epinio#112-to-113).  These READMEs go into detail describing the changes to the environment variables, CLI flags, and changes to the `values.yaml` interface.  Please refer to these before upgrading to **1.13**.