cwielenb/CNCF-Dataset huggingface dataset:
Project: Gloo (Orchestration & Management / API Gateway)
File: subset_spec.proto.sk.md

title: "subset_spec.proto" weight: 5 <!-- Code generated by solo-kit. DO NOT EDIT. --> - See envoy docs for details: https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/cluster/v3/cluster.proto#config-cluster-v3-cluster-lbsubsetconfig ```yaml "selectors": []options.gloo.solo.io.Selector "fallbackPolicy": .options.gloo.solo.io.FallbackPolicy "defaultSubset": .options.gloo.solo.io.Subset ``` | Field | Type | Description | | -- | - | -- | | `selectors` | | Defines the set of subsets of the upstream. | | `fallbackPolicy` | | The behavior used when no endpoint subset matches the selected routes metadata The default value is ANY_ENDPOINT. | | `defaultSubset` | | Specifies the default subset of endpoints used during fallback if fallbackpolicy is DEFAULTSUBSET. | ```yaml "keys": []string "singleHostPerSubset": bool ``` | Field | Type | Description | | -- | - | -- | | `keys` | `[]string` | A subset is created for each unique combination of key and value. | | `singleHostPerSubset` | `bool` | Selects a mode of operation in which each subset has only one host. Default is false. | ```yaml "values": map<string, string> ``` | Field | Type | Description | | -- | - | -- | | `values` | `map<string, string>` | Any host that matches all key/value pairs is part of this subset. | Description: | Name | Description | | -- | -- | | ANY_ENDPOINT | Any cluster endpoint may be returned (default) | | DEFAULTSUBSET | Load balancing over the endpoints matching the values from the defaultsubset field | | NO_FALLBACK | A result equivalent to no healthy hosts is reported | <!-- 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 -->
Project: DolphinScheduler (Orchestration & Management / Scheduling & Orchestration)
File: dameng.md

| Datasource | Description | |-|--| | Datasource | Select DAMENG. | | Datasource name | Enter the name of the DataSource. | | Description | Enter a description of the DataSource. | | IP/Host Name | Enter the DAMENG service IP. | | Port | Enter the DAMENG service port. | | Username | Set the username for DAMENG connection. | | Password | Set the password for DAMENG connection. | | Database name | Enter the schema name of the DAMENG connection. | | Jdbc connection parameters | Parameter settings for DAMENG connection, in JSON format. | No, read section example in `DataSource Center` section to activate this datasource.
Project: Gloo (Orchestration & Management / API Gateway)
File: upstream_proxy_protocol.proto.sk.md

title: "upstreamproxyprotocol.proto" weight: 5 <!-- Code generated by solo-kit. DO NOT EDIT. --> Configuration for PROXY protocol socket ```yaml "config": .solo.io.envoy.config.core.v3.ProxyProtocolConfig "transportSocket": .solo.io.envoy.config.core.v3.TransportSocket ``` | Field | Type | Description | | -- | - | -- | | `config` | | The PROXY protocol settings. | | `transportSocket` | | The underlying transport socket being wrapped. | <!-- 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 -->
Project: Traefik (Orchestration & Management / API Gateway)
File: stripprefixregex.md

title: "Traefik StripPrefixRegex Documentation" description: "In Traefik Proxy's HTTP middleware, StripPrefixRegex removes prefixes from paths before forwarding requests, using regex. Read the technical documentation." Removing Prefixes From the Path Before Forwarding the Request (Using a Regex) {: .subtitle } Remove the matching prefixes from the URL path. ```yaml tab="Docker & Swarm" labels: "traefik.http.middlewares.test-stripprefixregex.stripprefixregex.regex=/foo/[a-z0-9]+/[0-9]+/" ``` ```yaml tab="Kubernetes" apiVersion: traefik.io/v1alpha1 kind: Middleware metadata: name: test-stripprefixregex spec: stripPrefixRegex: regex: "/foo/[a-z0-9]+/[0-9]+/" ``` ```yaml tab="Consul Catalog" "traefik.http.middlewares.test-stripprefixregex.stripprefixregex.regex=/foo/[a-z0-9]+/[0-9]+/" ``` ```yaml tab="File (YAML)" http: middlewares: test-stripprefixregex: stripPrefixRegex: regex: "/foo/[a-z0-9]+/[0-9]+/" ``` ```toml tab="File (TOML)" [http.middlewares] [http.middlewares.test-stripprefixregex.stripPrefixRegex] regex = ["/foo/[a-z0-9]+/[0-9]+/"] ``` The StripPrefixRegex middleware strips the matching path prefix and stores it in a `X-Forwarded-Prefix` header. !!! tip Use a `stripPrefixRegex` middleware if your backend listens on the root path (`/`) but should be exposed on a specific prefix. The `regex` option is the regular expression to match the path prefix from the request URL. For instance, `/products` also matches `/products/shoes` and `/products/shirts`. If your backend is serving assets (e.g., images or JavaScript files), it can use the `X-Forwarded-Prefix` header to properly construct relative URLs. Using the previous example, the backend should return `/products/shoes/image.png` (and not `/images.png`, which Traefik would likely not be able to associate with the same backend). !!! tip Regular expressions and replacements can be tested using online tools such as or the . When defining a regular expression within YAML, any escaped character needs to be escaped twice: `example\.com` needs to be written as `example\\.com`.
Project: Tengine (Orchestration & Management / Service Proxy)
File: ngx_debug_pool.md

