cwielenb/CNCF-Dataset huggingface dataset:
Project: wasmCloud (Orchestration & Management / Scheduling & Orchestration)
File: 0015-actor-autoscaling.md

| Status | Deciders | Date | |-||| | Accepted | | 5 Oct 2023 | In wasmCloud, we face the challenge of managing application component scaling (actors or providers) efficiently. With the wasmtime enabling on-request instantiation with possible single digit nanosecond levels of latency, the concept of a fixed "count" of running instances has become obsolete. We aim to improve scalability and the developer experience by reimagining our approach to WebAssembly applications. The need for a more efficient, scalable approach to handling WebAssembly components in wasmCloud. Desire to improve the developer experience by simplifying the scaling process. Advancements in wasmtime that allow for on-demand instantiation of components. Modifying the Scale operation, deprecating the Start* operation, and removing the `count` field in favor of `max_concurrent`. Actors will no longer run a set number of instances, but will instead be instantiated on-demand. This approach will also allow for "scale to zero" functionality, where actors are only instantiated when a message is received up to a maximum number of concurrent instances. Maintaining the current approach with a fixed `count` for instances. Chosen option: "Modifying the Scale operation and deprecating the Start operation", because this approach aligns with the latest advancements in wasmtime, eliminates the need for pre-determined instance counts, and allows for more efficient, on-demand scaling of WebAssembly components. WebAssembly components in wasmCloud can be instantiated on-demand, leading to more efficient resource utilization. Simplifies the developer experience by removing the need to manage instance counts. Allows wasmCloud applications to scale more effectively based on load. Required significant changes in existing wasmCloud projects to adapt to the new scaling approach. Could lead to initial confusion or learning curve for developers accustomed to the previous model. Good, because it allows for on-demand instantiation of components, leading to better resource utilization. Good, because it simplifies the scaling process for developers. Bad, because it requires significant changes to existing wasmCloud projects. Good, because it requires no changes to existing projects. Bad, because it does not take advantage of the latest advancements in wasmtime. Bad, because it maintains a less efficient scaling model based on predetermined instance counts.
Project: Karmada (Orchestration & Management / Scheduling & Orchestration)
File: RELEASE.md

The `yaml` Project is released on an as-needed basis. The process is as follows: An issue is proposing a new release with a changelog since the last release All must LGTM this release An OWNER runs `git tag -s $VERSION` and inserts the changelog and pushes the tag with `git push $VERSION` The release issue is closed An announcement email is sent to `kubernetes-dev@googlegroups.com` with the subject `[ANNOUNCE] kubernetes-template-project $VERSION is released`
Project: CoreDNS (Orchestration & Management / Coordination & Service Discovery)
File: coredns-1.2.6.md

+++ title = "CoreDNS-1.2.6 Release" description = "CoreDNS-1.2.6 Release Notes." tags = ["Release", "1.2.6", "Notes"] release = "1.2.6" date = "2018-11-05T20:40:29+01:00" author = "coredns" +++ We are pleased to announce the of CoreDNS-1.2.6! Ignore the error when setting SO_REUSEPORT on a socket fails; this makes CoreDNS work on older kernels. has seen minor bugfixes. fixes a bug when dealing with a failing upstream. unifies all logging (done by this plugin and normal logs) and always use RFC3339 timestamps (with millisecond accuracy). The `{when}` verb has been made a noop, it will be removed in the next release. got some minor optimizations. (and log*) gotten a new option (`consolidate`) to suppress logging. will now read the `hosts` file without holding a write lock. makes the upstream optional. Carl-Magnus Bjrkell, Chris O'Haver, Dzmitry Razhanski, Francois Tur, Jiacheng Xu, Matthias Lechner, Miek Gieben, Ruslan Drozhdzh, Stuart Nelson. For documentation see our (in progress!) . For help and other resources, see our .
Project: Volcano (Orchestration & Management / Scheduling & Orchestration)
File: LICENSE.md

MIT License Copyright (c) 2019 Josh Bleecher Snyder Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Project: Contour (Orchestration & Management / Service Proxy)
File: CHANGELOG-v1.15.1.md

We are delighted to present version 1.15.1 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters. Upgrades the default Envoy version to 1.18.3 for security and bug fixes. See the for more details. (CVSS score 8.3, High): Envoy versions 1.18.2 and earlier does not decode escaped slash sequences %2F and %5C in HTTP URL paths. A remote attacker may craft a path with escaped slashes, e.g. /something%2F..%2Fadmin, to bypass access control, e.g. a block on /admin. A backend server could then decode slash sequences and normalize path which would provide an attacker access beyond the scope provided for by the access control policy.
Project: Istio (Orchestration & Management / Service Mesh)
File: calico.md

