cwielenb/CNCF-Dataset huggingface dataset:
Project: Avro (Orchestration & Management / Remote Procedure Call)
File: avro-1.7.1-released.md

title: "Avro 1.7.1" linkTitle: "Avro 1.7.1" date: 2012-07-18 <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> Apache Avro 1.7.1 has been released!
Project: Open Cluster Management (Orchestration & Management / Scheduling & Orchestration)
File: pull_request_template.md

<!-- Thanks for creating a pull request! If this is your first time, please make sure to review CONTRIBUTING.MD. Please copy the appropriate `:text:` or icon to the beginning of your PR title: :sparkles: feature :bug: bug fix :book: docs :memo: proposal :warning: breaking change :seedling: other/misc :question: requires manual review/categorization --> Fixes #
Project: Flomesh Service Mesh (FSM) (Orchestration & Management / Service Mesh)
File: automerge.md

title: "Automerge Pull Requests" description: "How to use labels and commands to automerge/autorebase your pull request." type: docs FSM uses to automatically merge (automerge), automatically squash and merge (autosquash), and automatically rebase (autorebase) pull requests. A pull request will be automerged via a merge commit if it meets the following criteria: Has the `automerge` label Does not have the `wip` label Does not have the `do-not-merge/hold` label Successfully completed all checks Has at least 2 maintainer approvals Base branch is either main or a release branch If the pull request has an `automerge` label, the FSM-PR-bot will also autorebase the pull request if the PR branch goes out-of-date. Note: Pull requests that are paths-ignore cannot be merged automatically. A pull request will be autosquashed (commits will be squashed then merged) if it meets the following criteria: Has the `automerge-squash` label Does not have the `wip` label Does not have the `do-not-merge/hold` label Successfully completed all checks Has at least 2 maintainer approvals Base branch is main branch If the pull request has an `automerge-squash` label, the FSM-PR-bot will also autorebase the pull request if the PR branch goes out-of-date. Note: Pull requests that are paths-ignore cannot be merged automatically. A pull request will be autorebased only and not automerged/autosquashed if it has the `autorebase` label, as long as there are no conflicts. The rebase action will be completed by FSM-PR-bot. Some Mergify commands can also be triggered via comments on the pull request. `@Mergifyio refresh` will re-evaluate the rules `@Mergifyio rebase` will rebase this PR on its base branch `@Mergifyio backport <destination>` will this PR on <destination> branch
Project: 3Scale (Orchestration & Management / API Gateway)
File: unittests.md

is the framework used for the unit tests. Using Docker you just need to run: ```shell make development ``` That will create a Docker container and run bash inside it. The project's source code will be available in the container and sync'ed with your local `apicast` directory, so you can edit files in your preferred environment and still be able to run whatever you need inside the Docker container. To install the dependencies inside the container run: ```shell make dependencies ``` To run the unit tests inside the container: ```shell make busted ``` To run a single file of tests ```shell make busted BUSTEDFILES=path/to/filespec.lua ``` To run a specific set of `it` tests, i.e. a contextual description defined by the `describe` function, add some unique token, for instance `ONLY`, to the `describe` function. ``` describe("ONLY should be awesome", function() ``` then, add `BUSTED_ARGS` with `--filter` param ```shell make busted BUSTEDFILES=path/to/filespec.lua BUSTED_ARGS="--filter='ONLY'" ```
Project: gRPC (Orchestration & Management / Remote Procedure Call)
File: bug_report_csharp.md

name: Report a gRPC C# bug about: Create a report to help us improve labels: kind/bug, priority/P2, lang/C# assignees: apolcyn <!-- PLEASE DO NOT POST A QUESTION HERE. This form is for bug reports and feature requests ONLY! For general questions and troubleshooting, please ask/look for answers at StackOverflow, with "grpc" tag: https://stackoverflow.com/questions/tagged/grpc For questions that specifically need to be answered by gRPC team members, please ask/look for answers at grpc.io mailing list: https://groups.google.com/forum/#!forum/grpc-io Issues specific to grpc-java, grpc-go, grpc-node, grpc-dart, grpc-web should be created in the repository they belong to (e.g. https://github.com/grpc/grpc-LANGUAGE/issues/new) --> Please provide either 1) A unit test for reproducing the bug or 2) Specific steps for us to follow to reproduce the bug. If theres not enough information to debug the problem, gRPC team may close the issue at their discretion. Youre welcome to re-open the issue once you have a reproduction. Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs). See for how to diagnose problems better.
Project: Pipy (Orchestration & Management / Service Proxy)
File: demuxer.md

