cwielenb/CNCF-Dataset huggingface dataset:
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_proxy.md

title: "glooctl proxy" weight: 5 interact with proxy instances managed by Gloo these commands can be used to interact directly with the Proxies Gloo is managing. They are useful for interacting with and debugging the proxies (Envoy instances) directly. ``` -h, --help help for proxy --name string the name of the proxy service/deployment to use (default "gateway-proxy") -n, --namespace string namespace for reading or writing resources (default "gloo-system") --port string the name of the service port to connect to (default "http") ``` ``` -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 - print the socket address for a proxy - dump Envoy config from one of the proxy instances - dump Envoy logs from one of the proxy instancesNote: this will enable verbose logging on Envoy - dump Envoy config being served by the Gloo xDS server - stats for one of the proxy instances - print the http endpoint for a proxy
Project: Traefik (Orchestration & Management / API Gateway)
File: include-acme-multiple-domains-example.md

```yaml tab="Docker & Swarm" labels: traefik.http.routers.blog.rule=Host(`example.com`) && Path(`/blog`) traefik.http.routers.blog.tls=true traefik.http.routers.blog.tls.certresolver=myresolver traefik.http.routers.blog.tls.domains[0].main=example.org traefik.http.routers.blog.tls.domains[0].sans=*.example.org ``` ```yaml tab="Docker (Swarm)" deploy: labels: traefik.http.routers.blog.rule=Host(`example.com`) && Path(`/blog`) traefik.http.services.blog-svc.loadbalancer.server.port=8080" traefik.http.routers.blog.tls=true traefik.http.routers.blog.tls.certresolver=myresolver traefik.http.routers.blog.tls.domains[0].main=example.org traefik.http.routers.blog.tls.domains[0].sans=*.example.org ``` ```yaml tab="Kubernetes" apiVersion: traefik.io/v1alpha1 kind: IngressRoute metadata: name: blogtls spec: entryPoints: websecure routes: match: Host(`example.com`) && Path(`/blog`) kind: Rule services: name: blog port: 8080 tls: certResolver: myresolver domains: main: example.org sans: '*.example.org' ``` ```yaml tab="File (YAML)" http: routers: blog: rule: "Host(`example.com`) && Path(`/blog`)" tls: certResolver: myresolver domains: main: "example.org" sans: "*.example.org" ``` ```toml tab="File (TOML)" [http.routers] [http.routers.blog] rule = "Host(`example.com`) && Path(`/blog`)" [http.routers.blog.tls] certResolver = "myresolver" # From static configuration [[http.routers.blog.tls.domains]] main = "example.org" sans = ["*.example.org"] ```
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_cluster_register.md

title: "glooctl cluster register" weight: 5 Register a cluster to the Gloo Federation control plane Register a cluster to the Gloo Federation control plane. Registered clusters can be targeted for discovery and configuration. ``` glooctl cluster register [flags] ``` ``` --cluster-name string name of the cluster to register --federation-namespace string namespace of the Gloo Federation control plane (default "gloo-system") -h, --help help for register --remote-context string name of the kubeconfig context to use for registration --remote-kubeconfig string path to the kubeconfig from which the registered cluster will be accessed --remote-namespace string namespace in the target cluster where registration artifacts should be written (default "gloo-system") ``` ``` -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) ``` - Cluster commands
Project: Pipy (Orchestration & Management / Service Proxy)
File: pull_request_template.md

We thank you for helping improve Pipy. In order to ease the reviewing process, we invite you to read the and ask you to consider the following points before submitting a PR: We prefer to discuss the underlying issue prior to discussing the code. Therefore, we kindly ask you to refer to an existing issue, or an existing discussion in a public space with members of the Core Team. In few cases, we acknowledge that this might not be necessary, for instance when refactoring code or small bug fixes. In this case, the PR must include the same information an issue would have: a clear explanation of the issue, reproducible code, etc. Focus the PR to the referred issue, and restraint from adding unrelated changes/additions. We do welcome another PR if you fixed another issue. If your change is big, consider breaking it into several smaller PRs. In general, the smaller the change, the quicker we can review it.
Project: gRPC (Orchestration & Management / Remote Procedure Call)
File: feature_request_core.md

name: Request a gRPC Core feature about: Suggest an idea for this project labels: kind/enhancement, priority/P2, lang/core, untriaged <!-- 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: Azure API Management (Orchestration & Management / API Gateway)
File: self-hosted-gateway.md

