cwielenb/CNCF-Dataset huggingface dataset:
Project: TARS (Orchestration & Management / Remote Procedure Call)
File: introduction.md

This folder is used to store the software for Tars performance Test. The test software consists of the client software and the server software. The Tars framework should be set up successfully prior to run the performance test software. In order to run the performance test, Tars framework is a must. You can setup the framework via script or do it step-by-step. Refer to the following link: https://github.com/TarsCloud/Tars/tree/master/shellDeploy https://github.com/TarsCloud/Tars#installation For the server side, For the client side, More informations you should pay special attention to.
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_get_proxy.md

title: "glooctl get proxy" weight: 5 read a proxy or list proxies in a namespace usage: glooctl get proxy ``` glooctl get proxy [flags] ``` ``` --edge include proxies produced from edge gateway resources -h, --help help for proxy --kube include proxies produced from k8s gateway resources ``` ``` -c, --config string set the path to the glooctl config file (default "<home_directory>/.gloo/glooctl-config.yaml") --consul-address string address of the Consul server. Use with --use-consul (default "127.0.0.1:8500") --consul-allow-stale-reads Allows reading using Consul's stale consistency mode. --consul-datacenter string Datacenter to use. If not provided, the default agent datacenter is used. Use with --use-consul --consul-root-key string key prefix for for Consul key-value storage. (default "gloo") --consul-scheme string URI scheme for the Consul server. Use with --use-consul (default "http") --consul-token string Token is used to provide a per-request ACL token which overrides the agent's default token. Use with --use-consul -i, --interactive use interactive mode --kube-context string kube context to use when interacting with kubernetes --kubeconfig string kubeconfig to use, if not standard one --name string name of the resource to read or write -n, --namespace string namespace for reading or writing resources (default "gloo-system") -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) ``` - Display one or a list of Gloo resources
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2015-07-01-mesoscon-seattle-keynote-speakers-announced.md

layout: post title: MesosCon Seattle 2015 Keynote Speakers Announced permalink: /blog/mesoscon-seattle-keynote-speakers-announced/ published: true post_author: display_name: Dave Lester twitter: davelester tags: MesosCon The countdown until has begun: <blockquote class="twitter-tweet" lang="en"><p lang="en" dir="ltr">Only 7 weeks until <a href="https://twitter.com/hashtag/MesosCon?src=hash">#MesosCon</a>! Register today and join us in Seattle <a href="http://t.co/bVJ9dL5CEO">http://t.co/bVJ9dL5CEO</a></p>&mdash; #MesosCon (@mesoscon) <a href="https://twitter.com/mesoscon/status/616320613922275332">July 1, 2015</a></blockquote> MesosCon is an annual conference organized by the Apache Mesos community, bringing together users and developers to share and learn about the project and its growing ecosystem. and join us in Seattle this August! Heres a rundown of several conference announcements: Weve curated a stellar line-up of invited keynote speakers, including: Adrian Crockroft (Battery Ventures) Benjamin Hindman (Mesosphere) Neha Narula (MIT) Peter Bailis (Berkeley) You dont want to miss these! Well also feature platinum sponsored keynotes from Cisco, Intel, and Mesosphere. The Mesos community will once again hold a day-long hackathon, this year on Wednesday, August 19th and sponsored by SignalFx. More details will be announced soon including the location and registration; stay tuned and hold the date! Want to present at MesosCon, but missed the call for full sessions? Weve opened a ; the application deadline is July 15th. The provides support to women, people of color, and people with disabilities who may not otherwise have the opportunity to attend MesosCon for financial reasons. Equal access and diversity are important to MesosCon, and we aim to remove this obstacle for underrepresented attendee groups. We want you at MesosCon, and we want to help you get there! Applications are beginning to be reviewed, and will be reviewed on a rolling basis. Apply today! We also encourage MesosCon attendees to donate toward the diversity scholarship program directly during the time of registration using the online system. As we make future announcements about the conference, stay in the loop and help us get the word out! Well be tweeting from @ApacheMesos and @MesosCon, blogging on the , and sharing updates on the projects user@ mailing lists. MesosCon will take place August 20 - 21, 2015 at Sheraton Seattle in Seattle, WA with a hackathon taking place the day prior to the event. The standard attendee registration fee will be US$399 (Through July 31, 2015), and late registration US$499 beginning August 1, 2015. Students are eligible for a special registration fee of US$99 (Note that a valid student id will be required at onsite check-in). Hope to see you at this years MesosCon!
Project: Crossplane (Orchestration & Management / Scheduling & Orchestration)
File: one-pager-package-annotations.md