ngxdebugpool ============== This module provides access to information of memory usage for nginx/tengine memory pool. Example ======= get information of worker process ``` http { server { listen 80; location = /debug_pool { debug_pool; } } } ``` Requesting URI /debug_pool, you will get information of memory usage for worker process which gets this request. The output page may look like as follows: ``` $ curl http://localhost:80/debug_pool pid:18821 size: 223784 num: 2 cnum: 1 lnum: 10 ngxinitcycle size: 1536 num: 4 cnum: 1 lnum: 10 ngxeventaccept size: 0 num: 1 cnum: 0 lnum: 0 ngxhttpluacreatefake_request size: 0 num: 1 cnum: 0 lnum: 0 main size: 0 num: 1 cnum: 0 lnum: 0 ngxhttpluacreatefake_connection size: 0 num: 1 cnum: 0 lnum: 6 ngxhttpserver_names size: 8192 num: 4 cnum: 1 lnum: 0 ngxhttpcreate_request size: 0 num: 1 cnum: 0 lnum: 0 ngxhttpluainitworker size: 228KB num: 15 cnum: 3 lnum: 26 [SUMMARY] ``` get information of specific process -- Also you can use gdb script to get information of specific process. Some process cannot handle HTTP request, such as master process or . The following example shows how to get information of master process. ``` $ gdb -q -x debug_pool.gdb -p <pid of master process> (gdb) debug_pool size: 16384 num: 1 cnum: 1 lnum: 0 ngxhttpuseragentcreatemainconf:24 size: 0 num: 1 cnum: 0 lnum: 0 main:224 size: 150312 num: 2 cnum: 1 lnum: 13 ngxinitcycle:824 size: 166696 num: 4 cnum: 2 lnum: 13 [SUMMARY] ``` Data ==== Every line except the last one of output content has the same format, as follows: "size: %12u num: %12u cnum: %12u lnum: %12u \<function name\>" size: size of current used memory of this pool num: number of created pool (including current used pool and destroyed pool) cnum: number of current used pool lnum: number of calling ngxpalloclarge() funcion name: which nginx/tengine C function creates this pool With function name of pool creator, we can know memory usage of every module, for example: pool created by `ngxhttpcreate_request` is used for one HTTP request. Because most modules allocates memory from this pool directly, it's hard to distinguish between them. pool created by `ngxeventaccept` is used for one TCP connection. pool created by `ngxinitcycle` is used for parsing nginx/tengine configuration and keeping other global data structures. pool created by `ngxhttpluainitworker` is used for conf.temp_pool of directive . ... Last line of output content summarizes the information of all memory pools. Install ======= ``` $ ./configure --add-module=./modules/ngxdebugpool $ make && make install ``` Directive ========= Syntax: debug_pool Default: `none` Context: `server, location` The information of nginx/tengine memory pool usage will be accessible from the surrounding location. Exception ========= Memory allocated without using memory pool does not get taken into account with this module. For example, ngxhttpspdymodule allocates a temporary buffer via malloc(ngxalloc) for raw data of SYN_REPLY frame. After being compressed, this buffer will be freed immediately.
Project: Volcano (Orchestration & Management / Scheduling & Orchestration)
File: podgroup-condition-reason.md