September 29, 2021 New stable version of the is now available. Full list of container versions can be found . None Concurrency bug in pooled connection acquisition logic that caused request failures under high load Bug causing intermittent failures of large (30MB+) requests Bug preventing request logs and gateway errors from appearing in standard output None August 31, 2021 New stable version of the is now available. Full list of container versions can be found . None Upgraded to use base image mcr.microsoft.com/dotnet/aspnet:3.1.18-alpine3.13 which addressed the following vulnerabilities: CVE-2021-36159 CVE-2021-22924 CVE-2021-22922 CVE-2021-22926 CVE-2021-36222 CVE-2021-22922 CVE-2021-22924 Fixed the issue causing gateway's failure to start rather than fallback to local configuration snapshot when cloud configuration endpoint is not available None August 25, 2021 New preview version of the is now available. Full list of container versions can be found . None Upgraded to use .NET Core base image .NET Core base image 3.1.18 (nightly) which addressed the following vulnerabilities: CVE-2021-36159 CVE-2021-22924 CVE-2021-22922 CVE-2021-22926 CVE-2021-36222 CVE-2021-22922 CVE-2021-22924 None July 8, 2021 New stable version of the is now available. Full list of container versions can be found . Removed the 30MB request size limit None None June 11, 2021 New stable version of the is now available. Full list of container versions can be found . None Upgraded to use .NET Core base image 3.1.16 which addressed the following vulnerabilities: CVE-2021-26701 (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-26701 ) CVE-2021-24112 (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-24112 ) None April 22, 2021 New stable version of the is now available. Full list of container versions can be found . None Plugged a memory leak in the backend response content processing logic. None April 20, 2021 New stable version of the is now available. Full list of container versions can be found . Support for Kubernetes Ingress object - see https://github.com/Azure/api-management-self-hosted-gateway-ingress. None None February 18, 2021 New stable version of the is now available. Full list of container versions can be found . Updated with support for . None None December 18, 2020 New stable version of the is now available. Full list of container versions can be found . None Rate limit policy throttling at a lower than configured rate. None November 3, 2020 New stable version of the is now available. Full list of container versions can be found . None TLS connection to upstream is unexpectedly terminated under certain conditions. None October 14, 2020 New stable version of the is now available. Full list of container versions can be found . Migrated to . Migrated to base image. Connection closed (not re-used) when empty response is received from the upstream. External cache selection is not updated when self-hosted gateway location is changed. None
Project: Serverless Devs (Orchestration & Management / Scheduling & Orchestration)
File: application_scopes.md

title: Scenarios description: 'Scenarios' position: 5 category: 'User model' The preceding specification only applies to the serverless applications that are supported and can be identified by Serverless Devs. Serverless application developers can use the preceding specification to easily use Serverless Devs to manage the entire lifecycle of the creation, development, and O&M of serverless applications. nrich API operations and capabilities based on the preceding specification. For example, you can enrich the stored metadata and extend the supported API operation capabilities. These extended capabilities of Serverless Registry and is not part of SRM.
Project: Easegress (Orchestration & Management / API Gateway)
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. Thanks for contributing !
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_plugin_list.md

title: "glooctl plugin list" weight: 5 List available glooctl plugins ``` glooctl plugin list [flags] ``` ``` --federation-namespace string namespace of the Gloo Federation control plane (default "gloo-system") -h, --help help for list ``` ``` -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) ``` - Commands for interacting with glooctl plugins
Project: Linkerd (Orchestration & Management / Service Mesh)
File: PULL_REQUEST_TEMPLATE.md

<!-- Thanks for sending a pull request! If you already have a well-structured git commit message, chances are GitHub set the title and description of this PR to the git commit message subject and body, respectively. If so, you may delete these instructions and submit your PR. If this is your first time, please read our contributor guide: https://github.com/linkerd/linkerd2/blob/main/CONTRIBUTING.md The title and description of your Pull Request should match the git commit subject and body, respectively. Git commit messages are structured as follows: ``` Subject Problem Solution Validation Fixes #[GitHub issue ID] DCO Sign off ``` Example git commit message: ``` Introduce Pull Request Template GitHub's community guidelines recommend a pull request template, the repo was lacking one. Introduce a `PULLREQUESTTEMPLATE.md` file. Once merged, the should indicate the repo now provides a pull request template. Fixes #3321 Signed-off-by: Jane Smith <jane.smith@example.com> ``` Note the git commit message subject becomes the pull request title. For more details around git commits, see the section on Committing in our contributor guide: https://github.com/linkerd/linkerd2/blob/main/CONTRIBUTING.md#committing -->
Project: Gravitee.io (Orchestration & Management / API Gateway)
File: management-api-properties.md

