cwielenb/CNCF-Dataset huggingface dataset:
Project: KrakenD (Orchestration & Management / API Gateway)
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 hello@krakend.io. 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: k8gb (Orchestration & Management / Coordination & Service Discovery)
File: ADOPTERS.md

This list captures the set of organizations that are using K8GB within their environments. If you are an adopter of K8GB and not yet on this list, we encourage you to add your organization here as well! Contributing to this list is a small effort that has a big impact to the project's growth, maturity, and momentum. Thank you to all adopters and contributors of the K8GB project! This list is sorted in the order that organizations were added to it. | Organization | Contact | Description of Use | | | - | | | @kuritka | K8GB was created in Absa and had there first production use in cross-regional datacenter context | @infbase | Multicloud and multi-region cloud native load balancing | @punasusi | As a cloud-native and devops consulting firm, we have used k8gb in customer engagements
Project: BFE (Orchestration & Management / Service Proxy)
File: tls.md

Description: Check whether tls sni matches host_list Parameters | Parameter | Description | | | -- | | host_list | String<br>a list of hosts which are concatenated using &#124; | Example ```go sestlssni_in("example.com|example.org") ``` Description: Check whether tls mutual authentication is enabled Description: Check whether tls mutual authentication is enabled and client ca matches ca_list Parameters | Parameter | Description | | | -- | | ca_list | String<br>a list of ca names which are concatenated using &#124; | Example ```go sestlsclientcain("ca1|ca2") ```
Project: Contour (Orchestration & Management / Service Proxy)
File: CHANGELOG-v1.21.1.md

