fix: remove sugar controller installation steps

Remove uninstall steps and yaml file from table
knative · Jan 30, 2024 · d71ee16 · d71ee16
1 parent b6c57d2
commit d71ee16
Show file tree

Hide file tree

Showing 3 changed files with 0 additions and 36 deletions.
diff --git a/docs/install/uninstall.md b/docs/install/uninstall.md
@@ -134,16 +134,6 @@ Uninstall any Eventing extensions you have installed by following the relevant p
 
 
 
-=== "Sugar Controller"
-
-    Uninstall the Eventing Sugar Controller by running:
-
-    ```bash
-    kubectl delete -f {{ artifact( repo="eventing", file="eventing-sugar-controller.yaml") }}
-    ```
-
-
-
 === "GitHub Source"
 
     Uninstall a single-tenant GitHub source by running:

diff --git a/docs/install/yaml-install/eventing/eventing-installation-files.md b/docs/install/yaml-install/eventing/eventing-installation-files.md
@@ -15,7 +15,6 @@ The following table describes the installation files included in Knative Eventin
 | [eventing-core.yaml]({{ artifact(repo="eventing",file="eventing-core.yaml")}}) | Required: Knative Eventing core components. |  [eventing-crds.yaml]({{ artifact(repo="eventing",file="eventing-crds.yaml")}}) |
 | [eventing-crds.yaml]({{ artifact(repo="eventing",file="eventing-crds.yaml")}}) | Required: Knative Eventing core CRDs. |  none |
 | [eventing-post-install.yaml]({{ artifact(repo="eventing",file="eventing-post-install.yaml")}}) | Jobs required for upgrading to a new minor version. | [eventing-core.yaml]({{ artifact(repo="eventing",file="eventing-core.yaml")}}), [eventing-crds.yaml]({{ artifact(repo="eventing",file="eventing-crds.yaml")}}) |
-| [eventing-sugar-controller.yaml]({{ artifact(repo="eventing",file="eventing-sugar-controller.yaml")}}) | Reconciler that watches for labels and annotations on certain resources to inject eventing components. | [eventing-core.yaml]({{ artifact(repo="eventing",file="eventing-core.yaml")}}) |
 | [eventing.yaml]({{ artifact(repo="eventing",file="eventing.yaml")}}) | Combines `eventing-core.yaml`, `mt-channel-broker.yaml`, and `in-memory-channel.yaml`. | none |
 | [in-memory-channel.yaml]({{ artifact(repo="eventing",file="in-memory-channel.yaml")}}) | Components to configure In-Memory Channels. | [eventing-core.yaml]({{ artifact(repo="eventing",file="eventing-core.yaml")}}) |
 | [mt-channel-broker.yaml]({{ artifact(repo="eventing",file="mt-channel-broker.yaml")}}) | Components to configure Multi-Tenant (MT) Channel Broker. | [eventing-core.yaml]({{ artifact(repo="eventing",file="eventing-core.yaml")}}) |
diff --git a/docs/install/yaml-install/eventing/install-eventing-with-yaml.md b/docs/install/yaml-install/eventing/install-eventing-with-yaml.md
@@ -228,31 +228,6 @@ The following tabs expand to show instructions for installing each Eventing exte
 
     For more information, see the [Kafka Sink](../../../eventing/sinks/kafka-sink.md) documentation.
 
-=== "Sugar Controller"
-
-    <!-- Unclear when this feature came in -->
-
-    1. Install the Eventing Sugar Controller by running the command:
-
-        ```bash
-        kubectl apply -f {{ artifact(repo="eventing",file="eventing-sugar-controller.yaml")}}
-        ```
-
-        The Knative Eventing Sugar Controller reacts to special labels and
-        annotations and produce Eventing resources. For example:
-
-        - When a namespace is labeled with `eventing.knative.dev/injection=enabled`, the
-          controller creates a default Broker in that namespace.
-        - When a Trigger is annotated with `eventing.knative.dev/injection=enabled`, the
-          controller creates a Broker named by that Trigger in the Trigger's namespace.
-
-    1. Enable the default Broker on a namespace (here `default`) by running the command:
-
-        ```bash
-        kubectl label namespace <namespace-name> eventing.knative.dev/injection=enabled
-        ```
-        Where `<namespace-name>` is the name of the namespace.
-
 === "GitHub Source"
 
     A single-tenant GitHub source creates one Knative service per GitHub source.