cwielenb/CNCF-Dataset huggingface dataset:
Project: BFE (Orchestration & Management / Service Proxy)
File: testcase1.md

Advertisement :) - high quality and fast image resize in browser. - developer friendly i18n with plurals support and easy syntax. You will like those projects! _ Enable typographer option to see result. (c) (C) (r) (R) (tm) (TM) (p) (P) +- test.. test... test..... test?..... test!.... !!!!!! ???? ,, -- "Smartypants, double quotes" and 'single quotes' This is bold text This is bold text This is italic text This is italic text Strikethrough Blockquotes can also be nested... > ...by using additional greater-than signs right next to each other... > > ...or with spaces between arrows. Unordered Create a list by starting a line with `+`, `-`, or `*` Sub-lists are made by indenting 2 spaces: Marker character change forces new list start: Ac tristique libero volutpat at Facilisis in pretium nisl aliquet Nulla volutpat aliquam velit Very easy! Ordered Lorem ipsum dolor sit amet Consectetur adipiscing elit Integer molestie lorem at massa You can use sequential numbers... ...or keep all the numbers as `1.` Start numbering with offset: foo bar Inline `code` Indented code // Some comments line 1 of code line 2 of code line 3 of code Block code "fences" ``` Sample text here... ``` Syntax highlighting ``` js var foo = function (bar) { return bar++; }; console.log(foo(5)); ``` | Option | Description | | | -- | | data | path to data files to supply the data that will be passed into templates. | | engine | engine to be used for processing templates. Handlebars is the default. | | ext | extension to be used for dest files. | Right aligned columns | Option | Description | | :| --:| | data | path to data files to supply the data that will be passed into templates. | | engine | engine to be used for processing templates. Handlebars is the default. | | ext | extension to be used for dest files. | Autoconverted link https://github.com/nodeca/pica (enable linkify to see) Like links, Images also have a footnote style syntax ! With a reference later in the document defining the URL location: The killer feature of `markdown-it` is very effective support of . Classic markup: :wink: :crush: :cry: :tear: :laughing: :yum: Shortcuts (emoticons): :-) :-( 8-) ;) see with twemoji. 19^th^ H~2~O ++Inserted text++ ==Marked text== Footnote 1 link[^first]. Footnote 2 link[^second]. Inline footnote^[Text of inline footnote] definition. Duplicated footnote reference[^second]. and multiple paragraphs. Term 1 : Definition 1 with lazy continuation. Term 2 with inline markup : Definition 2 { some code, part of Definition 2 } Third paragraph of definition 2. Compact style: Term 1 ~ Definition 1 Term 2 ~ Definition 2a ~ Definition 2b This is HTML abbreviation example. It converts "HTML", but keep intact partial entries like "xxxHTMLyyy" and so on. *[HTML]: Hyper Text Markup Language ::: warning here be dragons :::
Project: Sentinel (Orchestration & Management / Service Proxy)
File: README.md

Sentinel Metric Exporter is a module which provides the Sentinel metric data exporting ability. Now you can integrate it into your Sentinel application, and then get the metric data in JMX. You can also integrate the JMX data into your monitor system easily, like Prometheus. To use Sentinel Metric Exporter, you should add the following dependency: ```xml <dependency> <groupId>com.alibaba.csp</groupId> <artifactId>sentinel-metric-exporter</artifactId> <version>x.y.z</version> </dependency> ``` And then you can find the MBean info in your tool.
Project: Prefect (Orchestration & Management / Scheduling & Orchestration)
File: serverless-workers.md

