cwielenb/CNCF-Dataset huggingface dataset:
Project: CoreDNS (Orchestration & Management / Coordination & Service Discovery)
File: coredns-1.6.0.md

+++ title = "CoreDNS-1.6.0 Release" description = "CoreDNS-1.6.0 Release Notes." tags = ["Release", "1.6.0", "Notes"] release = "1.6.0" date = 2019-07-28T14:35:47+01:00 author = "coredns" +++ The CoreDNS team has released . The `-cpu` flag is removed from this version. This release sports changes in the file plugin. A speed up in the log plugin and fixes in the cache and hosts plugins. Upcoming deprecation: the kubernetes federation plugin [will be moved to](https://github.com/coredns/coredns/issues/3041) github.com/coredns/federation. This is likely to happen in CoreDNS 1.7.0. The got lot of bug fixes and it now loads zones lazily on start, i.e. if the zonefile does not exist, it keeps trying with every reload period. The fixes a race. Multiple fixes in the plugin. And the removes the `resyncperiod` option. The appended entries from /etc/hosts on each (re-)parse, instead of overwriting them. Speed ups in the plugin. Anshul Sharma, Charlie Vieth, Chris O'Haver, Christian Muehlhaeuser, Erfan Besharat, Jintao Zhang, Mat Lowery, Miek Gieben, Ruslan Drozhdzh, Yong Tang. core: Scrub: TC bit is always set (https://github.com/coredns/coredns/pull/3001) pkg/cache: Fix race in Add() and Evict() (https://github.com/coredns/coredns/pull/3013) pkg/replacer: Evaluate format once and improve perf by ~3x (https://github.com/coredns/coredns/pull/3002) plugin/file: Fix setting ReloadInterval (https://github.com/coredns/coredns/pull/3017) plugin/file: Make non-existent file non-fatal (https://github.com/coredns/coredns/pull/2955) plugin/file: New zone should have zero records (https://github.com/coredns/coredns/pull/3025) plugin/file: Rename do to walk and cleanup and document (https://github.com/coredns/coredns/pull/2987) plugin/file: Simplify locking (https://github.com/coredns/coredns/pull/3024) plugin/host: don't append the names when reparsing hosts file (https://github.com/coredns/coredns/pull/3045) plugin/kubernetes: Remove resyncperiod (https://github.com/coredns/coredns/pull/2923) plugin/log: Fix log plugin benchmark and slightly improve performance (https://github.com/coredns/coredns/pull/3004) plugin/metrics: Fix responsercodecount_total metric (https://github.com/coredns/coredns/pull/3029) plugin/rewrite: Fix domain length validation (https://github.com/coredns/coredns/pull/2995) plugin/route53: Fix IAM credential file (https://github.com/coredns/coredns/pull/2983) plugin/route53: Fix multiple credentials in route53 (https://github.com/coredns/coredns/pull/2859)
Project: MetalLB (Orchestration & Management / Service Proxy)
File: include.en.md

+++ description = "Displays content from other files" title = "Include" +++ The `include` shortcode includes other files from your project inside of the current page. While the examples are using shortcodes with named parameter you are free to use positional aswell or also call this shortcode from your own partials. {{< tabs groupid="shortcode-parameter">}} {{% tab title="shortcode" %}} ````go {{%/ include file="shortcodes/INCLUDE_ME.md" /%}} ```` {{% /tab %}} {{% tab title="shortcode (positional)" %}} ````go {{%/ include "shortcodes/INCLUDE_ME.md" /%}} ```` {{% /tab %}} {{% tab title="partial" %}} ````go {{ partial "shortcodes/include .html" (dict "page" . "file" "shortcodes/INCLUDE_ME.md" )}} ```` {{% /tab %}} {{< /tabs >}} The included files can even contain Markdown and will be taken into account when generating the table of contents. | Name | Position | Default | Notes | |-|-||-| | file | 1 | &lt;empty&gt; | The path to the file to be included. Path resolution adheres to | | hidefirstheading | 2 | `false` | When `true` and the included file contains headings, the first heading will be hidden. This comes in handy, eg. if you include otherwise standalone Markdown files. | ````go {{%/ include "shortcodes/INCLUDE_ME.md" /%}} ```` {{% include "shortcodes/INCLUDE_ME.md" %}}
Project: CoreDNS (Orchestration & Management / Coordination & Service Discovery)
File: coredns-1.9.3.md

+++ title = "CoreDNS-1.9.3 Release" description = "CoreDNS-1.9.3 Release Notes." tags = ["Release", "1.9.3", "Notes"] release = "1.9.3" date = "2022-05-27T00:00:00+00:00" author = "coredns" +++ This is a release with a focus on security (CVE-2022-27191 and CVE-2022-28948) fixes. Additionally, several feature enhancements and bug fixes have been added. Chris O'Haver, lobshunter, Naveen, Radim Hatlapatka, RetoHaslerMGB, Tintin, Yong Tang core: update gopkg.in/yaml.v3 to fix CVE-2022-28948 (https://github.com/coredns/coredns/pull/5408) core: update golang.org/x/crypto to fix CVE-2022-27191 (https://github.com/coredns/coredns/pull/5407) plugin/acl: adding a check to parse out zone info (https://github.com/coredns/coredns/pull/5387) plugin/dnstap: support FQDN TCP endpoint (https://github.com/coredns/coredns/pull/5377) plugin/errors: add `stacktrace` option to log a stacktrace during panic recovery (https://github.com/coredns/coredns/pull/5392) plugin/template: return SERVFAIL for zone-match regex-no-match case (https://github.com/coredns/coredns/pull/5180)
Project: Serverless Devs (Orchestration & Management / Scheduling & Orchestration)
File: CHANGELOG.md

All notable changes to this project will be documented in this file. The format is based on , and this project adheres to . due to - only use env component after being manually set (PR by ): only use env component after being manually set (#820) - only use env component after being manually set (PR by ) - flow stuck when flow projects > 1 and diff (PR by ) - support custom registry (commit by ) - support no input parameters (PR by ) - registry provider support huoshan (commit by ) - github registry default load from devsapp (PR by ) - action `fc3 invoke` timeout (PR by ) - component action command not found (PR by ) - remove dingtalk (commit by ) - command not found when load dev component (commit by )
Project: Gloo (Orchestration & Management / API Gateway)
File: caching.proto.sk.md

title: "caching.proto" weight: 5 <!-- Code generated by solo-kit. DO NOT EDIT. --> ```yaml "cachingServiceRef": .core.solo.io.ResourceRef "allowedVaryHeaders": []solo.io.envoy.type.matcher.v3.StringMatcher "timeout": .google.protobuf.Duration "maxPayloadSize": .google.protobuf.UInt32Value ``` | Field | Type | Description | | -- | - | -- | | `cachingServiceRef` | | The basic reference for the service. Details name and namespace. | | `allowedVaryHeaders` | | A list of string matchers that state what headers are allowed to vary and still be cached. Per upstream envoy allowed vary headers. | | `timeout` | | Connection timeout for retrieval from an sync cache. | | `maxPayloadSize` | | Max payload size to cache. If unset defaults to a reasonable value. If explicitly set to 0 will prevent anything with a body from being cached. | <!-- 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: Kubernetes (Orchestration & Management / Scheduling & Orchestration)
File: MIGRATION_GUIDE.md

Starting from , the import path will be: "github.com/golang-jwt/jwt/v4" The `/v4` version will be backwards compatible with existing `v3.x.y` tags in this repo, as well as `github.com/dgrijalva/jwt-go`. For most users this should be a drop-in replacement, if you're having troubles migrating, please open an issue. You can replace all occurrences of `github.com/dgrijalva/jwt-go` or `github.com/golang-jwt/jwt` with `github.com/golang-jwt/jwt/v4`, either manually or by using tools such as `sed` or `gofmt`. And then you'd typically run: ``` go get github.com/golang-jwt/jwt/v4 go mod tidy ``` The original migration guide for older releases can be found at https://github.com/dgrijalva/jwt-go/blob/master/MIGRATION_GUIDE.md.
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2015-08-05-mesoscon-goes-europe.md

layout: post title: MesosCon goes Europe permalink: /blog/mesoscon-goes-europe/ published: true post_author: display_name: Michael Hausenblas twitter: mhausenblas tags: MesosCon The Mesos has been growing steadily over the past years and on behalf of the #MesosCon Program Committee Im excited and proud to be able to share the great news with you: MesosCon is now a world-wide event and this fall it comes to Europe. Organized by the Apache Mesos community, brings together users and developers to share and learn about the project and its growing ecosystem. MesosCon Europe 2015 will take place in Dublin, Ireland and feature a full day of sessions to learn more about the Mesos core, an ecosystem developed around the project, and related technologies. The program will include workshops to get started with Mesos, keynote speakers from industry leaders, and sessions led by adopters and contributors. Day two will feature a hackathon held at the conference. Now is a good time to start preparing yourself for #MesosCon Europe: no matter if you want to contribute through a talk submission (see the for details) or want to support us through a sponsorship. Stay tuned via and mark these dates in your calendar: Early bird registration closes: 24 August 2015 CfP deadline: 25 August 2015 Schedule announced: 15 September 2015 Conference dates: 8 and 9 October 2015 More info: Help us make this first European #MesosCon event a big success by spreading the word and !
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_route_sort.md

title: "glooctl route sort" weight: 5 sort routes on an existing virtual service The order of routes matters. A route is selected for a request based on the first matching route matcher in the virtual service's list. Sort automatically sorts the routes in the virtual service Usage: `glooctl route sort [--name virtual-service-name] [--namespace virtual-service-namespace]` ``` glooctl route sort [flags] ``` ``` -h, --help help for sort -o, --output OutputType output format: (yaml, json, table, kube-yaml, wide) (default table) ``` ``` -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") --use-consul use Consul Key-Value storage as the backend for reading and writing config (VirtualServices, Upstreams, and Proxies) ``` - subcommands for interacting with routes within virtual services
Project: APISIX (Orchestration & Management / API Gateway)
File: request-id.md

title: request-id keywords: Apache APISIX API Gateway Request ID description: This document describes information about the Apache APISIX request-id Plugin, you can use it to track API requests by adding a unique ID to each request. <!-- --> The `request-id` Plugin adds a unique ID to each request proxied through APISIX. This Plugin can be used to track API requests. :::note The Plugin will not add a unique ID if the request already has a header with the configured `header_name`. ::: | Name | Type | Required | Default | Valid values | Description | | - | - | -- | -- | - | - | | header_name | string | False | "X-Request-Id" | | Header name for the unique request ID. | | includeinresponse | boolean | False | true | | When set to `true`, adds the unique request ID in the response header. | | algorithm | string | False | "uuid" | ["uuid", "nanoid", "range_id"] | Algorithm to use for generating the unique request ID. | | rangeid.charset | string | False | "abcdefghijklmnopqrstuvwxyzABCDEFGHIGKLMNOPQRSTUVWXYZ0123456789| The minimum string length is 6 | Character set for range_id | | rangeid.length | integer | False | 16 | Minimum 6 | Id length for rangeid algorithm | The example below enables the 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 http://127.0.0.1:9180/apisix/admin/routes/5 \ -H "X-API-KEY: $admin_key" -X PUT -d ' { "uri": "/hello", "plugins": { "request-id": { "includeinresponse": true } }, "upstream": { "type": "roundrobin", "nodes": { "127.0.0.1:8080": 1 } } }' ``` Once you have configured the Plugin as shown above, APISIX will create a unique ID for each request you make: ```shell curl -i http://127.0.0.1:9080/hello ``` ```shell HTTP/1.1 200 OK X-Request-Id: fe32076a-d0a5-49a6-a361-6c244c1df956 ``` To remove the `request-id` 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/5 \ -H "X-API-KEY: $admin_key" -X PUT -d ' { "uri": "/get", "plugins": { }, "upstream": { "type": "roundrobin", "nodes": { "127.0.0.1:8080": 1 } } }' ```
Project: Pipy (Orchestration & Management / Service Proxy)
File: log_format.md

leveldb Log format ================== The log file contents are a sequence of 32KB blocks. The only exception is that the tail of the file may contain a partial block. Each block consists of a sequence of records: block := record* trailer? record := checksum: uint32 // crc32c of type and data[] ; little-endian length: uint16 // little-endian type: uint8 // One of FULL, FIRST, MIDDLE, LAST data: uint8[length] A record never starts within the last six bytes of a block (since it won't fit). Any leftover bytes here form the trailer, which must consist entirely of zero bytes and must be skipped by readers. Aside: if exactly seven bytes are left in the current block, and a new non-zero length record is added, the writer must emit a FIRST record (which contains zero bytes of user data) to fill up the trailing seven bytes of the block and then emit all of the user data in subsequent blocks. More types may be added in the future. Some Readers may skip record types they do not understand, others may report that some data was skipped. FULL == 1 FIRST == 2 MIDDLE == 3 LAST == 4 The FULL record contains the contents of an entire user record. FIRST, MIDDLE, LAST are types used for user records that have been split into multiple fragments (typically because of block boundaries). FIRST is the type of the first fragment of a user record, LAST is the type of the last fragment of a user record, and MIDDLE is the type of all interior fragments of a user record. Example: consider a sequence of user records: A: length 1000 B: length 97270 C: length 8000 A will be stored as a FULL record in the first block. B will be split into three fragments: first fragment occupies the rest of the first block, second fragment occupies the entirety of the second block, and the third fragment occupies a prefix of the third block. This will leave six bytes free in the third block, which will be left empty as the trailer. C will be stored as a FULL record in the fourth block. We do not need any heuristics for resyncing - just go to next block boundary and scan. If there is a corruption, skip to the next block. As a side-benefit, we do not get confused when part of the contents of one log file are embedded as a record inside another log file. Splitting at approximate boundaries (e.g., for mapreduce) is simple: find the next block boundary and skip records until we hit a FULL or FIRST record. We do not need extra buffering for large records. No packing of tiny records. This could be fixed by adding a new record type, so it is a shortcoming of the current implementation, not necessarily the format. No compression. Again, this could be fixed by adding new record types.
Project: Gloo (Orchestration & Management / API Gateway)
File: wasm.proto.sk.md

title: "wasm.proto" weight: 5 <!-- Code generated by solo-kit. DO NOT EDIT. --> Options config for WASM filters ```yaml "filters": []wasm.options.gloo.solo.io.WasmFilter ``` | Field | Type | Description | | -- | - | -- | | `filters` | | list of WASM filters to be added into the filter chain. | This message defines a single Envoy WASM filter to be placed into the filter chain ```yaml "image": string "filePath": string "config": .google.protobuf.Any "filterStage": .wasm.options.gloo.solo.io.FilterStage "name": string "rootId": string "vmType": .wasm.options.gloo.solo.io.WasmFilter.VmType "failOpen": bool ``` | Field | Type | Description | | -- | - | -- | | `image` | `string` | name of image which houses the compiled wasm filter. Only one of `image` or `filePath` can be set. | | `filePath` | `string` | path from which to load wasm filter from disk. Only one of `filePath` or `image` can be set. | | `config` | | Filter/service configuration used to configure or reconfigure a plugin (proxyonconfiguration). `google.protobuf.Struct` is serialized as JSON before passing it to the plugin. `google.protobuf.BytesValue` and `google.protobuf.StringValue` are passed directly without the wrapper. | | `filterStage` | | the stage in the filter chain where this filter should be placed. | | `name` | `string` | the name of the filter, used for logging. | | `rootId` | `string` | the root_id of the filter which should be run, if this value is incorrect, or empty the filter will crash. | | `vmType` | | selected VM type. | | `failOpen` | `bool` | when true, bypass the filter if there is a fatal error on the VM; defaults to false. | represents the different types of WASM VMs available with which envoy can run the WASM filter module | Name | Description | | -- | -- | | `V8` | | | `WAVM` | | ```yaml "stage": .wasm.options.gloo.solo.io.FilterStage.Stage "predicate": .wasm.options.gloo.solo.io.FilterStage.Predicate ``` | Field | Type | Description | | -- | - | -- | | `stage` | | stage of the filter chain in which the selected filter should be added. | | `predicate` | | How this filter should be placed relative to the stage. | list of filter stages which can be selected for a WASM filter | Name | Description | | -- | -- | | `FaultStage` | | | `CorsStage` | | | `WafStage` | | | `AuthNStage` | | | `AuthZStage` | | | `RateLimitStage` | | | `AcceptedStage` | | | `OutAuthStage` | | | `RouteStage` | | During is the 0th member so that it is the default, even though the reading order can be a little confusing | Name | Description | | -- | -- | | `During` | | | `Before` | | | `After` | | <!-- 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: Azure API Management (Orchestration & Management / API Gateway)
File: SECURITY.md

<!-- BEGIN MICROSOFT SECURITY.MD V0.0.5 BLOCK --> Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include , , , , , and . If you believe you have found a security vulnerability in any Microsoft-owned repository that meets ), please report it to us as described below. Please do not report security vulnerabilities through public GitHub issues. Instead, please report them to the Microsoft Security Response Center (MSRC) at . If you prefer to submit without logging in, send email to . If possible, encrypt your message with our PGP key; please download it from the . You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at . Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue: Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.) Full paths of source file(s) related to the manifestation of the issue The location of the affected source code (tag/branch/commit or direct URL) Any special configuration required to reproduce the issue Step-by-step instructions to reproduce the issue Proof-of-concept or exploit code (if possible) Impact of the issue, including how an attacker might exploit the issue This information will help us triage your report more quickly. If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our page for more details about our active programs. We prefer all communications to be in English. Microsoft follows the principle of . <!-- END MICROSOFT SECURITY.MD BLOCK -->
Project: Netflix Eureka (Orchestration & Management / Coordination & Service Discovery)
File: README.md

