cwielenb/CNCF-Dataset huggingface dataset:
Project: Tyk (Orchestration & Management / API Gateway)
File: README.md

This is an area for tests that replicate demonstratable issues. Any test should follow the following convention: The name of the test file: `issue<jira-id>test.go` The name of the test function: `Test_Issue<jira-id>` Any test data required for the test: `testdata/issue-<jira-id>-<type>.<ext>` Additional files: `regression_test.go` - containing shared utilities for tests
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_istio_enable-mtls.md

title: "glooctl istio enable-mtls" weight: 5 Enables Istio mTLS for a given upstream Enables Istio mTLS for a given upstream, by adding an sslConfig which lets envoy know to get the certs via SDS ``` glooctl istio enable-mtls [flags] ``` ``` -h, --help help for enable-mtls -u, --upstream string upstream for which the istio sslConfig needs to change ``` ``` -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") --use-consul use Consul Key-Value storage as the backend for reading and writing config (VirtualServices, Upstreams, and Proxies) ``` - Commands for interacting with Istio in Gloo
Project: Gravitee.io (Orchestration & Management / API Gateway)
File: organization-configuration-roles.md

A role can be scoped to an API, an application, the portal or more globally to the platform management. Each role defines a set of permissions (READ, CREATE, UPDATE, DELETE (CRUD)) on the API Management resources. A role can be edited by clicking on the edit button on each role scope: ORGANIZATION role CRUD operations on: USER, ENVIRONMENT, ROLE. ENVIRONMENT role CRUD operations on: INSTANCE, GROUP, SHARDING TAG, TENANT, API, APPLICATION, AUDIT, PLATFORM, NOTIFICATION, MESSAGE, DICTIONARY, ALERT, ENTRYPOINTS, SETTINGS, DASHBOARD, QUALITY RULES, METADATA, DOCUMENTATION, VIEW, TOP APIS, API HEADERS, IDENTITY PROVIDERS, CLIENT REGISTRATION PROVIDER, PORTAL THEME. API role CRUD operations on: DEFINITION, GATEWAY_DEFINITION, PLAN, SUBSCRIPTION, MEMBER, METADATA, ANALYTICS, EVENT, HEALTH, LOG, DOCUMENTATION, RATINGS, RATINGS ANSWERS, AUSIT, DISCOVERY, NOTIFICATION, MESSAGE, ALERT, RESPONSE TEMPLATES, REVIEWS, QUALITY RULES. APPLICATION role CRUD operations on: DEFINITION, MEMBER, ANALYTICS, LOG, SUBSCRIPTION, NOTIFICATION, ALERT. Granting a GROUP permission for MANAGEMENT role will also require the READ operation for the ROLE permission in order to see which roles are provided by a group.
Project: TARS (Orchestration & Management / Remote Procedure Call)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: "[BUG]" labels: bug assignees: '' What version of TARS and what language are you using? What operating system (Linux, Windows, ...) and version? [e.g. CentOS 7.8] What runtime/compiler are you using? [e.g. JDK version or version of gcc] Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Go to '...' Click on '....' See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here.
Project: KubeStellar (Orchestration & Management / Scheduling & Orchestration)
File: pull_request_template.md

<!-- Thanks for creating a pull request! If this is your first time, please make sure to review CONTRIBUTING.MD. Please copy the appropriate `:text:` or icon to the beginning of your PR title: :sparkles: feature :bug: bug fix :book: docs :memo: proposal :warning: breaking change :seedling: other/misc :question: requires manual review/categorization --> Fixes #
Project: CoreDNS (Orchestration & Management / Coordination & Service Discovery)
File: coredns-1.0.3.md

