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

title: "xslt_transformer.proto" weight: 5 <!-- Code generated by solo-kit. DO NOT EDIT. --> Defines an XSLT Transformation. ```yaml "xslt": string "setContentType": string "nonXmlTransform": bool ``` | Field | Type | Description | | -- | - | -- | | `xslt` | `string` | XSLT transformation template which you want to transform requests/responses with. Invalid XSLT transformation templates will result will result in a NACK during envoy configuration-time and the configuration will not be loaded. | | `setContentType` | `string` | Changes the content-type header of the HTTP request/response to what is set here. This is useful in situations where an XSLT transformation is used to transform XML to JSON and the content-type should be changed from `application/xml` to `application/json`. If left empty, the content-type header remains unmodified by default. | | `nonXmlTransform` | `bool` | This should be set to true if the content being transformed is not XML. For example, if the content being transformed is from JSON to XML, this should be set to true. XSLT transformations can only take valid XML as input to be transformed. If the body is not a valid XML (e.g. using JSON as input in a JSON-to-XML transformation), setting `nonxmltransform` to true will allow the XSLT to accept the non-XML input without throwing an error by passing the input as XML CDATA. defaults to false. | <!-- 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: Gravitee.io (Orchestration & Management / API Gateway)
File: organization-configuration-notification-templates.md

Here you can find all the templates used when notifications are triggered in the platform as well as email templates used for specific actions. Templates are grouped by category: API Application Portal Templates for action In the last category Templates to include, you can find all html templates that can be included in others email templates. (e.g. `header.html`) Click on a template to edit a portal and/or an email notification. When a portal or an email notification has been customized, a `CUSTOM` label is added to the template name.
Project: Pipy (Orchestration & Management / Service Proxy)
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 opening an issue or contacting the project maintainers. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and 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: Avro (Orchestration & Management / Remote Procedure Call)
File: avro-1.4.0-released.md

title: "Avro 1.4.0" linkTitle: "Avro 1.4.0" date: 2010-09-08 <!-- 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.4.0 has been released!
Project: CoreDNS (Orchestration & Management / Coordination & Service Discovery)
File: coredns-1.8.4.md