description: Learn how to use Prefect to schedule work on serverless infrastructure that depends on a worker. tags: work pools deployments Cloud Run GCP Vertex AI AWS ECS Azure Container Instances ACI search: boost: 2 Prefect provides hybrid work pools for workers to run flows on the serverless platforms of major cloud providers. The following options are available: AWS Elastic Container Service (ECS) Azure Container Instances (ACI) Google Cloud Run Google Cloud Run V2 Google Vertex AI Create a work pool that sends work to your chosen serverless infrastructure Deploy a flow to that work pool Start a worker in your serverless cloud provider that will poll its matched work pool for scheduled runs Schedule a deployment run that a worker will pick up from the work pool and run on your serverless infrastructure !!! note "Push work pools don't require a worker" Options for push work pool versions of AWS ECS, Azure Container Instances, and Google Cloud Run that do not require a worker are available with Prefect Cloud. These push work pool options require connection configuration information to be stored on Prefect Cloud. Read more in the . This is a brief overview of the options to run workflows on serverless infrastructure. For in-depth guides, see the Prefect integration libraries: . For Google Vertex AI, follow the Cloud Run guide, substituting Google Vertex AI where Google Cloud Run is mentioned. !!! note "Choosing between Google Cloud Run and Google Vertex AI" Google Vertex AI is well-suited for machine learning model training applications in which GPUs or TPUs and high resource levels are desired. Make sure you have an user or service account on your chosen cloud provider with the necessary permissions to run serverless jobs Create the appropriate serverless work pool that uses a worker in the Prefect UI Create a deployment that references the work pool Start a worker in your chose serverless cloud provider infrastructure Run the deployment Options for push versions on AWS ECS, Azure Container Instances, and Google Cloud Run work pools that do not require a worker are available with Prefect Cloud. Read more in the . Learn more about workers and work pools in the . Learn about installing dependencies at runtime or baking them into your Docker image in the .
Project: k8gb (Orchestration & Management / Coordination & Service Discovery)
File: code-of-conduct.md

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 are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality. Examples of unacceptable behavior by participants include: The use of sexualized language or imagery Personal attacks Trolling or insulting/derogatory comments Public or private harassment Publishing others' private information, such as physical or electronic addresses, without explicit permission Other unethical or unprofessional conduct. 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. By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect of managing this project. Project maintainers who do not follow or enforce the Code of Conduct may be permanently removed from the project team. This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2019-02-26-mesos-1-4-3-released.md

layout: post title: Apache Mesos 1.4.3 Released permalink: /blog/mesos-1-4-3-released/ published: true post_author: display_name: Meng Zhu tags: Release The latest Mesos 1.4.x release, 1.4.3, is now available for . This release includes important bug fixes and improvements on top of 1.4.2. It is recommended to use this version if you are considering using Mesos 1.4. More specifically, this release includes the following notable fixes: - Make os::pipe file descriptors O_CLOEXEC. - Command checks should always call `WAITNESTEDCONTAINER` before `REMOVENESTEDCONTAINER` - Containers stuck in FETCHING possibly due to unresponsive server. - Agent leaking file descriptors into forked processes. - Autotools don't work with newer OpenJDK versions - Master authentication handling leads to request amplification. - Master has a fragile burned-in 5s authentication timeout. - Agent has a fragile burn-in 5s authentication timeout. - Agent and scheduler driver authentication retry backoff time could overflow. - Container stuck at ISOLATING due to FD leak. - Zookeeper doesn't compile with newer gcc due to format error. - Removing rootfs mounts may fail with EBUSY. - If some image layers are large, the image pulling may stuck due to the authorized token expired. - `docker inspect` may return an unexpected result to Docker executor due to a race condition. - Docker Containerizer 'usage' call might be expensive if mount table is big. - Docker containerizer actor can get backlogged with large number of containers. - Test `CGROUPSROOTPidNamespaceForward` and `CGROUPSROOTPidNamespaceBackward` fails on 1.4.x. - Container stuck at ISOLATING state due to libevent poll never returns. - Executor to framework message crashes master if framework has not re-registered. - Master may skip processing authorization results for `LAUNCH_GROUP`. - Persist CNI working directory across reboot. - Mesos executor fails to terminate and gets stuck after agent host reboot. - IOswitchboard cleanup could get stuck due to FD leak from a race. - CNI_NETNS should not be set for orphan containers that do not have network namespace. - ResourceOffersTest.ResourceOfferWithMultipleSlaves is flaky. - CniIsolatorTest.ROOT_CleanupAfterReboot is flaky. - Disallowed nan, inf and so on in `Value::Scalar`. - Extend `minallocatableresources` flag to cover non-scalar resources. Full release notes are available in the release Rolling upgrades from a Mesos 1.4.2 cluster to Mesos 1.4.3 are straightforward. Please refer to the for detailed information on upgrading to Mesos 1.4.2 from 1.0.x, 1.2.x, or 1.3.x. Please try out this release and let us know what you think. If you run into any issues, let us know on the . Thanks to the 18 contributors who made 1.4.3 possible: Alexander Rukletsov, Andrei Budnik, Andrew Schwartzmeyer, Benjamin Bannier, Benjamin Mahler, Benno Evers, Chun-Hung Hsiao, Deepak Goel, Gastn Kleiman, Gilbert Song, Greg Mann, James Peach, Jie Yu, Kapil Arya, Meng Zhu, Michael Park, Qian Zhang, Radhika Jandhyala
Project: Contour (Orchestration & Management / Service Proxy)
File: websockets.md

