cwielenb/CNCF-Dataset huggingface dataset:
Project: CoreDNS (Orchestration & Management / Coordination & Service Discovery)
File: coredns-1.6.8.md

+++ title = "CoreDNS-1.6.8 Release" description = "CoreDNS-1.6.8 Release Notes." tags = ["Release", "1.6.8", "Notes"] release = "1.6.8" date = 2020-03-24T10:00:00+00:00 author = "coredns" +++ The CoreDNS team has released . 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: 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: Apache bRPC (Orchestration & Management / Remote Procedure Call)
File: CHANGES.md

<!-- --> Add DISCLAIMER-WIP as license issues are not all resolved Fix many license related issues Ignore flow control in h2 when sending first request Add flame graph view for profiling builtin service Fix bug that avglatency maybe zero in lalb Fix bug that logging namespace conflicts with others Add gdbbthreadstack.py to read bthread stack Adapt to Arm64 Support redis server protocol Enable circuit breaker for backup request Support zone for bilibili discovery naming service when fetching server nodes Add brpc revision in release version Health (of a connection) can be checked at rpc-level Fix SSL-related compilation issues on Mac Support SSL-replacement lib MesaLink Support consistent hashing with ketama algo. bvar variables can be exported for prometheus services String[Multi]Splitter supports '\0' as separator Support for bilibili discovery service Improved CircuitBreaker grpc impl. supports timeout h2c/grpc are supported now, h2(encrypted) is not included. thrift support. Mac build support Extend ConcurrencyLimiter to control max-concurrency dynamically and an "auto" CL is supported by default CircuitBreaker support to isolate abnormal servers more effectively Contains major features of brpc, OK for production usages. No h2/h2c/rdma support, Mac/Windows ports are not ready yet.
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2019-01-28-mesos-1-7-1-released.md

layout: post title: "Apache Mesos 1.7.1 Released" published: true post_author: display_name: Chun-Hung Hsiao & Gastn Kleiman gravatar: 9447267537939b034faa02cbe08fef20 twitter: chhsia0 tags: Release Apache Mesos 1.7.1 is now available for . As we continue to focus on performance, the community can get access to the latest performance improvements in this release. The has been improved in this release as well. Last but not least, this release includes 38 bug fixes to 1.7.0. If you are considering using Mesos 1.7, it is recommended to use 1.7.1. Specifically, the following critical bugs are resolved in this release: - Health checks launching nested containers while a container is being destroyed lead to unkillable tasks. - SLRP does not clean up plugin containers after it is removed. - Docker Containerizer 'usage' call might be expensive if mount table is big. - SLRP gets a stale checkpoint after system crash. - Docker containerizer actor can get backlogged with large number of containers. - URI disk profile adaptor could deadlock. - Some master endpoints do not handle failed authorization properly. - Container stuck at ISOLATING state due to libevent poll never returns. - Executor to framework message crashes master if framework has not re-registered. - Master does not respect authorization result for `CREATEDISK` and `DESTROYDISK`. - Master may skip processing authorization results for `LAUNCH_GROUP`. - Mesos executor fails to terminate and gets stuck after agent host reboot. - IOswitchboard cleanup could get stuck due to FD leak from a race. - Official 1.7.0 tarball can't be built on Ubuntu 16.04 LTS. And this release includes the following critical improvements: - "Make the Resources wrapper ""copy-on-write"" to improve performance." - Improve sorting performance in the DRF sorter. - Avoid dirtying the DRF sorter when allocating resources. - Allow optional `profile` to be specified in `CREATE_DISK` offer operation. - Create cgoup recursively to workaround systemd deleting cgroups_root. - Add an optional `vendor` field in `Resource.DiskInfo.Source`. Full release notes are available in the release . Rolling upgrades from a Mesos 1.7.0 cluster to Mesos 1.7.1 are straightforward. However, if your framework is consuming the , the language binding used by the framework should be updated. For detailed information on upgrading to Mesos 1.7.1 from other versions, please refer to the . 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 20 contributors who made 1.7.1 possible: Alexander Rojas, Alexander Rukletsov, Andrei Budnik, Benjamin Bannier, Benjamin Mahler, Benno Evers, Chun-Hung Hsiao, Deepak Goel, Gastn Kleiman, Gilbert Song, Greg Mann, James Peach, Jie Yu, Joseph Wu, Kevin Klues, Meng Zhu, Qian Zhang, Till Toenshoff, Vinod Kone, Fei Long
Project: Skipper (Orchestration & Management / Service Proxy)
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. Describe the solution you would like A clear and concise description of what you want to happen. Describe alternatives you've considered (optional) A clear and concise description of any alternative solutions or features you've considered. Additional context (optional) Add any other context or screenshots about the feature request here. Would you like to work on it? Yes/No/Yes, but no time
Project: BFE (Orchestration & Management / Service Proxy)
File: rewrite.md