+++ title = "CoreDNS-1.0.3 Release" description = "CoreDNS-1.0.3 Release Notes." tags = ["Release", "1.0.3", "Notes"] draft = false release = "1.0.3" date = "2018-01-10T19:38:29+00:00" author = "coredns" +++ We are pleased to announce the of CoreDNS-1.0.3! This is a small bugfix release, but we also have a new plugin: . Manual pages are now generated from the READMEs, you can find them in the man/ directory. A coredns(1) and corefile(5) one where also added. The `fallthrough` directive was overhauled and now allows a list of zones to be specified. It will then only fallthrough for those zones, see `plugin/plugin.md`. A new plugin template was added. It allows you to use Go (text) templates to craft a response, see <https://coredns.io/plugins/template> for docs. dnssec* implements Cloudflares's NSEC blacklies better. kubernetes*, adds a fix for `pod insecure` look ups for non-IP addresses. health* adds a metrics for the duration it takes to GET /health. Useful for getting a sense of overloadedness of the process. The following people helped with getting this release done: John Belamaric, Miek Gieben, Rene Treffer, Yong Tang. If you want to help, please check out one of the and start coding! For documentation and help, see our .
Project: gRPC (Orchestration & Management / Remote Procedure Call)
File: feature_request_objc.md

name: Request a gRPC ObjC feature about: Suggest an idea for this project labels: kind/enhancement, priority/P2, lang/ObjC assignees: dennycd <!-- PLEASE DO NOT POST A QUESTION HERE. This form is for bug reports and feature requests ONLY! For general questions and troubleshooting, please ask/look for answers at StackOverflow, with "grpc" tag: https://stackoverflow.com/questions/tagged/grpc For questions that specifically need to be answered by gRPC team members, please ask/look for answers at grpc.io mailing list: https://groups.google.com/forum/#!forum/grpc-io Issues specific to grpc-java, grpc-go, grpc-node, grpc-dart, grpc-web should be created in the repository they belong to (e.g. https://github.com/grpc/grpc-LANGUAGE/issues/new) --> A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] A clear and concise description of what you want to happen. A clear and concise description of any alternative solutions or features you've considered. Add any other context about the feature request here.
Project: DolphinScheduler (Orchestration & Management / Scheduling & Orchestration)
File: introduction.md

Apache DolphinScheduler provides a distributed and easy to expand visual workflow task scheduling open-source platform. It is suitable for enterprise-level scenarios. It provides a solution to visualize operation tasks, workflows, and the entire data processing procedures. Apache DolphinScheduler aims to solve complex big data task dependencies and to trigger relationships in data OPS orchestration for various big data applications. Solves the intricate dependencies of data R&D ETL and the inability to monitor the health status of tasks. DolphinScheduler assembles tasks in the Directed Acyclic Graph (DAG) streaming mode, which can monitor the execution status of tasks in time, and supports operations like retry, recovery failure from specified nodes, pause, resume, and kill tasks, etc.
Project: Clusterpedia (Orchestration & Management / Scheduling & Orchestration)
File: CONDUCT.md

Cobra will follow a steady release cadence. Non breaking changes will be released as minor versions quarterly. Patch bug releases are at the discretion of the maintainers. Users can expect security patch fixes to be released within relatively short order of a CVE becoming known. For more information on security patch fixes see the CVE section below. Releases will follow . Users tracking the Master branch should expect unpredictable breaking changes as the project continues to move forward. For stability, it is highly recommended to use a release. We will maintain two major releases in a moving window. The N-1 release will only receive bug fixes and security updates and will be dropped once N+1 is released. Deprecation of Go versions or dependent packages will only occur in major releases. To reduce the change of this taking users by surprise, any large deprecation will be preceded by an announcement in the and an Issue on Github. Maintainers will make every effort to release security patches in the case of a medium to high severity CVE directly impacting the library. The speed in which these patches reach a release is up to the discretion of the maintainers. A low severity CVE may be a lower priority than a high severity one. Cobra maintainers will use GitHub issues and the as the primary means of communication with the community. This is to foster open communication with all users and contributors. Breaking changes are generally allowed in the master branch, as this is the branch used to develop the next release of Cobra. There may be times, however, when master is closed for breaking changes. This is likely to happen as we near the release of a new version. Breaking changes are not allowed in release branches, as these represent minor versions that have already been released. These version have consumers who expect the APIs, behaviors, etc, to remain stable during the lifetime of the patch stream for the minor release. Examples of breaking changes include: Removing or renaming exported constant, variable, type, or function. Updating the version of critical libraries such as `spf13/pflag`, `spf13/viper` etc... Some version updates may be acceptable for picking up bug fixes, but maintainers must exercise caution when reviewing. There may, at times, need to be exceptions where breaking changes are allowed in release branches. These are at the discretion of the project's maintainers, and must be carefully considered before merging. Maintainers will ensure the Cobra test suite utilizes the current supported versions of Golang. Changes to this document and the contents therein are at the discretion of the maintainers. None of the contents of this document are legally binding in any way to the maintainers or the users.
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_edit_settings_externalauth.md

