cwielenb/CNCF-Dataset huggingface dataset:
Project: Serverless Devs (Orchestration & Management / Scheduling & Orchestration)
File: PULL_REQUEST_TEMPLATE.md

Thank you for creating a pull request to contribute to Serverless Devs code! Before you open the request please answer the following questions to help it be more easily integrated. Please check the boxes "[ ]" with "[x]" when done too. Please select one of the PR types below to complete Bug detail The specific manifestation of the bug or the associated issue. Pull request tasks [ ] Add test cases for the changes [ ] Passed the CI test Reason for update Why do you need to update your documentation? Pull request tasks [ ] Update Chinese documentation [ ] Update English documentation Contributed content [ ] Code [ ] Package(Includes components, applications, plugins) [ ] Document Content detail ``` if contenttype == 'code' || contenttype == 'document': please tell us `PR url`like: https://github.com/Serverless-Devs/Serverless-Devs/pull/451 else if content_type == 'package': please tell us `package neme or repo`like: 'https://github.com/devsapp/fc' || 'start-django' else: please describe your contribution in detail ``` Reason for update Why do you need to update your documentation?
Project: k8gb (Orchestration & Management / Coordination & Service Discovery)
File: SECURITY.md

We're always looking for ways to improve our security posture and taking security vulnerabilities seriously. To report a vulnerability, send an email to the official k8gb maintainers list . Please make sure to provide the following information: vulnerability description version of the k8gb package version of the k8s cluster steps to reproduce the vulnerability The standard response time from k8gb project maintainers for a vulnerability report is less than 14 days. Once k8gb project maintainers have confirmed the relevance of the report, a will be created on Github. Please provide Github username to k8gb project maintainers if you wish to be invited to participate in advisory discussions. You can also request to be updated about advisory discussions directly via email. If the vulnerability is accepted, you'll be informed about the determined timeline for developing a patch, public disclosure, and patch release. You are expected to participate in the discussion of the timeline and respect the agreed dates for public disclosure.
Project: Azure Service Fabric (Orchestration & Management / Scheduling & Orchestration)
File: bug_report.md

name: Bug report about: Create a issue to track bug related to release/version in any environment to help us improve the experience title: '[BUG] -short desription of bug and milestone version' labels: 'type-code-defect' assignees: '' projects: 'ServiceFabric-Bugs' Describe the bug A clear and concise description of what the bug is. Area/Component: Please mention area or component in Service Fabric where issue was found. Ex: security, monitoring, placement or resource governance, Reliable services, Actors, programming models,SDK,.etc. To Reproduce Steps to reproduce the behavior: Go to '...' Click on '....' Scroll down to '....' See error Expected behavior A clear and concise description of what you expected to happen. Observed behavior: Screenshots If applicable, add screenshots to help explain your problem. Service Fabric Runtime Version: ex: 7.1., 7.2. Environment: Must be one of these values [Standalone OR Azure OR OneBox/Dev cluster] OS: [e.g. Windows 2019, Ubuntu 18.04] Version [e.g. 7.1, 7.2 ] If this is a regression, which version did it regress from? Additional context Add any other context about the problem here. Assignees: /cc @microsoft/service-fabric-triage
Project: Traefik Mesh (Orchestration & Management / Service Mesh)
File: CONTRIBUTING.md

Traefik Mesh is an open source project, and your feedback and contributions are needed and always welcome. [Issues] and [Pull Requests] are opened at https://github.com/traefik/mesh. Non trivial changes should be discussed with the project maintainers by opening a [Feature Request] clearly explaining rationale, background and possible implementation ideas. Feel free to provide code in such discussions. Once the proposal is approved, a Pull Request can be opened. If you want to provide early visibility to reviewers, create a [Draft Pull Request]. Traefik Mesh follows the scheme when releasing new versions. Therefore, all PR's (except fixing a bug in a specific version) should be made against the `master` branch. If you're attempting to fix a bug in an already released version, please use the correct branch of that release (e.g. `v1.1`). All bug-fixes made to a specific branch will be backported to master, prior to releasing a new (major / minor) version. Patch releases will be made out of the version branch. In order to release a new version of Traefik Mesh, the following steps have to be done: Create a Prepare release PR updating the chart version and app version to upcoming release Prepare a list of release notes for the #traefik-mesh Merge Prepare release PR Create and push a tag on the release commit Create a new release branch (v1.x) on upstream to allow versioned docs to be built
Project: DolphinScheduler (Orchestration & Management / Scheduling & Orchestration)
File: seatunnel.md