WebSocket support can be enabled on specific routes using the `enableWebsockets` field: ```yaml apiVersion: projectcontour.io/v1 kind: HTTPProxy metadata: name: chat namespace: default spec: virtualhost: fqdn: chat.example.com routes: services: name: chat-app port: 80 conditions: prefix: /websocket enableWebsockets: true # Setting this to true enables websocket for all paths that match /websocket services: name: chat-app port: 80 ```
Project: Traefik (Orchestration & Management / API Gateway)
File: configuration-overview.md

title: "Traefik Configuration Documentation" description: "Get started with Traefik Proxy. This page will introduce you to the dynamic routing and startup configurations. Read the technical documentation." How the Magic Happens {: .subtitle } Configuration in Traefik can refer to two different things: The fully dynamic routing configuration (referred to as the dynamic configuration) The startup configuration (referred to as the static configuration) Elements in the static configuration set up connections to and define the Traefik will listen to (these elements don't change often). The dynamic configuration contains everything that defines how the requests are handled by your system. This configuration can change and is seamlessly hot-reloaded, without any request interruption or connection loss. !!! warning "Incompatible Configuration" Please be aware that the old configurations for Traefik v1.x are NOT compatible with the v2.x config as of now. If you are running v2, please ensure you are using a v2 configuration. Traefik gets its dynamic configuration from : whether an orchestrator, a service registry, or a plain old configuration file. Since this configuration is specific to your infrastructure choices, we invite you to refer to the . !!! info "" In the , the dynamic configuration comes from docker in the form of labels attached to your containers. !!! info "HTTPS Certificates also belong to the dynamic configuration." You can add / update / remove them without restarting your Traefik instance. There are three different, mutually exclusive (i.e. you can use only one at the same time), ways to define static configuration options in Traefik: In a configuration file In the command-line arguments As environment variables These ways are evaluated in the order listed above. If no value was provided for a given option, a default value applies. Moreover, if an option has sub-options, and any of these sub-options is not specified, a default value will apply as well. For example, the `--providers.docker` option is enough by itself to enable the docker provider, even though sub-options like `--providers.docker.endpoint` exist. Once positioned, this option sets (and resets) all the default values of the sub-options of `--providers.docker`. At startup, Traefik searches for static configuration in a file named `traefik.yml` (or `traefik.yaml` or `traefik.toml`) in: `/etc/traefik/` `$XDGCONFIGHOME/` `$HOME/.config/` `.` (the working directory). You can override this using the `configFile` argument. ```bash traefik --configFile=foo/bar/myconfigfile.yml ``` To get the list of all available arguments: ```bash traefik --help docker run traefik[:version] --help ``` Check the for an overview about all available arguments. All available environment variables can be found in the . All the configuration options are documented in their related section. You can browse the available features in the menu, the , or the to see them in action. {!traefik-for-business-applications.md!}
Project: SRPC (Orchestration & Management / Remote Procedure Call)
File: docs-01-idl.md

Interface Description Languaue file Backward and forward compatibility Protobuf/Thrift You can follow the detailed example below: Take pb as an example. First, define an `example.proto` file with the ServiceName as `Example`. The name of the rpc interface is `Echo`, with the input parameter as `EchoRequest`, and the output parameter as `EchoResponse`. `EchoRequest` consists of two strings: `message` and `name`. `EchoResponse` consists of one string: `message`. ~~~proto syntax="proto2"; message EchoRequest { optional string message = 1; optional string name = 2; }; message EchoResponse { optional string message = 1; }; service Example { rpc Echo(EchoRequest) returns (EchoResponse); }; ~~~
Project: Gloo (Orchestration & Management / API Gateway)
File: changelog_types.md

title: Changelog Entry Types weight: 90 description: Explanation of the entry types used in our changelogs You will find several different kinds of changelog entries: Dependency Bumps A notice about a dependency in the project that had its version bumped in this release. Be sure to check for any "Breaking Change" entries accompanying a dependency bump. For example, a `gloo` version bump in Gloo Edge Enterprise may mean a change to a proto API. Breaking Changes A notice of a non-backwards-compatible change to some API. This can include things like a changed proto format, a change to the Helm chart, and other breakages. Occasionally a breaking change may mean that the process to upgrade the product is slightly different; in that case, we will be sure to specify in the changelog how the break must be handled. Helm Changes A notice of a change to our Helm chart. One of these entries does not by itself signify a breaking change to the Helm chart; you will find an accompanying "Breaking Change" entry in the release notes if that is the case. New Features A description of a new feature that has been implemented in this release. Fixes A description of a bug that was resolved in this release.
Project: kcp (Orchestration & Management / Scheduling & Orchestration)
File: partitions.md

description: > How to create shard partitions. `Partitions` and `PartitionSets` build an API that allows service providers and cluster administrators to create shard Partitions. These partitions can then be leveraged: for the deployment of the controllers of the service providers and other components. These APIs provide the information on shard topology required for the scheduling. for grouping APIExport endpoints of multiple shards in common buckets, that is `Partitions`. These buckets can the be used to achieve geo proximity: controllers should communicate with API servers of shards in the same region. They can also be leveraged for scalability and load distribution, that is to adapt the number of deployment/ processes to the load pattern specific to the controllers of a service provider. The partitioning of `Shards` is done through labels and . Here is an example of a `Partition`: ```yaml kind: Partition apiVersion: topology.kcp.io/v1alpha1 metadata: name: cloud-region-gcp-europe-xdfgs ownerReferences: ... spec: selector: matchLabels: cloud: gcp region: europe matchExpressions: key: country operator: NotIn values: LI ``` `Partitions` can be referenced in . `PartitionSets` is an API for convenience. `PartitionSet` can be used to get `Partitions` automatically created based on dimensions that match the shard label keys. The `Partitions` are created in the same workspace as the `PartitionSet`. They can then be copied to the desired workspace for consumption, for instance, by an `APIExportEndpointSlice`. Here is an example of a `PartitionSet`: ```yaml kind: PartitionSet apiVersion: topology.kcp.io/v1alpha1 metadata: name: cloud-region spec: dimensions: region cloud selectors: matchExpressions: key: region operator: NotIn values: Antarctica Greenland key: country operator: NotIn values: NK status: count: 10 ... ``` It is to note that a `Partition` is created only if it matches at least one shard. With the provided example if there is no shard in the cloud provider `aliyun` in the region `europe` no `Partition` will be created for it. An example of a `Partition` generated by this `PartitionSet` can be found above. The `dimensions` are translated into `matchLabels` with values specific to each `Partition`. An owner reference of the `Partition` will be set to the `PartitionSet`.
Project: Gloo (Orchestration & Management / API Gateway)
File: ingress.proto.sk.md

title: "ingress.proto" weight: 5 <!-- Code generated by solo-kit. DO NOT EDIT. --> Top-Level Resource A simple wrapper for a Kubernetes Ingress Object. ```yaml "kubeIngressSpec": .google.protobuf.Any "kubeIngressStatus": .google.protobuf.Any "metadata": .core.solo.io.Metadata ``` | Field | Type | Description | | -- | - | -- | | `kubeIngressSpec` | | a raw byte representation of the kubernetes ingress this resource wraps. | | `kubeIngressStatus` | | a raw byte representation of the ingress status of the kubernetes ingress object. | | `metadata` | | Metadata contains the object metadata for this resource. | <!-- 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: new-committer-christophe-le-saec.md

title: "New committer: Christophe Le Saec" linkTitle: "New committer: Christophe Le Saec" date: 2023-08-09 <!-- 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. --> The Project Management Committee (PMC) for Apache Avro has invited Christophe Le Saec to become a committer and we are pleased to announce that he has accepted. Christophe definitely puts in the work and, has an impressive breadth of knowledge about the languages of the Avro SDK! As an ASF project, we tend to be very conservative about making changes, and Christophe brings in fresh ideas and very quickly proposes concrete implementations to prove them. He has a good understanding of Avro, the motivation to move things forward, and the expertise to make changes! At the same time, he's easy to talk to and flexible in coming to a consensus. Thanks for all your hard work!
Project: Prefect (Orchestration & Management / Scheduling & Orchestration)
File: index.md

description: Learn the basics of creating and running Prefect flows and tasks. tags: tutorial getting started basics tasks flows subflows deployments workers work pools search: boost: 2 Learn the basics of creating and running Prefect flows and tasks. Prefect orchestrates workflows through the creation, scheduling, and monitoring of complex data pipelines. You can transform any Python function into a unit of work that can be observed and orchestrated. You define workflows as Python code and Prefect handles the rest. Prefect also provides error handling, retry mechanisms, and a user-friendly dashboard for monitoring. This tutorial provides a guided walk-through of Prefect's core concepts, including how to: (For advanced users who need more governance.) Before you start, make sure you have Python installed in a virtual environment. Then install Prefect: <div class="terminal"> ```bash pip install -U prefect ``` </div> See the for more detailed instructions. To get the most out of Prefect, you need to connect to a forever-free account. Create a new account or sign in at . Use the `prefect cloud login` CLI command to from your environment. <div class="terminal"> ```bash prefect cloud login ``` </div> Choose Log in with a web browser and click Authorize. If you have any issues with browser-based authentication, see the to learn how to authenticate with a manually created API key. As an alternative to using Prefect Cloud, you can self-host a . If you choose this option, run `prefect server start` to start a local Prefect server instance. Learn how to create your first .