As an API publisher, you can define properties for your API. These properties are automatically injected into the expression language context to be used later. For example, to get the value of the property `my-property` defined in API properties: `{#properties['my-property']}` The (+) button let you create a new property. To get access to dynamic properties click on the settings button. Dynamic properties let you fetch API properties from a remote resource, such as web service. You can set a polling frequency property and apply response transformation thanks to the . Do not forget to switch on dynamic properties and re-deploy the API to enable dynamic properties. Like classical properties, dynamic properties will be injected into the expression language context.
Project: Envoy (Orchestration & Management / Service Proxy)
File: javascript.md

This describes the flow used for developing, testing, and serving JavaScript, which is used to make the admin-site more useful. JavaScript, HTML, and CSS files are converted by the BUILD process and a script, . which generates a .cc file with `constexpr absl::string_view` objects defined to hold the file contents. These are inlined into an HTML response for the admin and stats pages. To reduce binary bloat for users that do need the HTML functionality on their admin site, the bazel option `admin_html=disabled` can be defined. The admin site is still functional, but without the HTML forms for entering in params to the endpoints. This also disables active mode, which is dependent on HTML. To facilitate debugging and iterating on the JavaScript, a simplified variant of envoy-static is provided in `test/integration/adminhtml:testserver`, which accepts `debug` as its first argument. In that case, `test_server` will read web resources from their source tree locations every time they are served. So you can debug JavaScript and tweak CSS by editing the file and refreshing the admin site in your browser, without rebuilding or restarting the binary. We have an ad-hoc testing mechanism for the JavaScript, HTML, and the C++ server behind them, loosely based on Google's Closure Compiler and jstest. However this mechanism does not pull in those infrastructural elements as dependencies. If there is significantly more JavaScript needed then migrating to that can be considered. The JavaScript is tested using a binary //test/integration:admintestserver, which is similar to envoy-static, but uses a post-server hook to add a /test endpoint to the admin port, enabling the test files to run in the same origin as the endpoint under test. This is needed for deep inspection of the document model during tests, which is possible only for same-origin iframes. For more details on testing mechanics, see . Note that the test is semi-automatic using a browser, and is not run in blaze tests or CI. A human must manually inspect the test results page for pass/fail logs, and the UI to make sure all looks good. The style is somewhat consistent with Envoy C++ code: 2-char indent, 100-char lines, and but with camel-case variables per Google JS convention, to be compatible with eslint settings. Doxygen style is used in a manner similar to that of Google JS: types specified for parameters and return values, "!" prefix for required (non-null), "?" prefix for optional. If using Closure Compiler, it would use these for strong type checking. The JavaScript here is not currently compiled, but it can be linted by https://validatejavascript.com/, 'Google' settings with `max-len` and `indent` checkboxes disabled.
Project: Contour (Orchestration & Management / Service Proxy)
File: contour-graph.md

Contour models its configuration using a directed acyclic graph (DAG) of internal objects. This can be visualized through a debug endpoint that outputs the DAG in format. To visualize the graph, you must have installed on your system. To download the graph and save it as a PNG: ```bash $ CONTOUR_POD=$(kubectl -n projectcontour get pod -l app=contour -o name | head -1) $ kubectl -n projectcontour port-forward $CONTOUR_POD 6060 $ curl localhost:6060/debug/dag | dot -T png > contour-dag.png ``` The following is an example of a DAG that maps `http://kuard.local:80/` to the `kuard` service in the `default` namespace: !
Project: Fluid (Orchestration & Management / Scheduling & Orchestration)
File: juicefs_for_s3.md

