mirror of https://github.com/knative/docs.git
Remove outdated YAML for Hugo (#4114)
This commit is contained in:
Ashleigh Brennan
GitHub
parent
7ee18955f1
commit
f95fdef486
|
|
@ -144,7 +144,6 @@ nav:
|
|||
- Code samples:
|
||||
- Overview: serving/samples/README.md
|
||||
- Cloud Events apps:
|
||||
- Overview: serving/samples/cloudevents/README.md
|
||||
- .NET: serving/samples/cloudevents/cloudevents-dotnet/README.md
|
||||
- Go: serving/samples/cloudevents/cloudevents-go/README.md
|
||||
- Node.js: serving/samples/cloudevents/cloudevents-nodejs/README.md
|
||||
|
|
@ -154,7 +153,6 @@ nav:
|
|||
- GitHub Webhook - Go: serving/samples/gitwebhook-go/README.md
|
||||
- gRPC Server - Go: serving/samples/grpc-ping-go/README.md
|
||||
- Hello world apps:
|
||||
- Overview: serving/samples/hello-world/README.md
|
||||
- .NET: serving/samples/hello-world/helloworld-csharp/README.md
|
||||
- Go: serving/samples/hello-world/helloworld-go/README.md
|
||||
- Java (Spark): serving/samples/hello-world/helloworld-java-spark/README.md
|
||||
|
|
|
|||
|
|
@ -1,12 +1,4 @@
|
|||
---
|
||||
title: "Welcome to Knative"
|
||||
linkTitle: "Documentation"
|
||||
weight: 10
|
||||
type: "docs"
|
||||
showlandingtoc: "false"
|
||||
aliases:
|
||||
- /docs/concepts/overview.md
|
||||
---
|
||||
# Welcome to Knative
|
||||
|
||||
The Knative project provides a set of [Kubernetes](https://kubernetes.io) components that introduce event-driven and serverless capabilities for Kubernetes clusters.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Checking the version of your Knative components"
|
||||
linkTitle: "Checking your install version"
|
||||
weight: 20
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Checking the version of your Knative components
|
||||
|
||||
To obtain the version of the Knative component that you have running on your cluster, you query for the
|
||||
|
|
|
|||
|
|
@ -1,13 +1,3 @@
|
|||
---
|
||||
title: "CLI tools"
|
||||
weight: 04
|
||||
type: "docs"
|
||||
showlandingtoc: "false"
|
||||
aliases:
|
||||
- /docs/reference/resources
|
||||
- /docs/client/connecting-kn-to-your-cluster
|
||||
---
|
||||
|
||||
# CLI tools
|
||||
|
||||
The following CLI tools are supported for use with Knative.
|
||||
|
|
|
|||
|
|
@ -1,9 +1,3 @@
|
|||
---
|
||||
title: "Customizing kn"
|
||||
weight: 03
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Customizing kn
|
||||
|
||||
You can customize your `kn` CLI setup by creating a `config.yaml` configuration file. You can provide this configuration by using the `--config` flag, otherwise the configuration is picked up from a default location. The default configuration location conforms to the [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html), and is different for Unix systems and Windows systems.
|
||||
|
|
|
|||
|
|
@ -1,11 +1,3 @@
|
|||
---
|
||||
title: "Installing kn"
|
||||
weight: 02
|
||||
type: "docs"
|
||||
aliases:
|
||||
- /docs/install/install-kn
|
||||
---
|
||||
|
||||
# Installing kn
|
||||
|
||||
This guide provides details about how you can install the Knative `kn` CLI.
|
||||
|
|
|
|||
|
|
@ -1,9 +1,3 @@
|
|||
---
|
||||
title: "kn plugins"
|
||||
weight: 04
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# kn plugins
|
||||
|
||||
The `kn` CLI supports the use of plugins. Plugins enable you to extend the functionality of your `kn` installation by adding custom commands and other shared commands that are not part of the core distribution of `kn`.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Accessing CloudEvent traces"
|
||||
#linkTitle: "OPTIONAL_ALTERNATE_NAV_TITLE"
|
||||
weight: 85
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Accessing CloudEvent traces
|
||||
|
||||
Depending on the request tracing tool that you have installed on your Knative
|
||||
|
|
|
|||
|
|
@ -1,12 +1,3 @@
|
|||
---
|
||||
title: "Brokers"
|
||||
weight: 60
|
||||
type: "docs"
|
||||
showlandingtoc: "false"
|
||||
aliases:
|
||||
- docs/eventing/broker/alternate
|
||||
---
|
||||
|
||||
# Brokers
|
||||
|
||||
Brokers are Kubernetes [custom resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) that define an event mesh for collecting a pool of [CloudEvents](https://cloudevents.io/). Brokers provide a discoverable endpoint, `status.address`, for event ingress, and triggers for event delivery. Event producers can send events to a broker by POSTing the event to the `status.address.url` of the broker.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Creating a broker"
|
||||
weight: 01
|
||||
type: "docs"
|
||||
showlandingtoc: "false"
|
||||
---
|
||||
|
||||
# Creating a broker
|
||||
|
||||
Once you have installed Knative Eventing, you can create an instance of the multi-tenant (MT) channel-based broker that is provided by default. The default backing channel type for an MT channel-based broker is InMemoryChannel.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Broker configuration example"
|
||||
weight: 04
|
||||
type: "docs"
|
||||
showlandingtoc: "false"
|
||||
---
|
||||
|
||||
# Broker configuration example
|
||||
|
||||
The following is a full example of a multi-tenant (MT) channel-based Broker object which shows the possible configuration options that you can modify:
|
||||
|
|
|
|||
|
|
@ -1,11 +1,3 @@
|
|||
---
|
||||
title: "Apache Kafka Broker"
|
||||
weight: 10
|
||||
type: "docs"
|
||||
aliases:
|
||||
- docs/eventing/broker/kafka-broker
|
||||
---
|
||||
|
||||
# Apache Kafka Broker
|
||||
|
||||
The Apache Kafka Broker is a native Broker implementation, that reduces
|
||||
|
|
|
|||
|
|
@ -1,12 +1,3 @@
|
|||
---
|
||||
title: "Triggers"
|
||||
weight: 02
|
||||
type: "docs"
|
||||
showlandingtoc: "false"
|
||||
aliases:
|
||||
- docs/eventing/triggers
|
||||
---
|
||||
|
||||
# Triggers
|
||||
|
||||
A trigger represents a desire to subscribe to events from a specific broker.
|
||||
|
|
|
|||
|
|
@ -1,12 +1,3 @@
|
|||
---
|
||||
title: "Channels"
|
||||
weight: 40
|
||||
type: "docs"
|
||||
showlandingtoc: "false"
|
||||
aliases:
|
||||
- /docs/eventing/channels/default-channels
|
||||
---
|
||||
|
||||
# Channels
|
||||
|
||||
Channels are Kubernetes [custom resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) that define a single event forwarding and persistence layer.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Channel types and defaults
|
||||
Knative uses two types of Channels:
|
||||
|
||||
Knative uses two types of Channels:
|
||||
|
||||
* A generic Channel object.
|
||||
* Channel implementations that each have their own custom resource definitions (CRDs), such as
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Debugging Knative Eventing"
|
||||
linkTitle: "Debugging"
|
||||
weight: 80
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Debugging Knative Eventing
|
||||
|
||||
This is an evolving document on how to debug a non-working Knative Eventing
|
||||
|
|
@ -373,11 +366,5 @@ However if we see something like:
|
|||
Then we know there was a problem posting to
|
||||
`http://svc.knative-debug.svc.cluster.local/`.
|
||||
|
||||
TODO Finish this section. Especially after the Channel Dispatcher emits K8s
|
||||
events about failures.
|
||||
|
||||
#### `fn`
|
||||
|
||||
TODO Fill in this section.
|
||||
|
||||
# TODO Finish the guide.
|
||||
<!--TODO Finish this section. Especially after the Channel Dispatcher emits K8s
|
||||
events about failures.-->
|
||||
|
|
|
|||
|
|
@ -1,9 +1,3 @@
|
|||
---
|
||||
title: "Event registry"
|
||||
weight: 25
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Event registry
|
||||
|
||||
## Overview
|
||||
|
|
|
|||
|
|
@ -1,11 +1,3 @@
|
|||
---
|
||||
title: "Eventing Flows"
|
||||
linkTitle: "Flows"
|
||||
weight: 31
|
||||
type: "docs"
|
||||
showlandingtoc: "false"
|
||||
---
|
||||
|
||||
# Eventing Flows
|
||||
|
||||
Knative Eventing provides a collection of [custom resource definitions (CRDs)](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) that you can use to define event flows:
|
||||
|
|
|
|||
|
|
@ -1,11 +1,3 @@
|
|||
---
|
||||
title: "Parallel"
|
||||
weight: 20
|
||||
type: "docs"
|
||||
aliases:
|
||||
- /docs/eventing/parallel.md
|
||||
---
|
||||
|
||||
# Parallel
|
||||
|
||||
Parallel CRD provides a way to easily define a list of branches, each receiving
|
||||
|
|
|
|||
|
|
@ -1,13 +1,3 @@
|
|||
---
|
||||
title: "Sequence"
|
||||
weight: 20
|
||||
type: "docs"
|
||||
aliases:
|
||||
- /docs/eventing/sequence.md
|
||||
- /docs/eventing/samples/sequence
|
||||
showlandingtoc: "false"
|
||||
---
|
||||
|
||||
# Sequence
|
||||
|
||||
Sequence CRD provides a way to define an in-order list of functions that will be
|
||||
|
|
|
|||
|
|
@ -1,12 +1,3 @@
|
|||
---
|
||||
title: "Sequence wired to event-display"
|
||||
linkTitle: "Displaying sequence output"
|
||||
weight: 20
|
||||
type: "docs"
|
||||
aliases:
|
||||
- /docs/eventing/samples/sequence/sequence-replay-to-event-display
|
||||
---
|
||||
|
||||
# Sequence wired to event-display
|
||||
|
||||
We are going to create the following logical configuration. We create a
|
||||
|
|
|
|||
|
|
@ -1,12 +1,3 @@
|
|||
---
|
||||
title: "Sequence wired to another Sequence"
|
||||
linkTitle: "Using Sequences in series"
|
||||
weight: 20
|
||||
type: "docs"
|
||||
aliases:
|
||||
- /docs/eventing/samples/sequence/sequence-reply-to-sequence
|
||||
---
|
||||
|
||||
# Sequence wired to another Sequence
|
||||
|
||||
We are going to create the following logical configuration. We create a
|
||||
|
|
|
|||
|
|
@ -1,12 +1,3 @@
|
|||
---
|
||||
title: "Sequence terminal"
|
||||
linkTitle: "Create additional events"
|
||||
weight: 20
|
||||
type: "docs"
|
||||
aliases:
|
||||
- /docs/eventing/samples/sequence/sequence-terminal
|
||||
---
|
||||
|
||||
# Sequence terminal
|
||||
|
||||
We are going to create the following logical configuration. We create a
|
||||
|
|
|
|||
|
|
@ -1,12 +1,3 @@
|
|||
---
|
||||
title: "Using Sequence with Broker and Trigger"
|
||||
linkTitle: "Using with Broker and Trigger"
|
||||
weight: 20
|
||||
type: "docs"
|
||||
aliases:
|
||||
- /docs/eventing/samples/sequence/sequence-with-broker-trigger
|
||||
---
|
||||
|
||||
# Using Sequence with Broker and Trigger
|
||||
|
||||
We are going to create the following logical configuration. We create a
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "CloudAuditLogsSource"
|
||||
linkTitle: "CloudAuditLogsSource"
|
||||
weight: 20
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# CloudAuditLogsSource
|
||||
|
||||
Please refer to the [example](https://github.com/google/knative-gcp/blob/master/docs/examples/cloudauditlogssource/README.md) in knative-gcp.
|
||||
|
|
|
|||
|
|
@ -1,12 +1,3 @@
|
|||
---
|
||||
title: "CloudPubSubSource"
|
||||
linkTitle: "CloudPubSubSource"
|
||||
weight: 20
|
||||
type: "docs"
|
||||
aliases:
|
||||
- /docs/eventing/samples/gcp-pubsub-source/README.md
|
||||
---
|
||||
|
||||
# CloudPubSubSource
|
||||
|
||||
Please refer to the [example](https://github.com/google/knative-gcp/blob/master/docs/examples/cloudpubsubsource/README.md) in knative-gcp.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "CloudSchedulerSource"
|
||||
linkTitle: "CloudSchedulerSource"
|
||||
weight: 20
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# CloudSchedulerSource
|
||||
|
||||
Please refer to the [example](https://github.com/google/knative-gcp/blob/master/docs/examples/cloudschedulersource/README.md) in knative-gcp.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "CloudStorageSource"
|
||||
linkTitle: "CloudStorageSource"
|
||||
weight: 20
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# CloudStorageSource
|
||||
|
||||
Please refer to the [example](https://github.com/google/knative-gcp/blob/master/docs/examples/cloudstoragesource/README.md) in knative-gcp.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Container Source Example"
|
||||
linkTitle: "Container source"
|
||||
weight: 10
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Container Source Example
|
||||
|
||||
ContainerSource will start a container image which will generate events under
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Knative Eventing - Hello World app"
|
||||
linkTitle: "Hello World"
|
||||
weight: 10
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Knative Eventing - Hello World app
|
||||
|
||||
Following examples include a simple web app written in the language of your choice that you can
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Hello World - Golang"
|
||||
linkTitle: "GO"
|
||||
weight: 20
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Hello World - Golang
|
||||
|
||||
A simple web app written in Go that you can use to test knative eventing. It
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Binding running services to an IoT core"
|
||||
linkTitle: "IoT core"
|
||||
weight: 40
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Binding running services to an IoT core
|
||||
|
||||
This sample shows how to bind a running service to an
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Apache Kafka Binding Example"
|
||||
linkTitle: "Binding Example"
|
||||
weight: 20
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Apache Kafka Binding Example
|
||||
|
||||
KafkaBinding is responsible for injecting Kafka bootstrap connection information
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Multiple Cases"
|
||||
linkTitle: "Multiple Cases"
|
||||
weight: 20
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Multiple Cases
|
||||
|
||||
We are going to create a Parallel with two branches:
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Mutual Exclusive Cases"
|
||||
linkTitle: "Mutual Exclusivity"
|
||||
weight: 20
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Mutual Exclusive Cases
|
||||
|
||||
In this example, we are going to see how we can create a Parallel with mutually
|
||||
|
|
|
|||
|
|
@ -1,11 +1,3 @@
|
|||
---
|
||||
title: "Knative Eventing Sugar Controller"
|
||||
linkTitle: "Sugar Controller"
|
||||
weight: 40
|
||||
type: "docs"
|
||||
showlandingtoc: "true"
|
||||
---
|
||||
|
||||
# Knative Eventing Sugar Controller
|
||||
|
||||
Knative Eventing Sugar Controller will react to special labels and annotations
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Knative Offerings"
|
||||
linkTitle: "Knative Offerings"
|
||||
weight: 07
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Knative Offerings
|
||||
|
||||
Knative has a rich community with many vendors participating, and many of those
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Knative Reference Documentation"
|
||||
linkTitle: "Reference"
|
||||
weight: 100
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Knative Reference Documentation
|
||||
|
||||
Knative reference documentation.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,4 @@
|
|||
---
|
||||
title: "Knative Release Notes"
|
||||
linkTitle: "Release notes"
|
||||
weight: 10
|
||||
type: "docs"
|
||||
showlandingtoc: "false"
|
||||
---
|
||||
# Knative release notes
|
||||
|
||||
For details about the Knative releases, see the following pages:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Knative code samples"
|
||||
linkTitle: "Code samples"
|
||||
weight: 90
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Knative code samples
|
||||
|
||||
Find and use Knative code samples to help you get up and running with common use
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Knative Serving"
|
||||
weight: 05
|
||||
type: "docs"
|
||||
showlandingtoc: "false"
|
||||
---
|
||||
|
||||
# Knative Serving
|
||||
|
||||
Knative Serving builds on Kubernetes and Istio to support deploying and serving
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Accessing request traces"
|
||||
#linkTitle: "OPTIONAL_ALTERNATE_NAV_TITLE"
|
||||
weight: 15
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Accessing request traces
|
||||
|
||||
Depending on the request tracing tool that you have installed on your Knative
|
||||
|
|
|
|||
|
|
@ -1,12 +1,3 @@
|
|||
---
|
||||
title: "Autoscaling"
|
||||
linkTitle: "Autoscaling"
|
||||
weight: 20
|
||||
type: "docs"
|
||||
aliases:
|
||||
- /docs/serving/configuring-autoscaling/
|
||||
---
|
||||
|
||||
# Autoscaling
|
||||
|
||||
One of the main features of Knative is automatic scaling of replicas for an application to closely match incoming demand, including scaling applications to zero if no traffic is being received.
|
||||
|
|
|
|||
|
|
@ -1,12 +1,3 @@
|
|||
---
|
||||
title: "Autoscale Sample App - Go"
|
||||
linkTitle: "Autoscale Sample App - Go"
|
||||
weight: 100
|
||||
type: "docs"
|
||||
aliases:
|
||||
- /docs/serving/samples/autoscale-go
|
||||
---
|
||||
|
||||
# Autoscale Sample App - Go
|
||||
|
||||
A demonstration of the autoscaling capabilities of a Knative Serving Revision.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Metrics"
|
||||
linkTitle: "Metrics"
|
||||
weight: 03
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Metrics
|
||||
|
||||
The metric configuration defines which metric type is watched by the Autoscaler.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Targets"
|
||||
linkTitle: "Targets"
|
||||
weight: 04
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Targets
|
||||
|
||||
Configuring a target provide the Autoscaler with a value that it tries to maintain for the configured metric for a revision.
|
||||
|
|
@ -56,6 +49,3 @@ The `target` annotation, used to configure per-revision targets, is _metric agn
|
|||
autoscaler:
|
||||
container-concurrency-target-default: "200"
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Additional autoscaling configuration for Knative Pod Autoscaler"
|
||||
linkTitle: "Additional autoscaling configuration for Knative Pod Autoscaler"
|
||||
weight: 60
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Additional autoscaling configuration for Knative Pod Autoscaler
|
||||
|
||||
The following settings are specific to the Knative Pod Autoscaler (KPA).
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Configuring the requests per second (RPS) target"
|
||||
linkTitle: "Configuring the requests per second (RPS) target"
|
||||
weight: 50
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Configuring the requests per second (RPS) target
|
||||
|
||||
This setting specifies a target for requests-per-second per replica of an application.
|
||||
|
|
@ -56,6 +49,3 @@ This setting specifies a target for requests-per-second per replica of an applic
|
|||
autoscaler:
|
||||
requests-per-second-target-default: "150"
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Configuring scale bounds"
|
||||
linkTitle: "Configuring scale bounds"
|
||||
weight: 50
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Configuring scale bounds
|
||||
|
||||
You can configure upper and lower bounds to control autoscaling behavior.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Configuring scale to zero"
|
||||
linkTitle: "Configuring scale to zero"
|
||||
weight: 20
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Configuring scale to zero
|
||||
|
||||
!!! warning
|
||||
|
|
|
|||
|
|
@ -1,12 +1,3 @@
|
|||
---
|
||||
title: "Getting Started with App Deployment"
|
||||
linkTitle: "Getting started"
|
||||
weight: 01
|
||||
type: "docs"
|
||||
aliases:
|
||||
- /docs/install/getting-started-knative-app/
|
||||
---
|
||||
|
||||
# Getting Started with App Deployment
|
||||
|
||||
This guide shows you how to deploy an app using Knative, then interact with it
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Installing cert-manager for TLS certificates"
|
||||
linkTitle: "Installing cert-manager"
|
||||
weight: 62
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Installing cert-manager for TLS certificates
|
||||
|
||||
Install the [Cert-Manager](https://github.com/jetstack/cert-manager) tool to
|
||||
|
|
|
|||
|
|
@ -1,9 +1,3 @@
|
|||
---
|
||||
title: "Load balancing"
|
||||
weight: 30
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Load balancing
|
||||
|
||||
You can turn on Knative load balancing, by placing the _Activator service_ in the request path to act as a load balancer.
|
||||
|
|
|
|||
|
|
@ -1,12 +1,3 @@
|
|||
---
|
||||
title: "Configuring target burst capacity"
|
||||
linkTitle: "Configuring target burst capacity"
|
||||
weight: 50
|
||||
type: "docs"
|
||||
aliases:
|
||||
- /docs/serving/autoscaling/target-burst-capacity
|
||||
---
|
||||
|
||||
# Configuring target burst capacity
|
||||
|
||||
_Target burst capacity_ is a [global and per-revision](../../serving/autoscaling/autoscaler-types.md#global-versus-per-revision-settings) integer setting that determines the size of traffic burst a Knative application can handle without buffering.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Knative Serving code samples"
|
||||
linkTitle: "Code samples"
|
||||
weight: 100
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Knative Serving code samples
|
||||
|
||||
Use the following code samples to help you understand the various Knative
|
||||
|
|
|
|||
|
|
@ -1,6 +0,0 @@
|
|||
---
|
||||
title: "Knative Serving 'Cloud Events' samples"
|
||||
linkTitle: "Cloud Events apps"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Cloud Events - .NET Core"
|
||||
linkTitle: ".NET"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Cloud Events - .NET Core
|
||||
|
||||
A simple web app written in ASP.NET and C# that can receive and send Cloud Events that you
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Cloud Events - Go"
|
||||
linkTitle: "Go"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Cloud Events - Go
|
||||
|
||||
A simple web app written in Go that can receive and send Cloud Events that you
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Cloud Events - Node.js"
|
||||
linkTitle: "Node.js"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Cloud Events - Node.js
|
||||
|
||||
A simple web app written in Node.js that can receive and send Cloud Events that you
|
||||
|
|
@ -134,6 +127,3 @@ To remove the sample app from your cluster, delete the service.
|
|||
```bash
|
||||
kn service delete cloudevents-nodejs
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Cloud Events - Rust"
|
||||
linkTitle: "Rust"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Cloud Events - Rust
|
||||
|
||||
A simple web app written in Rust using [Actix web](https://github.com/actix/actix-web)
|
||||
|
|
@ -166,6 +159,3 @@ To remove the sample app from your cluster, delete the service.
|
|||
```bash
|
||||
kn service delete cloudevents-rust
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Cloud Events - Java and Spring"
|
||||
linkTitle: "Java and Spring"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Cloud Events - Java and Spring
|
||||
|
||||
A simple web app written in Java using Spring Cloud Function that can receive CloudEvents. It
|
||||
|
|
@ -150,6 +143,3 @@ To remove the sample app from your cluster, delete the service:
|
|||
```bash
|
||||
kn service delete cloudevents-spring
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Cloud Events - Java and Vert.x"
|
||||
linkTitle: "Java and Vert.x"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Cloud Events - Java and Vert.x
|
||||
|
||||
A simple web app written in Java using Vert.x that can receive CloudEvents. It
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "GitHub webhook sample - Go"
|
||||
linkTitle: "GitHub Webhook - Go"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# GitHub webhook sample - Go
|
||||
|
||||
A handler written in Go that demonstrates interacting with GitHub through a
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "gRPC Server - Go"
|
||||
#linkTitle: ""
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# gRPC Server - Go
|
||||
|
||||
A [gRPC](https://grpc.io) server written in Go.
|
||||
|
|
@ -48,8 +41,8 @@ for production containers.
|
|||
3. Update the `service.yaml` file in the project to reference the published image from step 1.
|
||||
|
||||
Replace `{username}` in `service.yaml` with your Docker Hub user name:
|
||||
|
||||
|
||||
|
||||
|
||||
```yaml
|
||||
apiVersion: serving.knative.dev/v1
|
||||
kind: Service
|
||||
|
|
@ -64,7 +57,7 @@ for production containers.
|
|||
ports:
|
||||
- name: h2c
|
||||
containerPort: 8080
|
||||
```
|
||||
```
|
||||
|
||||
4. Use `kubectl` to deploy the service.
|
||||
|
||||
|
|
@ -116,4 +109,3 @@ docker run --rm {username}/grpc-ping-go \
|
|||
|
||||
The arguments after the container tag `{username}/grpc-ping-go` are used
|
||||
instead of the entrypoint command defined in the Dockerfile `CMD` statement.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +0,0 @@
|
|||
---
|
||||
title: "Knative 'Hello World' samples"
|
||||
linkTitle: "Hello world apps"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Hello world - .NET Core"
|
||||
linkTitle: ".NET"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Hello world - .NET Core
|
||||
|
||||
A simple web app written in C# using .NET Core 3.1 that you can use for testing.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Hello World - Go"
|
||||
linkTitle: "Go"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Hello World - Go
|
||||
|
||||
This guide describes the steps required to to create the `helloworld-go` sample app
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Hello World - Spark Java Framework"
|
||||
linkTitle: "Java (Spark)"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Hello World - Spark Java Framework
|
||||
|
||||
A simple web app written in Java using Spark Java Framework that you can use for
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Hello World - Kotlin"
|
||||
linkTitle: "Kotlin"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Hello World - Kotlin
|
||||
|
||||
A simple web app written in Kotlin using [Ktor](https://ktor.io/) that you can
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Hello World - Node.js"
|
||||
linkTitle: "Node.js"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Hello World - Node.js
|
||||
|
||||
A simple web app written in Node.js that you can use for testing. It reads in an
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Hello World - PHP"
|
||||
linkTitle: "PHP"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Hello World - PHP
|
||||
|
||||
A simple web app written in PHP that you can use for testing. It reads in an env
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Hello World - Python"
|
||||
linkTitle: "Python"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Hello World - Python
|
||||
|
||||
This guide describes the steps required to create the `helloworld-python` sample
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Hello World - Ruby"
|
||||
linkTitle: "Ruby"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Hello World - Ruby
|
||||
|
||||
This guide describes the steps required to create the `helloworld-ruby` sample app and deploy it to your cluster.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Hello World - Scala using Akka HTTP"
|
||||
linkTitle: "Scala"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Hello World - Scala using Akka HTTP
|
||||
|
||||
A microservice which demonstrates how to get set up and running with Knative
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Hello World - Shell"
|
||||
linkTitle: "Shell"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Hello World - Shell
|
||||
|
||||
This guide describes the steps required to create the `helloworld-shell` sample app and deploy it to your
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Routing across multiple Knative services - Go"
|
||||
linkTitle: "Routing services - Go"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Routing across multiple Knative services - Go
|
||||
|
||||
This example shows how to map multiple Knative services to different paths under
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Knative multi-container samples"
|
||||
linkTitle: "multi-container samples"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Knative multi-container samples
|
||||
|
||||
A simple web app written in Go that you can use for multi container testing.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Creating a RESTful Service - Go"
|
||||
linkTitle: "RESTful service - Go"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Creating a RESTful Service - Go
|
||||
|
||||
This "stock ticker" sample demonstrates how to create and run a simple RESTful
|
||||
|
|
|
|||
|
|
@ -1,10 +1,3 @@
|
|||
---
|
||||
title: "Knative Secrets - Go"
|
||||
linkTitle: "Secrets - Go"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Knative Secrets - Go
|
||||
|
||||
A simple web app written in Go that you can use for testing. It demonstrates how
|
||||
|
|
|
|||
|
|
@ -1,9 +1,3 @@
|
|||
---
|
||||
title: "Tag Header Based Routing"
|
||||
weight: 1
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Tag Header Based Routing
|
||||
|
||||
This sample explains the use of tag header based routing.
|
||||
|
|
|
|||
|
|
@ -1,11 +1,4 @@
|
|||
---
|
||||
title: "Setting up custom ingress gateway"
|
||||
linkTitle: "Configuring the ingress gateway"
|
||||
weight: 55
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Setting up custom ingress gateway
|
||||
# Configuring the ingress gateway
|
||||
|
||||
Knative uses a shared ingress Gateway to serve all incoming traffic within
|
||||
Knative service mesh, which is the `knative-ingress-gateway` Gateway under
|
||||
|
|
|
|||
|
|
@ -1,12 +1,3 @@
|
|||
---
|
||||
title: "Configuring HTTPS with TLS certificates"
|
||||
linkTitle: "Configuring HTTPS connections"
|
||||
weight: 60
|
||||
type: "docs"
|
||||
aliases:
|
||||
- /docs/serving/using-an-ssl-cert/
|
||||
---
|
||||
|
||||
# Configuring HTTPS with TLS certificates
|
||||
|
||||
Learn how to configure secure HTTPS connections in Knative using TLS
|
||||
|
|
|
|||
|
|
@ -1,9 +1,3 @@
|
|||
---
|
||||
title: "Exclude namespaces from the Knative webhook"
|
||||
weight: 70
|
||||
type: "docs"
|
||||
---
|
||||
|
||||
# Exclude namespaces from the Knative webhook
|
||||
|
||||
The Knative webhook examines resources that are created, read, updated, or deleted. This includes system namespaces, which can cause issues during an upgrade if the webhook becomes non-responsive. Cluster administrators may want to disable the Knative webhook on system namespaces to prevent issues during upgrades.
|
||||
|
|
@ -15,6 +9,6 @@ apiVersion: v1
|
|||
kind: Namespace
|
||||
metadata:
|
||||
name: knative-dev
|
||||
labels:
|
||||
labels:
|
||||
webhooks.knative.dev/exclude: "true"
|
||||
```
|
||||
```
|
||||
|
|
|
|||
Loading…
Reference in New Issue