title: "glooctl edit settings externalauth" weight: 5 Configure external auth settings (Enterprise) Let gloo know the location of the ext auth server. This is a Gloo Enterprise feature. ``` glooctl edit settings externalauth [flags] ``` ``` --extauth-server-name string name of the ext auth server upstream --extauth-server-namespace string namespace of the ext auth server upstream -h, --help help for externalauth ``` ``` -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) --resource-version string the resource version of the resource we are editing. if not empty, resource will only be changed if the resource version matches --use-consul use Consul Key-Value storage as the backend for reading and writing config (VirtualServices, Upstreams, and Proxies) ``` - root command for settings
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_proxy_stats.md

title: "glooctl proxy stats" weight: 5 stats for one of the proxy instances ``` glooctl proxy stats [flags] ``` ``` -h, --help help for stats ``` ``` -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 the name of the proxy service/deployment to use (default "gateway-proxy") -n, --namespace string namespace for reading or writing resources (default "gloo-system") --port string the name of the service port to connect to (default "http") --use-consul use Consul Key-Value storage as the backend for reading and writing config (VirtualServices, Upstreams, and Proxies) ``` - interact with proxy instances managed by Gloo
Project: Fluid (Orchestration & Management / Scheduling & Orchestration)
File: MAINTAINERS_COMMITTERS.md

This file lists the maintainers and committers of the Fluid project. More description of maintainers and committers are listed in the file. | Name | GitHub ID | Affiliation | | - | | -- | | | | Nanjing University | | | | Alibaba | | | | Alluxio | | | | Nanjing University | | | | Alibaba | | | | JuiceData | | | | China Telecom | | Name | GitHub ID | Affiliation | | - | | -- | | | | Tencent Cloud | | | | Alibaba | | | | Bilibili | | | | Baidu AI Cloud | | | | Shopee | | | | Unisound | | | | Alluxio | | | | 4Paradigm |
Project: Volcano (Orchestration & Management / Scheduling & Orchestration)
File: execution-flow.md

The Allocation of the workloads to the node in scheduler happens in each session and the workflow of the session is illustrated in the below diagram. Session Opens every 1 sec In every session local copies of Queues, JobsMap, PendingTasks and Node List is created. For Each Jobs in the Session If the Queued ID in the Job exists in the Local Copy of Queues then : Add the Queue in the Local Copy of Queues If the QueueID exists in local copyof JobsMap: Push the Job in the JobsMap If Not then Add the QueueID as the key in Local JobsMap and add the job in the Map. If Not then Give warning and continue to Step 3 For Each Item in Local Queues Pop an Queue from the Queues Check if Queue is overused If Yes then Continue to Step 4 If Not then get the list of JobsList from the JobsMap for the particular Queue. If List is empty then continue to Step 4 If Yes then Pop a Job from the JobsList If Job exits the Local PendingTasks If Not then : Create a Local Task List Get the List of Each Tasks in the pending state for that job If the required resource for the job is Empty then go back to previous step If Not then Add the tasks in the Local TasksList Add the local Tasks List to PendingTasks for that Job If Yes then : For each Tasks from the pendingTasksList for the Job. Pop the tasks Get the list of predicate nodes for the task. Score the predicate nodes and sort it. For each node in the sorted predicated + scored nodes If the Resource required by task is less than Idle resource of Nodes If Resource required by task is less than releasing resource of Node Then Add the tasks in Pipeline Check if Job is ready to be allocated If yes the push the Job If No then add the Queue back to the list. Continue till all the Job is ready Continue till each Queue is processed.
Project: Dubbo (Orchestration & Management / Remote Procedure Call)
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 dev@dubbo.apache.org. 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: Contour (Orchestration & Management / Service Proxy)
File: tracing.md