JuiceFS implements a distributed file system by adopting the architecture that separates "data" and "metadata" storage. When using JuiceFS to store data, the data itself is persisted in object storage (e.g., Amazon S3), and the corresponding metadata can be persisted in various databases such as Redis, MySQL, TiKV, etc., based on the scenarios and requirements. Therefore, to use JuiceFS in Fluid to synchronize existing data in S3, it is necessary to initialize the data in S3 into JuiceFS first. For the specific deployment method, please refer to the document . After the JuiceFSRuntime and Dataset are successfully created, wait for the worker pod to start successfully, and then refer to the following steps. In the worker pod, you can use `juicefs sync` to synchronize the data of the specified bucket to juicefs. For example, there is a file `JuiceFS_logo.png` in bucket `jfs-test-tmp`, in worker pod the mount point is `/runtime-mnt/juicefs/default/jfsdemo/juicefs-fuse`, sync it into JuiceFS as follows. The mount point format of worker pod is: `/runtime-mnt/juicefs/<namespace>/<runtimeName>/juicefs-fuse`. You can check it in the worker pod with the following command: ```shell $ kubectl exec -it jfsdemo-worker-0 bash root@jfsdemo-worker-0:~# df -h Filesystem Size Used Avail Use% Mounted on overlay 100G 29G 72G 29% / tmpfs 64M 0 64M 0% /dev tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup /dev/sdb1 100G 29G 72G 29% /etc/hosts shm 64M 0 64M 0% /dev/shm tmpfs 3.8G 12K 3.8G 1% /run/secrets/kubernetes.io/serviceaccount JuiceFS:minio 1.0P 1.1G 1.0P 1% /runtime-mnt/juicefs/default/jfsdemo/juicefs-fuse ``` ```shell $ kubectl exec -it jfsdemo-worker-0 bash root@jfsdemo-worker-0:~# juicefs sync s3://jfs-test-tmp/ /runtime-mnt/juicefs/default/jfsdemo/juicefs-fuse/ 2022/05/09 07:19:53.852821 juicefs[1995593] <INFO>: Syncing from s3://jfs-test-tmp/ to file:///runtime-mnt/juicefs/default/jfsdemo/juicefs-fuse/ [sync.go:571] Scanned objects count: 1 / 1 [==============================================================] done Copied objects count: 1 Copied objects bytes: 101.75 KiB (104192 Bytes) 305.10 KiB/s Checked objects bytes: 0.00 b (0 Bytes) 0.00 b/s Deleted objects count: 0 Skipped objects count: 0 Failed objects count: 0 2022/05/09 07:19:54.187294 juicefs[1995593] <INFO>: Found: 1, copied: 1 (101.75 KiB), checked: 0 B, deleted: 0, skipped: 0, failed: 0 [sync.go:795] root@jfsdemo-worker-0:~# ``` Address syntax of `juicefs sync` follows `BUCKET`. Refer to for more details. ```shell root@jfsdemo-worker-0:~# ls /runtime-mnt/juicefs/default/jfsdemo/juicefs-fuse/ JuiceFS_logo.png root@jfsdemo-worker-0:~# ``` You can see that the files in the bucket have been synced to JuiceFS. Finally, create a business Pod, where the Pod uses the `Dataset` created above to specify a PVC with the same name. This step is consistent with the document , and will not be repeated here.
Project: Gloo (Orchestration & Management / API Gateway)
File: upstream-discovery.md

A represents a destination for routing HTTP requests. An Upstream can be compared to in Envoy terminology. Upstreams can either be defined statically in a cluster, or can be discovered dynamically via Gloo Edge's Upstream Discovery feature. UDS runs in the component of Gloo Edge. Create a , which is responsible for the following: Emit a snapshot of the resources that are required for UDS to operate (Upstreams, Secrets, Kubernetes Namespaces) This set of resources is referred to as the Create and start a , which is responsible for the following: Open a goroutine for each type of Discovery plugin (Kubernetes, ec2..etc) Each plugin then discovers the corresponding Upstreams, and stores them in an Each time that the in-memory map is updated, the UDS Engine Resyncs, meaning it attempts to reconcile all the upstreams Create and start the : This follows our standard pattern of an Event Loop / Emitter / Syncer, where the event loop watches events, uses the emitter to producer a snapshot, and sends that Snapshot to the Sync to be Synced In this case, a Sync, just invokes on the UDS Engine. That method takes the up to date in memory upstreams, and reconciles them UDS supports multiple plugins for discovering upstreams. To determine which types of services are supported, search for all . Each plugin is responsible for discovering upstreams of a specific type. For example, the is responsible for discovering Kubernetes Services, and generating the corresponding Upstreams. UDS behavior can be configured globally, in the resource under `discovery.uds_options`.