Removing old versions from docs (#1995)

abrennan89 · knative-prow-robot · commit 3138186bef02 · 2019-12-02T11:36:34.000-08:00
* Removing old versions from docs

* Try fixing the broken list rending on the site

* add missing quotes

* use sentence style caps

* Try adding a weight to fix rendering

* try to fix poor list rendering (again)
diff --git a/docs/eventing/debugging/README.md b/docs/eventing/debugging/README.md
@@ -14,12 +14,6 @@ This document is intended for people that are familiar with the object model of
 [Knative Eventing](../README.md). You don't need to be an expert, but do need to
 know roughly how things fit together.
 
-## Version
-
-This Debugging content supports version v0.8.0 or later of
-[Knative Eventing](https://github.com/knative/eventing/releases/) and the
-[Eventing-contrib resources](https://github.com/knative/eventing-contrib/releases/).
-
 ## Prerequisites
 
 1. Setup [Knative Eventing and an Eventing-contrib resource](../README.md).
@@ -364,7 +358,7 @@ However if we see something like:
 
 <!--
  NOTE: This error has been produced by settings spec.ports[0].port to 8081
- kubectl patch -n knative-debug svc svc -p '{"spec":{"ports": [{"port": 8081, "targetPort":8080}]}}' --type='merge' 
+ kubectl patch -n knative-debug svc svc -p '{"spec":{"ports": [{"port": 8081, "targetPort":8080}]}}' --type='merge'
 -->
 ```shell
 {"level":"info","ts":"2019-08-16T16:10:16.859Z","logger":"inmemorychannel-dispatcher.in-memory-channel-dispatcher","caller":"provisioners/message_receiver.go:140","msg":"Received request for chan-kn-channel.knative-debug.svc.cluster.local","knative.dev/controller":"in-memory-channel-dispatcher"}
diff --git a/docs/eventing/samples/parallel/README.md b/docs/eventing/samples/parallel/README.md
@@ -6,8 +6,8 @@ various flows.
 All examples require:
 
 - A Kubernetes cluster with
-  - Knative Eventing v0.11+
-  - Knative Serving v0.8+
+  - Knative Eventing
+  - Knative Serving
 
 All examples are using the
 [default channel template](../../channels/default-channels.md).
diff --git a/docs/install/Knative-custom-install.md b/docs/install/Knative-custom-install.md
@@ -184,27 +184,6 @@ for details about installing the various supported observability plugins.
 **Tip**: From the table above, copy and paste the URL and filename into the
 commands below.
 
-1. If you are upgrading from Knative 0.3.x: Update your domain and static IP
-   address to be associated with the LoadBalancer `istio-ingressgateway` instead
-   of `knative-ingressgateway`. Then run the following to clean up leftover
-   resources:
-
-   ```
-   kubectl delete svc knative-ingressgateway -n istio-system
-   kubectl delete deploy knative-ingressgateway -n istio-system
-   ```
-
-   If you have the Knative Eventing Sources component installed, you will also
-   need to delete the following resource before upgrading:
-
-   ```
-   kubectl delete statefulset/controller-manager -n knative-sources
-   ```
-
-   While the deletion of this resource during the upgrade process will not
-   prevent modifications to Eventing Source resources, those changes will not be
-   completed until the upgrade process finishes.
-
 1. To install Knative components or plugins, specify the filenames in the
    `kubectl apply` command. To prevent install failures due to race conditions,
    run the install command first with the `-l knative.dev/crd-install=true`
@@ -267,9 +246,9 @@ commands below.
           --filename https://github.com/knative/serving/releases/download/{{< version >}}/monitoring.yaml
         ```
 
-   - To install all three Knative components without an observability plugin, 
+   - To install all three Knative components without an observability plugin,
      run the following commands.
-     
+
      1. Installs the CRDs only:
 
         ```bash
@@ -311,7 +290,7 @@ See the following topics for information about installing other Knative features
 
 - [Installing logging, metrics, and traces](../serving/installing-logging-metrics-traces.md):
   Learn how to install and set up the various observability plugins.
-   
+
 - [Installing Cert-Manager](../serving/installing-cert-manager.md):
   Learn how to set up and configure secure HTTPS requests and enable
   [automatic TLS cert provisioning](../serving/using-auto-tls.md).
diff --git a/docs/install/Knative-with-AKS.md b/docs/install/Knative-with-AKS.md
@@ -156,27 +156,6 @@ The following commands install all available Knative components. To customize
 your Knative installation, see
 [Performing a Custom Knative Installation](./Knative-custom-install.md).
 
-1. If you are upgrading from Knative 0.3.x: Update your domain and static IP
-   address to be associated with the LoadBalancer `istio-ingressgateway` instead
-   of `knative-ingressgateway`. Then run the following to clean up leftover
-   resources:
-
-   ```
-   kubectl delete svc knative-ingressgateway -n istio-system
-   kubectl delete deploy knative-ingressgateway -n istio-system
-   ```
-
-   If you have the Knative Eventing Sources component installed, you will also
-   need to delete the following resource before upgrading:
-
-   ```
-   kubectl delete statefulset/controller-manager -n knative-sources
-   ```
-
-   While the deletion of this resource during the upgrade process will not
-   prevent modifications to Eventing Source resources, those changes will not be
-   completed until the upgrade process finishes.
-
 1. To install Knative, first install the CRDs by running the `kubectl apply`
    command once with the `--selector knative.dev/crd-install=true` flag. This
    prevents race conditions during the install, which cause intermittent errors:
diff --git a/docs/install/Knative-with-ICP.md b/docs/install/Knative-with-ICP.md
@@ -136,27 +136,6 @@ The following commands install all available Knative components as well as the
 standard set of observability plugins. To customize your Knative installation,
 see [Performing a Custom Knative Installation](./Knative-custom-install.md).
 
-1. If you are upgrading from Knative 0.3.x: Update your domain and static IP
-   address to be associated with the LoadBalancer `istio-ingressgateway` instead
-   of `knative-ingressgateway`. Then run the following to clean up leftover
-   resources:
-
-   ```
-   kubectl delete svc knative-ingressgateway -n istio-system
-   kubectl delete deploy knative-ingressgateway -n istio-system
-   ```
-
-   If you have the Knative Eventing Sources component installed, you will also
-   need to delete the following resource before upgrading:
-
-   ```
-   kubectl delete statefulset/controller-manager -n knative-sources
-   ```
-
-   While the deletion of this resource during the upgrade process will not
-   prevent modifications to Eventing Source resources, those changes will not be
-   completed until the upgrade process finishes.
-
 1. Run the following commands to install Knative:
 
    ```shell
@@ -248,5 +227,3 @@ curl -L https://github.com/knative/serving/releases/download/{{< version >}}/mon
  | sed 's/LoadBalancer/NodePort/' \
  | kubectl delete --filename -
 ```
-
-
diff --git a/docs/install/Knative-with-MicroK8s.md b/docs/install/Knative-with-MicroK8s.md
@@ -8,7 +8,7 @@ type: "docs"
 [MicroK8s](https://microk8s.io) is a lightweight, powerful fully-conformant Kubernetes that tracks upstream releases and makes clustering trivial. It can run on any flavor of Linux that supports [Snap](https://snapcraft.io) packages. It can run on Windows and Mac OS using [Mutlipass](https://multipass.run).
 This guide walks you through the installation of Knative using MicroK8s.
 
-If you need help or support please reach out on the [Kubernetes forum](https://discuss.kubernetes.io/tags/microk8s) or Kubernetes.slack.com channel #microk8s. 
+If you need help or support please reach out on the [Kubernetes forum](https://discuss.kubernetes.io/tags/microk8s) or Kubernetes.slack.com channel #microk8s.
 Additionally if you wish to contribute or report an issue please visit [MicroK8s Github](https://github.com/ubuntu/microk8s).
 
 You can find [guides for other platforms here](./README.md).
@@ -30,9 +30,7 @@ sudo snap alias microk8s.kubectl kubectl
 ```shell
 echo 'N;' | microk8s.enable knative
 ```
-This command will install Knative Serving version 0.7.1 and Eventing version 0.7.1 components.
-
-NOTE: As of this writing, MicroK8s comes with version 0.7.1, this doc will be updated to reflect versioning changes. 
+This command will install the Knative Serving 0.9.0 and Knative Eventing 0.9.0 components.
 
 You can check the status of Knative pods using the following commands:
 
diff --git a/docs/install/Knative-with-OpenShift.md b/docs/install/Knative-with-OpenShift.md
diff --git a/docs/install/Knative-with-any-k8s.md b/docs/install/Knative-with-any-k8s.md
@@ -39,27 +39,6 @@ The following commands install all available Knative components. To customize
 your Knative installation, see
 [Performing a Custom Knative Installation](./Knative-custom-install.md).
 
-1. If you are upgrading from Knative 0.3.x: Update your domain and static IP
-   address to be associated with the LoadBalancer `istio-ingressgateway` instead
-   of `knative-ingressgateway`. Then run the following to clean up leftover
-   resources:
-
-   ```bash
-   kubectl delete svc knative-ingressgateway -n istio-system
-   kubectl delete deploy knative-ingressgateway -n istio-system
-   ```
-
-   If you have the Knative Eventing Sources component installed, you will also
-   need to delete the following resource before upgrading:
-
-   ```
-   kubectl delete statefulset/controller-manager -n knative-sources
-   ```
-
-   While the deletion of this resource during the upgrade process will not
-   prevent modifications to Eventing Source resources, those changes will not be
-   completed until the upgrade process finishes.
-
 1. To install Knative, first install the CRDs by running the `kubectl apply`
    command once with the `-l knative.dev/crd-install=true` flag. This prevents
    race conditions during the install, which cause intermittent errors:
diff --git a/docs/install/check-install-version.md b/docs/install/check-install-version.md
@@ -5,33 +5,19 @@ weight: 20
 type: "docs"
 ---
 
-
-To obtain the version of the Knative component that you have running on your cluster, you query for the 
+To obtain the version of the Knative component that you have running on your cluster, you query for the
 `[component].knative.dev/release` label with the following commands:
 
 * Knative Serving
-   ```bash
-   kubectl get namespace knative-serving -o 'go-template={{index .metadata.labels
-   "serving.knative.dev/release"}}'
-   ```
-
-* Knative Eventing
-   ```bash
-   kubectl get namespace knative-eventing -o 'go-template={{index .metadata.labels
-   "eventing.knative.dev/release"}}'
-   ```
 
-## Older versions
+  ```bash
+  kubectl get namespace knative-serving -o 'go-template={{index .metadata.labels
+  "serving.knative.dev/release"}}'
+  ```
 
-Early versions of Knative Eventing and Serving do not have release version
-labels on those components. Release labels were added in the following releases:
-
-* Knative Serving 0.4.0
-* Knative Eventing 0.7.0
-
-If you have an earlier version that excludes release labels, you must obtain the
-version from the container images of your Knative controllers:
+* Knative Eventing
 
-1. Query your Knative Controller to receive the `Image` URL. For example, you can run `kubectl describe deploy controller --namespace knative-serving` or `kubectl describe deploy eventing-controller --namespace knative-eventing`
-1. Navigate to the full `gcr.io` URL with your browser. 
-1. Review the contents for the release version from with the `Tags` section.
+  ```bash
+  kubectl get namespace knative-eventing -o 'go-template={{index .metadata.labels
+  "eventing.knative.dev/release"}}'
+  ```
diff --git a/docs/serving/debugging-application-issues.md b/docs/serving/debugging-application-issues.md
@@ -91,8 +91,7 @@ look deeper using Istio
 
 ### Check Ingress status
 
-Before Knative 0.3 we use a LoadBalancer service call `knative-ingressgateway`
-to handle ingress. Since Knative 0.3 we now use `istio-ingressgateway` Service.
+Knative uses a LoadBalancer service called `istio-ingressgateway` Service.
 
 To check the IP address of your Ingress, use
 
diff --git a/docs/serving/services/_index.md b/docs/serving/services/_index.md
@@ -0,0 +1,6 @@
+---
+title: "Knative Services"
+linkTitle: "Services"
+weight: 10
+type: "docs"
+---
diff --git a/docs/serving/services/creating-services.md b/docs/serving/services/creating-services.md
@@ -1,6 +1,7 @@
 ---
-title: Creating Knative Services
-type: “docs”
+title: "Creating Knative services"
+weight: 10
+type: "docs"
 ---
 
 Knative Services are used to deploy an application. Each Knative Service is defined by a Route and a Configuration, which have the same name as the Service, contained in a YAML file. Every time the Configuration is updated, a new Revision is created.
diff --git a/docs/serving/using-a-custom-domain.md b/docs/serving/using-a-custom-domain.md
@@ -101,12 +101,8 @@ You should see the full customized domain: `helloworld-go.default.mydomain.com`.
 And you can check the IP address of your Knative gateway by running:
 
 ```shell