The calico.yaml file is from Once downloaded, run the following sed command to replace the default docker.io images with istio-testing's copies of them: ```shell sed -ie "s?docker.io?gcr.io/istio-testing?g" calico.yaml ``` In order to upgrade versions of calico we'll need to update the version below and then have someone with the ability to push run the following: ```shell export VERSION=v3.27.0 crane cp {docker.io,gcr.io/istio-testing}/calico/cni:"${VERSION}" crane cp {docker.io,gcr.io/istio-testing}/calico/node:"${VERSION}" crane cp {docker.io,gcr.io/istio-testing}/calico/kube-controllers:"${VERSION}" ```
Project: Avro (Orchestration & Management / Remote Procedure Call)
File: avro-1.5.3-released.md

title: "Avro 1.5.3" linkTitle: "Avro 1.5.3" date: 2011-08-29 <!-- 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.5.3 has been released!
Project: CoreDNS (Orchestration & Management / Coordination & Service Discovery)
File: coredns-1.1.1.md

+++ title = "CoreDNS-1.1.1 Release" description = "CoreDNS-1.1.1 Release Notes." tags = ["Release", "1.1.1", "Notes"] release = "1.1.1" date = "2018-03-25T18:04:29+01:00" author = "coredns" +++ We are pleased to announce the of CoreDNS-1.1.1! This release fixes a critical bug in the cache plugin found by . All users are encouraged to upgrade. Fix a bug when scrubbing the reply to fit the request's buffer consumes 100% CPU and does not return the reply. fixes the critical spoof vulnerability. adds support for PTR records. The following people helped with getting this release done: Chris O'Haver, Mario Kleinsasser, Miek Gieben, Yong Tang. And of course the people in . Also special shout out to Mario Kleinsasser for helping to debug the . For documentation see our (in progress!) . For help and other resources, see our .
Project: DolphinScheduler (Orchestration & Management / Scheduling & Orchestration)
File: mysql.md

| Datasource | Description | |-|-| | Datasource | Select MYSQL. | | Datasource name | Enter the name of the DataSource. | | Description | Enter a description of the DataSource. | | IP/Host Name | Enter the MYSQL service IP. | | Port | Enter the MYSQL service port. | | Username | Set the username for MYSQL connection. | | Password | Set the password for MYSQL connection. | | Database name | Enter the database name of the MYSQL connection. | | Jdbc connection parameters | Parameter settings for MYSQL connection, in JSON format. | No, read section example in `DataSource Center` section to activate this datasource.
Project: Kuma (Orchestration & Management / Service Mesh)
File: new-policies.md

Use the tool: ```shell go run ./tools/policy-gen/bootstrap/... --name CaseNameOfPolicy ``` The output of the tool will tell you where the important files are! To enable policy you need to adjust configuration of two places: Remove `+kuma:policy:skip_registration=true` from your policy schema. Add import in `pkg/plugins/policies/imports.go` `pkg/plugins/policies/core/ordered/ordered.go`. Plugins name is equals to `KumactlArg` in file `zz_generated.resource.go`. It's important to place the plugin in the correct place because the order of executions is important. Field is mergeable if it is directly in `default` struct or any sub-struct. Field is not mergeable if it is inside the struct which is inside the list. ```yaml default: a: value_a b: c: value_c d: e: value_e f: g: value_g h: [] ``` Mergeable: a, b, c, d Not mergeable: e, f, g, h All mergeable fields are optional. ```go type SomeStruct struct { MyListField []ItemType `json:"myListField"` } ``` ```go type SomeStruct struct { MyListField *[]ItemType `json:"myListField,omitempty"` } ``` ```go type Conf struct { MyStructField StructType `json:"myStructField"` } ``` ```go type Conf struct { MyStructField *StructType `json:"myStructField,omitempty"` } ``` ```go type SomeStruct struct { MyField ItemType `json"myField"` } ``` ```go type SomeStruct struct { MyField *ItemType `json"myField,omitempty"` } ```
Project: Clusternet (Orchestration & Management / Scheduling & Orchestration)
File: MAINTAINERS.md

The maintainers are generally available in Slack at in channel #clusternet (obtain an invitation at ) for discussions and questions. Please keep the below list sorted with Github ID in ascending order. | Name | GitHub ID | Company/Affiliation | Email | |--|--|-|| | Di Xu | | Tencent | | | Garry Fang | | Tencent | | | Huifeng Le | | Intel | | | Lingming Xia | | Purple Mountain Laboratory | | | Yiwei Chen | | Tencent | | E-mail addresses are expected to be used for reporting security issues. Please use for reporting non-security issues.
Project: Kuma (Orchestration & Management / Service Mesh)
File: 000-template.md