Envoy has rich support for and supports exporting data to third-party providers (Zipkin, Jaeger, Datadog, etc.) is a CNCF project which is working to become a standard in the space. It was formed as a merger of the OpenTracing and OpenCensus projects. Contour supports configuring envoy to export data to OpenTelemetry, and allows users to customize some configurations. Custom service name, the default is `contour`. Custom sampling rate, the default is `100`. Custom the maximum length of the request path, the default is `256`. Customize span tags from literal or request headers. Customize whether to include the pod's hostname and namespace. In order to use this feature, you must first select and deploy an opentelemetry-collector to receive the tracing data exported by envoy. First we should deploy an opentelemetry-collector to receive the tracing data exported by envoy ```bash kubectl apply -f https://github.com/open-telemetry/opentelemetry-operator/releases/latest/download/opentelemetry-operator.yaml ``` Install an otel collector instance, with verbose logging exporter enabled: ```shell kubectl apply -f - <<EOF apiVersion: opentelemetry.io/v1alpha1 kind: OpenTelemetryCollector metadata: name: simplest namespace: projectcontour spec: config: | receivers: otlp: protocols: grpc: http: exporters: logging: verbosity: detailed service: pipelines: traces: receivers: [otlp] exporters: [logging] EOF ``` Define extension service: ```shell kubectl apply -f - <<EOF apiVersion: projectcontour.io/v1alpha1 kind: ExtensionService metadata: name: otel-collector namespace: projectcontour spec: protocol: h2c services: name: simplest-collector port: 4317 EOF ``` Update Contour config (needs a Contour deployment restart afterwards): ```shell kubectl apply -f - <<EOF apiVersion: v1 kind: ConfigMap metadata: name: contour namespace: projectcontour data: contour.yaml: | tracing: includePodDetail: true extensionService: projectcontour/otel-collector serviceName: some-service-name customTags: tagName: custom-tag literal: foo tagName: header-tag requestHeaderName: X-Custom-Header EOF ``` Install httpbin and test it: ```bash kubectl apply -f https://projectcontour.io/examples/httpbin.yaml ``` Access the api and view the logs of simplest: ```bash kubectl logs deploy/simplest-collector -n projectcontour ``` Now you should be able to see traces in the logs of the otel collector.
Project: kcp (Orchestration & Management / Scheduling & Orchestration)
File: replicate-new-resource.md

description: > How to add a new resource for replication by the cache server. As of today adding a new resource for replication is a manual process that consists of the following steps: You need to register a new CRD in the cache server. Registration is required otherwise the cache server wont be able to serve the new resource. It boils down to adding a new entry into . If you dont have a CRD definition file for your type, you can use against any kube-apiserver to create the required manifest. Next, you need to register the new type in the replication controller. For that you need to add a new entry into the following In general there are two types of resources. The ones that are replicated automatically (i.e. APIExports) and the ones that are subject to additional filtering, for example require some additional annotation (i.e. ClusterRoles). For optional resources we usually create which simply annotates objects that need to be replicated. Then during registration we provide a filtering function that checks for existence of the annotation (i.e. )