The service API '/service' is upgraded to '/v1/service' during evolution. To avoid from breaking existing clients, bfe rewrites requests with path '/service' and then forward to the backend service. Modify example configurations (conf/) as the following steps: Step 1. Modify conf/bfe.conf and enable mod_rewrite ```ini Modules = modrewrite # enable modrewrite ``` Step 2. Modify conf/modrewrite/modrewrite.conf and set the rule configuration file ```ini [basic] DataPath = mod_rewrite/rewrite.data ``` Step 3. Modify rewrite rules configuration ```json { "Version": "init version", "Config": { "example_product": [{ "Cond": "reqpathprefix_in(\"/service\", false)", "Actions": [{ "Cmd": "PATHPREFIXADD", "Params": [ "/v1/" ] }], "Last": true }] } } ``` Step 4. Verify configured rules ```bash curl -H "host: example.org" "http://127.1:8080/service" ``` The final path of request received by service 'clusterdemodynamic' is 'v1/service'.
Project: k8gb (Orchestration & Management / Coordination & Service Discovery)
File: ingress_annotations.md

Instead of direct Gslb resource creation there is ability to enable global load balancing by setting annotations on the standard Ingress objects. | Annotation | Description | Type | | - | - | | | k8gb.io/strategy | Glsb strategy | "`roundRobin`" \| "`failover`" | | k8gb.io/primary-geotag | Arbitrary geotag | string (e.g. "`eu`") |
Project: k8gb (Orchestration & Management / Coordination & Service Discovery)
File: deploy_route53.md