Status: {rejected | accepted | deprecated | superseded by | implemented in `<link to releavant PR/issue...>`} <!-- recommended to have the status as accepted proactively and then to change it if needed --> Technical Story: {description | ticket/issue URL} <!-- link to the github issue --> {Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in form of a question.} {driver 1, e.g., a force, facing concern, } {driver 2, e.g., a force, facing concern, } <!-- numbers of drivers can vary --> {option 1} {option 2} {option 3} <!-- numbers of options can vary --> Chosen option: "{option 1}", because {justification. e.g., only option, which meets k.o. criterion decision driver | which resolves force {force} | | comes out best (see below)}. {e.g., improvement of quality attribute satisfaction, follow-up decisions required, } {e.g., compromising quality attribute, follow-up decisions required, } {example | description | pointer to more information | } <!-- optional --> Good, because {argument a} Good, because {argument b} Bad, because {argument c} <!-- numbers of pros and cons can vary --> {example | description | pointer to more information | } <!-- optional --> Good, because {argument a} Good, because {argument b} Bad, because {argument c} <!-- numbers of pros and cons can vary --> {example | description | pointer to more information | } <!-- optional --> Good, because {argument a} Good, because {argument b} Bad, because {argument c} <!-- numbers of pros and cons can vary --> {Link type} {Link to ADR} <!-- example: Refined by --> <!-- numbers of links can vary -->
Project: Open Cluster Management (Orchestration & Management / Scheduling & Orchestration)
File: RELEASING.md

A Gomega release is a tagged sha and a GitHub release. To cut a release: Ensure CHANGELOG.md is up to date. Use ```bash LAST_VERSION=$(git tag --sort=version:refname | tail -n1) CHANGES=$(git log --pretty=format:'- %s [%h]' HEAD...$LAST_VERSION) echo -e "## NEXT\n\n$CHANGES\n\n### Features\n\n### Fixes\n\n### Maintenance\n\n$(cat CHANGELOG.md)" > CHANGELOG.md ``` to update the changelog Categorize the changes into Breaking Changes (requires a major version) New Features (minor version) Fixes (fix version) Maintenance (which in general should not be mentioned in `CHANGELOG.md` as they have no user impact) Update GOMEGAVERSION in `gomegadsl.go` Commit, push, and release: ``` git commit -m "vM.m.p" git push gh release create "vM.m.p" git fetch --tags origin master ```
Project: Istio (Orchestration & Management / Service Mesh)
File: install-OpenShift.md

Note: Be aware of the when installing Istio. To install with Helm, you must first create the namespace that you wish to install in if the namespace does not exist already. The default namespace used is `istio-system` and can be created as follows: ```console kubectl create namespace istio-system ``` Istio's helm charts come with a common `openshift` profile that can be used during installation. The installation process using the Helm charts is as follows: 1) `base` chart creates cluster-wide CRDs, cluster bindings and cluster resources. It is possible to change the namespace from `istio-system` but it is not recommended. ```console helm install istio-base -n istio-system manifests/charts/base --set profile=openshift ``` 2) `istio-cni` chart installs the CNI plugin. This should be installed after the `base` chart and prior to `istiod` chart. Need to add `--set pilot.cni.enabled=true` to the `istiod` install to enable its usage. ```console helm install istio-cni -n kube-system manifests/charts/istio-cni --set profile=openshift ``` 3) `istio-control/istio-discovery` chart installs a revision of istiod. ```console helm install -n istio-system istiod manifests/charts/istio-control/istio-discovery --set profile=openshift ``` 4) `gateways` charts install a load balancer with `ingress` and `egress`. Ingress secrets and access should be separated from the control plane. ```console helm install -n istio-system istio-ingress manifests/charts/gateways/istio-ingress --set profile=openshift ``` Egress secrets and access should be separated from the control plane. ```console helm install -n istio-system istio-egress manifests/charts/gateways/istio-egress --set profile=openshift ```
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: presentations.md