`SeaTunnel` task type for creating and executing `SeaTunnel` tasks. When the worker executes this task, it will parse the config file through the `start-seatunnel-spark.sh` , `start-seatunnel-flink.sh` or `seatunnel.sh` command. Click for more information about `Apache SeaTunnel`. Click Project Management -> Project Name -> Workflow Definition, and click the "Create Workflow" button to enter the DAG editing page. Drag the <img src="../../../../img/tasks/icons/seatunnel.png" width="15"/> from the toolbar to the drawing board. Please refer to `Default Task Parameters` section for default parameters. Startup script: Select script name to start the task, including `seatunnel.sh`, `start-seatunnel-flink-13-connector-v2.sh`, `start-seatunnel-flink-15-connector-v2.sh`, `start-seatunnel-flink-connector-v2.sh`, `start-seatunnel-flink.sh`, `start-seatunnel-spark-2-connector-v2.sh`, `start-seatunnel-spark-3-connector-v2.sh`, `start-seatunnel-spark-connector-v2.sh`, `start-seatunnel-spark.sh` FLINK Run model: supports `run` and `run-application` modes Option parameters: used to add the parameters of the Flink engine, such as `-m yarn-cluster -ynm seatunnel` SPARK Deployment mode: specify the deployment mode, `cluster` `client` Master: Specify the `Master` model, `yarn` `local` `spark` `mesos`, where `spark` and `mesos` need to specify the `Master` service address, for example: 127.0.0.1:7077 SEATUNNEL_ENGINE Deployment mode: specify the deployment mode, `cluster` `local` > Click for more information on the usage of `Apache SeaTunnel command` Custom Configuration: Supports custom configuration or select configuration file from Resource Center > Click for more information about `Apache > >> SeaTunnel config` file Script: Customize configuration information on the task node, including four parts: `env` `source` `transform` `sink` This sample demonstrates using the Flink engine to read data from a Fake source and print to the console. If you want to use the SeaTunnel task type in the production environment, you need to configure the required environment first. The configuration file is as follows: `/dolphinscheduler/conf/env/dolphinscheduler_env.sh`. According to the above parameter description, configure the required content. ```Config env { execution.parallelism = 1 } source { FakeSource { resulttablename = "fake" field_name = "name,age" } } transform { sql { sql = "select name,age from fake" } } sink { ConsoleSink {} } ``` v2.3.1 v2.3.2 v2.3.3
Project: CoreDNS (Orchestration & Management / Coordination & Service Discovery)
File: coredns-1.6.9.md

+++ title = "CoreDNS-1.6.9 Release" description = "CoreDNS-1.6.9 Release Notes." tags = ["Release", "1.6.9", "Notes"] release = "1.6.9" date = 2020-03-24T10:00:00+00:00 author = "coredns" +++ The CoreDNS team has released . This release is identical to 1.6.8. (Yes there was a , but our automation broke after tagging it in Git - hence another bump in the minor version) Again a small release with some nice improvements in the forward plugin, and overall polish. See "Noteworthy Changes" for more detail. Note that 1.7.0 will contain a bunch of backward incompatible changes: the federation plugin will be full removed and the metrics name will be changed to inline with the naming recommendation from the Prometheus project. Andy Bursavich, Chris O'Haver, Christian Tryti, Darshan Chaudhary, Kohei Yoshida, LongKB, Miek Gieben, Ricky S, Sylvain Rabot, Zou Nengren. plugin/azure: Add private DNS support for azure plugin (https://github.com/coredns/coredns/pull/1516) plugin/cache: Fix negative cache masking cases (https://github.com/coredns/coredns/pull/3744) plugin/cache: explain drop metric (https://github.com/coredns/coredns/pull/3706) plugin/forward: Add configuration flag to set if RecursionDesired should be set on health checks (https://github.com/coredns/coredns/pull/3679) plugin/forward: Add exponential backoff to healthcheck (https://github.com/coredns/coredns/pull/3643) plugin/forward: Add max_concurrent option (https://github.com/coredns/coredns/pull/3640) plugin/hosts: Modifies NODATA handling (https://github.com/coredns/coredns/pull/3536) plugin/kubernetes: fix metadata (https://github.com/coredns/coredns/pull/3642) plugin/kubernetes: Return all records with matching IP for reverse queries (https://github.com/coredns/coredns/pull/3687) plugin/metrics: Add query type to latency as well (https://github.com/coredns/coredns/pull/3685) plugin/pkg/up: Make default intervals shorter (https://github.com/coredns/coredns/pull/3651)
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_edit_virtualservice_ratelimit_client-config.md