Currently, there are only two podgroup condition type: `Unschedulable` and `Scheduled`. If job is not enqueued, it has not been scheduled. And the event reason is `Unschedulable` and podgroup condition reason is `NotEnoughResources`. These reasons is not coresponding with the real reason `job is not enqueued` In order to classify the uninqueueable reason from other unscheduleable reasons add `Uninqueueable` reason for podgroup events ```go // PodGroupUnInqueueable is Uninqueueable event type PodGroupUnInqueueable PodGroupConditionType = "Uninqueueable" ``` add `NotInqueueable` reason for podgroup conditions reason ```go // NotInqueueableReason if probed if job is rejected to enqueue NotInqueueableReason string = "NotInqueueable" ```
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2018-07-30-mesoscon-2018-cfp-is-now-open.md

layout: post title: MesosCon 2018 CFP is now open! permalink: /blog/mesoscon-2018-cfp-is-now-open/ published: true post_author: display_name: Gastn Kleiman gravatar: fceac4890b4c4eef571732de53d1330a twitter: kleimang tags: MesosCon, Announcement MesosCon is an annual conference organized by the Apache Mesos community, bringing together users and developers to share and learn about the project and its growing ecosystem. We are excited to announce that MesosCon 2018 will be held in San Francisco on November 5th-7th, 2018. Talk submissions and sponsorship opportunities are now open for the conference! Several formats are being accepted for speaking proposals, including: Presentations, Panels, Keynotes, and Lightning Talks. Submissions are being accepted through August 27, 2018. You can take a look at the for ideas. If you are unsure about your proposal, or want some feedback or advice in general, please do not hesitate to reach out to the mailing list. We will be happy to help out! Further details are available on the . MesosCon is a community run conference and your support is needed. Sponsoring this event will provide a great opportunity for your organization to further engage with the Mesos community. to learn more. Help us make #MesosCon 2018 a big success by spreading the word and submitting your proposal! Hope to see you at this years MesosCon! Edit: This post previously said New York City, but this was changed to San Francisco.
Project: DolphinScheduler (Orchestration & Management / Scheduling & Orchestration)
File: features.md

Visual DAG: User-friendly drag-and-drop workflow definition and facility for run-time control. Modular Operation: Modularity facilitates easy customization and maintenance. Multiple Task Type Support: Supports more than 10 task types, like Shell, MR, Spark, SQL, etc., with cross-language support making it easy to extend Workflow Ops: Workflow can be timed, paused, resumed and stopped, enabling easy maintenance and control of global and local parameters. Reliability: Decentralized designs ensure stability. Self-supporting HA task queue to avoid overload fault tolerant capability. DolphinScheduler facilitates a highly robust environment. Scalability: Supports multitenancy and online resource management. Stable operation of 100,000 data tasks per day is supported.
Project: Gloo (Orchestration & Management / API Gateway)
File: shadowing.proto.sk.md

title: "shadowing.proto" weight: 5 <!-- Code generated by solo-kit. DO NOT EDIT. --> Specifies traffic shadowing configuration for the associated route. If set, Envoy will send a portion of the route's traffic to the shadowed upstream. This can be a useful way to preview a new service's behavior before putting the service in the critical path. Note that this plugin is only applicable to routes with upstream destinations (not redirect or direct response routes). See here for additional information on Envoy's shadowing capabilities: https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/route/v3/route.proto#envoy-api-msg-route-routeaction-requestmirrorpolicy ```yaml "upstream": .core.solo.io.ResourceRef "percentage": float ``` | Field | Type | Description | | -- | - | -- | | `upstream` | | The upstream to which the shadowed traffic should be sent. | | `percentage` | `float` | This should be a value between 0.0 and 100.0, with up to 6 significant digits. | <!-- 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 -->
Project: Kusk Gateway (Orchestration & Management / API Gateway)
File: 42crunch.md