We are delighted to present version v1.21.1 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters. A big thank you to everyone who contributed to the release. Bumps Envoy to security patch version 1.22.2. Envoy CI had a few issues releasing 1.22.1 so a subsequent patch, 1.22.2 was released. Envoy announcement . See Envoy release notes and . (#4573, @sunjayBhatia) When validating secrets, don't log an error for an Opaque secret that doesn't contain a `ca.crt` key. (#4528, @skriss) Fixes TLS private key validation logic which previously ignored errors for PKCS1 and PKCS8 private keys. (#4544, @sunjayBhatia) Update gopkg.in/yaml.v3 to v3.0.1 to address CVE-2022-28948. (#4551, @tsaarni) For a fresh install of Contour, consult the . To upgrade an existing Contour installation, please consult the . Contour v1.21.1 is tested against Kubernetes 1.21 through 1.23. Were immensely grateful for all the community contributions that help make Contour even better! If you're using Contour and want to add your organization to our adopters list, please visit this . If you prefer to keep your organization name anonymous but still give us feedback into your usage and scenarios for Contour, please post on this .
Project: Traefik Mesh (Orchestration & Management / Service Mesh)
File: documentation.md

title: "Traefik Mesh Documentation" description: "You've found something unclear in the documentation and want to give a try at explaining it better? Learn how you can do so in this article." You've found something unclear in the documentation and want to give a try at explaining it better? Let's see how. This is built with . You can build the documentation and test it locally (with live reloading), using the `serve` target: ```bash $ make serve docker build -t traefik-mesh-docs -f docs.Dockerfile ./ docker run --rm -v /home/user/traefik-mesh/docs:/mkdocs -p 8000:8000 traefik-mesh-docs mkdocs serve INFO - Building documentation... INFO - Cleaning site directory [I 200408 14:36:33 server:296] Serving on http://0.0.0.0:8000 [I 200408 14:36:33 handlers:62] Start watching changes [I 200408 14:36:33 handlers:64] Start detecting changes ``` !!! Note By default, the local documentation server listens on . To build the documentation without serving it locally, use the `build` target. First, make sure you have `python` and `pip` installed. MkDocs supports `python` versions `2.7.9+`, `3.4`, `3.5`, `3.6` and `3.7`. ```bash $ python --version Python 2.7.14 $ pip --version pip 19.3.1 from /usr/local/lib/python2.7/site-packages/pip (python 2.7) ``` Then, install MkDocs with `pip`. ```bash pip install --user -r requirements.txt ``` To build the documentation and serve it locally, run `mkdocs serve` from the root directory. This starts a local server, and exposes the documentation on `http://127.0.0.1:8000`: ```bash $ mkdocs serve INFO - Building documentation... INFO - Cleaning site directory [I 160505 22:31:24 server:281] Serving on http://127.0.0.1:8000 [I 160505 22:31:24 handlers:59] Start watching changes [I 160505 22:31:24 handlers:61] Start detecting changes ``` To check that the documentation meets standard expectations (no dead links, html markup validity, ...), use the `verify` target. If you've made changes to the documentation, it's safer to clean it before verifying it. ```bash $ make clean verify docker build -t traefik-mesh-docs -f docs.Dockerfile ./ docker run --rm -v /home/user/traefik-mesh/docs:/mkdocs -p 8000:8000 traefik-mesh-docs sh -c "mkdocs build && chown -R 501:20 ./site" === Checking HTML content... ``` !!! Note "Disabling Verification" Verification can be disabled by setting the environment variable `DOCSVERIFYSKIP` to `true`: ```bash $ DOCSVERIFYSKIP=true make verify DOCSVERIFYSKIP is true: no verification done. ```
Project: Fluid (Orchestration & Management / Scheduling & Orchestration)
File: CHANGES.md

Documentation updates. Small linter cleanups. Added example in test. Document the usage of Cleanup when re-reading a file (thanks to @lesovsky) for issue #18. Add example directories with example and tests for issues. Fix of checksum problem because of forced tag. No changes to the code. Incorporated PR 162 by by Mohammed902: "Simplify non-Windows build tag". Incorporated PR 9 by mschneider82: "Added seekinfo to Tail". Incorporated PR 7: "Fix deadlock when stopping on non-empty file/buffer", fixes upstream issue 93. Incorporated changes of unmerged upstream PR 149 by mezzi: "added line num to Line struct". Incorporated changes of unmerged upstream PR 128 by jadekler: "Compile-able code in readme". Incorporated changes of unmerged upstream PR 130 by fgeller: "small change to comment wording". Incorporated changes of unmerged upstream PR 133 by sm3142: "removed spurious newlines from log messages". Incorporated changes of unmerged upstream PR 126 by Code-Hex: "Solved the problem for never return the last line if it's not followed by a newline". Incorporated changes of unmerged upstream PR 131 by StoicPerlman: "Remove deprecated os.SEEK consts". The changes bumped the minimal supported Go release to 1.9. migration to go modules. release of master branch of the dormant upstream, because it contains fixes and improvement no present in the tagged release.
Project: Contour (Orchestration & Management / Service Proxy)
File: CHANGELOG-v1.22.6.md

We are delighted to present version v1.22.6 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters. Update to Envoy v1.23.7. 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.22.6 is tested against Kubernetes 1.22 through 1.24. 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: Contour (Orchestration & Management / Service Proxy)
File: SITE_CONTRIBUTION.md

is a static HTML site built using the Hugo static site generator. All site content is written in Markdown. Contribution and still apply to site contributions. Please familiarize yourself with Hugo and Markdown if you intend on contributing to the site. You must have Hugo installed. Follow the instructions for your platform. To verify the installation, you should see a list of help commands when you run the following command: ``` hugo help ``` A local copy of the contour repository The website content is located in the `site/content` directory. The `site` directory is organized as follows: ``` site archetypes content community # Community page docs # Versioned product documentation main v1.0.0 v1.0.1 ... examples getting-started # Getting started guide guides # Guides to configuring specific features posts # Blog posts resources # Resources such as videos, podcasts, and community articles data img public # Blog resources themes ``` Reference table links are preferred over inline links as reference tables make it easier to find and update links. Reference table links use the following Markdown format: ``` If you encounter issues, review the page, , or talk to us on the on Kubernetes Slack. ``` A reference table, located at the end of the Markdown file, uses the following format: ``` ``` Several URL parameters are available for you to use when creating reference table links: base_url: "https://projectcontour.io" twitter_url: "https://twitter.com/projectcontour" github_url: "https://github.com/projectcontour/contour" slack_url: "https://kubernetes.slack.com/messages/contour" latest_version: latest document version You can use parameters to build URL strings in the link reference table. For example: ``` ``` Notices are used to call out specific information. There are four types of notices: Tip Information Warning Notes Notice types use the following format: ``` {{< notice tip >}} This is a TIP {{< /notice >}} {{< notice info >}} This is INFORMATION {{< /notice >}} {{< notice warning >}} This is a WARNING {{< /notice >}} {{< notice note >}} This is a NOTE {{< /notice >}} ``` Most IDEs have spellcheck or a spellcheck plugin to assist with identifying common spelling errors. If you would like, have someone else review your changes as an additional check. To test your website changes, run the following command from the `site` directory: ``` hugo server ``` Go to `http://localhost:1313` to view the website and changes in your browser. When ready, commit and push your changes to GitHub and create a Pull Request (PR). You can let the team know in the that you have created a PR. Have questions? Send a Slack message on the Contour channel, an email on the mailing list, or join a Contour meeting. Slack: kubernetes.slack.com Join us in a or meeting Join the for the latest information
Project: TARS (Orchestration & Management / Remote Procedure Call)
File: Contributing.md

If you contributed but cannot find your ID in the file, please submit PR and add your GitHub ID to both contributing file under your contributed repo and . ruanshudong loveyacper LawlietLi meijing0114 medns dpp2009 TOKISAKIKURUMI change93 helloopenworld meiping copyrenzhe bobzhangyong wjx82850707 Spacebody souldancer zerolocusta markshan 9chu Abioy bartdong bishaoqing bobzhangyong change93 Cnlouds copyrenzhe cygsxak deepzliu dolphinxwc dpp2009 duoyu119 ETZhangSX Fr1ck ganziqim guzitajiu helloopenworld higithubhi isabellavieira jerrylucky KatharineOzil kuangxc lanffy lanyutc LawlietLee LawlietLi loveyacper maplebeats marklightning mdhender medns meijing0114 meiping MR-workaholic munglechina parchk qiuxin ruanshudong sandyskies scguoi serverlessplus songvy souldancer Spacebody sy-records tarstest TCZWJ TimmyYu tinkercloud TOKISAKIKURUMI wjx82850707 youngdou YoungZiyi yuansx yukkiball zehuaiWANG zerolocusta BeyondWUXF ruanshudong markshan Abioy jerrylucky langio marklightning ruanshudong shevqko Spacebody TCZWJ viest YMChenLiye zhanleewo BeyondWUXF forrestlinfeng markshan forrestlinfeng wincsb diracccc ruanshudong ruanshudong markshan bartdong Frankie franklee0817 ruanshudong RuizhaoLi ruanshudong KatharineOzil bartdong Cnlouds markshan bartdong Cnlouds danielzheng-Tencent jerrylucky KatharineOzil meijing0114 ruanshudong yukkiball zouchengzhuo ruanshudong wincsb markshan diracccc ETZhangSX jerrylucky lanhy MindHook mygrsun renyang9876 ruanshudong shevqko wincsb ypingcn yuansx BeyondWUXF sandyskies jchalex chenhengqi MonkeyLi tensorchen rikewang markshan lbbniu 0xflotus agchrys Andrew-M-C bartdong BurningXFlame chenhengqi Clark-zhang ClaudeLiang cokeboL defool erjanmx hooligan520 hotWing17 imthx jchalex jyuan68 lanhy louishlz marklightning maplebeats mdhender mjaow MonkeyLi mountkin nickwanninger philippgille qiuxin rbarros rikewang ruanshudong sandyskies skelway TauWu tensorchen terryding77 wqliang wzshiming xiaoxubeii xuri YaffaBeauty YouEclipse lbbniu BeyondWUXF TimmyYu XenoAmess diracccc LawlietLi markshan diracccc kahn LawlietLi LiuMenghan TimmyYu walkertest woodwind XenoAmess yukkiball meijing0114 bobzhangyong copyrenzhe dpp2009 markshan bobzhangyong copyrenzhe cuixg danielzheng-Tencent dpp2009 meijing0114 wodetian55 medmin sy-records ruanshudong shevqko markshan jerrylucky ruanshudong shevqko hpeiy98 ruanshudong zouchengzhuo ziyang314 shevqko markshan airycanon ETZhangSX jerrylucky lanhy ouliuquan ruanshudong sandyskies shevqko wjx82850707 ypingcn ziyang314 zouchengzhuo BeyondWUXF boycs007 jnlunsb markshan boycs007 jnlunsb juliuslu-tencent medmin markshan medmin bartdong defool markshan bartdong defool hpeiy98 KatharineOzil andyguo1023 cheney-ying heisewuyu16 Quentin-by harveyxu-tme markshan harveyxu-tme hpeiy98 shevqko markshan shevqko ruanshudong hpeiy98 wincsb KatharineOzil dankohn KatharineOzil dankohn bartdong jordinl83 heisewuyu16 shevqko eatonzhang markshan shevqko eatonzhang markshan hpeiy98
Project: Gloo (Orchestration & Management / API Gateway)
File: endpoint.proto.sk.md

title: "endpoint.proto" weight: 5 <!-- Code generated by solo-kit. DO NOT EDIT. --> Top-Level Resource Endpoints represent dynamically discovered address/ports where an upstream service is listening ```yaml "upstreams": []core.solo.io.ResourceRef "address": string "port": int "hostname": string "healthCheck": .gloo.solo.io.HealthCheckConfig "metadata": .core.solo.io.Metadata ``` | Field | Type | Description | | -- | - | -- | | `upstreams` | | List of the upstreams the endpoint belongs to. | | `address` | `string` | Address of the endpoint (ip or hostname). | | `port` | `int` | listening port for the endpoint. | | `hostname` | `string` | hostname to use for the endpoint (e.g., auto host rewrite) if provided. | | `healthCheck` | | configuration for health checking the endpoint. | | `metadata` | | Metadata contains the object metadata for this resource. | ```yaml "hostname": string ``` | Field | Type | Description | | -- | - | -- | | `hostname` | `string` | hostname to use for the endpoint health checks if provided. | <!-- 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: Fluid (Orchestration & Management / Scheduling & Orchestration)
File: api_proxy.md

Alluxio provides an access interface based on the for secondary development in Python, Java and Golang. AlluxioRuntime also provides support for this, and the feature is not turned on by default. It can be turned on via a CRD declaration. Create Dataset and AlluxioRuntime resource objects ```yaml $ cat<<EOF >dataset.yaml apiVersion: data.fluid.io/v1alpha1 kind: Dataset metadata: name: spark spec: mounts: mountPoint: https://mirrors.bit.edu.cn/apache/spark/ name: spark apiVersion: data.fluid.io/v1alpha1 kind: AlluxioRuntime metadata: name: spark spec: replicas: 1 tieredstore: levels: mediumtype: MEM path: /dev/shm quota: 1Gi high: "0.95" low: "0.7" properties: alluxio.user.streaming.data.timeout: 300sec apiGateway: enabled: true EOF ``` Note: Just set apiGateway to true to enable this capability. Check Access Endpoint ``` $ kubectl get alluxioruntimes.data.fluid.io -owide NAME READY MASTERS DESIRED MASTERS MASTER PHASE READY WORKERS DESIRED WORKERS WORKER PHASE READY FUSES DESIRED FUSES FUSE PHASE API GATEWAY AGE spark 1 1 Ready 1 1 Ready 0 0 Ready spark-master-0.default:20009 110s ``` You can see that the API Gateway is accessed at spark-master-0.default:20009. You can access it from this address.
Project: Skipper (Orchestration & Management / Service Proxy)
File: east-west-usage.md

If you run Skipper with an [East-West setup](ingress-controller.md#run-as-api-gateway-with-east-west-setup), you can use the configured ingress also to do service-to-service calls, bypassing your ingress loadbalancer and stay inside the cluster. You can connect via HTTP to your application based on its ingress configuration. Example: ```yaml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: demo namespace: default spec: rules: host: demo.skipper.cluster.local http: paths: backend: service: name: example port: number: 80 pathType: ImplementationSpecific ``` Or as a : ```yaml apiVersion: zalando.org/v1 kind: RouteGroup metadata: name: demo namespace: default spec: hosts: demo.skipper.cluster.local backends: name: backend type: service serviceName: example servicePort: 80 defaultBackends: backendName: backend ``` Your clients inside the cluster should call this example with `demo.skipper.cluster.local` in their host header. Example from inside a container: ``` curl http://demo.skipper.cluster.local/ ``` You can also use the same ingress or RouteGroup object to accept internal and external traffic: ```yaml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: demo namespace: default spec: rules: host: demo.example.com http: paths: backend: service: name: example port: number: 80 pathType: ImplementationSpecific host: demo.skipper.cluster.local http: paths: backend: service: name: example port: number: 80 pathType: ImplementationSpecific ``` Or, again, as a : ```yaml apiVersion: zalando.org/v1 kind: RouteGroup metadata: name: demo namespace: default spec: hosts: demo.skipper.cluster.local demo.example.com backends: name: backend type: service serviceName: example servicePort: 80 defaultBackends: backendName: backend ``` Metrics will change, because skipper stores metrics per HTTP Host header, which changes with cluster internal calls from `demo.example.org` to `demo.default.skipper.cluster.local`. You can use all features as defined in [Ingress Usage](ingress-usage.md), , via [annotations as before](ingress-usage.md#filters-and-predicates) and also .
Project: Volcano (Orchestration & Management / Scheduling & Orchestration)
File: scheduling-reason.md

; Aug 13, 2021 ; Dec 12, 2022 Currently, the reason and message in `pod.status.conditions["PodScheduled"]` and `podgroup.status.conditions["Unschedulable"]` is NOT informative, for example `x/x tasks in gang unschedulable: pod group is not ready, x Pending, x minAvailable`. Users want to know which one breaks the scheduling cycle and why is that. (@tgaddair): However, cluster autoscaling systems like explicitly check for the `Unschedulable` reason on the pod to trigger scale-up (see ). As such, we need to keep the `Reason` field consistent with default scheduler behavior. Introducing an extra scheduling reasons in PodScheduled PodCondition: `Schedulable`: means that the scheduler can schedule the pod right now, but not bind yet. An additional reason was originally considered that conflicts with cluster autoscaler. Instead, this reason only appears in the detailed `Message` field, and shows up with `Reason: Unschedulable` in the pod: `Undetermined`: means that the scheduler skips scheduling the pod which left the pod `Undetermined`, for example due to unschedulable pod already occurred. Case: 3 nodes: node1, node2, node3; 6 tasks in the PodGroup(`minAvailable = 6`); only 1 task(Task6) is unschedulable and other 5 tasks(Task1 ~ 5) can be scheduled, thus the whole job is unscheduable. Current information: |Tasks|Reason|Message| |-|-|-| |PodGroup |NotEnoughResources|6/6 tasks in gang unschedulable: pod group is not ready, 6 Pending, 6 minAvailable | |Task1 ~ 5|Unschedulable|6/6 tasks in gang unschedulable: pod group is not ready, 6 Pending, 6 minAvailable| |Task6|Unschedulable| all nodes are unavailable: 1 plugin InterPodAffinity predicates failed node(s) didn't match pod affinity/anti-affinity, node(s) didn't match pod affinity rules, 2 node(s) resource fit failed.| Improved information: |Tasks|Reason|Message| |-|-|-| |PodGroup |(same)| 3/6 tasks in gang unschedulable: pod group is not ready, 6 Pending, 6 minAvailable; Pending: 1 Unschedulable, 2 Undetermined, 3 Schedulable | |Task1 ~ 2|Unschedulable| 3/6 tasks in gang unschedulable: pod group is not ready, 6 Pending, 6 minAvailable; Pending: 1 Unschedulable, 2 Undetermined, 3 Schedulable | |Task3|Schedulable| Pod ns1/task-1 can possibly be assgined to node1 | |Task4|Schedulable| Pod ns1/task-2 can possibly be assgined to node2 | |Task5|Schedulable| Pod ns1/task-3 can possibly be assgined to node3 | |Task6|Unschedulable| all nodes are unavailable: 1 plugin InterPodAffinity predicates failed node(s) didn't match pod affinity/anti-affinity, node(s) didn't match pod affinity rules, 2 node(s) resource fit failed.| Note: Task1 & 2 are `Unschedulable` maybe because that this two locate after task6 by `TaskOrderFn`; In improved information, we can easily find the one that breaks the whole scheduling cycle and why dose that happen. Additionally, we can find the histogram of reason why there are some tasks whose status is pending.