Owner: Nic Cope (@negz) Reviewers: Crossplane Maintainers Status: Proposed This one-pager has been superseded by the [`xpkg` specification]. extend Crossplane with new functionality. The `Provider` and `Configuration` Crossplane resources are powered by packages; they represent a declarative intent to install a provider or configuration package. Crossplane packages are OCI images that deliver a payload of valid Kubernetes resources. Provider packages deliver CRDs for the managed resources a provider defines, while Configurations deliver XRDs and Compositions. All packages contain general package metadata in the form of a `crossplane.yaml` file, per the . The `crossplane.yaml` file contains Kubernetes-like YAML, and is of kind `Provider` or `Configuration` in API group `meta.pkg.crossplane.io`. The package manager propagates any annotations from the `crossplane.yaml` file to its corresponding `ProviderRevision` or `ConfigurationRevision` in the Kubernetes API server. Such annotations are referred to as 'passthrough metadata' about a package, because they are not meaningful to Crossplane or the package manager. The package format one pager provides an example of a `crossplane.yaml` with annotations such as `company` and `maintainer`, but is not opinionated about the format of the annotations, or which annotations should exist. The goal of this document is to encourage - but not require - consistent package annotations. e.g. To increase the likelihood that all package authors will align on using the `maintainer` annotation to indicate the package's maintainer. This document recommends that packages include the following annotations: ```yaml apiVersion: meta.pkg.crossplane.io/v1alpha1 kind: Provider metadata: name: example annotations: meta.crossplane.io/maintainer: Example T. Maintainer <example@example.org> meta.crossplane.io/source: https://github.com/crossplane/provider-example meta.crossplane.io/license: Apache-2.0 meta.crossplane.io/description: | The Google Cloud Platform (GCP) Crossplane provider adds support for managing GCP resources in Kubernetes. meta.crossplane.io/readme: | provider-example is a really great Crossplane provider... meta.crossplane.io/iconURI: data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciLz4KBIWXMA friendly-name.meta.crossplane.io: "Example Provider" friendly-group-name.meta.crossplane.io/database.example.org: "Databases" friendly-kind-name.meta.crossplane.io/cloudsqlinstance.database.example.org: "CloudSQL Instance" spec: controller: image: crossplane/provider-example:v0.1.0 ``` Note that these annotations are not constrained to packages specifically. If it makes sense (for example) for a specific XRD, Composition, or CRD to contain this metadata it may.
Project: Avro (Orchestration & Management / Remote Procedure Call)
File: avro-joins-apache.md

title: "Avro joins Apache" linkTitle: "Avro joins Apache" date: 2009-04-10 <!-- 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. --> Avro has joined the Apache Software Foundation as a Hadoop subproject.
Project: CoreDNS (Orchestration & Management / Coordination & Service Discovery)
File: coredns-1.0.4.md

+++ title = "CoreDNS-1.0.4 Release" description = "CoreDNS-1.0.4 Release Notes." tags = ["Release", "1.0.4", "Notes"] draft = false release = "1.0.4" date = "2018-01-18T15:54:29+00:00" author = "coredns" +++ We are announcing the of CoreDNS-1.0.4! This is a release that fixes a vulnerability in the underlying DNS library. See <https://github.com/miekg/dns/issues/627> and the (still embargoed) CVE-2017-15133. Thanks to Tom Thorogood for bringing this issue to our attention. CoreDNS-1.0.4 is recompiled with a patched DNS library.
Project: KubeStellar (Orchestration & Management / Scheduling & Orchestration)
File: community_meeting.md

title: KubeStellar Community Meeting {{ date | date('add', 28, 'days') | date('MMMM Do, YYYY') }} assignees: clubanderson labels: community-meeting Bi-Weekly At 10am Eastern, 7am Pacific, 2pm UTC; <b>Video call link: </b> Or dial: 1-844-531-0958 PIN: 145 377 9958# More phone numbers: https://ibm.webex.com/webappng/sites/ibm/meeting/scheduler Or join via SIP: sip:1453779958@ibm.webex.com Meeting recordings available on YouTube at <b>Agenda is here: </b> (Join our mailing list at to get access to the Agenda and other artifacts) Add topics you'd like to discuss below! <b>Contributor Code of Conduct</b> As contributors and maintainers in the CNCF community, 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 the CNCF community 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.
Project: Volcano (Orchestration & Management / Scheduling & Orchestration)
File: prepare-for-development.md

