cwielenb/CNCF-Dataset huggingface dataset:
Project: Clusterpedia (Orchestration & Management / Scheduling & Orchestration)
File: CODE_OF_CONDUCT.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at oss-conduct@uber.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at .
Project: APISIX (Orchestration & Management / API Gateway)
File: grpc-web.md

title: grpc-web keywords: Apache APISIX API Gateway Plugin gRPC Web grpc-web description: This document contains information about the Apache APISIX grpc-web Plugin. <!-- --> The `grpc-web` Plugin is a proxy Plugin that can process requests from JavaScript clients to a gRPC service. | Name | Type | Required | Default | Description | |-||-|--|-| | corsallowheaders | string | False | "content-type,x-grpc-web,x-user-agent" | Headers in the request allowed when accessing a cross-origin resource. Use `,` to add multiple headers. | You can enable the `grpc-web` Plugin on a specific Route as shown below: :::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/1 -H "X-API-KEY: $admin_key" -X PUT -d ' { "uri":"/grpc/web/*", "plugins":{ "grpc-web":{} }, "upstream":{ "scheme":"grpc", "type":"roundrobin", "nodes":{ "127.0.0.1:1980":1 } } }' ``` :::info IMPORTANT While using the `grpc-web` Plugin, always use a prefix matching pattern (`/`, `/grpc/example/`) for matching Routes. This is because the gRPC Web client passes the package name, the service interface name, the method name and other information in the proto in the URI. For example, `/path/a6.RouteService/Insert`. So, when absolute matching is used, the Plugin would not be hit and the information from the proto would not be extracted. ::: Refer to or to learn how to setup your web client. Once you have your gRPC Web client running, you can make a request to APISIX from the browser or through Node.js. :::note The supported request methods are `POST` and `OPTIONS`. See . The supported `Content-Type` includes `application/grpc-web`, `application/grpc-web-text`, `application/grpc-web+proto`, and `application/grpc-web-text+proto`. See . ::: To remove the `grpc-web` 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":"/grpc/web/*", "plugins":{}, "upstream":{ "scheme":"grpc", "type":"roundrobin", "nodes":{ "127.0.0.1:1980":1 } } }' ```
Project: Open Cluster Management (Orchestration & Management / Scheduling & Orchestration)
File: CONTRIBUTING.md

Welcome to Kubernetes. We are excited about the prospect of you joining our ! The Kubernetes community abides by the CNCF . Here is an excerpt: As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities. We have full documentation on how to get started contributing here: <! If your repo has certain guidelines for contribution, put them here ahead of the general k8s resources --> Kubernetes projects require that you sign a Contributor License Agreement (CLA) before we can accept your pull requests - Main contributor documentation, or you can just jump directly to the - Common resources for existing developers - We have a diverse set of mentorship programs available that are always looking for volunteers! <! Custom Information - if you're copying this template for the first time you can add custom content here, for example: - Replace `kubernetes-users` with your slack channel string, this will send users directly to your channel. --> ontributor-cheatsheet) - Common resources for existing developers You can reach the maintainers of this project via the . - We have a diverse set of mentorship programs available that are always looking for volunteers!
Project: DolphinScheduler (Orchestration & Management / Scheduling & Orchestration)
File: project-parameter.md

Project-level parameters are valid for all task nodes under the entire project. On the project page, click Project Parameters and Create Parameters, and fill in the parameter name and parameter value. As shown below: Take the shell task as an example, enter `echo ${param}` in the script content, where `param` is the project-level parameter created in the previous step. Run the shell task. On the task instance page, you can view the task log to verify whether the parameters are valid.
Project: Serverless Devs (Orchestration & Management / Scheduling & Orchestration)
File: component.md

title: Component Command description: 'Component Command' position: 5 category: 'Command' `component` is used to get the details of installed components. - When we execute `s component -h`, we can get help information: ```shell script $ s component -h Usage: s component [options] Get details of installed components. Example: $ s component Document: https://serverless.help/t/s/component Options: -h, --help Display help for command. ``` No parameters are required. We can execute `s component` to get all installed components, for example: ```shell script $ s component serverless registry [https://registry.serverless-devs.com] Component Version Size Description fc 0.1.27 100 MB Aliyun Function Compute Base Component devsapp/fc 0.1.27 100 MB Aliyun Function Compute Base Component fc api 0.0.44 100 MB Function Compute api operation component ```
Project: KEDA (Orchestration & Management / Scheduling & Orchestration)
File: MAINTAINERS.md

