cwielenb/CNCF-Dataset huggingface dataset:
Project: DolphinScheduler (Orchestration & Management / Scheduling & Orchestration)
File: incompatible.md

This document records the incompatible updates between each version. You need to check this document before you upgrade to related version. Upgrade mysql driver version from 8.0.16 to 8.0.33 () Change env `PYTHONHOME` to `PYTHONLAUNCHER` and `DATAXHOME` to `DATAXLAUNCHER` () Change regex matching sql params in SQL task plugin () Remove the spark version of spark task (). Change the default unix shell executor from sh to bash (). Remove `deleteSource` in `download()` of `StorageOperate` () Remove default key for attribute `data-quality.jar.name` in `common.properties` () Rename attribute `data-quality.jar.name` to `data-quality.jar.dir` in `common.properties` and represent for directory () Remove parameter `description` from public interfaces of new resource center () Copy and import workflow without 'copy' suffix Use semicolon as default sql segment separator Add required field `database` in /datasources/tables && /datasources/tableColumns Api
Project: MetalLB (Orchestration & Management / Service Proxy)
File: cncf-sandbox-proposal.md

MetalLB was originally written by Dave Anderson and was later transitioned to a team of that currently maintain the project. The maintainers come from different companies and desire a neutral home that can own assets of the project, such as the domain names. This proposal is for MetalLB to apply to become a [CNCF Sandbox Project](https://www.cncf.io/sandbox-projects/). While Dave Anderson is no longer actively involved with the project, he still owns the MetalLB domain names. When discussing what to do with them, transferring them to an individual or the employer of one or more of the maintainers doesn't seem like an ideal solution. An alternative which is becoming increasingly common in the open source ecosystem is to use an open source foundation as a neutral home for those assets. The CNCF seems like the most natural foundation home for MetalLB given its coupling to the Kubernetes project, which is also part of the CNCF. Align with other CNCF ecosystem projects in terms of policies and processes. Transfer assets to a neutral third party (i.e. domains). Gain more visibility in the CNCF ecosystem to attract others who may be interested in contributing to MetalLB development and maintenance. No changes to the MetalLB code are in scope of this proposal. This proposal is only about the community future. No changes to committer processes are proposed here. We already have a documented [process for adding and removing maintainers](https://metallb.universe.tf/community/maintainers/). Apply to become a [CNCF Sandbox project](https://www.cncf.io/sandbox-projects/). The section discusses some of the immediate changes we should expect, but some of the other services provided by the CNCF may be very beneficial to MetalLB in the future. The CNCF web site does a nice job discussing what services they offer projects on the page. (russellb) Write this proposal. (everyone) Provide feedback on initial proposal, reach consensus. (russellb) If approved, apply through the . (danderson) If accepted, transfer project assets as appropriate to CNCF. This includes transferring domains to CNCF, and likely MetalLB trademark assignment to the CNCF. See the CNCF [IP Policy](https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy). (russellb) Work with CNCF on any other CNCF onboarding tasks required, such as adding CNCF info to the web site footer. This alternative is mostly the status quo, except we would need to decide which individual or maintainer Dave should transfer domains to.
Project: OpenELB (Orchestration & Management / Service Proxy)
File: ADOPTERS.md

OpenELB has been adopted by many companies. If you are using OpenELB in your organization, welcome to join the end user community and add your logo to the list! <img alt="Baiwang-580" width="150px" src="./docs/img/adopters/baiwang-580.png"><img alt="Benlai" width="150px" src="./docs/img/adopters/benlai.png"> <img alt="CVTE" width="150px" src="./docs/img/adopters/cvte.png"><img alt="Jollychic" width="150px" src="./docs/img/adopters/jollychic.png"> <img alt="QingCloud" width="150px" src="./docs/img/adopters/qingcloud.png"><img alt="SBS" width="150px" src="./docs/img/adopters/sbs.png"> <img alt="Wisdom World" width="150px" src="./docs/img/adopters/wisdomworld.png"><img alt="Yicheng Health" width="150px" src="./docs/img/adopters/yicheng-health.png"> <img alt="PITS Global Data Recovery Services" width="150px" src="./docs/img/adopters/pits-logo-274-135.png">
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_check-crds.md

title: "glooctl check-crds" weight: 5 Checks Gloos CRDs for consistency against an official (or local) helm charts CRDs usage: glooctl check-crds [-o FORMAT] ``` glooctl check-crds [flags] ``` ``` -h, --help help for check-crds --local-chart string check against CRDs in helm chart at path specified by this flag (supersedes --version) --show-yaml show full yaml of both CRDs that differ --version string version of gloo's CRDs to check against ``` ``` -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 --use-consul use Consul Key-Value storage as the backend for reading and writing config (VirtualServices, Upstreams, and Proxies) ``` - CLI for Gloo
Project: Flomesh Service Mesh (FSM) (Orchestration & Management / Service Mesh)
File: pull_request_template.md

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

modauthrequest supports sending request to the specified service for authentication. conf/modauthrequest/modauthrequest.conf | Config Item | Description | | -- | | | Basic.DataPath | String<br>Path of rule configuration | | Basic.AuthAddress | String<br>Address of authentication service | | Basic.AuthTimeout | Number<br>Timeout for authentication | | Log.OpenDebug | Boolean<br/>Whether enable debug log<br/>Default False | ```ini [Basic] DataPath = modauthrequest/authrequestrule.data AuthAddress = http://127.0.0.1 AuthTimeout = 100 [Log] OpenDebug = false ``` | Config Item | Description | | | | | Version | String<br>Version of config file | | Config | Object<br>Request auth rules for each product | | Config{k} | String<br>Product name | | Config{v} | Object<br> A list of request auth rules | | Config{v}[] | Object<br> A request auth rule | | Config{v} | | Config{v}[].Enable | Boolean<br>Whether enable request auth rule | ```json { "Config": { "example_product": [ { "Cond": "reqpathin(\"/auth_request\", false)", "Enable": true } ] }, Version": "20190101000000" } ``` For exampleproduct, for request to path /authrequest (e.g., www.example.com/auth_request), BFE will create a request and send it to http://127.0.0.1 for authentication. | Action | Condition | | | | | Forbid | Response status code is 401 or 403 | | Pass | Response status code is 200 or other | | Metric | Description | | - | -- | | AUTHREQUESTCHECKED | Counter for checked request | | AUTHREQUESTPASS | Counter for passed request | | AUTHREQUESTFORBIDDEN | Counter for forbidden request | | AUTHREQUESTUNAUTHORIZED | Counter for unauthorized request | | AUTHREQUESTFAIL | Counter for failed request | | AUTHREQUESTUNCERTAIN | Counter for uncertain request | Method: Request Method of HTTP Request created by BFE is GET* Header: The request header created by the BFE is originated from the original request*, but BFE makes following changes to the request: Delete following headers: Content-Length/Connection/Keep-Alive/Proxy-Authenticate/Proxy-Authorization/Te/Trailers/Transfer-Encoding/Upgrade Add following headers: X-Forwarded-Method(Original Request MethodX-Forwarded-UriOriginal Request URI Body: Body of HTTP Request created by BFE is null*
Project: DolphinScheduler (Orchestration & Management / Scheduling & Orchestration)
File: sqlserver.md

| Datasource | Description | |-|--| | Datasource | Select SQLSERVER. | | Datasource Name | Enter the name of the datasource. | | Description | Enter a description of the datasource. | | IP/Host Name | Enter the SQLSERVER service IP. | | Port | Enter the SQLSERVER service port. | | Username | Set the username for SQLSERVER connection. | | Password | Set the password for SQLSERVER connection. | | Database Name | Enter the database name of the SQLSERVER connection. | | jdbc connect parameters | Parameter settings for SQLSERVER connection, in JSON format. | Yes, could use this datasource by default.
Project: Service Mesh Performance (Orchestration & Management / Service Mesh)
File: ROADMAP.md

Enhance workload metadata model with integration with Open Application Model. Enhance service mesh configuration model with integration with Service Mesh Interface. Identification of representative workloads. Establishment of standard benchmark configurations. Characterization of comparative differences (apples-to-oranges) performance comparisons of service mesh deployments. Continous publication of service mesh performance benchmarks on CNCF and IEEE venues. Increase individual service mesh project participation. Exchange of performance information from system-to-system / mesh-to-mesh. collaborative, academic research on a universal performance index to gauge a service meshs efficiency against deployments in other organizations environments. collaborative, academic research on performance characterization of new distributing tracing sampling algorithms.
Project: Contour (Orchestration & Management / Service Proxy)
File: envoy-admin-interface.md

Getting access to the Envoy can be useful for diagnosing issues with routing or cluster health. However, Contour doesn't expose the entire Envoy Administration interface since that interface contains many options, such as shutting down Envoy or draining traffic. To prohibit this behavior, Contour only exposes the read-only options from the admin interface which still allows for debugging Envoy, but without the options mentioned previously. Those endpoints are: /certs /clusters /listeners /config_dump /memory /ready /runtime /server_info /stats /stats/prometheus /stats/recentlookups The Envoy administration interface is bound by default to `http://127.0.0.1:9001`. To access it from your workstation use `kubectl port-forward` like so: ```sh ENVOY_POD=$(kubectl -n projectcontour get pod -l app=envoy -o name | head -1) kubectl -n projectcontour port-forward $ENVOY_POD 9001 ``` Then navigate to `http://127.0.0.1:9001/` to access the administration interface for the Envoy container running on that pod.
Project: BFE (Orchestration & Management / Service Proxy)
File: mod_doh.md

Module doh supports DNS over HTTPS. conf/moddoh/moddoh.conf | Config Item | Description | | - | - | | Basic.Cond | String<br>Condition for DoH requests, see | | Dns.Address | String<br>Address of DNS server | | Dns.RetryMax | Int<br>Maximum retries <br>Defaults to 0 (no retry) | | Dns.Timeout | Int<br>A cumulative timeout for dial, write and read (ms) | | Log.OpenDebug | Boolean<br>Whether enable debug log<br>Defaults to False | ```ini [Basic] Cond = "default_t()" [Dns] Address = "127.0.0.1:53" Timeout = 1000 [Log] OpenDebug = false ```
Project: Avro (Orchestration & Management / Remote Procedure Call)
File: _index.md

title: "PMC onboarding guide" linkTitle: "PMC onboarding guide" weight: 6 <!-- 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. --> Use https://whimsy.apache.org you can check that you got added to the PMC list properly Validate you are in the PMC group in JIRA and the Confluence Wiki Subscribe to private@avro.apache.org; you can use whimsy to do this for whatever email account you want, or send mail from that mail address to private-subscribe@ You should have access also to https://reporter.apache.org which seeds our board reports You can now access and read the private list archive (for linking to vote threads, etc) at https://lists.apache.org/list.html?private@avro.apache.org Review the ASF PMC guides. There are a few, but you should re-read what the responsibilities are. The PMC keeps a set of valuable resources in https://svn.apache.org/repos/private/pmc
Project: Pipy (Orchestration & Management / Service Proxy)
File: feature-request.md

name: "\U0001F680 Feature Request" about: I want to propose a new feature. labels: kind:feature Is your feature request related to a problem? Please describe clearly and concisely what is it. Describe the feature you would like, optionally illustrated by examples, and how it will solve the above problem. Describe considered alternative solutions, and the reasons why you have not proposed them as a solution here. Does it break backward compatibility, if yes then what's the migration path?
Project: Armada (Orchestration & Management / Scheduling & Orchestration)
File: libraries.md

This document is an overview of Armada client libraries. Here, we give an overview of the Armada Python client. For an installation and quick-start guide, please see the . For full documentation of our python module API, please see our To see more about the Armada Server API, please see the Information relevant to developers working to improve the python client can be found in the . Armada provides C# client bindings. This client can be accessed in the .
Project: APISIX (Orchestration & Management / API Gateway)
File: install-dependencies.md

title: Install Dependencies <!-- --> Since v2.0 Apache APISIX would not support the v2 protocol storage to etcd anymore, and the minimum etcd version supported is v3.4.0. What's more, etcd v3 uses gRPC as the messaging protocol, while Apache APISIX uses HTTP(S) to communicate with etcd cluster, so be sure the is enabled. Now by default Apache APISIX uses HTTP protocol to talk with etcd cluster, which is insecure. Please configure certificate and corresponding private key for your etcd cluster, and use "https" scheme explicitly in the etcd endpoints list in your Apache APISIX configuration, if you want to keep the data secure and integral. See the etcd section in `conf/config-default.yaml` for more details. If it is OpenResty 1.19, APISIX will use OpenResty's built-in LuaJIT to run `bin/apisix`; otherwise it will use Lua 5.1. If you encounter `luajit: ljasmx86.h:2819: asmloop fixup: Assertion '((intptr_t)target & 15) == 0' failed`, this is a problem with the low version of OpenResty's built-in LuaJIT under certain compilation conditions. On some platforms, installing LuaRocks via the package manager will cause Lua to be upgraded to Lua 5.3, so we recommend installing LuaRocks via source code. if you install OpenResty and its OpenSSL develop library (openresty-openssl111-devel for rpm and openresty-openssl111-dev for deb) via the official repository, then . If you compile OpenResty yourself, you can refer to the above script and change the path in it. If you don't specify the OpenSSL library path when you compile, you don't need to configure the OpenSSL variables in LuaRocks, because the system's OpenSSL is used by default. If the OpenSSL library is specified at compile time, then you need to ensure that LuaRocks' OpenSSL configuration is consistent with OpenResty's. OpenResty is a dependency of APISIX. If it is your first time to deploy APISIX and you don't need to use OpenResty to deploy other services, you can stop and disable OpenResty after installation since it will not affect the normal work of APISIX. Please operate carefully according to your service. For example in Ubuntu: `systemctl stop openresty && systemctl disable openresty`. Run the following command to install Apache APISIX's dependencies on a supported operating system. Supported OS versions: CentOS7, Fedora31 & 32, Ubuntu 16.04 & 18.04, Debian 9 & 10, Arch Linux. Note that in the case of Arch Linux, we use `openresty` from the AUR, thus requiring a AUR helper. For now `yay` and `pacaur` are supported. ``` curl https://raw.githubusercontent.com/apache/apisix/master/utils/install-dependencies.sh -sL | bash - ``` If you have cloned the Apache APISIX project, execute in the Apache APISIX root directory: ``` bash utils/install-dependencies.sh ```
Project: Gloo (Orchestration & Management / API Gateway)
File: issues.md

GitHub issues are the main way for reporting bugs and requesting features in Gloo Edge. If you encounter a bug or have a feature request, please take the following approach: Search for existing issues. If you find a similar issue, add a comment with additional information or add a reaction to indicate your agreement. If there are no similar issues, Issues in this repo should not contain any sensitive information. If sensitive information is critical to the issue, please reach out to Solo.io support to open a ticket. Issues can include links to private resources, such as Slack conversations or private code. Private Enterprise issues can be used to track Open Source work. The more details about the issue, the better. Please include the following information: Gloo Edge version Kubernetes version Operating system Steps to reproduce Expected behavior Actual behavior Logs Screenshots Any other relevant information Detailed description of the use case for the feature If possible, a description of how the feature is implemented in other tools Include a link to the failed CI job. Copy the error message from the failed job (logs are discarded after a few months). We take Gloo Edge's security very seriously. If you've found a security issue or a potential security issue in Gloo Edge, please DO NOT file a public Github issue. Instead, send your report privately to security@solo.io
Project: Eraser (Orchestration & Management / Scheduling & Orchestration)
File: faq.md

title: FAQ Eraser currently targets non-running images, so any vulnerable images that are currently running will not be removed. In addition, the default vulnerability scanning with Trivy removes images with `CRITICAL` vulnerabilities. Any images with lower vulnerabilities will not be removed. This can be configured using the . The native garbage collection in Kubernetes works a bit differently than Eraser. By default, garbage collection begins when disk usage reaches 85%, and stops when it gets down to 80%. More details about Kubernetes garbage collection can be found in the , and configuration options can be found in the . There are a couple core benefits to using Eraser for image cleanup: Eraser can be configured to use image vulnerability data when making determinations on image removal By interfacing directly with the container runtime, Eraser can clean up images that are not managed by Kubelet and Kubernetes
Project: Gloo (Orchestration & Management / API Gateway)
File: tls_cipher_inspector.proto.sk.md

title: "tlscipherinspector.proto" weight: 5 <!-- Code generated by solo-kit. DO NOT EDIT. --> ```yaml ``` | Field | Type | Description | | -- | - | -- | <!-- 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: gRPC (Orchestration & Management / Remote Procedure Call)
File: bazel_support.md

The `grpc/grpc` repository's primary build system is Bazel. Rules are provided for C++, Python, and Objective-C. While C++ supports other build systems such as CMake, these rules are actually generated from the Bazel definitions. Projects built with Bazel may use the `grpc/grpc` repo not only to add a dependency on the library itself, but also to generate protobuf, stub, and servicer code. To do so, one must invoke the `grpcdeps` and `grpcextra_deps` repository rules in their `WORKSPACE` file: ```starlark workspace(name = "example_workspace") load("@bazeltools//tools/builddefs/repo:http.bzl", "http_archive") http_archive( name = "comgithubgrpc_grpc", strip_prefix = "grpc-1.45.0", sha256 = "ec19657a677d49af59aa806ec299c070c882986c9fcc022b1c22c2a3caf01bcd", urls = ["https://github.com/grpc/grpc/archive/refs/tags/v1.45.0.tar.gz"], ) load("@comgithubgrpcgrpc//bazel:grpcdeps.bzl", "grpc_deps") grpc_deps() load("@comgithubgrpcgrpc//bazel:grpcextradeps.bzl", "grpcextra_deps") grpcextradeps() ``` gRPC supports building with the latest stable release of Bazel, as well as the previous major version release for at least 6 months after it transitions into maintenance mode. This is consistent with the supported build systems of . However individual releases may have a broader compatibility range. The currently supported versions are captured by the following list: NOTE: gRPC doesn't support bzlmod yet.