title: Apache Mesos - Video and Slides of Mesos Presentations layout: documentation (Listed in reverse chronological order) Sunil Shah, Kyle Kelly, and Timmy Zhu Presented November 1, 2017 at + + + Joe Stein Presented February 26, 2015 at Paco Nathan Presented April 15, 2014 at Eugen Cepoi Presented April 9, 2014 at Paris Hadoop User Group Tom Petr Presented April 3rd, 2014 at @TwitterOSS #conf Benjamin Hindman Presented March 25th, 2014 at Bill Farner Presented March 25th, 2014 at Christina Delimitrou Presented April 3rd, 2014 at @TwitterOSS #conf Paco Nathan Presented February 13th, 2014 at Abhishek Parolkar Presented November 14th, 2013 at Benjamin Hindman Presented August 29th, 2013 at Vinod Kone Presented July 25, 2013 at Brenden Matthews Presented July 25, 2013 at Benjamin Hindman Presented August 20, 2013 at Florian Leibert Presented August 20, 2013 at Benjamin Hindman Presented September 6, 2012 at Benjamin Hindman Presented August 22, 2012 at Matei Zaharia Presented March 2011 at Benjamin Hindman Presented November 8, 2010 at Matei Zaharia Presented Summer 2010 at Karl Whitford Packt (November 2017) Manuj Aggarwal Packt (January 2018)
Project: Aeraki Mesh (Orchestration & Management / Service Mesh)
File: PULL_REQUEST_TEMPLATE.md

<! Why is this change required? What problem does it solve? --> <! If it fixes an open issue, please link to the issue here. --> <!-- Please follow the Requirements: Use Draft if the PR is not ready to be reviewed Test cases is recommended for the feat/fix PR Doc is required for the feat PR Use a new commit to resolve review instead of `push -f` Use "request review" to notify the reviewer once you have resolved the review --> [ ] Did you explain what problem does this PR solve? Or what new features have been added? [ ] Have you added related test cases? [ ] Have you modified the related document? [ ] Is this PR backward compatible?
Project: Gravitee.io (Orchestration & Management / API Gateway)
File: management-api-policy-studio-resources.md

Resources are link to the API lifecycle. They are initialized when the API is starting and released when API is stopped. Resources are used via the API policies to enhance API behavior. Differents resource types are available : Cache Used to store re-usable data to avoid subsequent calls. OAuth 2.0 Used to introspect an access_token via an external OAuth 2.0 authorization server. The (+) button let you create a new resource.
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_completion.md

title: "glooctl completion" weight: 5 generate auto completion for your shell Output shell completion code for the specified shell (bash or zsh). The shell code must be evaluated to provide interactive completion of glooctl commands. This can be done by sourcing it from the .bash_profile. Note for zsh users: [1] zsh completions are only supported in versions of zsh >= 5.2 ``` glooctl completion SHELL [flags] ``` ``` brew install bash-completion brew install bash-completion@2 glooctl completion bash > $(brew --prefix)/etc/bash_completion.d/glooctl source <(glooctl completion bash) glooctl completion bash > ~/.glooctl/completion.bash.inc printf " source '$HOME/.glooctl/completion.bash.inc' " >> $HOME/.bash_profile source $HOME/.bash_profile source <(glooctl completion zsh) glooctl completion zsh > "${fpath[1]}/_glooctl" ``` ``` -h, --help help for completion ``` ``` -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: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: engineering-principles-and-practices.md

title: Apache Mesos - Engineering Principles And Practices layout: documentation This document is an attempt to capture a shared set of values for the project. Many companies rely on Mesos as a foundational layer of their software infrastructure and it is imperative that we ship robust, high quality code. We aim to foster a culture where we can trust and rely upon the work of the community. The following are some of the aspirational principles and practices that guide us: We value craftsmanship: code should be easy to read and understand, should be written with high attention to detail, and should be consistent in its style. Code is written for humans to read and maintain! We value resiliency: our system must be highly-available, stable, and backwards-compatible. We must consider the implications of failures. We value accountability: we own and support our software, and are accountable for improving it, fixing issues, and learning from our mistakes. We value design and code review: review helps us maintain a high quality system architecture and high quality code, it also helps us mentor new contributors, learn to collaborate more effectively, and reduce the amount of mistakes. We value automated testing: automated testing allows us to iterate and refactor in our large codebase, while verifying correctness and preventing regression. We value benchmarking: benchmarking allows us to identify the right locations to target performance improvements. It also allows us to iterate and refactor in our large codebase, while observing the performance implications.
Project: Gloo (Orchestration & Management / API Gateway)
File: versioning.proto.sk.md

title: "versioning.proto" weight: 5 <!-- Code generated by solo-kit. DO NOT EDIT. --> ```yaml "previousMessageType": string ``` | Field | Type | Description | | -- | - | -- | | `previousMessageType` | `string` | Track the previous message type. E.g. this message might be xds.foo.v3alpha.Foo and it was previously xds.bar.v2.Bar. This information is consumed by UDPA via proto descriptors. | <!-- 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: go-zero (Orchestration & Management / Remote Procedure Call)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: '' assignees: '' Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Additional context Add any other context or screenshots about the feature request here.