+++ title = "CoreDNS-1.8.4 Release" description = "CoreDNS-1.8.4 Release Notes." tags = ["Release", "1.8.4", "Notes"] release = "1.8.4" date = 2021-05-28T07:00:00+00:00 author = "coredns" +++ The CoreDNS team has released . This release includes a bunch of bugfixes and a few enhancements mostly in the dnssec and kubernetes plugins, and a new (small) plugin called minimal. It also include a fix when using the "reverse zone cidr syntax", e.g. 10.0.0.0/15, now return the proper set of reverse zones. Chris O'Haver, cuirunxing-hub, Frank Riley, Keith Coleman, Miek Gieben, milgradesec, Mohammad Yosefpor, ntoofu, Paco Xu, Soumya Ghosh Dastidar, Steve Greene, Thotime Lvque, Uwe Krueger, wangchenglong01, Yong Tang, Yury Tsarev. core: fix reverse zones expansion (https://github.com/coredns/coredns/pull/4538) plugins: fix Normalize (https://github.com/coredns/coredns/pull/4621) reverse zone: make Normalize return proper reverse zones (https://github.com/coredns/coredns/pull/4621) plugin/bind: Bind by interface name (https://github.com/coredns/coredns/pull/4522) plugin/bind: Exclude interface or ip address (https://github.com/coredns/coredns/pull/4543) plugin/dnssec: Check for two days of remaining validity (https://github.com/coredns/coredns/pull/4606) plugin/dnssec: interface type correction for `periodicClean` sig validity check (https://github.com/coredns/coredns/pull/4608) plugin/dnssec: use entire RRset as key input (https://github.com/coredns/coredns/pull/4537) plugin/etcd: Bump etcd to v3.5.0-beta.3 (https://github.com/coredns/coredns/pull/4638) plugin/forward: Add upstream metadata (https://github.com/coredns/coredns/pull/4521) plugin/health: add logging for local health request (https://github.com/coredns/coredns/pull/4533) plugin/kubernetes: consider nil ready as ready (https://github.com/coredns/coredns/pull/4632) plugin/kubernetes: do endpoint/slice check in retry loop (https://github.com/coredns/coredns/pull/4492) plugin/kubernetes: Exclude unready endpoints from endpointslices (https://github.com/coredns/coredns/pull/4580) plugin/metrics: remove RR type (https://github.com/coredns/coredns/pull/4534) plugin/minimal: Add minimal-responses plugin (https://github.com/coredns/coredns/pull/4417) plugin/rewrite: streamline the ResponseRule handling. (https://github.com/coredns/coredns/pull/4473) plugin/sign: Revert "plugin/sign: track zone file's mtime (https://github.com/coredns/coredns/pull/4431)" plugin/transfer: reply with refused (https://github.com/coredns/coredns/pull/4510)
Project: Reactive Interaction Gateway (Orchestration & Management / API Gateway)
File: user-authorization.md

id: user-authorization title: User Authorization sidebar_label: User Authorization RIG supports the (JWT) standard for authorizing users when forwarding HTTP requests, or when handling event subscription or submission requests. Note that RIG does not do authentication - you will need to provide a service for that yourself. This means that RIG does not create any tokens on its own. Given a JWT, RIG only checks its validity, using a shared secret key or a public key, depending on the algorithm used. Please refer to the for the corresponding configuration options. Also note the following: For incoming HTTP requests, JWT validation can be enabled on a per endpoint basis using the `secured` option. Event subscriptions can be secured using JWT validation by setting `SUBSCRIPTIONCHECK` to `jwtvalidation`. Likewise, event submissions can be secured using JWT validation by setting `SUBMISSIONCHECK` to `jwtvalidation`. Again, refer to the for details on those environment variables. For symmetric hashing (HS256, RS256), please make sure you are using keys of appropriate length, as described in . For example, if you use HS256, your secret key should be at least 32 character (256 bit) in length. Example of a minimal JWT: ```javascript // Header: { "alg": "HS256", "typ": "JWT" } // Payload: { "exp": 99999999 } ```
Project: Serverless Devs (Orchestration & Management / Scheduling & Orchestration)
File: cli_design.md

title: Cli specification description: 'Serverless Devs Command line design specification' position: 10 category: 'Overview' Serverless Devs, as a developer tool in the serverless field, the standardization and standardization of its output will have a more obvious impact on the user experience to a certain extent. This document will standardize and upgrade the output of Serverless Devs command line tools through some text and cases. The canonical goals of the output format are: Clearer More concise Does not affect the function and practicality Based on the above three principles, we can use examples to illustrate the normal output form and the abnormal output form. The basic output form includes two parts as a whole: Project implementation phase The project execution phase mainly includes a basic format: ``` Steps for process ==================== ``` The rewrite mechanism is used to continuously update the output content. After each project is executed, the corresponding result can be output. Example: ``` Steps for process ==================== Pre-action completed (10s) ``` Result output stage The project execution phase mainly includes a basic format: ``` Result for process ==================== ``` The specific project output is output in the format of `Yaml`. When outputting, the project name should be underlined. If there is no output, the project will be ended directly. Example: ``` Result for process ==================== MyProject deployed (11s) fc-deploy-test: region: cn-hangzhou service: name: fc-deploy-service memorySize: 128 ``` When the user enters the debug mode with `--debug`, very detailed information will be printed on the console, but the information will be printed out in gray to maintain the overall sense of hierarchy: When an error occurs in execution, Serverless Devs must sense and output the corresponding content: ``` Steps for process ==================== MyProject pre-action completed (10s) MyProject failed to deploy: Error Message: t[r] is not a function Env: darwin, node v15.14.0 Docs: https://github.com/serverless-devs/docs Bugs: https://github.com/Serverless-Devs/Serverless-Devs/issues Logs: ~/demo/demo/demo/s.log ``` The dynamic effects are:
Project: BFE (Orchestration & Management / Service Proxy)
File: reload.md

BFE has a built-in feature of configuration hot-reload. A new configuration file can be reload by sending a reload request. Set MonitorPort in BFE core configuration file(conf/bfe.conf) ```ini [Server] MonitorPort = 8421 ``` Reload APIs only allows to be accessed using localhost127.0.0.1/::1and only supports GET requests ```bash $ curl http://localhost:8421/reload/serverdataconf ``` The complete list of reload APIs can be viewed at http://localhost:8421/reload | Function | Default configuration file | Reload API | | - | - | -- | | routing | serverdataconf/hostrule.data<br>serverdataconf/viprule.data<br>serverdataconf/routerule.data<br>serverdataconf/clusterconf.data | /reload/serverdataconf | | balancing | clusterconf/clustertable.data<br>clusterconf/gslb.data | /reload/gslbdata_conf | | name conf | serverdataconf/nameconf.data | /reload/nameconf | | TLS rule | tlsconf/servercertconf.data<br>tlsconf/tlsruleconf.data | /reload/tls_conf | | TLS session ticket key | tlsconf/sessionticketkey.data | /reload/tlssessionticketkey | | Module | Default configuration file | Reload API | | -- | - | -- | | modauthbasic | modauthbasic/authbasicrule.data | /reload/modauthbasic| | modblock | modblock/blockrules.data<br>modblock/ipblocklist.data | /reload/modblock.productruletable<br>/reload/modblock.globalip_table | | modcompress | modcompress/compressrule.data | /reload/modcompress | | moderrors | moderrors/errorsrule.data | /reload/moderrors | | modgeo | modgeo/geo.db | /reload/mod_geo | | modheader | modheader/headerrule.data | /reload/modheader | | modredirect | modredirect/redirect.data | /reload/mod_redirect | | modrewrite | modrewrite/rewrite.data | /reload/mod_rewrite | | modstatic | modstatic/staticrule.data<br>modstatic/mimetype.data | /reload/modstatic<br>/reload/modstatic.mimetype | | modtrustclientip | modtrustclientip/trustclientip.data | /reload/modtrustclientip |
Project: Open Service Mesh (Orchestration & Management / Service Mesh)
File: pull_request_template.md

<!-- Please describe the motivation for this PR and provide enough information so that others can review it. --> Description: <!-- Please describe how this change was tested. You could include supporting information such as logs, snippets, and screenshots. --> Testing done: <!-- Please mark with X for applicable areas. --> Affected area: | Functional Area | | | -- | | | New Functionality | [ ] | | CI System | [ ] | | CLI Tool | [ ] | | Certificate Management | [ ] | | Control Plane | [ ] | | Demo | [ ] | | Documentation | [ ] | | Egress | [ ] | | Ingress | [ ] | | Install | [ ] | | Networking | [ ] | | Observability | [ ] | | Performance | [ ] | | SMI Policy | [ ] | | Security | [ ] | | Sidecar Injection | [ ] | | Tests | [ ] | | Upgrade | [ ] | | Other | [ ] | Please answer the following questions with yes/no. Does this change contain code from or inspired by another project? Did you notify the maintainers and provide attribution? Is this a breaking change? Has documentation corresponding to this change been updated in the repo (if applicable)?
Project: DolphinScheduler (Orchestration & Management / Scheduling & Orchestration)
File: enterprise-wechat.md

If you need to use `Enterprise WeChat` to alert, create an alert instance in the alert instance management, and choose the `WeChat` plugin. The following is the `WeChat` configuration example: The parameter `send.type` corresponds to sending messages to Enterprise WeChat customized APP and group chat created by API respectively. The APP sends type means to notify the alert results via Enterprise WeChat customized APPs, supports sending messages to both specified users and all members. Currently, send to specified enterprise department and tags are not supported, a new PR to contribute is welcomed. The following is the `APP` alert config example: The following is the `APP` `MARKDOWN` alert message example: The following is the `APP` `TEXT` alert message example: Need to create a new customized APP in Enterprise WeChat before sending messages to APP, create at the and acquire the APP `AgentId` and set its visible scope to the root of the hierarchy. The Enterprise WeChat APPs support sending messages to both specified users and all members, using `|` to separate multiple `userIds` and using `@all` to send messages to everyone. To acquire user `userId` refer to , acquire `userId` by user phone number. The following is the `query userId` API example: APP: https://work.weixin.qq.com/api/doc/90000/90135/90236 The Group Chat send type means to notify the alert results via group chat created by Enterprise WeChat API, sending messages to all members of the group and specified users are not supported. The following is the `Group Chat` alert config example: The following is the `APP` `MARKDOWN` alert message example: The following is the `Group Chat` `TEXT` alert message example: Before sending messages to group chat, create a new group chat by Enterprise WeChat API, refer to to create a new one and acquire `chatid`. To acquire user `userId` refer to , acquire `userId` by user phone number. The following is the `create new group chat` API and `query userId` API example: Group Chathttps://work.weixin.qq.com/api/doc/90000/90135/90248
Project: Envoy (Orchestration & Management / Service Proxy)
File: README.md

This directory contains tools which is useful for developers using VSCode. It is recommended to use , or setting up an equivalent environment. Recommended extensions and settings are listed in . `tools/vscode/refresh_compdb.sh` is a script to refresh compilation database, it may take a while to generate all dependencies for code completion, such as protobuf generated codes, external dependencies. If you changed proto definition, or changed any bazel structure, rerun this to get code completion correctly. Note that it is recommended to disable VSCode Microsoft C/C++ extension and use `vscode-clangd` instead for C/C++ code completion. For developers in China, you might need to set `httpproxy`, `httpsproxy`, `all_proxy` in advance. If you see the following error message: ``` ERROR: /workspaces/envoy/contrib/hyperscan/matching/inputmatchers/source/BUILD:21:12: Foreign Cc - CMake: Building hyperscan failed: (Exit 1): bash failed: error executing command /bin/bash -c bazel-out/k8-fastbuild/bin/contrib/hyperscan/matching/inputmatchers/source/hyperscanforeigncc/wrapperbuildscript.sh ...... -- Performing Test HAVE_SSSE3 -- Performing Test HAVE_SSSE3 - Failed -- Performing Test HAVE_AVX2 -- Performing Test HAVE_AVX2 - Failed -- Performing Test HAVE_AVX512 -- Performing Test HAVE_AVX512 - Failed -- Building without AVX2 support -- Building without AVX512 support CMake Error at cmake/arch.cmake:108 (message): A minimum of SSSE3 compiler support is required ...... ``` Please check the cpu info of your virtual machine (e.g., ssse3): `cat /proc/cpuinfo | grep ssse3` If there is no output from this command, change the default cpu type `kvm64` to `max`. `tools/vscode/generatedebugconfig.py` is a script to generate VSCode debug config in `.vscode/launch.json`. The generated config will be named `<debugger type> <bazel target>`. For example: ``` tools/vscode/generatedebugconfig.py //source/exe:envoy-static --args "-c envoy.yaml" ``` Generates an entry named `gdb //source/exe:envoy-static` for GDB in `launch.json`. It can be used to generate config for tests also. The generated `gdb` config are compatible with extension, `lldb` config are compatible with extension.
Project: BFE (Orchestration & Management / Service Proxy)
File: getting_help.md

We are very interested in building a community around BFE. If you are interested in using it or need help, please feel free to contact us. Welcome to submit issues at https://github.com/bfenetworks/bfe/issues/new/choose, we will reply you in working days Security issues and bugs should be reported privately to bfe-security@baidu.com. Please do not open issues for anything you think might have a security implication. We sincerely appreciate your contribution. Please visit https://github.com/bfenetworks/bfe and follow the . Welcome to email us at bfe-osc@baidu.com
Project: Kusk Gateway (Orchestration & Management / API Gateway)
File: README.md

Ensure you have a cluster running and have Kusk Gateway and an EnvoyFleet deployed. For minikube, you can do this with make `create-env` Run all smoke tests ``` make check-all ``` or individually: ``` make check-basic ``` Before adding a smoke test first add test in Makefile.variables in form check-{test_name} Next add a directory in smoketest {test_name}. Ensure that you are implementing tests like this: ``` type SomeTestCheckSuite struct { common.KuskTestSuite } ``` s/websocket``` . Run test, by connecting to the external IP address of EnvoyFleet and typing anything when it runs - the response should be HELO from ws service. We need to use "--network=host" for Docker to see any Kubernetes clusters deployed on the local host. ```sh // endpoint from the StaticRoute definition docker run --rm -ti --network=host solsson/websocat ws://ExternalIPAddress>:80/staticwebsocket blablabla '[ws] HELO' // endpoint from the API definition docker run --rm -ti --network=host solsson/websocat ws://ExternalIPAddress>:80/apiwebsocket blablabla '[ws] HELO' // endpoint from the API definition, this one must fail docker run --rm -ti --network=host solsson/websocat ws://ExternalIPAddress>:80/disabledapiwebsocket websocat: WebSocketError: WebSocket response error websocat: error running ``` In the stdout of the Envoy container should be access log entry like: ``` "[2022-01-04T12:31:16.991Z]" "GET" "/staticewebsocket" "101" "4298" ``` where 101 is the response HTTP code from Envoy Proxy to the request with HTTP Upgrade header present during the tunnel setup.
Project: KEDA (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. -->