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

| Datasource | Description | |-|--| | Datasource | Select OCEANBASE. | | Datasource name | Enter the name of the DataSource. | | Description | Enter a description of the DataSource. | | IP/Host name | Enter the OceanBase service IP. | | Port | Enter the OceanBase service port. | | Username | Set the username for OceanBase connection. | | Password | Set the password for OceanBase connection. | | Database name | Enter the database name of the OceanBase connection. | | Compatible mode | Set the compatible mode of the OceanBase connection. | | Jdbc connection parameters | Parameter settings for OceanBase connection, in JSON format. | No, you need to import the OceanBase jdbc driver first, refer to the section example in `DataSource Center` section. The compatible mode of the datasource can be 'mysql' or 'oracle', if you only use OceanBase with 'mysql' mode, you can also treat OceanBase as MySQL and manage the datasource referring to
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: performance-profiling.md

title: Apache Mesos - Performance Profiling layout: documentation This document over time will be home to various guides on how to use various profiling tools to do performance analysis of Mesos. is a visualization tool for exploring different time ranges as . In order to use the tool, you first need to obtain stack traces, here's how to obtain a 60 second recording of the mesos master process at 100 hertz using Linux perf: ``` $ sudo perf record --freq=100 --no-inherit --call-graph dwarf -p <mesos-master-pid> -- sleep 60 $ sudo perf script --header | c++filt > mesos-master.stacks $ gzip mesos-master.stacks ``` If you'd like to solicit help in analyzing the performance data, upload the `mesos-master.stacks.gz` to a publicly accessible location and file with `dev@mesos.apache.org` for analysis, or send the file over to the #performance channel. Alternatively, to do the analysis yourself, place mesos-master.stacks into the `examples` folder of a flamescope git checkout.
Project: Contour (Orchestration & Management / Service Proxy)
File: CHANGELOG-v1.24.4.md

We are delighted to present version v1.24.4 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters. Fix for bug in HTTPProxy duplicate include detection that caused memory usage spikes when root HTTPProxies with a large number of includes using header match conditions are present. Update to Envoy v1.25.6. 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.24.4 is tested against Kubernetes 1.24 through 1.26. 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: Gloo (Orchestration & Management / API Gateway)
File: glooctl_create.md

title: "glooctl create" weight: 5 Create a Gloo resource Gloo resources be created from files (including stdin) ``` glooctl create [flags] ``` ``` --dry-run print kubernetes-formatted yaml rather than creating or updating a resource -f, --file string file to be read or written to -h, --help help for create --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) ``` ``` -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 - Create an Auth Config - Create a secret - Create an Upstream - Create an Upstream Group - Create a Virtual Service
Project: Kusk Gateway (Orchestration & Management / API Gateway)
File: cache.md

The HTTP Cache stores a response associated with a request and reuses the stored response for subsequent requests. Caches reduce latency and network traffic, as the response is directly returned from the gateway. Kusk Gateway implements all the complexity of HTTP caching semantics. For more information, read . Kusk makes caching easy to configure using a simple OpenAPI extension: ```yaml openapi: 3.0.0 info: title: simple-api version: 0.1.0 x-kusk: cache: enabled: true max_age: 60 .. ``` The example above caches responses to HTTP GET requests for 60 seconds. You can also specify different caching settings for a specific operation or path. The following example shows rate limiting configuration for a specific operation: ```yaml ... paths: /hello: get: operationId: getHello x-kusk: cache: enabled: true max_age: 60 .. ``` See all available Caching configuration options in the .
Project: Hango (Orchestration & Management / API Gateway)
File: Update Gateway.md

```shell curl -v -H "Content-Type:application/json" -d '{ "Gwid":1, "ApiPlaneAddr": "http://api-plane-sm.qa-ci.service.163.org", "Description": "Hango gateway test.", "GatewayConfigInfo": { "AuthAddr": "", "EnvId": "prod", "AuditDatasourceSwitch": "", "AuditDbConfig": "" }, "GwAddr": "http://gateway-proxy.qa-ci.service.163.org", "GwClusterName": "prod-gateway", "GwName": "hangoenvoygateway", "GwType": "envoy", "ProjectIds": [ 0, 1, 3 ] }' http://apigw-gportal-envoy.qa-ci.service.163.org/gdashboard?Action=UpdateGateway&Version=2018-08-09 ```
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_delete_upstreamgroup.md