The eureka example requires 3 participants: a centralized eureka server for registration and discovery an example service to register with eureka that exposes a REST endpoint an example client that discovers the example service via discovery, and then queries the example service on it's registered REST endpoint. Edit and uncomment the two settings that makes the demo server start up faster (via disabling safeguards) the application. The above build also sets up all the libraries needed for running the demo service and the demo client. Copy the WAR artifact to your tomcat deployment directory under $TOMCATHOME/webapps/ <pre><code> cp ./eureka-server/build/libs/eureka-server-XXX-SNAPSHOT.war $TOMCAT_HOME/webapps/eureka.war </pre></code> Create (or add to) a setenv.sh in tomcat/bin/ with the following java opts (these are for the demo server to start up fast, see EurekaServerConfig.java for their documentation): <pre> JAVA_OPTS=" \ -Deureka.waitTimeInMsWhenSyncEmpty=0 \ -Deureka.numberRegistrySyncRetries=0" </pre> Start your tomcat server. Access **http://localhost:8080/eureka** to verify the information there. Your server's eureka client should register itself in 30 seconds and you should see that information there. Start up a local eureka server Run the example service first with <code>./gradlew :eureka-examples:runExampleService</code> and wait until you see "Service started and ready to process requests.." indicating that is had registered with eureka. Run the example client with <code>./gradlew :eureka-examples:runExampleClient</code>. Start up a local eureka server Build a zip distribution with <code>./gradlew :eureka-examples:distZip</code> In the distribution run <code>./bin/ExampleEurekaService</code> and wait until you see "Service started and ready to process requests.." indicating that is had registered with eureka. In the distribution run <code>./bin/ExampleEurekaClient</code> to run the example client. An example service that registers itself with eureka. (Note: prefer the DI version of creation in ExampleEurekaGovernatedService). The same as the ExampleEurekaService, where Governator/Guice is used to initialize everything. The gradle javaExec for this is <code>./gradlew :eureka-examples:runExampleGovernatedService</code> and the distribution generated script is <code>./bin/ExampleEurekaGovernatedService</code> An example use case of the eureka client to find a particular application/vip (in this case the example service) via eureka for communication.