remove cert-manager from serving install (#1692)

* remove cert-manager from serving install

* add dynamic version

* remove mention of auto tls

docs/install/Knative-with-AKS.md

@@ -133,11 +133,6 @@ recommended configuration for a cluster is:
 
 ## Installing Istio
 
-> Note: [Ambassador](https://www.getambassador.io/) and
-> [Gloo](https://gloo.solo.io/) are available as an alternative to Istio.
-> [Click here](./Knative-with-Ambassador.md) to install Knative with Ambassador.
-> [Click here](./Knative-with-Gloo.md) to install Knative with Gloo.
-
 Knative depends on Istio. If your cloud platform offers a managed Istio
 installation, we recommend installing Istio that way, unless you need the
 ability to customize your installation.
@@ -150,6 +145,11 @@ Minkube or similar, see the
 You must install Istio on your Kubernetes cluster before continuing with these
 instructions to install Knative.
 
+> Note: [Ambassador](https://www.getambassador.io/) and
+> [Gloo](https://gloo.solo.io/) are available as an alternative to Istio.
+> [Click here](./Knative-with-Ambassador.md) to install Knative with Ambassador.
+> [Click here](./Knative-with-Gloo.md) to install Knative with Gloo.
+
 ## Installing Knative
 
 The following commands install all available Knative components. To customize
@@ -194,22 +194,11 @@ your Knative installation, see
    Knative and its dependencies:
 
    ```bash
-   kubectl apply --filename https://github.com/knative/serving/releases/download/{{< version >}}/serving.yaml --selector networking.knative.dev/certificate-provider!=cert-manager \
+   kubectl apply --filename https://github.com/knative/serving/releases/download/{{< version >}}/serving.yaml \
    --filename https://github.com/knative/eventing/releases/download/{{< version >}}/release.yaml \
    --filename https://github.com/knative/serving/releases/download/{{< version >}}/monitoring.yaml
    ```
 
-   > **Notes**:
-   >
-   > - By default, the Knative Serving component installation (`serving.yaml`)
-   >   includes a controller for
-   >   [enabling automatic TLS certificate provisioning](../serving/using-auto-tls.md).
-   >   If you do intend on immediately enabling auto certificates in Knative,
-   >   you can remove the
-   >   `--selector networking.knative.dev/certificate-provider!=cert-manager`
-   >   statement to install the controller. Otherwise, you can choose to install
-   >   the auto certificates feature and controller at a later time.
-
 1. Monitor the Knative components until all of the components show a `STATUS` of
    `Running`:
    ```bash
@@ -223,12 +212,15 @@ your Knative installation, see
 Now that your cluster has Knative installed, you can see what Knative has to
 offer.
 
-To deploy your first app with Knative, follow the step-by-step
+To deploy your first app with the
 [Getting Started with Knative App Deployment](./getting-started-knative-app.md)
 guide.
 
-To get started with Knative Eventing, pick one of the
-[Eventing Samples](../eventing/samples/) to walk through.
+Get started with Knative Eventing by walking through one of the
+[Eventing Samples](../eventing/samples/).
+
+[Install Cert-Manager](../serving/installing-cert-manager.md) if you want to use the
+[automatic TLS cert provisioning feature](../serving/using-auto-tls.md).
 
 ## Cleaning up
 

docs/install/Knative-with-Ambassador.md

@@ -36,26 +36,15 @@ see Performing a Custom Knative Installation.
     race conditions during the install, which cause intermittent errors:
 
         kubectl apply -l knative.dev/crd-install=true \
-        --filename https://github.com/knative/serving/releases/download/v0.7.1/serving.yaml \
-                --filename https://github.com/knative/serving/releases/download/v0.7.1/monitoring.yaml
+        --filename https://github.com/knative/serving/releases/download/{{< version >}}/serving.yaml \
+                --filename https://github.com/knative/serving/releases/download/{{< version >}}/monitoring.yaml
 
 2.  To complete the install of Knative and it's dependencies, run the
     `kubectl apply` command again, this time without the
     `-l knative.dev/crd-install=true`:
 
-        kubectl apply --filename https://github.com/knative/serving/releases/download/v0.7.1 serving.yaml --selector networking.knative.dev/certificate-provider!=cert-manager \
-                --filename https://github.com/knative/serving/releases/download/v0.7.1/monitoring.yaml
-
-    > **Notes**:
-    >
-    > - By default, the Knative Serving component installation (`serving.yaml`)
-    >   includes a controller for
-    >   [enabling automatic TLS certificate provisioning](../serving/using-auto-tls.md).
-    >   If you do intend on immediately enabling auto certificates in Knative,
-    >   you can remove the
-    >   `--selector networking.knative.dev/certificate-provider!=cert-manager`
-    >   statement to install the controller. Otherwise, you can choose to
-    >   install the auto certificates feature and controller at a later time.
+        kubectl apply --filename https://github.com/knative/serving/releases/download/{{< version >}}/serving.yaml \
+                --filename https://github.com/knative/serving/releases/download/{{< version >}}/monitoring.yaml
 
 3.  Monitor the Knative namespaces and wait until all of the pods come up with a
     `STATUS` of `Running`:
@@ -158,5 +147,5 @@ manage and route to serverless applications!
 - Try the
   [Getting Started with App Deployment guide](./getting-started-knative-app/)
   for Knative serving.
-- Take a look at the rest of what
-  [Knative has to offer](https://knative.dev/docs/index.html)
+- Get started with Knative Eventing by walking through one of the
+  [Eventing Samples](../eventing/samples/).

docs/install/Knative-with-Docker-for-Mac.md

@@ -33,56 +33,34 @@ continuing.
 
 ## Installing Istio
 
-Knative depends on Istio. Run the following to install Istio. (This changes
-`LoadBalancer` to `NodePort` for the `istio-ingress` service).
+Knative depends on [Istio](https://istio.io/docs/concepts/what-is-istio/) for
+traffic routing and ingress. You have the option of injecting Istio sidecars and
+enabling the Istio service mesh, but it's not required for all Knative
+components.
 
-```shell
-curl -L https://raw.githubusercontent.com/knative/serving/v0.5.2/third_party/istio-1.0.7/istio.yaml \
-  | sed 's/LoadBalancer/NodePort/' \
-  | kubectl apply --filename -
-
-# Label the default namespace with istio-injection=enabled.
-kubectl label namespace default istio-injection=enabled
-```
-
-Monitor the Istio components until all of the components show a `STATUS` of
-`Running` or `Completed`:
-
-```shell
-kubectl get pods --namespace istio-system
-```
+If your cloud platform offers a managed Istio installation, we recommend
+installing Istio that way, unless you need the ability to customize your
+installation.
 
-It will take a few minutes for all the components to be up and running; you can
-rerun the command to see the current status.
-
-> Note: Instead of rerunning the command, you can add `--watch` to the above
-> command to view the component's status updates in real time. Use CTRL+C to
-> exit watch mode.
+If you prefer to install Istio manually, if your cloud provider doesn't offer a
+managed Istio installation, or if you're installing Knative locally using
+Minkube or similar, see the
+[Installing Istio for Knative guide](./installing-istio.md).
 
 ## Installing Knative Serving
 
 Next, install [Knative Serving](https://github.com/knative/serving).
 
 Because you have limited resources available, use the
-`https://github.com/knative/serving/releases/download/v0.5.2/serving.yaml` file,
+`https://github.com/knative/serving/releases/download/{{< version >}}/serving.yaml` file,
 which installs only Knative Serving:
 
 ```shell
 curl -L https://github.com/knative/serving/releases/download/{{< version >}}/serving.yaml \
   | sed 's/LoadBalancer/NodePort/' \
-  | kubectl apply --selector networking.knative.dev/certificate-provider!=cert-manager --filename -
+  | kubectl apply --filename -
 ```
 
-**Notes**:
-
-> - By default, the Knative Serving component installation (`serving.yaml`)
->   includes a controller for
->   [enabling automatic TLS certificate provisioning](../serving/using-auto-tls.md).
->   If you do intend on immediately enabling auto certificates in Knative, you
->   can remove the
->   `--selector networking.knative.dev/certificate-provider!=cert-manager`
->   statement to install the controller.
-
 > Note: Unlike minikube, we're not changing the LoadBalancer to a NodePort here.
 > Docker for Mac will assign `localhost` as the host for that LoadBalancer,
 > making the applications available easily.
@@ -119,6 +97,12 @@ head to the [sample apps](../serving/samples/README.md) repo.
 > Note: You can replace the {IP_ADDRESS} placeholder used in the samples with
 > `localhost` as mentioned above.
 
+Get started with Knative Eventing by walking through one of the
+[Eventing Samples](../eventing/samples/).
+
+[Install Cert-Manager](../serving/installing-cert-manager.md) if you want to use the
+[automatic TLS cert provisioning feature](../serving/using-auto-tls.md).
+
 ## Cleaning up
 
 Docker for Mac supports several levels of resetting its state and thus cleaning

docs/install/Knative-with-GKE.md

@@ -170,22 +170,11 @@ see [Performing a Custom Knative Installation](./Knative-custom-install.md).
    complete the install of Knative and its dependencies:
 
    ```bash
-   kubectl apply --filename https://github.com/knative/serving/releases/download/{{< version >}}/serving.yaml --selector networking.knative.dev/certificate-provider!=cert-manager \
+   kubectl apply --filename https://github.com/knative/serving/releases/download/{{< version >}}/serving.yaml \
    --filename https://github.com/knative/eventing/releases/download/{{< version >}}/eventing.yaml \
    --filename https://github.com/knative/serving/releases/download/{{< version >}}/monitoring.yaml
    ```
 
-   > **Notes**:
-   >
-   > - By default, the Knative Serving component installation (`serving.yaml`)
-   >   includes a controller for
-   >   [enabling automatic TLS certificate provisioning](../serving/using-auto-tls.md).
-   >   If you do intend on immediately enabling auto certificates in Knative,
-   >   you can remove the
-   >   `--selector networking.knative.dev/certificate-provider!=cert-manager`
-   >   statement to install the controller. Otherwise, you can choose to install
-   >   the auto certificates feature and controller at a later time.
-
 1. Monitor the Knative components until all of the components show a `STATUS` of
    `Running`:
 
@@ -200,12 +189,15 @@ see [Performing a Custom Knative Installation](./Knative-custom-install.md).
 Now that your cluster has Knative installed, you can see what Knative has to
 offer.
 
-To deploy your first app with Knative, follow the step-by-step
+To deploy your first app with the
 [Getting Started with Knative App Deployment](./getting-started-knative-app.md)
 guide.
 
-To get started with Knative Eventing, pick one of the
-[Eventing Samples](../eventing/samples/) to walk through.
+Get started with Knative Eventing by walking through one of the
+[Eventing Samples](../eventing/samples/).
+
+[Install Cert-Manager](../serving/installing-cert-manager.md) if you want to use the
+[automatic TLS cert provisioning feature](../serving/using-auto-tls.md).
 
 ## Cleaning up
 

docs/install/Knative-with-Gardener.md

@@ -125,22 +125,11 @@ see [Performing a Custom Knative Installation](./Knative-custom-install.md).
    complete the install of Knative and its dependencies:
 
    ```bash
-   kubectl apply --filename https://github.com/knative/serving/releases/download/{{< version >}}/serving.yaml --selector networking.knative.dev/certificate-provider!=cert-manager \
+   kubectl apply --filename https://github.com/knative/serving/releases/download/{{< version >}}/serving.yaml \
    --filename https://github.com/knative/eventing/releases/download/{{< version >}}/release.yaml \
    --filename https://github.com/knative/serving/releases/download/{{< version >}}/monitoring.yaml
    ```
 
-   > **Notes**:
-   >
-   > - By default, the Knative Serving component installation (`serving.yaml`)
-   >   includes a controller for
-   >   [enabling automatic TLS certificate provisioning](../serving/using-auto-tls.md).
-   >   If you do intend on immediately enabling auto certificates in Knative,
-   >   you can remove the
-   >   `--selector networking.knative.dev/certificate-provider!=cert-manager`
-   >   statement to install the controller. Otherwise, you can choose to install
-   >   the auto certificates feature and controller at a later time.
-
 1. Monitor the Knative components until all of the components show a `STATUS` of
    `Running`:
    ```bash
@@ -185,12 +174,15 @@ kind: ConfigMap
 Now that your cluster has Knative installed, you can see what Knative has to
 offer.
 
-To deploy your first app with Knative, follow the step-by-step
+To deploy your first app with the
 [Getting Started with Knative App Deployment](./getting-started-knative-app.md)
 guide.
 
-To get started with Knative Eventing, pick one of the
-[Eventing Samples](../eventing/samples/) to walk through.
+Get started with Knative Eventing by walking through one of the
+[Eventing Samples](../eventing/samples/).
+
+[Install Cert-Manager](../serving/installing-cert-manager.md) if you want to use the
+[automatic TLS cert provisioning feature](../serving/using-auto-tls.md).
 
 ## Cleaning up
 

docs/install/Knative-with-ICP.md

@@ -162,19 +162,9 @@ see [Performing a Custom Knative Installation](./Knative-custom-install.md).
    ```shell
    curl -L https://github.com/knative/serving/releases/download/{{< version >}}/serving.yaml \
      | sed 's/LoadBalancer/NodePort/' \
-     | kubectl apply --selector networking.knative.dev/certificate-provider!=cert-manager --filename -
+     | kubectl apply --filename -
    ```
 
-   **Notes**:
-
-   > - By default, the Knative Serving component installation (`serving.yaml`)
-   >   includes a controller for
-   >   [enabling automatic TLS certificate provisioning](../serving/using-auto-tls.md).
-   >   If you do intend on immediately enabling auto certificates in Knative,
-   >   you can remove the
-   >   `--selector networking.knative.dev/certificate-provider!=cert-manager`
-   >   statement to install the controller.
-
    ```shell
    curl -L https://github.com/knative/eventing/releases/download/{{< version >}}/release.yaml \
      | sed 's/LoadBalancer/NodePort/' \
@@ -217,7 +207,7 @@ Now you can deploy an app to your newly created Knative cluster.
 Now that your cluster has Knative installed, you can see what Knative has to
 offer.
 
-To deploy your first app with Knative, follow the step-by-step
+To deploy your first app with the
 [Getting Started with Knative App Deployment](./getting-started-knative-app.md)
 guide.
 
@@ -230,9 +220,12 @@ echo $(ICP cluster ip):$(kubectl get svc istio-ingressgateway --namespace istio-
 --output 'jsonpath={.spec.ports[?(@.port==80)].nodePort}')
 ```
 
-To get started with Knative Eventing, walk through one of the
+Get started with Knative Eventing by walking through one of the
 [Eventing Samples](../eventing/samples/).
 
+[Install Cert-Manager](../serving/installing-cert-manager.md) if you want to use the
+[automatic TLS cert provisioning feature](../serving/using-auto-tls.md).
+
 ## Cleaning up
 
 To remove Knative from your IBM Cloud Private cluster, run the following

docs/install/Knative-with-IKS.md

@@ -209,22 +209,11 @@ see [Performing a Custom Knative Installation](./Knative-custom-install.md).
    complete the install of Knative and its dependencies:
 
    ```bash
-   kubectl apply --filename https://github.com/knative/serving/releases/download/{{< version >}}/serving.yaml --selector networking.knative.dev/certificate-provider!=cert-manager \
+   kubectl apply --filename https://github.com/knative/serving/releases/download/{{< version >}}/serving.yaml \
    --filename https://github.com/knative/eventing/releases/download/{{< version >}}/release.yaml \
    --filename https://github.com/knative/serving/releases/download/{{< version >}}/monitoring.yaml
    ```
 
-   > **Notes**:
-   >
-   > - By default, the Knative Serving component installation (`serving.yaml`)
-   >   includes a controller for
-   >   [enabling automatic TLS certificate provisioning](../serving/using-auto-tls.md).
-   >   If you do intend on immediately enabling auto certificates in Knative,
-   >   you can remove the
-   >   `--selector networking.knative.dev/certificate-provider!=cert-manager`
-   >   statement to install the controller. Otherwise, you can choose to install
-   >   the auto certificates feature and controller at a later time.
-
 1. Monitor the Knative components until all of the components show a `STATUS` of
    `Running`:
    ```bash
@@ -238,12 +227,15 @@ see [Performing a Custom Knative Installation](./Knative-custom-install.md).
 Now that your cluster has Knative installed, you can see what Knative has to
 offer.
 
-To deploy your first app with Knative, follow the step-by-step
+To deploy your first app with the
 [Getting Started with Knative App Deployment](./getting-started-knative-app.md)
 guide.
 
-To get started with Knative Eventing, pick one of the
-[Eventing Samples](../eventing/samples/) to walk through.
+Get started with Knative Eventing by walking through one of the
+[Eventing Samples](../eventing/samples/).
+
+[Install Cert-Manager](../serving/installing-cert-manager.md) if you want to use the
+[automatic TLS cert provisioning feature](../serving/using-auto-tls.md).
 
 ## Cleaning up