title: "glooctl delete upstreamgroup" weight: 5 delete an upstream group usage: glooctl delete upstreamgroup [NAME] [--namespace=namespace] ``` glooctl delete upstreamgroup [flags] ``` ``` -h, --help help for upstreamgroup ``` ``` -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) ``` - Delete a Gloo resource
Project: Karmada (Orchestration & Management / Scheduling & Orchestration)
File: resource_deletion_protection_test.md

| Test Case | E2E Describe Text | Comments | |-|-|| | Test the basic protection for deployment | Delete the protected deployment | | | Test the basic protection for namespace | Delete the protected namespace | | | Test delete the unprotected namespace that contains a protected Deployment | Delete the no protected namespace, the deployment is protected | | | Test delete the namespace after the protection has been removed | Delete the namespace after the protection has been removed | |
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: deploy-scripts.md

title: Apache Mesos - Deployment Scripts layout: documentation Mesos includes a set of scripts in `[install-prefix]/sbin` that can be used to deploy it on a cluster. To use these scripts, you need to create two configuration files: `[install-prefix]/var/mesos/deploy/masters`, which should list the hostname(s) of the node(s) you want to be your masters (one per line), and `[install-prefix]/var/mesos/deploy/agents`, which should contain a list of hostnames for your agents (one per line). You can then start a cluster with `[install-prefix]/sbin/mesos-start-cluster.sh` and stop it with `[install-prefix]/sbin/mesos-stop-cluster.sh`. It is also possible to set environment variables, ulimits, etc that will affect the master and agent by editing `[install-prefix]/var/mesos/deploy/mesos-deploy-env.sh`. One particularly useful setting is `LIBPROCESS_IP`, which tells the master and agent binaries which IP address to bind to; in some installations, the default interface that the hostname resolves to is not the machine's external IP address, so you can set the right IP through this variable. Besides the common environment variables of master and agent configured in `[install-prefix/var/mesos/deploy/mesos-deploy-env.sh`, it is also possible to set master specific environment variables in `[install-prefix]/var/mesos/deploy/mesos-master-env.sh`, agent specific environment variables in `[install-prefix]/var/mesos/deploy/mesos-agent-env.sh`. Finally, the deploy scripts do not use ZooKeeper by default. If you want to configure Mesos to use ZooKeeper to coordinate multiple master nodes, please see the documentation for details. The deploy scripts assume that Mesos is located in the same directory on all nodes. If you want to enable multiple Unix users to submit to the same cluster, you need to run the Mesos agents as root (or possibly set the right attributes on the `mesos-agent` binary). Otherwise, they will fail to `setuid`.
Project: Tengine (Orchestration & Management / Service Proxy)
File: ngx_log_pipe.md

Syntax: pipe:rollback [logpath] interval=[interval] baknum=[baknum] maxsize=[maxsize] adjust=[adjust] Default: none Context: http, server, location log pipe module write log use special log proccess, it may not block worker, worker communicate with log proccess use pipe, rollback depend on log pipe module, it support log file auto rollback by tengine self. it support rollback by time and file size, also can configure backup file number. log rollback module will rename log file to backup filename, then reopen the log file and write again rollback configurge is built-in accesslog and errorlog ``` access_log "pipe:rollback [logpath] interval=[interval] baknum=[baknum] maxsize=[maxsize] adjust=[adjust]" proxyformat; error_log "pipe:rollback [logpath] interval=[interval] baknum=[baknum] maxsize=[maxsize] adjust=[adjust]" info; ``` logpath: log output file path and name intervallog rollback interval, default 0 (never) baknumbackup file number, default 1 (keep 1 backup file) maxsizelog file max size, default 0 (never) adjust: delay random rollback time when rollback by interval, to avoid all server focus on rollback default 60 (60s) example ``` errorlog "pipe:rollback logs/errorlog interval=60m baknum=5 maxsize=2048M" info; http { logformat main '$remoteaddr - $remoteuser [$timelocal] "$request" ' '$status $bodybytessent "$http_referer" ' '"$httpuseragent" "$httpxforwarded_for"'; accesslog "pipe:rollback logs/accesslog interval=1h baknum=5 maxsize=2G" main; } ```
Project: BFE (Orchestration & Management / Service Proxy)
File: cookie.md

