updating ApiServerSource example to use v1 (#2880)

* updating ApiServerSource example to use v1

* changed apiserversource.md to v1 apiserversource

* changed badge to v1
This commit is contained in:
capri-xiyue 2020-10-06 17:44:20 -07:00 committed by GitHub
parent 1d46f99575
commit 44f48560a4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 6 additions and 6 deletions

View File

@ -177,7 +177,7 @@ something went wrong during `chan` reconciliation. See
##### `src`
`src` is a
[`ApiServerSource`](https://github.com/knative/eventing/blob/master/pkg/apis/sources/v1beta1/apiserver_types.go).
[`ApiServerSource`](https://github.com/knative/eventing/blob/master/pkg/apis/sources/v1/apiserver_types.go).
First we will verify that `src` is writing to `chan`.

View File

@ -1,4 +1,4 @@
apiVersion: sources.knative.dev/v1beta1
apiVersion: sources.knative.dev/v1
kind: ApiServerSource
metadata:
name: testevents-kafka-03

View File

@ -96,7 +96,7 @@ all the YAML files deployed in this sample to point at that namespace.
block below into it.
```yaml
apiVersion: sources.knative.dev/v1beta1
apiVersion: sources.knative.dev/v1
kind: ApiServerSource
metadata:
name: testevents

View File

@ -1,4 +1,4 @@
apiVersion: sources.knative.dev/v1beta1
apiVersion: sources.knative.dev/v1
kind: ApiServerSource
metadata:
name: testevents

View File

@ -5,7 +5,7 @@ weight: 31
type: "docs"
---
![version](https://img.shields.io/badge/API_Version-v1beta1-red?style=flat-square)
![version](https://img.shields.io/badge/API_Version-v1-red?style=flat-square)
An APIServerSource brings Kubernetes API server events into Knative.
@ -123,7 +123,7 @@ In order to receive kubernetes events, you need to create a concrete APIServerSo
{{% tab name="YAML" %}}
```shell
kubectl -n apiserversource-example apply -f - << EOF
apiVersion: sources.knative.dev/v1beta1
apiVersion: sources.knative.dev/v1
kind: ApiServerSource
metadata:
name: testevents