This page lists all active maintainers of this repository. If you were a maintainer and would like to add your name to the Emeritus list, please send us a PR. See for governance guidelines and how to become a maintainer. See for general contribution guidelines. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC
Project: Karmada (Orchestration & Management / Scheduling & Orchestration)
File: ROADMAP.md

This document defines a high level roadmap for Karmada development and upcoming releases. Community and contributor involvement is vital for successfully implementing all desired items for each release. We hope that the items listed below will inspire further engagement from the community to keep Karmada progressing and shipping exciting and valuable features. Cluster scheduling group Multiple schedulers support Application-level failover Multi-cluster HPA (Horizontal Pod Autoscaling) Karmada operator ResourceInterpreter include third-party CRD resources Karmada playground Karmada Dashboard - alpha release Multi-cluster workflow Cluster addon management Multi-cluster Application Multi-cluster monitoring Multi-cluster logging Multi-cluster storage Multi-cluster RBAC Multi-cluster networking Data migration across clusters Integration with terraform Cluster lifecycle management Image registry across clouds Multi-cluster Service Mesh solutions
Project: Service Mesh Performance (Orchestration & Management / Service Mesh)
File: template.md

caption: #what displays in the post grid: title: Example subtitle: subtitle thumbnail: https://place-hold.it/400x300 title: Title published: false subtitle: subtitle lorem ipsum dolor sit amet consectetur. image: https://place-hold.it/400x300 #main image, can be a link or a file in assets/img/posts alt: image alt text Use this area to describe your post. Markdown supported. optional info list (delete if not using): {:.list-inline} Date: Client: Category:
Project: Higress (Orchestration & Management / API Gateway)
File: SECURITY.md

| Version | Supported | | - | | | 1.x.x | :whitecheckmark: | | < 1.0.0 | :x: | Please report any security issue or Higress crash report to (Alibaba Security Response Center) where the issue will be triaged appropriately. Thank you in advance for helping to keep Higress secure.
Project: Consul (Orchestration & Management / Service Mesh)
File: LICENSE.md

This license is temporary while a more official one is drafted. However, this should make it clear: The text contents of this website are MPL 2.0 licensed. The design contents of this website are proprietary and may not be reproduced or reused in any way other than to run the website locally. The license for the design is owned solely by HashiCorp, Inc.
Project: Gloo (Orchestration & Management / API Gateway)
File: http_inputs.proto.sk.md

