mirror of https://github.com/knative/docs.git
Format markdown (#1600)
* Format markdown Produced via: `prettier --write --prose-wrap=always $(find -name '*.md' | grep -v vendor | grep -v .github)` /assign @samodell * Remove backticks The indentation and backticks are redundant, so the backticks show up in the `<pre>` block.
This commit is contained in:
parent
e850446660
commit
14cb5fb401
|
@ -35,7 +35,8 @@ to run multiple installation commands.
|
|||
|
||||
## Installing Istio
|
||||
|
||||
> Note: [Ambassador](https://www.getambassador.io/) and [Gloo](https://gloo.solo.io/) are available as an alternative to 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.
|
||||
|
||||
|
|
|
@ -133,7 +133,8 @@ 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.
|
||||
> 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.
|
||||
|
||||
|
|
|
@ -6,8 +6,7 @@ type: "docs"
|
|||
---
|
||||
|
||||
[Ambassador](https://www.getambassador.io/) is a popular Kubernetes-native,
|
||||
open-source API gateway built on
|
||||
[Envoy Proxy](https://www.envoyproxy.io/).
|
||||
open-source API gateway built on [Envoy Proxy](https://www.envoyproxy.io/).
|
||||
|
||||
This guide walks you through the installation of the latest version of Knative
|
||||
using pre-built images.
|
||||
|
@ -26,11 +25,12 @@ This guide assumes that you have already
|
|||
|
||||
## Install Ambassador
|
||||
|
||||
Knative was originally built using Istio to handle cluster networking. While
|
||||
the Istio gateway provides the functionality needed to serve requests to your
|
||||
Knative was originally built using Istio to handle cluster networking. While the
|
||||
Istio gateway provides the functionality needed to serve requests to your
|
||||
application, installing a service mesh to handle north-south traffic carries
|
||||
some operational overhead with it. Ambassador provides a way to get traffic to
|
||||
your Knative application without the overhead or complexity of a full service mesh.
|
||||
your Knative application without the overhead or complexity of a full service
|
||||
mesh.
|
||||
|
||||
You can install Ambassador with `kubectl`:
|
||||
|
||||
|
@ -67,21 +67,19 @@ see Performing a Custom Knative Installation.
|
|||
command once with the `-l knative.dev/crd-install=true` flag. This prevents
|
||||
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/build/releases/download/v0.7.1/build.yaml \
|
||||
--filename https://github.com/knative/serving/releases/download/v0.7.1/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/build/releases/download/v0.7.1/build.yaml \
|
||||
--filename https://github.com/knative/serving/releases/download/v0.7.1/monitoring.yaml
|
||||
```
|
||||
|
||||
> **Notes**:
|
||||
>
|
||||
> - By default, the Knative Serving component installation (`serving.yaml`)
|
||||
|
@ -90,11 +88,11 @@ race conditions during the install, which cause intermittent errors:
|
|||
> 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.
|
||||
> statement to install the controller. Otherwise, you can choose to
|
||||
> install the auto certificates feature and controller at a later time.
|
||||
|
||||
3. Monitor the Knative namespaces and wait until all of the pods come up with
|
||||
a `STATUS` of `Running`:
|
||||
3. Monitor the Knative namespaces and wait until all of the pods come up with a
|
||||
`STATUS` of `Running`:
|
||||
|
||||
```
|
||||
kubectl get pods -w --all-namespaces
|
||||
|
@ -108,8 +106,8 @@ route traffic to a serverless application.
|
|||
1. Create a `Knative Service`
|
||||
|
||||
For this demo, a simple helloworld application written in go will be used.
|
||||
Copy the YAML below to a file called `helloworld-go.yaml` and apply it
|
||||
with `kubectl`
|
||||
Copy the YAML below to a file called `helloworld-go.yaml` and apply it with
|
||||
`kubectl`
|
||||
|
||||
```yaml
|
||||
apiVersion: serving.knative.dev/v1alpha1
|
||||
|
@ -133,10 +131,10 @@ route traffic to a serverless application.
|
|||
|
||||
2. Send a request
|
||||
|
||||
`Knative Service`s are exposed via a `Host` header assigned by Knative.
|
||||
By default, Knative will assign the
|
||||
`Host`: `{service-name}.{namespace}.example.com`. You can verify this by
|
||||
checking the `EXTERNAL-IP` of the `helloworld-go` service created above.
|
||||
`Knative Service`s are exposed via a `Host` header assigned by Knative. By
|
||||
default, Knative will assign the `Host`:
|
||||
`{service-name}.{namespace}.example.com`. You can verify this by checking the
|
||||
`EXTERNAL-IP` of the `helloworld-go` service created above.
|
||||
|
||||
```
|
||||
$ kubectl get service helloworld-go
|
||||
|
@ -165,5 +163,3 @@ manage and route to serverless applications!
|
|||
for Knative serving.
|
||||
- Take a look at the rest of what
|
||||
[Knative has to offer](https://knative.dev/docs/index.html)
|
||||
|
||||
|
||||
|
|
|
@ -58,7 +58,8 @@ minikube start --memory=8192 --cpus=6 \
|
|||
|
||||
## Installing Istio
|
||||
|
||||
> Note: [Ambassador](https://www.getambassador.io/) and [Gloo](https://gloo.solo.io/) are available as an alternative to 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.
|
||||
|
||||
|
|
|
@ -29,9 +29,9 @@ Currently, three options exist which provide this functionality:
|
|||
## Installing Knative with Ambassador
|
||||
|
||||
[Installing with Ambassador](./Knative-with-Ambassador.md) gives us an
|
||||
alternative to installing a service mesh for routing to applications
|
||||
with the Knative Serving component. Note that Istio is required for the
|
||||
Knative Eventing component.
|
||||
alternative to installing a service mesh for routing to applications with the
|
||||
Knative Serving component. Note that Istio is required for the Knative Eventing
|
||||
component.
|
||||
|
||||
## Installing Knative with Gloo
|
||||
|
||||
|
|
Loading…
Reference in New Issue