Automatically run security and vulnerabilities scan on your OpenAPI definition. | Name | Description | Type | Required | | :- | - ||-| | `security.42crunch` | Enables 42Crunch scan assesment | object | true | | `security.42crunch.token` | Object holding API Token for 42Crunch | object | true | | `security.42crunch.token.name` | Name of the kubernetes secret | string | true | | `security.42crunch.token.namespace` | Namespace of the kubernetes secret | string | true | A minimal example of the configuration for this filter is: ```yaml title=crunch42.yaml" openapi: 3.0.0 info: title: simple-api version: 0.1.0 x-kusk: cors: origins: "*" methods: GET POST upstream: service: name: hello-world-svc namespace: default port: 8080 security: 42crunch: token: name: demo-secret namespace: default paths: /hello: get: responses: "200": description: A simple hello world! content: application/json: schema: type: object properties: message: type: string example: message: Hello from a mocked response! ``` Create a 42Crunch account https://platform.42crunch.com/login. Get 42Crunch API token https://platform.42crunch.com/settings/tokens Store the token in a Kubernetes secret ```bash $ export 42CRUNCHTOKEN=[yourapi_token] $ echo $42CRUNCH_TOKEN | base64 bXk0MmNydW5jaHRva2VuCg== ``` Copy the output and paste it under `CRUNCH42_TOKEN` property of the secret ```yaml apiVersion: v1 kind: Secret metadata: name: demo-secret namespace: default type: Opaque data: CRUNCH42_TOKEN: bXk0MmNydW5jaHRva2VuCg== ``` Run `kubectl apply -f openapi.yaml` (use the example above) Log in into and look for the API collection named simple-api and within it there will be your API with all security scans ran.
Project: Karmada (Orchestration & Management / Scheduling & Orchestration)
File: spread_by_region_test.md

| Test Case | E2E Describe Text | Comments | ||--|--| | Verifying the deployment spread across multiple regions | multiple region deployment testing(check whether deployment is scheduled to multiple regions) | | | Updating the propagation policy and verifying its constraints | multiple region deployment testing(update propagation policy to propagate to one region) | |
Project: Contour (Orchestration & Management / Service Proxy)
File: CHANGELOG-v1.24.3.md

We are delighted to present version v1.24.3 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters. Update to Envoy v1.25.4. See the for more information about the content of the release and details on the addressed CVEs can be found . Update to Go v1.19.8. See the for more information. For a fresh install of Contour, consult the . To upgrade an existing Contour installation, please consult the . Contour v1.24.3 is tested against Kubernetes 1.24 through 1.26. 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: TARS (Orchestration & Management / Remote Procedure Call)
File: Readme.md

WeChat Offical Account: TarsCloud QQ Group: 733605310, 579079160(Full), 669339903(Full) Twitter: TARS is a Linux Foundation project. It is a high-performance RPC framework based on name service and Tars protocol, also integrated administration platform, and implemented hosting-service via flexible schedule. Tars, aka TAF(Total Application Framework), has been used in Tencent since 2008. It supports C++, Java, Nodejs and PHP for now. This framework offers a set of solution for development, maintenance and testing, which making development, deployment and testing service efficiently. It integrated extensible protocol for encoding/decoding, high-performance RPC communication framework, name service, monitor, statistics and configuration. You can use it to develop your reliable distributed application based on microservice fast, and reach fully efficient service management. Nowadays it's used by hundreds of bussiness in Tencent, services that developed base on TAF run on 16 thousands of machines. See the detailed introduction . For now it supports OS as below: Linux Mac(>=2.1.0 support) Windows (>= Windows 7) For now it supports following languages: C++ Java Nodejs PHP Go Tars is composed of many modules, scattered in many warehouses, and the basic framework version and language version can develop independently. In view of this, from version 2.1.0, the Framework version tag is printed on the tarsframework warehouse, no longer reflected in the tars warehouse In addition, each component will have its own version. When there is a version dependency specification, each component will have its own version If you are new to Tars, please read documentation . First deploy, please read documentation . Install by docker, detail information: Directory |Features |- framework |Source code implementation of C++ language framework basic service cpp |C++ language framework rpc source code implementation java |java language framework rpc source code implementation go |go language framework rpc source code implementation nodejs |nodejs language framework rpc source code implementation php |php language framework rpc source code implementation tup |source code implementation of tup group protocol in each language web |manage tars web source implementation See . The open-source protocol Tars used is BSD-3-Clause, see .
Project: Kusk Gateway (Orchestration & Management / API Gateway)
File: custom-auth-upstream.md