-# In Knative 0.2.x and prior versions, the `knative-ingressgateway` service was used instead of `istio-ingressgateway`.
-export INGRESSGATEWAY=knative-ingressgateway
+export INGRESSGATEWAY=istio-ingressgateway
 
-# The use of `knative-ingressgateway` is deprecated in Knative v0.3.x.
-# Use `istio-ingressgateway` instead, since `knative-ingressgateway`
-# will be removed in Knative v0.4.
 if kubectl get configmap config-istio -n knative-serving &> /dev/null; then
     export INGRESSGATEWAY=istio-ingressgateway
 fi
@@ -174,5 +170,3 @@ If you are using Google Cloud DNS, you can find step-by-step instructions in the
 Once the domain update has propagated, you can access your app using the fully
 qualified domain name of the deployed route, for example
 `http://helloworld-go.default.mydomain.com`
-
-
diff --git a/docs/serving/using-auto-tls.md b/docs/serving/using-auto-tls.md
@@ -16,7 +16,7 @@ You must meet the following prerequisites to enable automatic certificate
 provisioning:
 
 - The following must be installed on your Knative cluter:
-  - [Knative Serving version 0.6.0 or higher](../install/).
+  - [Knative Serving](../install/).
   - [Istio with SDS, version 1.1 or higher](../install/installing-istio.md#installing-istio-with-SDS-to-secure-the-ingress-gateway) or [Gloo, version 0.18.16 or higher](../install/Knative-with-Gloo.md).
     Note: Currently, [Ambassador](https://github.com/datawire/ambassador) is unsupported.
   - [cert-manager version `0.6.1` or higher](./installing-cert-manager.md).
@@ -36,7 +36,7 @@ To enable support for automatic TLS certificate provisioning in Knative:
     ```
 
 1. If `networking-certmanager` is not found, run the following command:
-   
+
     ```shell
     kubectl apply --filename https://github.com/knative/serving/releases/download/{{< version >}}/serving-cert-manager.yaml
     ```
diff --git a/docs/serving/using-cert-manager-on-gcp.md b/docs/serving/using-cert-manager-on-gcp.md
@@ -30,7 +30,7 @@ and Cloud DNS:
 - [Google Cloud DNS](https://cloud.google.com/dns/docs/how-to) must set up and
   configure for your domain.
 - You must have a Knative cluster with the following requirements:
-  - Knative Serving v0.6.0 or higher running.
+  - Knative Serving running.
   - The Knative cluster must be running on Google Cloud Platform. For details
     about installing the Serving component, see the
     [Knative installation guides](../install/).