Here we provide an example of k8gb deployment in AWS context with Route53 as edgeDNS provider. Two EKS clusters in `eu-west-1` and `us-east-1`. Terraform code for cluster reference setup can be found Feel free to reuse this code fully or partially and adapt for your existing scenario custom configuration like Existing VPC names Existing Public/private subnets tags EKS custom tags IRSA(IAM Roles for Service Accounts) role reference ```sh kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v0.40.2/deploy/static/provider/aws/deploy.yaml ``` Example helm configuration files can be found Modify them to reflect your `dnsZone`, `edgeDNSZone`, valid `hostedZoneID` and `irsaRole` ARN. Clone k8gb repository and use `helm` with custom values ```sh git clone https://github.com/k8gb-io/k8gb.git cd k8gb helm repo add k8gb https://www.k8gb.io helm repo update helm -n k8gb upgrade -i k8gb k8gb/k8gb --create-namespace -f ./docs/examples/route53/k8gb/k8gb-cluster-eu-west-1.yaml helm -n k8gb upgrade -i k8gb k8gb/k8gb --create-namespace -f ./docs/examples/route53/k8gb/k8gb-cluster-us-east-1.yaml ``` Note: here and for all occurrences below whenever we speak about application to each cluster, we assume that you switch kubectl context and apply the same command to all clusters. Deploy test application to each* cluster. ```sh make deploy-test-apps ``` Modify sample to reflect desired `.spec.ingress.rules[0].host` FQDN Apply Gslb CR to each* cluster ```sh kubectl apply -f ./docs/examples/route53/k8gb/gslb-failover.yaml ``` Check Gslb status. ```sh kubectl -n test-gslb get gslb test-gslb-failover -o yaml ``` Check route53 entries. ```sh aws route53 list-resource-record-sets --hosted-zone-id $YOURHOSTEDZONE_ID ``` You should see that `gslb-ns-$dnsZone-$geotag` NS and glue A records were created to automatically configure DNS zone delegation. Check test application availability. ```sh curl -s failover.test.k8gb.io| grep message "message": "eu-west-1", ``` Replace `failover.test.k8gb.io` with the domain you specified in Gslb spec. Notice that traffic was routed to `eu-west-1`. Emulate the failure in `eu-west-1` ```sh kubectl -n test-gslb scale deploy frontend-podinfo --replicas=0 ``` Observe Gslb status change. ```sh kubectl -n test-gslb get gslb test-gslb-failover -o yaml | grep status -A6 status: geoTag: us-east-1 healthyRecords: failover.test.k8gb.io: 35.168.91.100 serviceHealth: failover.test.k8gb.io: Healthy ``` IP in healthyRecords should change to the IP address of NLB in `us-east-1` Check failover to `us-east-1` ```sh curl -s failover.test.k8gb.io| grep message "message": "us-east-1", ``` Notice that traffic is properly failed over to `us-east-1` Experiment Now you can scale `eu-west-1` back and observe that traffic is routed back to the primary cluster. In addition, you can test `roundRobin` load balancing strategy, which is spreading the traffic over the clusters in active-active mode.
Project: KEDA (Orchestration & Management / Scheduling & Orchestration)
File: PULL_REQUEST_TEMPLATE.md

<!-- Thank you for contributing! Read more about how you can contribute in our contribution guide: https://github.com/kedacore/keda/blob/main/CONTRIBUTING.md --> Provide a description of what has been changed [ ] Tests have been added ) (if applicable, ie. when deployment manifests are modified) ) (if applicable) ) <!-- Make sure to link the related issue for this change If it requires multiple PRs and/or a PR on another repo as well, please use "Relates to" instead. --> Fixes # <!-- Make sure to link the related PRs for changes such as documentation & Helm charts --> Relates to #
Project: Contour (Orchestration & Management / Service Proxy)
File: redeploy-envoy.md

The Envoy process, the data path component of Contour, at times needs to be re-deployed. This could be due to an upgrade, a change in configuration, or a node-failure forcing a redeployment. When implementing this roll out, the following steps should be taken: Stop Envoy from accepting new connections Start draining existing connections in Envoy by sending a `POST` request to `/healthcheck/fail` endpoint Wait for connections to drain before allowing Kubernetes to `SIGTERM` the pod Contour implements a new `envoy` sub-command which has a `shutdown-manager` whose job is to manage a single Envoy instances lifecycle for Kubernetes. The `shutdown-manager` runs as a new container alongside the Envoy container in the same pod. It exposes two HTTP endpoints which are used for `livenessProbe` as well as to handle the Kubernetes `preStop` event hook. livenessProbe: This is used to validate the shutdown manager is still running properly. If requests to `/healthz` fail, the container will be restarted. preStop: This is used to keep the container running while waiting for Envoy to drain connections. The `/shutdown` endpoint blocks until the connections are drained. ```yaml name: shutdown-manager command: /bin/contour args: envoy shutdown-manager image: docker.io/projectcontour/contour:main imagePullPolicy: Always lifecycle: preStop: exec: command: /bin/contour envoy shutdown livenessProbe: httpGet: path: /healthz port: 8090 initialDelaySeconds: 3 periodSeconds: 10 ``` The Envoy container also has some configuration to implement the shutdown manager. First the `preStop` hook is configured to use the `/shutdown` endpoint which blocks the Envoy container from exiting. Finally, the pod's `terminationGracePeriodSeconds` is customized to extend the time in which Kubernetes will allow the pod to be in the `Terminating` state. The termination grace period defines an upper bound for long-lived sessions. If during shutdown, the connections aren't drained to the configured amount, the `terminationGracePeriodSeconds` will send a `SIGTERM` to the pod killing it. !{: .center-image } The shutdown manager has a set of arguments that can be passed to change how it behaves: check-interval: Time to poll Envoy for open connections. Type: duration (Default 5s) check-delay: Time wait before polling Envoy for open connections. Type: duration (Default 60s) min-open-connections: Min number of open connections when polling Envoy. Type: integer (Default 0) serve-port: Port to serve the http server on. Type: integer (Default 8090)
Project: Contour (Orchestration & Management / Service Proxy)
File: CHANGELOG-v1.23.3.md

