knative
/
docs
mirror of https://github.com/knative/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix: remove sugar controller installation steps (#5834) 

Remove uninstall steps and yaml file from table
This commit is contained in:
Davide Pruscini 2024-01-30 09:55:05 +01:00 committed by GitHub
parent f3932554a3
commit 396134f130
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 0 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/install/uninstall.md
View File

@ -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:

1
docs/install/yaml-install/eventing/eventing-installation-files.md
View File

@ -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")}}) |

25
docs/install/yaml-install/eventing/install-eventing-with-yaml.md
View File

@ -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.