Packet Demuxer ============== This is a QUIC specific module that parses headers of incoming packets and decides what to do next. Demuxer requirements for MVP These are the requirements that were identified for MVP: multiple QUIC packets in an UDP packet handling as packet coalescing must be supported client must discard any packets that do not match existing connection ID client must discard any packets with version different from the one initially selected Optional demuxer requirements -- These are optional features of the client side demuxer, not required for MVP but otherwise desirable: optionally trigger sending stateless reset packets if a received packet on the client is well-formed but does not belong to a known connection Demuxer requirements for server Further requirements after MVP for server support: on the server side packets can create a new connection potentially server side packet handling for unsupported version packets: trigger sending version negotiation packets if the server receives a packet with an unsupported version and is large enough to initiate a new connection; limit the number of such packets with the same destination discard smaller packets with unsupported versions packet handling on server for well-formed packets with supported versions but with unknown connection IDs: if the packet is a well-formed Initial packet, trigger the creation of a new connection if the packet is a well-formed 0RTT packet, mark the packet to be buffered for short period of time (as Initial packet might arrive late) this is optional - enabled only if 0RTT support is enabled by the application discard any other packet with unknown connection IDs optionally trigger sending stateless reset packets as above for client
Project: CoreDNS (Orchestration & Management / Coordination & Service Discovery)
File: coredns-011.md

+++ title = "CoreDNS-011 Release" description = "CoreDNS-011 Release Notes." tags = ["Release", "011", "Notes"] draft = false release = "011" date = "2017-09-10T20:24:43-04:00" author = "coredns" +++ CoreDNS-011 has been ! CoreDNS is a DNS server that chains plugins, where each plugin implements a DNS feature. Release v011 is a major release, with backwards incompatible changes in the kubernetes plugin. This release has backwards incompatible changes for the kubernetes plugin. Stop vendoring `github.com/miekg/dns` and `golang.org/x/net/context`. This enables external plugin to compile without tripping over vendored types that mismatch. Allow an easy way to specify reverse zones in the Corefile, just use (e.g) `10.0.0.0/24` as the zone name, CoreDNS translates this to 0.0.10.in-addr.arpa. This is only done when the netmask is a multiple of 8 and for both IPv4 and IPv6. Bug and stability fixes. Make kubernetes, file, secondary, hosts, erratic and metrics now fail on unknown properties in the Corefile. federation*: enables federation via kubernetes. autopath*: enables autopath-ing. Can be used standalone, but its main use is with kubernetes. log* adds an `>rflags` replacer that shows the flags from the response - this has been enabled by default. kubernetes* deprecates: `cidr`: use the reverse syntax in the Corefile `federation`: use the new federation* plugin `autopath`: use the new autopath* plugin kubernetes*: add TTL option allowing to set minimal TTL for responses. Multiple k8s API endpoints could be specified, separated by `","`s, e.g. `endpoint http://k8s-endpoint1:8080,http://k8s-endpoint2:8080`. CoreDNS will automatically perform a healthcheck and proxy to the healthy k8s API endpoint. rewrite*: allow for dynamic* properties to be used, like client IP address in rewrite rules, i.e. `rewrite edns0 local set 0xffee {client_ip}` add support for EDNS0 Client Subnet dnstap now reports messages proxied by proxy*, and support remote IP endpoints by specifying `tcp://`. dnssec* now warns if keys can't be used to sign the configured zones. health* now allows for per plugin health status; no plugin makes use of this yet, though. secondary* parses a secondary with a zone (`secondary example.org {...}`) correctly. The following people helped with getting this release done: Brad Beam, Chris O'Haver, insomniac, James Mills, John Belamaric, Markus Sommer, Miek Gieben Mohammed Naser, Sandeep Rajan, Thong Huynh, varyoo, Yong Tang, . If you want to help, please check out one of the and start coding! For documentation and help, see our .
Project: Contour (Orchestration & Management / Service Proxy)
File: CHANGELOG-v1.23.1.md