We are delighted to present version v1.23.3 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters. A big thank you to everyone who contributed to the release. Update to Envoy v1.24.2. See the for more information about the content of the release. Update to Go v1.19.5. See the for more information about the content of the release. For a fresh install of Contour, consult the . To upgrade an existing Contour installation, please consult the . Contour v1.23.3 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 .
Project: MetalLB (Orchestration & Management / Service Proxy)
File: icon.en.md

+++ aliases = "/cont/icons" description = "Nice icons for your page" title = "Icon" +++ The `icon` shortcode displays icons using the library. {{% icon exclamation-triangle %}} {{% icon angle-double-up %}} {{% icon skull-crossbones %}} While the examples are using shortcodes with positional parameter you are free to also call this shortcode from your own partials. {{< tabs groupid="shortcode-parameter">}} {{% tab title="shortcode" %}} ````go {{%/ icon icon="exclamation-triangle" /%}} {{%/ icon icon="angle-double-up" /%}} {{%/ icon icon="skull-crossbones" /%}} ```` {{% /tab %}} {{% tab title="shortcode (positional)" %}} ````go {{%/ icon exclamation-triangle /%}} {{%/ icon angle-double-up /%}} {{%/ icon skull-crossbones /%}} ```` {{% /tab %}} {{% tab title="partial" %}} ````go {{ partial "shortcodes/icon.html" (dict "page" . "icon" "exclamation-triangle" )}} {{ partial "shortcodes/icon.html" (dict "page" . "icon" "angle-double-up" )}} {{ partial "shortcodes/icon.html" (dict "page" . "icon" "skull-crossbones" )}} ```` {{% /tab %}} {{< /tabs >}} | Name | Position | Default | Notes | |--|-|--|-| | icon | 1 | &lt;empty&gt; | to be displayed. It will be displayed in the text color of its according context. | Browse through the available icons in the . Notice that the free filter is enabled, as only the free icons are available by default. Once on the Font Awesome page for a specific icon, for example the page for the , copy the icon name and paste into the Markdown content. Font Awesome provides many ways to modify the icon Change color (by default the icon will inherit the parent color) Increase or decrease size Rotate Combine with other icons Check the full documentation on for more. ````go Built with {{%/ icon heart /%}} by Relearn and Hugo ```` Built with {{% icon heart %}} by Relearn and Hugo While the shortcode simplifies using standard icons, the icon customization and other advanced features of the Font Awesome library require you to use HTML directly. Paste the `<i>` HTML into markup, and Font Awesome will load the relevant icon. ````html Built with <i class="fas fa-heart"></i> by Relearn and Hugo ```` Built with <i class="fas fa-heart"></i> by Relearn and Hugo To use these native HTML elements in your Markdown, add this in your `hugo.toml`: ````toml [markup.goldmark.renderer] unsafe = true ````
Project: BFE (Orchestration & Management / Service Proxy)
File: install_from_source.md