title: "glooctl edit virtualservice ratelimit client-config" weight: 5 Add rate-limits (Enterprise) Configure rate-limits, which are composed of rate-limit actions that translate request characteristics to rate-limit descriptor tuples. For available actions and more information see: https://www.envoyproxy.io/docs/envoy/v1.9.0/api-v2/api/v2/route/route.proto#route-ratelimit-action This is a Gloo Enterprise feature. ``` glooctl edit virtualservice ratelimit client-config [flags] ``` ``` -h, --help help for client-config ``` ``` -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) ``` - Configure rate limit settings (Enterprise)
Project: Gravitee.io (Orchestration & Management / API Gateway)
File: management-configuration-portal.md

Be careful before updating values, they will be automatically available on every new user session. For example, you are able to select the Theme to apply on the portal or toggle features like Support or Rating Some settings are read-only because they are set with environment variables. The custom API Key mode allows you to set arbitrary values as API Keys. This way, API publishers are able to silently migrate to Gravitee.io without changing consumers API Key. The shared API Key mode will make consumers reuse the same API Key across all API subscriptions of this application. With this mode enabled, consumers will be asked on their second subscription to choose between reusing their key across all subscriptions or generate one different API Key for each subscription (which is the default mode). This choice is permanent and consumers will not be able to switch back to one key per subscription for their application. When disabling the shared API Key mode, applications that have already been configured to use a shared key will continue to work this way, but consumers will stop being asked to choose between one mode or the other on their second subscription.
Project: Avro (Orchestration & Management / Remote Procedure Call)
File: avro-1.8.2-released.md

title: "Avro 1.8.2" linkTitle: "Avro 1.8.2" date: 2017-05-20 <!-- 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. --> Apache Avro 1.8.2 has been released!
Project: Istio (Orchestration & Management / Service Mesh)
File: SECURITY.md

Information about supported Istio versions can be found on the [Support Announcements] page on Istio's website. Instructions for reporting a vulnerability can be found on the [Istio Security Vulnerabilities] page. The Istio Product Security Working Group receives vulnerability and security issue reports, and the company affiliation of the members of the group can be found at [Early Disclosure Membership]. Information about previous Istio vulnerabilities can be found on the [Security Bulletins] page.
Project: gRPC (Orchestration & Management / Remote Procedure Call)
File: feature_request_python.md

name: Request a gRPC Python feature about: Suggest an idea for this project labels: kind/enhancement, priority/P2, lang/Python assignees: gnossen XuanWang-Amos <!-- 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: Gloo (Orchestration & Management / API Gateway)
File: enterprise_helm_chart_values.md