This document helps you get started developing code for Volcano. If you follow this guide and find some problem, please take a few minutes to update this file. Volcano components only have few external dependencies you need to set up before being able to build and run the code. All Volcano components are written in the programming language. To build, you'll need a Go development environment. If you haven't set up a Go development environment, please follow to install the Go tools. Volcano currently builds with Go 1.14 Istio has a Docker build system for creating and publishing Docker images. To leverage that you will need: Docker platform: To download and install Docker follow . Docker Hub ID: If you do not yet have a Docker ID account you can follow to create one. This ID will be used in a later step when setting up the environment variables. We require Kubernetes version 1.12 or higher with CRD support. If you aren't sure which Kubernetes platform is right for you, see . This is only necessary for core contributors in order to push changes to the main repos. You can make pull requests without two-factor authentication but the additional security is recommended for everyone. To be part of the Volcano organization, we require two-factor authentication, and you must setup a personal access token to enable push via HTTPS. Please follow for how to create a token. Alternatively you can . Once you've set up the prerequisites, continue with for more details about how to build & test Volcano.
Project: Karmada (Orchestration & Management / Scheduling & Orchestration)
File: CHANGELOG-0.9.md

Users are now able to upgrade from the previous version smoothly. With the feature of CRD, objects with different schemas can be automatically converted between versions. Karmada uses the [semantic versioning](https://semver.org/) and will provide workarounds for inevitable breaking changes. In this release, the ResourceBining and ClusterResourceBinding promote to v1alpha2 and the previous v1alpha1 version is still available for one more release. With the , the previous version of Karmada can promote smoothly. Karmada scheduler aims to assign workload to clusters according to constraints and available resources of each member cluster. The `kube-scheduler` working on each cluster takes the responsibility to assign Pods to Nodes. Even though Karmada has the capacity to reschedule failure workload between member clusters, but the community still commits lots of effort to improve the accuracy of the end-to-end scheduling. The `karmada-scheduler-estimator` is the effective assistant of `karmada-scheduler`, it provides prediction-based scheduling decisions that can significantly improve the scheduling efficiency and avoid the wave of rescheduling among clusters. Note that this feature is implemented as a pluggable add-on. For the instructions please refer to . A bunch of significant maintainability improvements were added to this release, including: Simplified Karmada installation with . Provided metrics to observe scheduler status, the metrics API now served at `/metrics` of `karmada-scheduler`. With these metrics, users are now able to evaluate the scheduler's performance and identify the bottlenecks. Provided events to Karmada API objects as supplemental information to debug problems. karmada-controller-manager: The ResourceBinding/ClusterResourceBinding won't be deleted after associate PropagationPolicy/ClusterPropagationPolicy is removed and is still available until resource template is removed.() Introduced --leader-elect-resource-namespace which is used to specify the namespace of election object to components karmada-controller-manager/karmada-scheduler/karmada-agent`. () Deprecation: The API ReplicaSchedulingPolicy has been deprecated and will be removed from the following release. The feature now has been integrated into ReplicaScheduling. Introduced kubectl-karmada commands as the extensions for kubectl. () karmada-controller-manager introduced a version command to represent version information. ( ) karmada-scheduler/karmada-webhook/karmada-agent/karmada-scheduler-estimator introduced a version command to represent version information. ( ) Provided instructions about how to use the Submariner to connect the network between member clusters. ( ) Added four metrics to the karmada-scheduler to monitor scheduler performance. ()
Project: Lunar.dev (Orchestration & Management / API Gateway)
File: SPOA.md

<div align="center"> <img margin=auto src="../readme-files/detailed-architecture.png" alt="Architecture" width="600"/> </div> Coming soon... The runs plugins according to configured policies. <br/>Each policy is set on a method and endpoint (e.g. `GET` and `httpbin.org/json`), and has a policy type and configuration. When a request arrives on a method and endpoint with a set policy, the policy's plugins will run in order. A plugin is a subclass of `spoapython.plugins.Plugin` which implements the `onrequest` and `on_response` methods. These methods receive the policy's configuration as an argument (`config`), a transaction id with the same value for the request and response (`id`), as well as arguments describing the request/response (). They return an . | Event | Arguments | Example | | -- | -- | -- | | <pre><b>on_request</b></pre> | <pre><b>id: </b>str,<br/><b>config</b>: ,<br/><b>method</b>: str,<br/><b>path</b>: str,<br/><b>query</b>: str,<br/><b>headers</b>: str,<br/><b>body</b>: str</pre> | <pre>$ curl http://localhost/json --header "Host: httpbin.org:443"<br/><br/>Values:<br/><b>id = </b>"f2eb8567-b6c4-4c30-b927-0eb9d8012aa5"<br/><b>method = </b>"GET"<br/><b>path = </b>"/json"<br/><b>query = </b>"var=2"<br/><b>headers = </b><br/> "Host: httpbin.org<br/> Accept: /<br/> User-Agent: curl/7.79.1"<br/><b>body = </b>""</pre> | | <pre><b>on_response</b></pre> | <pre><b>id</b>: str,<br/><b>config</b>: ,<br/><b>status</b>: int,<br/><b>headers</b>: str,<br/><b>body</b>: str</pre> | <pre>$ curl http://localhost/json --header "Host: httpbin.org:443"<br/><br/>Values:<br/><b>id = </b>"f2eb8567-b6c4-4c30-b927-0eb9d8012aa5"<br/><b>status = </b>200<br/><b>headers = </b><br /> "Content-Type: application/json<br/> Content-Length: 429<br/> &lt;rest of headers&gt;"<br/> <b>body = </b>'{<br/> "slideshow": {<br/> "author": "Yours Truly",<br/> "date": "date of publication",<br/> &lt;rest of body&gt;<br/> }'</pre> | Currently supported actions are: | Action | Arguments | Details | | -- | -- | -- | | `NoOpAction` | None | Do nothing | | `EarlyResponseAction` | `status`, `headers`, `body` | Return a response without reaching the provider |
Project: BFE (Orchestration & Management / Service Proxy)
File: condition_naming_convention.md

BFE adopts the following naming convention for condition primitives. Name prefix of the request primitive is "req_" e.g. reqhostin() Name prefix of the response primitive is "res_" e.g. rescodein() Name prefix of the session primitive is "ses_" e.g. sesvipin() Name prefix of the system primitive is "bfe_" e.g. bfetimerange() match: exact match eg. reqtagmatch() in: whether an element exists in a set or not eg. reqhostin() prefix_in: whether the prefix exists in a set or not eg. reqpathprefix_in() suffix_in: whether the suffix exists in a set or not eg. reqpathsuffix_in() key_exist: whether the specified key exists or not eg. reqquerykey_exist() value_in: whether the value exists in a set or not eg. reqquerykey_exist() value_prefix_in: whether the value prefix exists in a set or not eg. reqheadervalueprefixin() value_suffix_in: whether the value suffix exists in a set or not eg. reqheadervaluesuffixin() range: range match eg. reqciprange() regmatch: use regular expression to match eg. requrlregmatch() Warning: Inappropriate use can significantly affect performance contain: string match eg. reqcookievalue_contain()
Project: Gloo (Orchestration & Management / API Gateway)
File: grpc.proto.sk.md

title: "grpc.proto" weight: 5 <!-- Code generated by solo-kit. DO NOT EDIT. --> Service spec describing GRPC upstreams. This will usually be filled automatically via function discovery (if the upstream supports reflection). If your upstream service is a GRPC service, use this service spec (an empty spec is fine), to make sure that traffic to it is routed with http2. Deprecated: prefer using GrpcJsonTranscoder ```yaml "descriptors": bytes "grpcServices": []grpc.options.gloo.solo.io.ServiceSpec.GrpcService ``` | Field | Type | Description | | -- | - | -- | | `descriptors` | `bytes` | Descriptors that contain information of the services listed below. this is a serialized google.protobuf.FileDescriptorSet. These will be discovered if FDS is enabled and may be modified by Gloo. | | `grpcServices` | | List of services used by this upstream. These services must be present in the descriptors. | Describes a grpc service ```yaml "packageName": string "serviceName": string "functionNames": []string ``` | Field | Type | Description | | -- | - | -- | | `packageName` | `string` | The package of this service. | | `serviceName` | `string` | The service name of this service. | | `functionNames` | `[]string` | The functions available in this service. | This is only for upstream with Grpc service spec. Deprecated: prefer providing descriptors on Upstream in GrpcJsonTranscoder ```yaml "package": string "service": string "function": string "parameters": .transformation.options.gloo.solo.io.Parameters ``` | Field | Type | Description | | -- | - | -- | | `package` | `string` | The proto package of the function. | | `service` | `string` | The name of the service of the function. | | `function` | `string` | The name of the function. | | `parameters` | | Parameters describe how to extract the function parameters from the request. | <!-- 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: Inlets (Orchestration & Management / Service Proxy)
File: reference.md

For a single private on-premises Java API service, one exit-server is provisioned on public cloud, its Public IP is the VirtualIP for the private cluster. Ports 80 and 443 are forwarded to the Java API, which can serve its own TLS certificate. For a single private on-premises Java API service, two exit-servers are provisioned on public cloud, each with a Public VirtualIP. DNS is used to provide high-availability and fail-over. Ports 80 and 443 are forwarded to the Java API, which can serve its own TLS certificate. Example: A private or on-premises Kubernetes cluster serving traffic from a Node.js Pod on port 3000. An IngressController performs TLS termination and stores a certificate within the private cluster. The certificate can be obtained from LetsEncrypt using standard tooling such as . Example: You have a remote TCP service such as a PostgreSQL database which is running in a private network such as a client's site, at an edge location, or on-premises. You need to access that database from a public or central cluster. The PostgreSQL database must not be exposed on the Internet, and a split-plane is used where only the control-plane of inlets-pro is public. From within your destination cluster, services can access the database via a private ClusterIP.