golang 1.17+ git 2.0+ glibc-static 2.17+ ```bash $ git clone https://github.com/bfenetworks/bfe ``` Execute the following command to build bfe: ```bash $ cd bfe $ make ``` !!! tip If you encounter an error such as "https fetch: Get ... connect: connection timed out", please set the GOPROXY and try again. See Execute the following command to run tests: ```bash $ make test ``` Executable object file location: ```bash $ file output/bin/bfe output/bin/bfe: ELF 64-bit LSB executable, ... ``` Run BFE with example configuration files: ```bash $ cd output/bin/ $ ./bfe -c ../conf -l ../log ``` Get familiar with Get started with
Project: Knative (Orchestration & Management / Scheduling & Orchestration)
File: SECURITY.md

Join the [kubernetes-security-announce] group for security and vulnerability announcements. You can also subscribe to an RSS feed of the above using . Instructions for reporting a vulnerability can be found on the [Kubernetes Security and Disclosure Information] page. Information about supported Kubernetes versions can be found on the [Kubernetes version and version skew support policy] page on the Kubernetes website.
Project: Open Cluster Management (Orchestration & Management / Scheduling & Orchestration)
File: CHANGELOG-v0.10.md

Add evictionStartTime for appliedmanifestwork. ( ) Add spread policy ( ) Introduce a PlaceWork API ( ) Add agentID in AppliedManifestWork ( ) add merge strategy for cma supportconfigs ( ) Add work configuration field for klusterlet ( ) Upgrade github action ( ) add work helpers ( ) Put all common labels/annotations in api repo ( ) add constant annotaitons for addon ( ) Fix: the plural of placemanifestwork is not correct ( ) make the workbuilder.ManifestWorkSpecEqual accessible ( ) N/A
Project: DolphinScheduler (Orchestration & Management / Scheduling & Orchestration)
File: project-list.md

This page describes details regarding Project screen in Apache DolphinScheduler. Here, you will see all the functions which can be handled in this screen. The following table explains commonly used terms in Apache DolphinScheduler: | Glossary | description | ||| | DAG | Tasks in a workflow are assembled in form of Directed Acyclic Graph (DAG). A topological traversal is performed from nodes with zero degrees of entry until there are no subsequent nodes. | | Workflow Definition | Visualization formed by dragging task nodes and establishing task node associations (DAG). | | Workflow Instance | Instantiation of the workflow definition, which can be generated by manual start or scheduled scheduling. Each time the process definition runs, a workflow instance is generated. | | Workflow Relation | Shows dynamic status of all the workflows in a project. | | Task | Task is a discrete action in a Workflow. Apache DolphinScheduler supports SHELL, SQL, SUBPROCESS (sub-process), PROCEDURE, MR, SPARK, PYTHON, DEPENDENT ( depends), and plans to support dynamic plug-in expansion, (SUBPROCESS). It is also a separate process definition that can be started and executed separately. | | Task Instance | Instantiation of the task node in the process definition, which identifies the specific task execution status. | On the project screen, list of all the existing projects along with details like name, owner, workflow definition, process instance, create and update time. This page also facilitates operations like create, edit, and delete project. Click `Project Management` to enter the project management page, click the `Create Project` button, enter the project name, project description, and click "Submit" to create a new project. Click the project name link on the project management page to enter the project home page, as shown in the figure below, the project home page contains the task status statistics, process status statistics, and workflow definition statistics of the project. The introduction for those metrics: Task status statistics: Within the specified time range, count the number of task instances status as successful submission, running, ready to pause, pause, ready to stop, stop, failure, success, need fault tolerance, kill and waiting threads Process status statistics: Within the specified time range, count the number of workflow instances status as submission success, running, ready to pause, pause, ready to stop, stop, failure, success, need fault tolerance, kill and waiting threads Workflow definition statistics: Count the workflow definitions created by this user and granted by the administrator