title: "Enterprise Gloo Edge" description: Listing of Helm values for the Enterprise Gloo Edge chart weight: 30 The table below describes all the values that you can override in your custom values file when working with the Helm chart for Enterprise Gloo Edge. More information on using a Helm chart to install the Gloo Edge can be found . {{% notice warning %}} Because the Gloo Edge Enterprise Helm chart uses the open source chart as a dependency, you must add the `gloo.` prefix to all open source Gloo Edge chart values. This applies to all values except for `global.*`. For example, when you install Gloo Edge Enterprise, `ingress.deployment.nodeName` must be changed to `gloo.ingress.deployment.nodeName`, but `global.glooRbac.create` remains unchanged. {{% /notice %}} {{< readfile file="static/content/glooe-values.docgen" markdown="true" >}} Most changes that need to be made to the default helm chart are supported by the helm values above. However, there may be a case where the helm values do not cover a necessary change. Helm values which expose the kubernetes API (ie Service, Deployment) now include a `KubeResourceOverride` field. The following example uses `KubeResourceOverride` to add labels to a deployment, which is not explicitly implemented in the helm chart: Gloo deployment: ```yaml apiVersion: v1 kind: Deployment metadata: labels: gloo: gloo name: gloo ``` We want to add the `resource-owner: infra-team` label to the Deployment. We can do so by specifying the `KubeResourceOverride` in the helm values file: ```yaml gloo: deployment: kubeResourceOverride: metadata: labels: resource-owner: infra-team ``` Yaml under the `kubeResourceOverride` is merged in to the deployment yaml, to create the resulting kube resource: ```yaml apiVersion: v1 kind: Deployment metadata: labels: gloo: gloo resource-owner: infra-team ``` {{% notice note %}} `kubeResourceOverride` does not support merging in lists, and a list in the override will replace the list in the original resource. {{% /notice %}} is another solution for patching resources generated by helm. The following table enumerates differences between the offered solutions. | Kustomize | Helm KubeResourceOverride | |-|--| | - Finer control over merges, e.g. merging lists <br>- Requires additional files (overlays)<br>- Unsupported in older versions of flux helm operator | - Can be done only with helm, does not require CI/CD pipeline changes <br>- Specified through values.yaml file or command line arguments |
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2018-08-20-mesos-1.4.2-released.md

layout: post title: Apache Mesos 1.4.2 Released permalink: /blog/mesos-1-4-2-released/ published: true post_author: display_name: Kapil Arya tags: Release The latest Mesos 1.4.x release, 1.4.2, is now available for . This release includes important bug fixes and improvements on top of 1.4.2. It is recommended to use this version if you are considering using Mesos 1.4. More specifically, this release includes the following notable fixes: - Roles can exceed limit allocation via reservations. - Quota can be exceeded due to coarse-grained offer technique. - Reservation may not be allocated when the role has no quota. - Quota headroom may be insufficiently held when role has more reservation than quota. - Resources may get over allocated to some roles while fail to meet the quota of other roles. - Docker bug can cause unkillable tasks. - Quota headroom tracking may be incorrect in the presence of hierarchical reservation. - Agent gc on old slave sandboxes could empty persistent volume data - Master crash when removing quota. - Quota limit "chopping" can lead to cpu-only and memory-only offers. - Implement a Random Sorter for offer allocations. - Master streaming API does not send (health) check updates for tasks. - Master asks agent to shutdown upon auth errors. - Port mapper CNI plugin might fail with "Resource temporarily unavailable" - Port mapper CNI plugin might deadlock iptables on the agent. Full release notes are available in the release Rolling upgrades from a Mesos 1.4.1 cluster to Mesos 1.4.2 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 24 contributors who made 1.4.2 possible: Akash Gupta, Alexander Rojas, Alexander Rukletsov, Andrei Budnik, Armand Grillet, Benjamin Bannier, Benjamin Hindman, Benjamin Mahler, Benno Evers, Bin Zheng, Chun-Hung Hsiao, Gastn Kleiman, Gilbert Song, Greg Mann, He Yi Hua, James Peach, Jason Lai, Jie Yu, Kapil Arya, Kjetil Joergensen, Meng Zhu, Michael Park, Qian Zhang, Zhitao Li
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_istio_uninject.md

title: "glooctl istio uninject" weight: 5 Remove SDS & istio-proxy sidecars from gateway-proxy pod Removes the istio-proxy sidecar from the gateway-proxy pod. Also removes the sds sidecar from the gateway-proxy pod. Also removes the gatewayproxysds cluster from the gateway-proxy envoy bootstrap ConfigMap. ``` glooctl istio uninject [flags] ``` ``` -h, --help help for uninject --include-upstreams whether or not to modify upstreams when uninstalling mTLS ``` ``` -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: Contour (Orchestration & Management / Service Proxy)
File: CHANGELOG-v1.23.2.md

We are delighted to present version v1.23.2 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters. A big thank you to everyone who contributed to the release. Updates Go to 1.19.4, see . (#4924, @skriss) For a fresh install of Contour, consult the . To upgrade an existing Contour installation, please consult the . Contour v1.23.2 is tested against Kubernetes 1.23 through 1.25. If you're using Contour and want to add your organization to our adopters list, please visit this . If you prefer to keep your organization name anonymous but still give us feedback into your usage and scenarios for Contour, please post on this .