Currently you can use any Header based authentication methods by means of custom Authentication Upstream . This includes: Basic Authentication JWT Tokens Bearer Tokens To set up a custom authentication upstream, add the following section to your `x-kusk` settings block: ```yaml openapi: 3.0.0 info: title: simple-api version: 0.1.0 x-kusk: auth: custom: host: hostname: auth-upstream-svc.default port:8080 ``` :::info The `hostname` field can contain internal cluster domains but also external domains to your cluster that can handle your header based authentication. ::: The example above authenticates requests to the whole API. You can also specify different authentication settings for specific operations or paths. The following example shows an example authentication configuration for a specific operation: ```yaml ... paths: /hello: get: operationId: getHello auth: custom: host: hostname: auth-upstream-svc.default port:8080 .. ``` In the example, in the `hostname` section we're referencing an upstream service in our cluster that will handle request authentication. The flow is as follows: See all available Authentication configuration options in the .
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_init-plugin-manager.md

title: "glooctl init-plugin-manager" weight: 5 Install the Gloo Edge Enterprise CLI plugin manager ``` glooctl init-plugin-manager [flags] ``` ``` -f, --force Delete any existing plugin data if found and reinitialize --gloo-home string Gloo home directory (default: $HOME/.gloo) -h, --help help for init-plugin-manager ``` ``` -c, --config string set the path to the glooctl config file (default "<home_directory>/.gloo/glooctl-config.yaml") --consul-address string address of the Consul server. Use with --use-consul (default "127.0.0.1:8500") --consul-allow-stale-reads Allows reading using Consul's stale consistency mode. --consul-datacenter string Datacenter to use. If not provided, the default agent datacenter is used. Use with --use-consul --consul-root-key string key prefix for for Consul key-value storage. (default "gloo") --consul-scheme string URI scheme for the Consul server. Use with --use-consul (default "http") --consul-token string Token is used to provide a per-request ACL token which overrides the agent's default token. Use with --use-consul -i, --interactive use interactive mode --kube-context string kube context to use when interacting with kubernetes --kubeconfig string kubeconfig to use, if not standard one --use-consul use Consul Key-Value storage as the backend for reading and writing config (VirtualServices, Upstreams, and Proxies) ``` - CLI for Gloo
Project: Envoy (Orchestration & Management / Service Proxy)
File: RELEASE.md

Active development is happening on the `main` branch, and a new versions will be released on major development milestones and/or following upstream Envoy releases. Update the . Add a new `Pending Release` section with `Bugfixes:` and `Features:` section at the top of the file. Update the old `Pending Release` section with the release version and release date. Make sure all changes since the last release (``git log `git rev-list --tags --max-count=1`..HEAD``) are reflected in the current release. If building the quarterly release, also note the Envoy tagged release (e.g. as done in the release If building the quarterly release, ensure the Envoy checkout points to the latest Bump the version in and files Create a PR with the above changes, get it approved and merged Optionally, wait for CI to pass on main Draft a new release . Copy in the release notes you just created and publish it. Wait for the for the tag release to finish running. Click on the workflow run to find the generated artifacts (e.g. ). Download `envoyandroidaarsources`, `envoyioscocoapods`, and `envoyios_framework`. Go back to your tagged release, edit the release, and upload the 3 files from the previous step.
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_edit_virtualservice_ratelimit.md

title: "glooctl edit virtualservice ratelimit" weight: 5 Configure rate limit settings (Enterprise) Let gloo know the location of the rate limit server. This is a Gloo Enterprise feature. ``` -h, --help help for ratelimit ``` ``` -c, --config string set the path to the glooctl config file (default "<home_directory>/.gloo/glooctl-config.yaml") --consul-address string address of the Consul server. Use with --use-consul (default "127.0.0.1:8500") --consul-allow-stale-reads Allows reading using Consul's stale consistency mode. --consul-datacenter string Datacenter to use. If not provided, the default agent datacenter is used. Use with --use-consul --consul-root-key string key prefix for for Consul key-value storage. (default "gloo") --consul-scheme string URI scheme for the Consul server. Use with --use-consul (default "http") --consul-token string Token is used to provide a per-request ACL token which overrides the agent's default token. Use with --use-consul -i, --interactive use interactive mode --kube-context string kube context to use when interacting with kubernetes --kubeconfig string kubeconfig to use, if not standard one --name string name of the resource to read or write -n, --namespace string namespace for reading or writing resources (default "gloo-system") -o, --output OutputType output format: (yaml, json, table, kube-yaml, wide) (default table) --resource-version string the resource version of the resource we are editing. if not empty, resource will only be changed if the resource version matches --use-consul use Consul Key-Value storage as the backend for reading and writing config (VirtualServices, Upstreams, and Proxies) ``` - edit a virtualservice in a namespace - Add rate-limits (Enterprise)