Description: Judge if cookie key matches configured patterns Parameters | Parameter | Description | | | - | | key_list | String<br>a list of cookie keys which are concatenated using &#124; | Example ```go reqcookiekey_in("uid|cid|uss") ``` Description: Judge if value of cookie key matches configured patterns Parameters | Parameter | Description | | | - | | key | String<br>cookie key | | value_list | String<br>a list of hash values which are concatenated using &#124; | | case_insensitive | Boolean<br>case insensitive | Example ```go reqcookievalue_in("deviceid", "testid", true) ``` Description: Judge if value prefix of cookie key matches configured patterns Parameters | Parameter | Description | | | - | | key | String<br>cookie key | | valueprefixlist | String<br>a list of values which are concatenated using &#124; | | case_insensitive | Boolean<br>case insensitive | Example ```go reqcookievalueprefixin("deviceid", "x", true) ``` Description: Judge if value suffix of cookie key matches configured patterns Parameters | Parameter | Description | | | - | | key | String<br>cookie key | | valuesuffixlist | String<br>a list of values which are concatenated using &#124; | | case_insensitive | Boolean<br>case insensitive | Example ```go reqcookievaluesuffixin("deviceid", "1", true) ``` Description: Judge if hash value of specified cookie matches configured patterns(value range: 09999) Parameters | Parameter | Description | | | - | | key | String<br>cookie key | | value_list | String<br>a list of hash values which are concatenated using &#124; | | case_insensitive | Boolean<br>case insensitive | Example ```go reqcookievaluehashin("uid", "100", true) ``` Description: Judge if value of cookie key contains configured patterns Parameters | Parameter | Description | | | - | | key | String<br>cookie key | | value | String<br>a string | | case_insensitive | Boolean<br>case insensitive | Example ```go reqcookievalue_contain("deviceid", "test", true) ```
Project: Koordinator (Orchestration & Management / Scheduling & Orchestration)
File: koordlet-runtime-hooks.md

* * * * * * Runtime Hooks acts as the back-end server of Runtime Hook Manager. Runtime Hook Manager is a CRI Proxy, intercepting the CRI request, calling the back-end server to inject policies, such as setting resource isolation parameters by pod priorities, and applying resource allocation policies. Runtime Hooks provides a framework to maintain different kinds of policies, and provides flexible extension points during the lifecycle of containers. Detailed design of runtime hook module. Developing reference for runtime hook plugin. Usage manual for Koordlet users. `Hooks` module provides a framework for plugins to inject resource parameters for pods and containers. For each new implemented plugin, there are two interfaces need to be implemented: register to `Rule` module for policy configuration management. register to `Hooks` framework for `gRPC Server` calling at corresponding injection stage. The `gRPC Server` provides the service for runtime injection, which implements the protocol defined by Runtime Manager. After registered the service endpoint to Runtime Manager, the gRPC Server module will receive requests of different injection stage from Runtime Manager, such as `PreRunPodSandboxHook` and `PreStartContainerHook`. For each request, the gRPC Server will call corresponding plugins to do the injections, fill the protocol parameters and response to Runtime Manager. The `Rule` module is responsible for configuration management, parsing the `NodeSLO` changes and update the local cache of injection policies. For each policy update, the `Rule` module also provides a callback procedure to refresh the parameters of pods and containers. Runtime Hooks supports two working modes for different scenarios: `Proxy` and `Standalone`. `Proxy` is the recommended working mode for Runtime Hooks, which acts as a proxy layer between Kubelet and Runtime Service(e.g. Containerd, Docker). With Proxy running mode, users need to change the cri endpoint config of Kubelet to `Koordinator Runtime Manager`. For each cri request, `Runtime Manager` will intercept and call `Runtime Hooks` to execute the injection synchronously. `Proxy` running mode has a better performance which can guarantee the related parameters set timely and appropriately. `Standalone` working mode simplifies the runtime configuration and architecture. `Runtime Manager` is not needed in this working mode, so that `Runtime Hooks` works as an independent module. Without the proxy intercepts requests between Kubelet and Runtime, `Runtime Hooks` can only set related parameters asynchronously, which limits the using scenarios. Group Identity is a kernel feature implemented by Anolis OS, which allows user to configure identities for CPU cgroups to prioritize tasks in the cgroups. In the mechanism of Koordlet QoS Management, `LS` pods will get higher identity than `BE` pods, which is implemented as a plugin in `Runtime Hooks` by setting the cgroup parameters at `PreRunPodSandboxHook` stage.
Project: Kusk Gateway (Orchestration & Management / API Gateway)
File: kusk_upgrade.md

