Uninstalling Knative

    To uninstall a YAML-based Knative installation:

    Uninstall any Serving extensions you have installed by performing the steps in the following relevant tab:

    HPA autoscalingTLS with cert-managerTLS via HTTP01

    Knative also supports the use of the Kubernetes Horizontal Pod Autoscaler (HPA) for driving autoscaling decisions. The following command will uninstall the components needed to support HPA-class autoscaling:

    1. Uninstall the component that integrates Knative with cert-manager:

    2. Optional: if you no longer need cert-manager, uninstall it by following the steps in the cert-manager documentation.

    Uninstall the net-http01 controller by running:

    1. kubectl delete -f https://github.com/knative/net-http01/releases/download/knative-v1.8.0/release.yaml

    Uninstalling a networking layer

    Follow the relevant procedure to uninstall the networking layer you installed:

    ContourIstioKourier

    The following commands uninstall Contour and enable its Knative integration.

    1. Uninstall the Knative Contour controller by running:

      1. kubectl delete -f https://github.com/knative/net-contour/releases/download/knative-v1.8.0/net-contour.yaml

    The following commands uninstall Istio and enable its Knative integration.

    1. Uninstall the Knative Istio controller by running:

      1. kubectl delete -f https://github.com/knative/net-istio/releases/download/knative-v1.8.0/net-istio.yaml
    2. Optional: if you no longer need Istio, uninstall it by running:

      1. kubectl delete -f https://github.com/knative/net-istio/releases/download/knative-v1.8.0/istio.yaml
    1. kubectl delete -f https://github.com/knative/net-kourier/releases/download/knative-v1.8.0/kourier.yaml

    Uninstalling the Serving component

    1. Uninstall the Serving core components by running:

      1. kubectl delete -f https://storage.googleapis.com/knative-nightly/serving/latest/serving-core.yaml
    2. Uninstall the required custom resources by running:

    Uninstall any Eventing extensions you have installed by following the relevant procedure:

    Apache Kafka SinkSugar ControllerGitHub SourceApache Kafka SourceGCP SourcesApache CouchDB SourceVMware Sources and Bindings

    1. Uninstall the Kafka Sink data plane:

    2. Uninstall the Kafka controller:

      1. kubectl delete -f https://github.com/knative-sandbox/eventing-kafka-broker/releases/download/knative-v1.8.4/eventing-kafka-controller.yaml

    Uninstall the Eventing Sugar Controller by running:

    1. kubectl delete -f https://github.com/knative/eventing/releases/download/knative-v1.8.1/eventing-sugar-controller.yaml

    Uninstall a single-tenant GitHub source by running:

    1. kubectl delete -f https://github.com/knative-sandbox/eventing-github/releases/download/knative-v1.8.0/github.yaml

    Uninstall a multi-tenant GitHub source by running:

    1. kubectl delete -f https://github.com/knative-sandbox/eventing-github/releases/download/knative-v1.8.0/mt-github.yaml

    Uninstall the Apache Kafka source by running:

    1. kubectl delete -f https://github.com/knative-sandbox/eventing-kafka-broker/releases/download/knative-v1.8.4/eventing-kafka-source.yaml

    Uninstall the GCP sources by running:

    1. kubectl delete -f https://github.com/google/knative-gcp/releases/latest/download/cloud-run-events.yaml

    Uninstall the Apache CouchDB source by running:

      Uninstall the VMware sources and bindings by running:

      1. kubectl delete -f https://github.com/vmware-tanzu/sources-for-knative/releases/download/v0.35.0/release.yaml

      Uninstalling an optional Broker (Eventing) layer

      Uninstall a Broker (Eventing) layer, if you installed one:

      Apache Kafka BrokerMT-Channel-based

      1. Uninstall the Kafka controller by running the following command:

      Uninstall the broker by running:

      1. kubectl delete -f https://github.com/knative/eventing/releases/download/knative-v1.8.1/mt-channel-broker.yaml

      Uninstalling optional channel (messaging) layers

      Uninstall each channel layer you have installed:

      Apache Kafka ChannelGoogle Cloud Pub/Sub ChannelIn-Memory (standalone)NATS Channel

      Uninstall the Apache Kafka Channel by running:

      1. kubectl delete -f https://github.com/knative-sandbox/eventing-kafka-broker/releases/download/knative-v1.8.4/eventing-kafka-channel.yaml

      Uninstall the Google Cloud Pub/Sub Channel by running:

      1. kubectl delete -f https://github.com/google/knative-gcp/releases/latest/download/cloud-run-events.yaml

      Uninstall the in-memory channel implementation by running:

      1. kubectl delete -f https://github.com/knative/eventing/releases/download/knative-v1.8.1/in-memory-channel.yaml
      1. Uninstall the NATS Streaming channel by running:

        1. kubectl delete -f https://github.com/knative-sandbox/eventing-natss/releases/latest/download/eventing-natss.yaml
      2. Uninstall NATS Streaming for Kubernetes. For more information, see the eventing-natss repository in GitHub.

      1. Uninstall the Eventing core components by running:

        1. kubectl delete -f https://storage.googleapis.com/knative-nightly/eventing/latest/eventing-core.yaml
      2. Uninstall the required custom resources by running:

        1. kubectl delete -f https://storage.googleapis.com/knative-nightly/eventing/latest/eventing-crds.yaml

      Uninstall an Operator-based Knative installation

      To uninstall an Operator-based Knative installation, follow these procedures:

      Removing the Knative Serving component

      Remove the Knative Serving CR:

      1. kubectl delete KnativeServing knative-serving -n knative-serving

      Removing Knative Eventing component

      Remove the Knative Eventing CR:

      Knative operator prevents unsafe removal of Knative resources. Even if the Knative Serving and Knative Eventing CRs are successfully removed, all the CRDs in Knative are still kept in the cluster. All your resources relying on Knative CRDs can still work.

      If you have installed Knative from source, uninstall it using the following command while in the root directory for the source:

      1. ko delete -f config/