title: "http_inputs.proto" weight: 5 <!-- Code generated by solo-kit. DO NOT EDIT. --> Specifies that matching should be performed on the set of :ref:`HTTP attributes <archoverviewattributes>`. The attributes will be exposed via `Common Expression Language <https://github.com/google/cel-spec>`_ runtime to associated CEL matcher. Refer to :ref:`Unified Matcher API <envoyv3apimsg.xds.type.matcher.v3.Matcher>` documentation for usage details. [#comment:TODO(sergiitk): When implemented, add the extension tag.] ```yaml ``` | Field | Type | Description | | -- | - | -- | <!-- 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: Avro (Orchestration & Management / Remote Procedure Call)
File: avro-1.3.1-released.md

title: "Avro 1.3.1" linkTitle: "Avro 1.3.1" date: 2010-03-19 <!-- 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.3.1 has been released!
Project: KubeAdmiral (Orchestration & Management / Scheduling & Orchestration)
File: MAINTAINERS.md

This file lists the maintainers of the KubeAdmiral project. The responsibilities of maintainers are listed in the file. | Name | GitHub | Affiliation | | - | | -- | | Chan Kwan Yin | | ByteDance | | Deliang Fan | | ByteDance | | Gary Liu | | ByteDance | | Jingsi Ren | | ByteDance | | Lim Haw Jia | | ByteDance | | Shengli Liu | | ByteDance | | Yixiang Chen | | ByteDance |
Project: Kong (Orchestration & Management / API Gateway)
File: COMMUNITY_PLEDGE.md

Kong Gateway is not only an awesome open source project, but also part of the product offering of Kong Inc. We have a large team of product people, software developers, testers and release engineers working on Kong Gateway. We make many of the enhancements to Kong Gateway in the Community Edition, so our open source community directly benefits from the commercial work that we do. Recognizing that we operate as a commercial entity, we face the challenge of balancing our commercial interests with the desire to accommodate and support open source users and contributors effectively. In the Kong Gateway team, we're committed to maintaining a rapid and timely response to community contributions, promising to acknowledge and engage within a dedicated timeframe of 10 working days. It is important to note, however, that while we strive to be as responsive as possible, we may not always be able to offer immediate solutions to every reported problem or incorporate every submitted pull request into the product. We will be closing pull requests or issue reports when we made the decision that we will not be able to merge or resolve them in the foreseeable future. We do that in the interest of keeping our working set manageable, as accumulating pull requests and issues which don't make progress does not help improving Kong Gateway in the long run. We automatically close issues and pull requests for which we do not get responses to our questions or update requests within 3 weeks.
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_create_upstream_ec2.md

title: "glooctl create upstream ec2" weight: 5 Create an EC2 Upstream EC2 Upstreams represent a collection of EC2 instance endpoints that match the specified tag filters. You can use private (default) or public IP addresses and and any port on the instance (default: 80).EC2 Upstreams require a valid set of AWS Credentials to be provided, either as an AWS secret, or in the environment. You can optionally provide a Role for Gloo to assume on behalf of this upstream. ``` glooctl create upstream ec2 [flags] ``` ``` --aws-region string region for AWS services this upstream utilize (default "us-east-1") --aws-role-arn string Amazon Resource Number (ARN) of role that Gloo should assume on behalf of the upstream --aws-secret-name glooctl create secret aws --help name of a secret containing AWS credentials created with glooctl. See glooctl create secret aws --help for help creating secrets --aws-secret-namespace glooctl create secret aws --help namespace where the AWS secret lives. See glooctl create secret aws --help for help creating secrets (default "gloo-system") --ec2-port uint32 port to use to connect to the EC2 instance (default 80) (default 80) -h, --help help for ec2 --public-ip use instance's public IP address --tag-key-filters strings list of tag keys that must exist on EC2 instances associated with this upstream --tag-key-value-filters strings list of tag keys and corresponding values that must exist on EC2 instances associated with this upstream ``` ``` -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 --dry-run print kubernetes-formatted yaml rather than creating or updating a resource -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) --use-consul use Consul Key-Value storage as the backend for reading and writing config (VirtualServices, Upstreams, and Proxies) ``` - Create an Upstream
Project: Lunar.dev (Orchestration & Management / API Gateway)
File: README.md

A behavior-driven-design (BDD) test suite aimed at ensuring Lunar Interceptor is functioning according to its required specification. Testing is done from the outside (i.e. blackbox testing). See chart above. Testing encapsulate the usage site in a container which is called client. Each client runs with a specific language and version (e.g. Python 3.10). The functionality of Lunar Proxy is mocked, by using mox. The path that the client makes an HTTP call to is set up in mox as well in order to emulate potential early response from Lunar Proxy. Navigate to `interceptor-integration-tests` Install dependencies: ```shell pipenv install --dev ``` Run the test suite for the desired client: ```shell CLIENTLANGUAGE=python CLIENTVERSION=3.10 pipenv run behave ``` or ```shell CLIENT_LANGUAGE=java pipenv run behave ``` Note that java client does not support different versions at the moment.
Project: Azure Service Fabric (Orchestration & Management / Scheduling & Orchestration)
File: Service-Fabric-71CU8-releasenotes.md

This release includes bug fixes as described in this document. This release is made available only and will not be available through automatic upgrades. The following packages and versions are part of this release: | Service | Platform | Version | ||-|| |Service Fabric Runtime| Ubuntu 16 <br> Ubuntu 18 <br> Windows | N/A <br> N/A <br> 7.1.503.9590 | |Service Fabric for Windows Server|Service Fabric Standalone Installer Package | N/A | |.NET SDK |Windows .NET SDK <br> Microsoft.ServiceFabric <br> Reliable Services and Reliable Actors <br> ASP.NET Core Service Fabric integration| 4.1.458 <br> 7.1.458 <br> 4.1.458 <br> 4.1.458 | |Java SDK |Java for Linux SDK | 1.0.6 | |Service Fabric PowerShell and CLI | AzureRM PowerShell Module <br> SFCTL | 0.3.15 <br> 10.0.0 | Microsoft Azure Service Fabric 7.1 Eighth Refresh Release Notes | Versions | IssueType | Description | Resolution | |-|-|-|-| | Windows 7.1.503.9590 <br> | Bug | Assert when error code not read/checked | Brief desc: This release includes a fix for an assert that happens because an error code was not read/checked. <br> Impact: Assert occurs when the error code cannot be read/checked. <br> Workaround: N/A <br> Fix: Upgrade to the latest version.
Project: CoreDNS (Orchestration & Management / Coordination & Service Discovery)
File: coredns-1.2.2.md

+++ title = "CoreDNS-1.2.2 Release" description = "CoreDNS-1.2.2 Release Notes." tags = ["Release", "1.2.2", "Notes"] release = "1.2.2" date = "2018-08-29T07:10:29+01:00" author = "coredns" +++ We are pleased to announce the of CoreDNS-1.2.2! This is a (small) release that helps out our friends at : make the default cache size smaller. The following people helped with getting this release done: Chris O'Haver, Miek Gieben. For documentation see our (in progress!) . For help and other resources, see our .
Project: Eraser (Orchestration & Management / Scheduling & Orchestration)
File: architecture.md

title: Architecture At a high level, Eraser has two main modes of operation: manual and automated. Manual image removal involves supplying a list of images to remove; Eraser then deploys pods to clean up the images you supplied. Automated image removal runs on a timer. By default, the automated process removes images based on the results of a vulnerability scan. The default vulnerability scanner is Trivy, but others can be provided in its place. Or, the scanner can be disabled altogether, in which case Eraser acts as a garbage collector -- it will remove all non-running images in your cluster. <img title="manual cleanup" src="/eraser/docs/img/eraser_manual.png" /> <img title="automated cleanup" src="/eraser/docs/img/eraser_timer.png" />
Project: Fluid (Orchestration & Management / Scheduling & Orchestration)
File: fuzzy_mode_convert_table.md

| json type \ dest type | bool | int | uint | float |string| | | | | |--|--| | number | positive => true <br/> negative => true <br/> zero => false| 23.2 => 23 <br/> -32.1 => -32| 12.1 => 12 <br/> -12.1 => 0|as normal|same as origin| | string | empty string => false <br/> string "0" => false <br/> other strings => true | "123.32" => 123 <br/> "-123.4" => -123 <br/> "123.23xxxw" => 123 <br/> "abcde12" => 0 <br/> "-32.1" => -32| 13.2 => 13 <br/> -1.1 => 0 |12.1 => 12.1 <br/> -12.3 => -12.3<br/> 12.4xxa => 12.4 <br/> +1.1e2 =>110 |same as origin| | bool | true => true <br/> false => false| true => 1 <br/> false => 0 | true => 1 <br/> false => 0 |true => 1 <br/>false => 0|true => "true" <br/> false => "false"| | object | true | 0 | 0 |0|originnal json| | array | empty array => false <br/> nonempty array => true| [] => 0 <br/> [1,2] => 1 | [] => 0 <br/> [1,2] => 1 |[] => 0<br/>[1,2] => 1|original json|
Project: APISIX (Orchestration & Management / API Gateway)
File: gm.md

title: GM keywords: Apache APISIX Plugin GM description: This article introduces the basic information and usage of the Apache APISIX `gm` plugin. <!-- --> :::info The function usage scenarios introduced in this article are mainly in China, so this article only has a Chinese version temporarily. You can click for more details. If you are interested in this feature, welcome to translate this document. :::