mirror of https://github.com/knative/eventing.git
Drop master references to knative repos (#5036)
This commit is contained in:
Markus Thömmes
GitHub
parent
32fc262aaa
commit
37e702765d
|
|
@ -10,7 +10,7 @@ assignees: ''
|
|||
**Problem**
|
||||
A short explanation of the problem, including relevant restrictions.
|
||||
|
||||
**[Persona:](https://github.com/knative/eventing/blob/master/docs/personas.md)**
|
||||
**[Persona:](https://github.com/knative/eventing/blob/main/docs/personas.md)**
|
||||
Which persona is this feature for?
|
||||
|
||||
**Exit Criteria**
|
||||
|
|
|
|||
|
|
@ -125,21 +125,21 @@ kubectl -n knative-eventing logs $(kubectl -n knative-eventing get pods -l app=e
|
|||
## Install Channels
|
||||
|
||||
Install the
|
||||
[In-Memory-Channel](https://github.com/knative/eventing/tree/master/config/channels/in-memory-channel)
|
||||
[In-Memory-Channel](https://github.com/knative/eventing/tree/main/config/channels/in-memory-channel)
|
||||
since this is the
|
||||
[default channel](https://github.com/knative/docs/blob/master/docs/eventing/channels/default-channels.md).
|
||||
[default channel](https://github.com/knative/docs/blob/main/docs/eventing/channels/default-channels.md).
|
||||
|
||||
```shell
|
||||
ko apply -f config/channels/in-memory-channel/
|
||||
```
|
||||
|
||||
Depending on your needs you might want to install other
|
||||
[channel implementations](https://github.com/knative/docs/blob/master/docs/eventing/channels/channels-crds.md).
|
||||
[channel implementations](https://github.com/knative/docs/blob/main/docs/eventing/channels/channels-crds.md).
|
||||
|
||||
## Install Broker
|
||||
|
||||
Install the
|
||||
[MT Channel Broker](https://github.com/knative/eventing/tree/master/config/brokers/mt-channel-broker)
|
||||
[MT Channel Broker](https://github.com/knative/eventing/tree/main/config/brokers/mt-channel-broker)
|
||||
or any of the other Brokers available inside the `config/brokers/` directory.
|
||||
|
||||
```shell
|
||||
|
|
@ -147,7 +147,7 @@ ko apply -f config/brokers/mt-channel-broker/
|
|||
```
|
||||
|
||||
Depending on your needs you might want to install other
|
||||
[Broker implementations](https://github.com/knative/eventing/tree/master/docs/broker).
|
||||
[Broker implementations](https://github.com/knative/eventing/tree/main/docs/broker).
|
||||
|
||||
## (Optional) Install Sugar controller
|
||||
|
||||
|
|
|
|||
|
|
@ -3,8 +3,8 @@
|
|||
[](https://pkg.go.dev/knative.dev/eventing)
|
||||
[](https://goreportcard.com/report/knative/eventing)
|
||||
[](https://github.com/knative/eventing/releases)
|
||||
[](https://github.com/knative/eventing/blob/master/LICENSE)
|
||||
[](https://codecov.io/gh/knative/eventing)
|
||||
[](https://github.com/knative/eventing/blob/main/LICENSE)
|
||||
[](https://codecov.io/gh/knative/eventing)
|
||||
[](https://testgrid.knative.dev/eventing)
|
||||
[](https://slack.knative.dev)
|
||||
[](https://knative.slack.com/archives/C9JP909F0)
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ const (
|
|||
// Constants for the underlying HTTP Client transport. These would enable better connection reuse.
|
||||
// Purposely set them to be equal, as the ingress only connects to its channel.
|
||||
// These are magic numbers, partly set based on empirical evidence running performance workloads, and partly
|
||||
// based on what serving is doing. See https://github.com/knative/serving/blob/master/pkg/network/transports.go.
|
||||
// based on what serving is doing. See https://github.com/knative/serving/blob/main/pkg/network/transports.go.
|
||||
defaultMaxIdleConnections = 1000
|
||||
defaultMaxIdleConnectionsPerHost = 1000
|
||||
defaultMetricsPort = 9092
|
||||
|
|
|
|||
|
|
@ -42,7 +42,7 @@ These are exported by core sources.
|
|||
## Prometheus Collection
|
||||
|
||||
Accessing metrics requires Prometheus and Grafana installed. Follow the
|
||||
[instructions to install Prometheus and Grafana](https://github.com/knative/docs/blob/master/docs/serving/installing-logging-metrics-traces.md)
|
||||
[instructions to install Prometheus and Grafana](https://github.com/knative/docs/blob/main/docs/serving/installing-logging-metrics-traces.md)
|
||||
in namespace `knative-monitoring`.
|
||||
|
||||
> _All commands assume root of repo._
|
||||
|
|
@ -116,7 +116,7 @@ And then restart Prometheus.
|
|||
### Prometheus
|
||||
|
||||
Follow the
|
||||
[instructions to open Prometheus UI](https://github.com/knative/docs/blob/master/docs/serving/accessing-metrics.md#prometheus),
|
||||
[instructions to open Prometheus UI](https://github.com/knative/docs/blob/main/docs/serving/accessing-metrics.md#prometheus),
|
||||
then you will access the metrics at
|
||||
[http://localhost:9090](http://localhost:9090).
|
||||
|
||||
|
|
@ -130,7 +130,7 @@ kubectl patch configmap grafana-dashboard-definition-knative --patch "$(cat conf
|
|||
```
|
||||
|
||||
Follow the
|
||||
[instructions to open Grafana dashboard](https://github.com/knative/docs/blob/master/docs/serving/accessing-metrics.md#grafana),
|
||||
[instructions to open Grafana dashboard](https://github.com/knative/docs/blob/main/docs/serving/accessing-metrics.md#grafana),
|
||||
then you will access the metrics at
|
||||
[http://localhost:3000](http://localhost:3000).
|
||||
|
||||
|
|
|
|||
|
|
@ -152,8 +152,8 @@ Each instantiated Channel (ie, Custom Object) SHOULD have an annotation
|
|||
indicating which version of the `Channelable` duck type it conforms to. We
|
||||
currently have these versions:
|
||||
|
||||
1. [v1beta1](https://github.com/knative/eventing/blob/master/pkg/apis/duck/v1beta1/channelable_types.go)
|
||||
1. [v1](https://github.com/knative/eventing/blob/master/pkg/apis/duck/v1/channelable_types.go)
|
||||
1. [v1beta1](https://github.com/knative/eventing/blob/main/pkg/apis/duck/v1beta1/channelable_types.go)
|
||||
1. [v1](https://github.com/knative/eventing/blob/main/pkg/apis/duck/v1/channelable_types.go)
|
||||
|
||||
So, for example to indicate that the Channel supports v1beta1 duck type, you
|
||||
should annotate it like so (only showing the annotations):
|
||||
|
|
@ -175,7 +175,7 @@ if no annotation is given, we assume it's `v1alpha1`.
|
|||
##### v1beta1 Spec
|
||||
|
||||
Each channel CRD MUST contain an array of subscribers:
|
||||
[`spec.subscribers`](https://github.com/knative/eventing/blob/master/pkg/apis/duck/v1beta1/subscribable_types.go)
|
||||
[`spec.subscribers`](https://github.com/knative/eventing/blob/main/pkg/apis/duck/v1beta1/subscribable_types.go)
|
||||
|
||||
Note: The array of subscribers MUST NOT be set directly on the generic Channel
|
||||
custom object, but rather appended to the backing channel by the subscription
|
||||
|
|
@ -184,7 +184,7 @@ itself.
|
|||
##### v1 Spec
|
||||
|
||||
Each channel CRD MUST contain an array of subscribers:
|
||||
[`spec.subscribers`](https://github.com/knative/eventing/blob/master/pkg/apis/duck/v1/subscribable_types.go)
|
||||
[`spec.subscribers`](https://github.com/knative/eventing/blob/main/pkg/apis/duck/v1/subscribable_types.go)
|
||||
|
||||
Note: The array of subscribers MUST NOT be set directly on the generic Channel
|
||||
custom object, but rather appended to the backing channel by the subscription
|
||||
|
|
@ -193,7 +193,7 @@ itself.
|
|||
#### Channelable and Subscription Delivery Spec
|
||||
|
||||
Both Channelable and Subscription have a
|
||||
[`delivery`](https://github.com/knative/eventing/blob/master/pkg/apis/duck/v1/delivery_types.go)
|
||||
[`delivery`](https://github.com/knative/eventing/blob/main/pkg/apis/duck/v1/delivery_types.go)
|
||||
field that allows the user to define the dead letter sink and retries. The
|
||||
Channelable `spec.delivery` field is global across all the Subscriptions
|
||||
registered with that particular Channelable, while the Subscription
|
||||
|
|
@ -206,30 +206,30 @@ that particular Subscription.
|
|||
|
||||
Each channel CRD MUST have a `status` subresource which contains
|
||||
|
||||
- [`address`](https://github.com/knative/pkg/blob/master/apis/duck/v1/addressable_types.go)
|
||||
- [`subscribers`](https://github.com/knative/eventing/blob/master/pkg/apis/duck/v1beta1/subscribable_types.go)
|
||||
- [`address`](https://github.com/knative/pkg/blob/main/apis/duck/v1/addressable_types.go)
|
||||
- [`subscribers`](https://github.com/knative/eventing/blob/main/pkg/apis/duck/v1beta1/subscribable_types.go)
|
||||
(as an array)
|
||||
|
||||
Each channel CRD SHOULD have the following fields in `Status`
|
||||
|
||||
- [`observedGeneration`](https://github.com/knative/pkg/blob/master/apis/duck/v1/status_types.go)
|
||||
- [`observedGeneration`](https://github.com/knative/pkg/blob/main/apis/duck/v1/status_types.go)
|
||||
MUST be populated if present
|
||||
- [`conditions`](https://github.com/knative/pkg/blob/master/apis/duck/v1/status_types.go)
|
||||
- [`conditions`](https://github.com/knative/pkg/blob/main/apis/duck/v1/status_types.go)
|
||||
(as an array) SHOULD indicate status transitions and error reasons if present
|
||||
|
||||
##### v1 Status
|
||||
|
||||
Each channel CRD MUST have a `status` subresource which contains
|
||||
|
||||
- [`address`](https://github.com/knative/pkg/blob/master/apis/duck/v1/addressable_types.go)
|
||||
- [`subscribers`](https://github.com/knative/eventing/blob/master/pkg/apis/duck/v1/subscribable_types.go)
|
||||
- [`address`](https://github.com/knative/pkg/blob/main/apis/duck/v1/addressable_types.go)
|
||||
- [`subscribers`](https://github.com/knative/eventing/blob/main/pkg/apis/duck/v1/subscribable_types.go)
|
||||
(as an array)
|
||||
|
||||
Each channel CRD SHOULD have the following fields in `Status`
|
||||
|
||||
- [`observedGeneration`](https://github.com/knative/pkg/blob/master/apis/duck/v1/status_types.go)
|
||||
- [`observedGeneration`](https://github.com/knative/pkg/blob/main/apis/duck/v1/status_types.go)
|
||||
MUST be populated if present
|
||||
- [`conditions`](https://github.com/knative/pkg/blob/master/apis/duck/v1/status_types.go)
|
||||
- [`conditions`](https://github.com/knative/pkg/blob/main/apis/duck/v1/status_types.go)
|
||||
(as an array) SHOULD indicate status transitions and error reasons if present
|
||||
|
||||
#### Channel Status
|
||||
|
|
@ -363,7 +363,7 @@ to subscribers using [W3C Tracecontext](https://w3c.github.io/trace-context/),
|
|||
although internally it MAY use another mechanism(s) to propagate the tracing
|
||||
information. The Channel SHOULD sample and write traces to the location
|
||||
specified in
|
||||
[`config-tracing`](https://github.com/knative/eventing/blob/master/config/config-tracing.yaml).
|
||||
[`config-tracing`](https://github.com/knative/eventing/blob/main/config/config-tracing.yaml).
|
||||
|
||||
Spans emitted by the Channel SHOULD follow the
|
||||
[OpenTelemetry Semantic Conventions for Messaging Systems](https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/trace/semantic_conventions/messaging.md)
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ Knative Eventing.
|
|||
|
||||
_Note: only Knative leads can create versioned releases._
|
||||
|
||||
See https://github.com/knative/test-infra/blob/master/ci for more information on
|
||||
See https://github.com/knative/test-infra/blob/main/ci for more information on
|
||||
creating releases.
|
||||
|
||||
### Creating a major version release
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@
|
|||
# limitations under the License.
|
||||
|
||||
# Documentation about this script and how to use it can be found
|
||||
# at https://github.com/knative/test-infra/tree/master/ci
|
||||
# at https://github.com/knative/test-infra/tree/main/ci
|
||||
|
||||
source $(dirname $0)/../vendor/knative.dev/hack/release.sh
|
||||
|
||||
|
|
|
|||
|
|
@ -49,7 +49,7 @@ const (
|
|||
// Constants for the underlying HTTP Client transport. These would enable better connection reuse.
|
||||
// Set them on a 10:1 ratio, but this would actually depend on the Triggers' subscribers and the workload itself.
|
||||
// These are magic numbers, partly set based on empirical evidence running performance workloads, and partly
|
||||
// based on what serving is doing. See https://github.com/knative/serving/blob/master/pkg/network/transports.go.
|
||||
// based on what serving is doing. See https://github.com/knative/serving/blob/main/pkg/network/transports.go.
|
||||
defaultMaxIdleConnections = 1000
|
||||
defaultMaxIdleConnectionsPerHost = 100
|
||||
)
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ const (
|
|||
// Defaults for the underlying HTTP Client transport. These would enable better connection reuse.
|
||||
// Set them on a 10:1 ratio, but this would actually depend on the Subscriptions' subscribers and the workload itself.
|
||||
// These are magic numbers, partly set based on empirical evidence running performance workloads, and partly
|
||||
// based on what serving is doing. See https://github.com/knative/serving/blob/master/pkg/network/transports.go.
|
||||
// based on what serving is doing. See https://github.com/knative/serving/blob/main/pkg/network/transports.go.
|
||||
defaultMaxIdleConnections = 1000
|
||||
defaultMaxIdleConnectionsPerHost = 100
|
||||
)
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Samples
|
||||
|
||||
_Knative eventing_ samples have moved to
|
||||
[the docs repository](https://github.com/knative/docs/tree/master/docs/eventing/samples).
|
||||
[the docs repository](https://github.com/knative/docs/tree/main/docs/eventing/samples).
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ community contact's duty (subject to change) is as followed:
|
|||
### Monday
|
||||
|
||||
- Check 'Eventing Triage' Peribolos group
|
||||
https://github.com/knative/community/blob/master/peribolos/knative.yaml and
|
||||
https://github.com/knative/community/blob/main/peribolos/knative.yaml and
|
||||
send a PR to add yourself if you aren't already in there.
|
||||
- Check the [Eventing test grid](https://testgrid.k8s.io/knative-eventing) for
|
||||
flakiness to pick a test and focus on fixing it during your week. Once you
|
||||
|
|
|
|||
|
|
@ -129,10 +129,10 @@ automatically._
|
|||
The [`upload-test-images.sh`](./upload-test-images.sh) script can be used to
|
||||
build and push the test images used by the e2e tests. It requires:
|
||||
|
||||
- [`KO_DOCKER_REPO`](https://github.com/knative/serving/blob/master/DEVELOPMENT.md#environment-setup)
|
||||
- [`KO_DOCKER_REPO`](https://github.com/knative/serving/blob/main/DEVELOPMENT.md#environment-setup)
|
||||
to be set
|
||||
- You to be
|
||||
[authenticated with your `KO_DOCKER_REPO`](https://github.com/knative/serving/blob/master/DEVELOPMENT.md#environment-setup)
|
||||
[authenticated with your `KO_DOCKER_REPO`](https://github.com/knative/serving/blob/main/DEVELOPMENT.md#environment-setup)
|
||||
- [`docker`](https://docs.docker.com/install/) to be installed
|
||||
|
||||
`PLATFORM` environment variable is optional. If it is specified, test images
|
||||
|
|
@ -163,4 +163,4 @@ uploading test images, `ko` will build an image from this folder.
|
|||
## Flags
|
||||
|
||||
Flags are similar to those in
|
||||
[`Knative Serving`](https://github.com/knative/serving/blob/master/test/README.md#flags-1).
|
||||
[`Knative Serving`](https://github.com/knative/serving/blob/main/test/README.md#flags-1).
|
||||
|
|
|
|||
|
|
@ -2,14 +2,14 @@
|
|||
|
||||
Conformance tests verifies knative eventing implementation for expected behavior
|
||||
described in
|
||||
[specification](https://github.com/knative/eventing/tree/master/docs/spec).
|
||||
[specification](https://github.com/knative/eventing/tree/main/docs/spec).
|
||||
|
||||
## Running performance tests
|
||||
|
||||
Run test with e2e tag and optionally select conformance test
|
||||
|
||||
> NOTE: Make sure you have built the
|
||||
> [test images](https://github.com/knative/eventing/tree/master/test#building-the-test-images)!
|
||||
> [test images](https://github.com/knative/eventing/tree/main/test#building-the-test-images)!
|
||||
|
||||
```shell
|
||||
ko apply -Rf test/config/
|
||||
|
|
|
|||
|
|
@ -914,7 +914,7 @@ const (
|
|||
)
|
||||
|
||||
// CreateRBACResourcesForBrokers creates required RBAC resources for creating Brokers,
|
||||
// see https://github.com/knative/docs/blob/master/docs/eventing/broker-trigger.md - Manual Setup.
|
||||
// see https://github.com/knative/docs/blob/main/docs/eventing/broker-trigger.md - Manual Setup.
|
||||
func (c *Client) CreateRBACResourcesForBrokers() {
|
||||
c.CreateServiceAccountOrFail(saIngressName)
|
||||
c.CreateServiceAccountOrFail(saFilterName)
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@
|
|||
|
||||
1. Install Knative eventing and components used in the performance test, such as
|
||||
MT broker, by following the steps in
|
||||
https://github.com/knative/eventing/blob/master/DEVELOPMENT.md.
|
||||
https://github.com/knative/eventing/blob/main/DEVELOPMENT.md.
|
||||
|
||||
1. Create a ConfigMap called `config-mako` in your chosen namespace containing
|
||||
the Mako config file.
|
||||
|
|
@ -23,7 +23,7 @@ kubectl create configmap -n perf-eventing config-mako --from-file=test/performan
|
|||
kubectl edit configmap -n perf-eventing config-mako
|
||||
```
|
||||
|
||||
[`NewConfigFromMap`](https://github.com/knative/pkg/blob/master/test/mako/config.go#L41)
|
||||
[`NewConfigFromMap`](https://github.com/knative/pkg/blob/main/test/mako/config.go#L41)
|
||||
determines the valid keys in this ConfigMap. Current keys are:
|
||||
|
||||
- `environment`: Select a Mako config file in the ConfigMap. E.g.
|
||||
|
|
@ -60,7 +60,7 @@ To run a benchmark once, and use the result from `mako-stub` for plotting:
|
|||
1. Wait until all the pods in namespace `perf-eventing` are completed.
|
||||
|
||||
1. Retrieve results from mako-stub using the script in
|
||||
[knative/pkg](https://github.com/knative/pkg/blob/master/test/mako/stub-sidecar/read_results.sh)
|
||||
[knative/pkg](https://github.com/knative/pkg/blob/main/test/mako/stub-sidecar/read_results.sh)
|
||||
where `pod_name` is the name of the aggregator pod:
|
||||
|
||||
```
|
||||
|
|
@ -101,7 +101,7 @@ gnuplot -c test/performance/latency-and-thpt-plot.plg data.csv 0.005 480 520
|
|||
Most eventing binaries under `cmd` package are bootstrapped by either
|
||||
`sharedmain.Main` in `knative.dev/pkg/injection/sharedmain` or `adapter.Main` in
|
||||
`knative.dev/eventing/pkg/adapter`. These `Main` helper functions uses the
|
||||
[profiling](https://github.com/knative/pkg/blob/master/profiling/server.go)
|
||||
[profiling](https://github.com/knative/pkg/blob/main/profiling/server.go)
|
||||
package to enable golang profiling by reading the `profiling.enable` flag in the
|
||||
`config-observability` configmap.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue