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

If you need to use `DingTalk` for alerting, create an alert instance in the alert instance management and select the `DingTalk` plugin. The following shows the `DingTalk` configuration example: | Parameter | Description | |-|--| | Warning Type | Alert on success or failure or both. | | WebHook | The format is: | | Keyword | Custom keywords for security settings. | | Secret | Signature of security settings | | Msg Type | Message parse type (support txt, markdown, markdownV2, html). | | At User Mobile | When a custom bot sends a message, you can specify the "@person list" by their mobile phone number. When the selected people in the "@people list" receive the message, there will be a `@` message reminder. `No disturb` mode always receives reminders, and "someone @ you" appears in the message. The "At User Mobile" represents mobile phone number of the "@person" | | At User Ids | The user ID by "@person" | | Proxy | The proxy address of the proxy server. | | Port | The proxy port of Proxy-Server. | | User | Authentication(Username) for the proxy server. | | Password | Authentication(Password) for the proxy server. |
Project: Knative (Orchestration & Management / Scheduling & Orchestration)
File: fuzzy_mode_convert_table.md

| json type \ dest type | bool | int | uint | float |string| | | | | |--|--| | number | positive => true <br/> negative => true <br/> zero => false| 23.2 => 23 <br/> -32.1 => -32| 12.1 => 12 <br/> -12.1 => 0|as normal|same as origin| | string | empty string => false <br/> string "0" => false <br/> other strings => true | "123.32" => 123 <br/> "-123.4" => -123 <br/> "123.23xxxw" => 123 <br/> "abcde12" => 0 <br/> "-32.1" => -32| 13.2 => 13 <br/> -1.1 => 0 |12.1 => 12.1 <br/> -12.3 => -12.3<br/> 12.4xxa => 12.4 <br/> +1.1e2 =>110 |same as origin| | bool | true => true <br/> false => false| true => 1 <br/> false => 0 | true => 1 <br/> false => 0 |true => 1 <br/>false => 0|true => "true" <br/> false => "false"| | object | true | 0 | 0 |0|originnal json| | array | empty array => false <br/> nonempty array => true| [] => 0 <br/> [1,2] => 1 | [] => 0 <br/> [1,2] => 1 |[] => 0<br/>[1,2] => 1|original json|
Project: Fluid (Orchestration & Management / Scheduling & Orchestration)
File: PULL_REQUEST_TEMPLATE.md

<!-- Please make sure you have read and understood the contributing guidelines; https://github.com/fluid-cloudnative/fluid/blob/master/CONTRIBUTING.md--> <!--If so, add "fixes #xxxx" so that the issue will be closed when this PR is merged (for example, "fixes #15" to close Issue #15). Otherwise, add "NONE" --> fixes #XXXX
Project: Consul (Orchestration & Management / Service Mesh)
File: ui_issues.md

name: Web UI Feedback about: You have usage feedback for the browser based UI <! When filing a bug, please include the following headings if possible. Any example text in this template can be deleted. > <! Please provide a paragraph or two about the issue you're experiencing / suggestion for improvement. > <! Steps to reproduce this issue/view the area for improvement, eg: Visit the UI page at `/ui/services` Click .... then click...etc. View error/area. > <! If this is an improvement rather than a bug, a clear and concise description of what you want to happen. How have you seen this problem solved in other UIs? > <! This can be found either in the footer of the UI (Consul versions pre 1.10) or at the top of the help menu that is in the top right side of the UI. > <! Browser, Browser Version, OS, and any other information you can provide about the environment that may be relevant. > <! If you think it's worthwhile, include appropriate screengrabs showing the error/area for improvement. Try to include the URL bar of the browser so we can see the current URL where the error manifests. Please be careful to obfuscate any sensitive information either in the URL or in the browser page itself. >
Project: Karmada (Orchestration & Management / Scheduling & Orchestration)
File: namespace_test.md

| Test Case | E2E Describe Text | Comments | |--|-|-| | Create a namespace that needs to be automatically synchronized across all member clusters | create a namespace in karmada-apiserver | | | Delete a namespace, and all member clusters need to automatically synchronize the deletion | delete a namespace from karmada-apiserver | | | When a new cluster joins, the namespaces on the Karmada control plane (excluding reserved namespaces) need to be synchronized to that cluster | joining new cluster | |
Project: DolphinScheduler (Orchestration & Management / Scheduling & Orchestration)
File: stored-procedure.md

Execute the stored procedure according to the selected DataSource. Drag from the `PROCEDURE` task node into the canvas, as shown in the figure below: <p align="center"> <img src="../../../../img/procedure_edit.png" width="80%" /> </p> Please refer to `Default Task Parameters` section for default parameters. | Parameter | Description | |-|-| | DataSource | The DataSource type of the stored procedure supports MySQL and POSTGRESQL, select the corresponding DataSource. | | Method | The method name of the stored procedure. | | Custom parameters | The custom parameter types of the stored procedure support `IN` and `OUT`, and the data types support: VARCHAR, INTEGER, LONG, FLOAT, DOUBLE, DATE, TIME, TIMESTAMP and BOOLEAN. | Prepare: Create a stored procedure in the database, e.g. ``` CREATE PROCEDURE dolphinscheduler.test(in in1 INT, out out1 INT) begin set out1=in1; END ```
Project: Gravitee.io (Orchestration & Management / API Gateway)
File: management-api-policies.md

Policies let you customize, enhance API behavior and functionalities. Policies can enforce security, enhance performance, transform request/response and let you implement some logic via the Groovy Policy or dynamic routing policy. Policy can be chained, applied to root path (/) or for specific paths. You can drag and drop policy at the center of the screen to apply policy for a specific path, and the right part of the screen let you configure your policy. The (+) button let you create a new path to specify its behavior via the policies.
Project: Prefect (Orchestration & Management / Scheduling & Orchestration)
File: INFO.md

This directory contains files for building and publishing the `prefect-client` library. `prefect-client` is built by removing source code from `prefect` and packages its own `requirements.txt` and `setup.py`. This process can happen in one of three ways: automatically whenever a PR is created (see `.github/workflows/prefect-client.yaml`) automatically whenever a Github release is published (see `.github/workflows/prefect-client-publish.yaml`) manually by running the `client/build_client.sh` script locally Note that whenever a Github release is published the `prefect-client` will not only get built but will also be distributed to PyPI. `prefect-client` releases will have the same versioning as `prefect` - only the package names will be different. This directory also includes a "minimal" flow that is used for smoke tests to ensure that the built `prefect-client` is functional. In general, these builds, smoke tests, and publish steps should be transparent. It these automated steps fail, use the `client/build_client.sh` script to run the build and smoke test locally and iterate on a fix. The failures will likely be from: including a new dependency that is not installed in `prefect-client` re-arranging or adding files in such a way that a necessary file is rm'd at build time
Project: Knative (Orchestration & Management / Scheduling & Orchestration)
File: CHANGES.md

provide unmarshal options for streams () () bump protobuf dep to v1.33 () () v2/callctx:* fix SetHeader race by cloning header map () () add XGoogFieldMaskHeader constant () () v2/callctx:* add new callctx package () () v2:* add BuildHeaders and InsertMetadataIntoOutgoingContext to header () () v2:* add GoVersion package variable () () v2:* handle space in non-devel go version () () update dependencies () () v2:* drop cloud lro test dep () (), refs apierror:* add method to return HTTP status code conditionally () (), refs add ref to usage with clients () (), refs v2:* add WithTimeout option () () v2/apierror:* return Unknown GRPCStatus when err source is HTTP () (), refs update google.golang.org/api to latest () () v2/apierror:* add apierror.FromWrappingError () () v2:* copy DetermineContentType functionality () () v2:* resolve bad genproto pseudoversion in go.mod () () add ExtractProtoMessage to apierror () () v2:* add OnHTTPCodes CallOption () () v2/apierror:* use errors.As in FromError () () v2:* bump release-please processing () ()
Project: OpenResty (Orchestration & Management / Service Proxy)
File: advice.md