We are delighted to present version v1.23.1 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters. A big thank you to everyone who contributed to the release. Bumps Envoy to security patch version 1.24.1. See Envoy release notes . (#4903, @sunjayBhatia) Various updates to dependencies for security updates, upgrade to Go 1.19.3, and bump go module version to go 1.17. (#4874, #4881, #4883, @sunjayBhatia) For a fresh install of Contour, consult the . To upgrade an existing Contour installation, please consult the . Contour v1.23.1 is tested against Kubernetes 1.23 through 1.25. If you're using Contour and want to add your organization to our adopters list, please visit this . If you prefer to keep your organization name anonymous but still give us feedback into your usage and scenarios for Contour, please post on this .
Project: Traefik Mesh (Orchestration & Management / Service Mesh)
File: thank-you.md

title: "Traefik Mesh Feedback and Contributions" description: "Traefik Mesh is an open-source project, your feedback and contributions are needed and always welcome! Read the docs to learn how you can contribute." Traefik Mesh is an , your feedback and contributions are needed and always welcome! !!! Question "Where to Go Next?" If you want to: Propose and idea, request a feature a report a bug, read the page . Discover how to make an efficient contribution, read the page . Learn how to build and test Traefik Mesh, the page is for you. Contribute to the documentation, read the related page .
Project: Gravitee.io (Orchestration & Management / API Gateway)
File: management-api-subscriptions.md

Retrieve all the registered subscriptions per application. Subscription represents the plans a consumer has subscribed to. Subscriptions can be: Accepted Subscription is valid and consumer can use its API Key to perform operations of the API. The subscription can be renewed, revoked or valid until its expiration date. Pending A consumer has asked access for the API, you can accept its subscription or rejected it. Rejected Subscription is rejected and consumer cannot use the API. Closed Subscription is closed and consumer cannot use the API. The (+) button let you create a new subscription for a given application and a given plan.
Project: Envoy (Orchestration & Management / Service Proxy)
File: STYLE.md

General style guidelines -- like newlines at the end of file -- are linted for using The rules enforced are available in the repo's . You can install pre-commit locally with these . The linter may be run locally using `pre-commit run --all-files`. Additionally it can be installed as a commit hook with `pre-commit install`. C++ code uses the Code is auto-formatted using `clang-format` with Java code is auto-formatted using `clang-format` with Objective-C code is auto-formatted using `clang-format` with Kotlin code style is validated using The rules enforced are available in the repo's . We build upon the default config provided by Swift code style is validated using The rules enforced are available in the repo's The linter may be run locally using `swiftlint` or auto-corrected with `swiftlint autocorrect` There's no directly supported way to universally share an enumeration across platforms. In order to provide some enforced consistency, we've adopted the convention of defining the enum at the lowest applicable layer (core/bridge) of the library, and then declaring public `extern const` values defined in terms of the enumeration, to be shared across bridge and platform code. See, for example: https://github.com/envoyproxy/envoy-mobile/blob/2a1b53427100d94878551b55bb564e9117f83fe6/library/common/types/c_types.h#L25 ``` tools/check_format.sh ``` ``` tools/check_format.sh fix ```
Project: Traefik (Orchestration & Management / API Gateway)
File: building-testing.md

title: "Traefik Building & Testing Documentation" description: "Compile and test your own Traefik Proxy! Learn how to build your own Traefik binary from the sources, and read the technical documentation." Compile and Test Your Own Traefik! {: .subtitle } You want to build your own Traefik binary from the sources? Let's see how. You need: - `make` - - if you are using Docker Desktop !!! tip "Source Directory" It is recommended that you clone Traefik into the `~/go/src/github.com/traefik/traefik` directory. This is the official golang workspace hierarchy that will allow dependencies to be properly resolved. !!! note "Environment" Set your `GOPATH` and `PATH` variable to be set to `~/go` via: ```bash export GOPATH=~/go export PATH=$PATH:$GOPATH/bin ``` For convenience, add `GOPATH` and `PATH` to your `.bashrc` or `.bash_profile` Verify your environment is setup properly by running `$ go env`. Depending on your OS and environment, you should see an output similar to: ```bash GOARCH="amd64" GOBIN="" GOEXE="" GOHOSTARCH="amd64" GOHOSTOS="linux" GOOS="linux" GOPATH="/home/<yourusername>/go" GORACE="" ``` Once you've set up your go environment and cloned the source repository, you can build Traefik. ```bash $ make binary SHA: 8fddfe118288bb5280eb5e77fa952f52def360b4 cheddar 2024-01-11_03:14:57PM CGO_ENABLED=0 GOGC=off GOOS=darwin GOARCH=arm64 go build -ldflags "-s -w \ -X github.com/traefik/traefik/v2/pkg/version.Version=8fddfe118288bb5280eb5e77fa952f52def360b4 \ -X github.com/traefik/traefik/v2/pkg/version.Codename=cheddar \ -X github.com/traefik/traefik/v2/pkg/version.BuildDate=2024-01-11_03:14:57PM" \ -installsuffix nocgo -o "./dist/darwin/arm64/traefik" ./cmd/traefik $ ls dist/ traefik* ``` You will find the Traefik executable (`traefik`) in the `./dist` directory. Run unit tests using the `test-unit` target. Run integration tests using the `test-integration` target. Run all tests (unit and integration) using the `test` target. ```bash $ make test-unit GOOS=darwin GOARCH=arm64 go test -cover "-coverprofile=cover.out" -v ./pkg/... ./cmd/... go test -cover -coverprofile=cover.out . ok github.com/traefik/traefik 0.005s coverage: 4.1% of statements Test success ``` For development purposes, you can specify which tests to run by using (only works the `test-integration` target): ??? note "Configuring Tailscale for Docker Desktop user" Create `tailscale.secret` file in `integration` directory. This file need to contains a (an ephemeral, but reusable, one is recommended). Add this section to your tailscale ACLs to auto-approve the routes for the containers in the docker subnet: ```json "autoApprovers": { // Allow myself to automatically // advertize routes for docker networks "routes": { "172.31.42.0/24": ["yourtailscaleidentity"], }, }, ``` ```bash TESTFLAGS="-test.run TestAccessLogSuite" make test-integration TESTFLAGS="-test.run TestAccessLogSuite -testify.m ^TestAccessLog$" make test-integration ```
Project: BFE (Orchestration & Management / Service Proxy)
File: latency.md

| Endpoint | Description | | - | -- | | /monitor/proxyhandshakedelay | Latency of the TLS handshake | | /monitor/proxyhandshakefull_delay | Latency of the TLS full handshake | | /monitor/proxyhandshakeresume_delay | Latency of the TLS abbreviated handshake | | /monitor/proxy_delay | Forwarding Latency for the GET requests | | /monitor/proxypostdelay | Forwarding Latency for the POST requests | | Metric | Description | | | -- | | Interval | Statistical period (second) | | ProgramName | Program name | | KeyPrefix | Key prefix | | CurrTime | Start time of current statistics | | Current | Latency histogram for current statistics | | PastTime | Start time of last statistics | | Past | Latency histogram for last statistics | BFE can expose metrics in various formats. Unlike other formats, in the Prometheus format latency histogram, counter for a bucket with lager upper bound will include the number of events in buckets with smaller upper bound. See in Prometheus document for more detail. Example: proxyhandshakedelayPastbucket{le="1000"} is counter of handshakes with <= 1000 ms delay in last statistic interval proxyhandshakedelayPastbucket{le="2000"} is counter of handshakes with <= 2000 ms delay (includes those with <=1000 ms delay) in last statistic interval proxyhandshakedelayPastbucket{le="+Inf"} is counter of handshakes with less than infinity (equals total count) in last statistic interval. It is equal to proxyhandshakedelayPastcount.
Project: APISIX (Orchestration & Management / API Gateway)
File: ext-plugin-post-resp.md

title: ext-plugin-post-resp keywords: Apache APISIX API Gateway Plugin ext-plugin-post-resp description: This document contains information about the Apache APISIX ext-plugin-post-resp Plugin. <!-- --> The `ext-plugin-post-resp` Plugin is for running specific external Plugins in the Plugin Runner before executing the built-in Lua Plugins. The `ext-plugin-post-resp` plugin will be executed after the request gets a response from the upstream. This plugin uses library under the hood to send requests to the upstream, due to which the , , and plugins are not available to be used alongside this plugin. Also, is not yet supported. See to learn more. :::note Execution of External Plugins will affect the response of the current request. ::: | Name | Type | Required | Default | Valid values | Description | |-||-||--|| | conf | array | False | | [{"name": "ext-plugin-A", "value": "{\"enable\":\"feature\"}"}] | List of Plugins and their configurations to be executed on the Plugin Runner. | | allow_degradation | boolean | False | false | | Sets Plugin degradation when the Plugin Runner is not available. When set to `true`, requests are allowed to continue. | The example below enables the `ext-plugin-post-resp` Plugin on a specific Route: :::note You can fetch the `admin_key` from `config.yaml` and save to an environment variable with the following command: ```bash adminkey=$(yq '.deployment.admin.adminkey[0].key' conf/config.yaml | sed 's/"//g') ``` ::: ```shell curl -i http://127.0.0.1:9180/apisix/admin/routes/1 -H "X-API-KEY: $admin_key" -X PUT -d ' { "uri": "/index.html", "plugins": { "ext-plugin-post-resp": { "conf" : [ {"name": "ext-plugin-A", "value": "{\"enable\":\"feature\"}"} ] } }, "upstream": { "type": "roundrobin", "nodes": { "127.0.0.1:1980": 1 } } }' ``` Once you have configured the External Plugin as shown above, you can make a request to execute the Plugin: ```shell curl -i http://127.0.0.1:9080/index.html ``` This will reach the configured Plugin Runner and the `ext-plugin-A` will be executed. To remove the `ext-plugin-post-resp` Plugin, you can delete the corresponding JSON configuration from the Plugin configuration. APISIX will automatically reload and you do not have to restart for this to take effect. ```shell curl http://127.0.0.1:9180/apisix/admin/routes/1 -H "X-API-KEY: $admin_key" -X PUT -d ' { "uri": "/index.html", "upstream": { "type": "roundrobin", "nodes": { "127.0.0.1:1980": 1 } } }' ```
Project: kratos (Orchestration & Management / Remote Procedure Call)
File: SECURITY.md

Use this section to tell people about which versions of your project are currently being supported with security updates. | Version | Supported | |-|--| | 2.0.rc1 | :whitecheckmark: | | < 2.0.beta3 | :x: | Use this section to tell people how to report a vulnerability. Tell them where to go, how often they can expect to get an update on a reported vulnerability, what to expect if the vulnerability is accepted or declined, etc.
Project: Tengine (Orchestration & Management / Service Proxy)
File: ngx_http_upstream_iwrr_module.md

ngxhttpupstreamiwrrmodule. The `IWRR` module is an efficient load balancing algorithm with `O(1)` time complexity, but `IWRR` is no need to incremental initialization. Compared with Nginx's official `SWRR` algorithm and `VNSWRR`, `IWRR` abandons smoothness on the premise of ensuring the correctness of the weighted load balancing algorithm, ensuring that no matter how the total weight of the cluster changes, `IWRR` space The complexity is always `O(n)`. ``` http { upstream backend { iwrr; # enable IWRR load balancing algorithm. 127.0.0.1 port=81; 127.0.0.1 port=82 weight=2; 127.0.0.1 port=83; 127.0.0.1 port=84 backup; 127.0.0.1 port=85 down; } server { server_name localhost; location / { proxy_pass http://backend; } } } ``` Build Tengine with this module from source: ``` ./configure --add-module=./modules/ngxhttpupstreamiwrrmodule/ make make install ``` iwrr ======= ``` Syntax: iwrr [max_init=number] Default: none Context: upstream ``` Enable `iwrr` load balancing algorithm.
Project: Gloo (Orchestration & Management / API Gateway)
File: sanitize.proto.sk.md

title: "sanitize.proto" weight: 5 <!-- Code generated by solo-kit. DO NOT EDIT. --> ```yaml "headersToRemove": []string "customAuthServerName": string ``` | Field | Type | Description | | -- | - | -- | | `headersToRemove` | `[]string` | | | `customAuthServerName` | `string` | The name of the custom ext auth server This is only set in the case where multiple auth servers exist. | ```yaml "customAuthServerName": string ``` | Field | Type | Description | | -- | - | -- | | `customAuthServerName` | `string` | The name of the custom ext auth server This is only set in the case where multiple auth servers exist. | <!-- Start of HubSpot Embed Code --> <script type="text/javascript" id="hs-script-loader" async defer src="//js.hs-scripts.com/5130874.js"></script> <!-- End of HubSpot Embed Code -->