Upgrade kusk-gateway, envoy-fleet, api, and dashboard in a single command Upgrade kusk-gateway, envoy-fleet, api, and dashboard in a single command. $ kusk cluster upgrade Will upgrade kusk-gateway, a public (for your APIS) and private (for the kusk dashboard and api) envoy-fleet, api, and dashboard in the kusk-system namespace using helm. $ kusk cluster upgrade --name=my-release --namespace=my-namespace Will upgrade a helm release named with --name in the namespace specified by --namespace. $ kusk cluster upgrade --install Will upgrade kusk-gateway, the dashboard, api, and envoy-fleets and install them if they are not installed ``` kusk cluster upgrade [flags] ``` ``` -h, --help help for upgrade --install install components if not installed --name string name of release to update (default "kusk-gateway") --namespace string namespace to upgrade in (default "kusk-system") ``` ``` --config string config file (default is $HOME/.kusk.yaml) ``` -
Project: CoreDNS (Orchestration & Management / Coordination & Service Discovery)
File: coredns-010.md

+++ title = "CoreDNS-010 Release" description = "CoreDNS-010 Release Notes." tags = ["Release", "010", "Notes"] draft = false release = "010" date = "2017-07-25T11:24:43-04:00" author = "coredns" +++ CoreDNS-010 has been ! CoreDNS is a DNS server that chains plugins, where each plugin implements a DNS feature. Release v010 is mostly a bugfix release, with one new plugin - dnstap. No changes. dnstap* is a new plugin that allows you to get dnstap information from CoreDNS. file* now handles multiple wildcard below each other correctly, and handles wildcards at the apex. hosts, and kubernetes* have been fixed to return success with no data in cases where records exist but not of the requested type. This fixes an issue with getting NXDOMAIN for the AAAA record even when the A record exists confusing some resolvers. Many updates to README files. The following people helped with getting this release done: Antoine Debuisson, Chris O'Haver, John Belamaric, Miek Gieben, Pat Moroney If you want to help, please check out one of the and start coding! For documentation and help, see our .
Project: BFE (Orchestration & Management / Service Proxy)
File: log_rotation.md

As time passes, the size of log files increases and occupies more and more disk space. BFE has a built-in feature of log file rotation which can automatically rotate log files, remove old ones and retain the recent ones. | Name | Path | Rotation Configuration | | -- | -- | | | Server Log | log/bfe.log | rotate log file at midnight; retain the recent 7 log files | | Access Log | log/access.log | | | TLS Key Log | log/key.log | |
Project: MetalLB (Orchestration & Management / Service Proxy)
File: weave.md

title: Issues with Weave weight: 20 Weave Net doesn't support `externalTrafficPolicy: Local` in its default configuration. If you switch a service to use the local traffic policy, Weave will blackhole the traffic. If you want to use the local traffic policy, you need to use Weave version 2.4.0 or later, and enable the `NOMASQLOCAL` flag, as described in [Weave's documentation](https://www.weave.works/docs/net/latest/kubernetes/kube-addon/#configuration-options). In version and later, the `NOMASQLOCAL` flag is enabled by default.
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2015-10-12-mesos-0-25-0-released.md

layout: post title: Apache Mesos 0.25.0 Released permalink: /blog/mesos-0-25-0-released/ published: true post_author: display_name: Niklas Q. Nielsen twitter: quarfot tags: Release The latest Mesos release, 0.25.0, is now available for . This release includes the following features and improvements: - Experimental support for maintenance primitives. Please refer to for more information. - Added master endpoints /reserve and /unreserve for dynamic reservations. Please refer to for more information. - Extended Module APIs to enable IP per container assignment, isolation and resolution. Please refer to for more information. Furthermore, 100+ bugs and improvements have made it into this release. For full release notes with all features and bug fixes, please refer to the . Rolling upgrades from a Mesos 0.24.x cluster to Mesos 0.25 are straightforward, but there are a few caveats/deprecations. Please refer to the for detailed information on upgrading to Mesos 0.25. 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 40 contributors who made 0.25.0 possible: Adam B, Aditi Dixit, Alex Clemmer, Alexander Rukletsov, Anand Mazumdar, Artem Harutyunyan, Ben Mahler, Bernd Mathiske, Chi Zhang, Cong Wang, Eijsermans, Eren Gve, Felix Abecassis, Greg Mann, Guangya Liu, Isabel Jimenez, James Peach, Jan Schlicht, Jiang Yan Xu, Jie Yu, Joerg Schad, Jojy Varghese, Joris Van Remoortere, Joseph Wu, Kapil Arya, Klaus Ma, Lily Chen, M Bauer, Marco Massenzio, Michael Park, Neil Conway, Niklas Nielsen, Paul Brett, Qian Zhang, Timothy Chen, Vaibhav Khanduja, Vinod Kone, Wojciech Sielski, Yong Qiao Wang and Haosdent Huang