<!-- See https://github.com/check-spelling/check-spelling/wiki/Configuration-Examples%3A-advice --> <!-- markdownlint-disable MD033 MD041 --> <details><summary>If the flagged items are false positives</summary> If items relate to a ... binary file (or some other file you wouldn't want to check at all). Please add a file path to the `excludes.txt` file matching the containing file. File paths are Perl 5 Regular Expressions - you can [test]( https://www.regexplanet.com/advanced/perl/) yours before committing to verify it will match your files. `^` refers to the file's path from the root of the repository, so `^README\.md$` would exclude [README.md]( ../tree/HEAD/README.md) (on whichever branch you're using). well-formed pattern. If you can write a that would match it, try adding it to the `patterns.txt` file. Patterns are Perl 5 Regular Expressions - you can [test]( https://www.regexplanet.com/advanced/perl/) yours before committing to verify it will match your lines. Note that patterns can't match multiline strings. </details>
Project: Easegress (Orchestration & Management / API Gateway)
File: 5.2.Kernel-Tuning.md

To make Easegress good performance, some of the kernel parameters might need to be optimized. Here is a possible configuration for `/etc/sysctl.conf` and `/etc/security/limits.conf`. The values need to be aligned with actual memory. ```conf soft nproc 2067554 hard nproc 2067554 ``` The values need to be aligned with actual memory, CPU, and network. Increase range of ephemeral ports that can be used ```conf net.ipv4.iplocalport_range = 1024 65535 ``` Increase the max number of open files ```conf fs.file-max = 150000 ``` Enable TCP window scaling (enabled by default). Refer to ```conf net.ipv4.tcpwindowscaling = 1 ``` Turn off SYN-flood protections ```conf net.ipv4.tcp_syncookies = 0 ``` Increase the number of packets that can be queued in the network card before being handed to the CPU ```conf net.core.netdevmaxbacklog = 3240000 ``` Max number of "backlogged sockets" (connection requests that can be queued for any given listening socket) ```conf net.core.somaxconn = 65535 ``` TCP memory tuning. Refer to ```conf net.core.rmem_default=16777216 net.core.wmem_default=16777216 net.core.optmem_max=16777216 net.core.rmem_max=16777216 net.core.wmem_max=16777216 net.ipv4.tcp_mem=16777216 16777216 16777216 net.ipv4.tcp_wmem=4096 87380 16777216 net.ipv4.tcp_rmem=4096 87380 16777216 ``` Number of packets to keep in the backlog before the kernel starts dropping them ```conf net.ipv4.tcpmaxsyn_backlog = 3240000 ``` Only retry creating TCP connections 3 times. Minimize the time it takes for a connection attempt to fail ```conf net.ipv4.tcpsynretries=3 net.ipv4.tcpsynackretries=3 net.ipv4.tcporphanretries=3 ``` How many retries TCP makes on data segments (default 15). Some guides suggest reducing this value ```conf net.ipv4.tcp_retries2 = 8 ``` Increase max number of sockets allowed in TIME_WAIT ```conf net.ipv4.tcpmaxtw_buckets = 1440000 ``` Keepalive Optimizations. By default, the keepalive routines wait for two hours (7200 secs) before sending the first keepalive probe, and then resend it every 75 seconds. If no ACK response is received for 9 consecutive times, the connection is marked as broken. ```conf net.ipv4.tcpkeepalivetime = 600 # default 7200 net.ipv4.tcpkeepaliveintvl = 10 # default 75 net.ipv4.tcpkeepaliveprobes = 9 # default 9 ``` The TCP FIN timeout specifies the amount of time a port must be inactive before it can be reused for another connection. The default is often 60 seconds, but can normally be safely reduced to 30 or even 15 seconds https://www.linode.com/docs/web-servers/nginx/configure-nginx-for-optimized-performance ```conf net.ipv4.tcpfintimeout = 7 ``` Refer to this ```conf net.ipv4.tcpslowstartafteridle = 0 net.ipv4.tcpnometrics_save = 1 ``` If listening service is too slow to accept new connections, reset them. Default state is FALSE. It means that if overflow occurred due to a burst, connection will recover. Enable this option only if you are really sure that listening daemon cannot be tuned to accept connections faster. Enabling this option can harm clients of your server. Refer to ```conf net.ipv4.tcpaborton_overflow=0 ```
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2018-07-25-mesos-1-6-1-released.md

layout: post title: "Apache Mesos 1.6.1 Released" published: true post_author: display_name: Greg Mann gravatar: 20c5c9695f0891b6b093704331238133 twitter: greggomann tags: Release Apache Mesos 1.6.1 is now available for . This release includes important bug fixes and improvements to 1.6.0; if you're considering using Mesos 1.6, it's recommended that you use 1.6.1. The following notable fixes are included: - ZooKeeper connection should retry on `EAI_NONAME`. - Agent gc on old slave sandboxes could empty persistent volume data - Agent may fail to recover if the agent dies before image store cache checkpointed. - Master crash when removing quota. - Implement a Random Sorter for offer allocations. - Master check failure due to CHECK_SOME(providerId). - Executor crash trying to print container ID. - mesos-slave can deadlock with docker pull. - `slave.available()` in the allocator is expensive and drags down allocation performance. - Master asks agent to shutdown upon auth errors. - GCC 8.1 build failure in os::Fork::Tree. - Mesos master segfaults with stack overflow under load. - The container which joins CNI network and has checkpoint enabled will be mistakenly destroyed by agent. Full release notes are available in the release . Rolling upgrades from a Mesos 1.6.0 cluster to Mesos 1.6.1 are straightforward. Please refer to the for detailed information on upgrading to Mesos 1.6.1 from other versions. 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.6.1 possible: Alexander Rojas, Alexander Rukletsov, Andrew Schwartzmeyer, Armand Grillet, Benjamin Bannier, Benjamin Mahler, Benno Evers, bin zheng, Chun-Hung Hsiao, Gastn Kleiman, Gilbert Song, Greg Mann, he yi hua, James Peach, Jie Yu, Kjetil Joergensen, Meng Zhu, Zhitao Li
Project: CoreDNS (Orchestration & Management / Coordination & Service Discovery)
File: coredns-1.2.5.md

+++ title = "CoreDNS-1.2.5 Release" description = "CoreDNS-1.2.5 Release Notes." tags = ["Release", "1.2.5", "Notes"] release = "1.2.5" date = "2018-10-24T20:40:29+01:00" author = "coredns" +++ We are pleased to announce the of CoreDNS-1.2.5! Correctly make a reply fit in the client's buffer, especially when EDNS0 is not used. This used to be the responsibility of a plugin, now the server will handle it. Documentation and smaller updates for various plugins, as well as: - resets min TTL default back to 5 second (instead of 0). - now allows aZSK/KSK split as well as a CSK setup. - answer rewrite is now automatic for exact name rewrites. Andrey Meshkov, Chris O'Haver, Francois Tur, Kevin Nisbet, Manuel Stocker, Miek Gieben, Paul G, Ruslan Drozhdzh, Sandeep Rajan, Yong Tang. For documentation see our (in progress!) . For help and other resources, see our .
Project: Contour (Orchestration & Management / Service Proxy)
File: CHANGELOG-v1.15.2.md

We are delighted to present version 1.15.2 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters. As an additional mitigation for , has been backported to this release. Previously an ExternalName service with an address of `localhost` and port matching the Envoy admin interface listener port could expose admin endpoints that would allow an attacker to shut down Envoy remotely. Contour's bootstrap command now configures Envoy to listen on a Unix domain socket to ensure an ExternalName service cannot expose the "writable" endpoints of the admin interface. For backwards compatibility Contour now configures an additional Envoy listener to expose endpoints useful for debugging. This listener does not expose any endpoints that can be used to modify data, set Envoy healthcheck status, or shut down Envoy. See for some more detail. Note: While this fix does mitigate some aspects of CVE-2021-32783, ExternalName service usage is still discouraged as they can still be used to expose services across namespaces. If you have been using the Contour example YAMLs to deploy Contour and Envoy, no changes are required except to deploy the updated YAMLs for release 1.15.2. If you are managing your Envoy DaemonSet using another method, be sure to inspect the . An is required and it must be mounted in the and containers to ensure both have access to the Unix domain socket Envoy is now configured to listen on. Upgrades the default Envoy version to 1.18.4 for security and bug fixes. See the for more details.
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2017-11-16-mesos-1-4-1-released.md

layout: post title: Apache Mesos 1.4.1 Released permalink: /blog/mesos-1-4-1-released/ published: true post_author: display_name: Kapil Arya tags: Release The latest Mesos 1.4.x release, 1.4.1, is now available for . This release includes important bug fixes and improvements on top of 1.4.0. It is recommended to use this version if you are considering using Mesos 1.4. More specifically, this release includes the following: - Expose `ExecutorInfo.ContainerInfo.NetworkInfo` in Mesos `state` endpoint. - ProcessManager::resume sometimes crashes accessing EventQueue. - Heavy-duty GC makes the agent unresponsive. - Handle `/proc/self/ns/pidforchildren` when parsing available namespace. - Handle cgroups v2 hierarchy when parsing /proc/self/cgroups. - Stout fails to compile with libc >= 2.26. - Killing TASK_GROUP fail to kill some tasks. - The default executor does not propagate missing task exit status correctly. - Mesos 1.4.0 crashes with 1.3.x agent with oversubscription - Masters can lose track of tasks' executor IDs. - Incorrect master validation forces executor IDs to be globally unique. Full release notes are available in the release Rolling upgrades from a Mesos 1.4.0 cluster to Mesos 1.4.1 are straightforward. Please refer to the for detailed information on upgrading to Mesos 1.4.1 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 11 contributors who made 1.4.1 possible: Benjamin Mahler, Chun-Hung Hsiao, Deepak Goel, Gaston Kleiman, James DeFelice, James Peach, Jiang Yan Xu, Kapil Arya, Michael Park, Qian Zhang, Zhitao Li
Project: Volcano (Orchestration & Management / Scheduling & Orchestration)
File: summer2020.md

This is a program hosted by ISCAS(Institute of Software Chinese Academy of Sciences) and openEuler community. It is very similar with Google Summer of Code, the only difference is that it is only targeted for Chinese students. This year(2020) is their first time to host this event. Official website: https://isrc.iscas.ac.cn/summer2020 Volcano is a kubernetes native batch system, it aims to cover the shortage of kubernetes on batch service. And it has supported Tensorflow, MPI, Spark, MindSpore and so many other frameworks covering many areas, such as AI, BigData, HPC and Genomic. Volcano makes use of CRD to declare a common API for batch job, and provides the capability on advanced job lifecycle management. It also provides advanced scheduling capability intended for batch and HPC scenarios, including gang-scheduling, fairshare, drf, binpack, preempt, topology-aware, etc. More details please refer to As this program is designed for Chinese students, all proposed tasks are listed in Chinese.
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2017-08-31-mesos-1-1-3-released.md

layout: post title: Apache Mesos 1.1.3 Released permalink: /blog/mesos-1-1-3-released/ published: true post_author: display_name: AlexR tags: Release The latest Mesos release, 1.1.3, is now available for . This release includes some important bug fixes and improvements on top of 1.1.2. It is highly recommended that users use this version if you are considering using Mesos 1.1. More specifically, this release includes the following major fixes and improvements: - The filesystem/linux isolator does not set the permissions of the host_path. - Docker executor hangs forever if `docker stop` fails. - Launching two tasks with the same Docker image simultaneously may cause a staging dir never cleaned up. - Add an agent flag for executor re-registration timeout. - Allow "old" executors with half-open connections to be preserved during agent upgrade / restart. - Libprocess can crash on malformed request paths for libprocess messages. - The agent can crash when an unknown executor tries to register. - Fix interference of external Boost installations when using some unbundled dependencies. - Mesos fails to exec a custom executor when no shell is used. - Java HTTP adapter crashes JVM when leading master disconnects. - Persistent volume might not be mounted if there is a sandbox volume whose source is the same as the target of the persistent volume. - Agent failed to recover due to mount namespace leakage in Docker 1.12/1.13. - LIBPROCESS_IP isn't passed on to the fetcher. - Sandbox_path volume does not have ownership set correctly. - Agent may drop pending kill task status updates. - Agent may process a kill task and still launch the task. Full release notes are available in the release Rolling upgrades from a Mesos 1.1.2 cluster to Mesos 1.1.3 are straightforward. Please refer to the for detailed information on upgrading to Mesos 1.1.3. We encourage you to try out this release and let us know what you think. If you run into any issues, please let us know on the . Thanks to the 11 contributors who made 1.1.3 possible: Aaron Wood, Alexander Rukletsov, Andrei Budnik, Benjamin Bannier, Benjamin Mahler, Chun-Hung Hsiao, Gastn Kleiman, Gilbert Song, Greg Mann, Jie Yu, and Qian Zhang.