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

title: "glooctl create secret header" weight: 5 Create a header secret with the given name Create a header secret with the given name. The format of the secret data is: `{"headers" : [name=value,...]}` ``` glooctl create secret header [flags] ``` ``` --headers strings comma-separated list of header name=value entries -h, --help help for header ``` ``` -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 --dry-run print kubernetes-formatted yaml rather than creating or updating a resource -i, --interactive use interactive mode --kube-context string kube context to use when interacting with kubernetes --kubeconfig string kubeconfig to use, if not standard one --name string name of the resource to read or write -n, --namespace string namespace for reading or writing resources (default "gloo-system") -o, --output OutputType output format: (yaml, json, table, kube-yaml, wide) (default table) --use-consul use Consul Key-Value storage as the backend for reading and writing config (VirtualServices, Upstreams, and Proxies) --use-vault use Vault Key-Value storage as the backend for reading and writing secrets --vault-address string address of the Vault server. This should be a complete URL such as "http://vault.example.com". Use with --use-vault (default "https://127.0.0.1:8200") --vault-ca-cert string CACert is the path to a PEM-encoded CA cert file to use to verify the Vault server SSL certificate.Use with --use-vault --vault-ca-path string CAPath is the path to a directory of PEM-encoded CA cert files to verify the Vault server SSL certificate.Use with --use-vault --vault-client-cert string ClientCert is the path to the certificate for Vault communication.Use with --use-vault --vault-client-key string ClientKey is the path to the private key for Vault communication.Use with --use-vault --vault-path-prefix string The Secrets Engine to which Vault should route traffic. (default "secret") --vault-root-key string key prefix for Vault key-value storage inside a storage engine. (default "gloo") --vault-tls-insecure Insecure enables or disables SSL verification.Use with --use-vault --vault-tls-server-name string TLSServerName, if set, is used to set the SNI host when connecting via TLS.Use with --use-vault --vault-token string The root token to authenticate with a Vault server. Use with --use-vault ``` - Create a secret
Project: Katalyst (Orchestration & Management / Scheduling & Orchestration)
File: MAINTAINERS.md

This file lists the maintainers of the Katalyst Core project. The responsibilities of maintainers are listed in the file. | Name | GitHub ID | Affiliation | |-|--|-| | | | ByteDance | | | | ByteDance | | | | ByteDance | | | | ByteDance | | | | ByteDance | | | | ByteDance |
Project: Clusternet (Orchestration & Management / Scheduling & Orchestration)
File: bug-report.md

name: Bug Report about: Report a bug encountered while operating Clusternet labels: kind/bug <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! --> Clusternet version: Clusternet-agent version (user `clusternet-agent --version=json`): Clusternet-hub version (user `clusternet-hub --version=json`): Kubernetes version (use `kubectl version`): Cloud provider or hardware configuration: OS (e.g: `cat /etc/os-release`): Kernel (e.g. `uname -a`): Others:
Project: Tengine (Orchestration & Management / Service Proxy)
File: ngx_limit_upstream.md

limit upstream retries Limits retries for upstream servers (proxy, memcached, fastcgi, scgi, uwsgi). Using one of the directives below will enable this feature. http { upstream test { server 127.0.0.1:8081; server 127.0.0.2:8081; server 127.0.0.3:8081; server 127.0.0.4:8081; } server { proxyupstreamtries 2; proxysetheader Host $host; location / { proxy_pass test; } } } Syntax: fastcgi\_upstream\_tries num Default: - Context: http, server, locatioon Limit the maximum number of tries for fastcgi proxy. Nginx tries to connect different server each time. Syntax: proxy\_upstream\_tries num Default: - Context: http, server, locatioon Limit the maximum number of tries for http proxy. Nginx tries to connect different server each time. Syntax: memcached\_upstream\_tries num Default: - Context: http, server, locatioon Limit the maximum number of tries for memcached proxy. Nginx tries to connect different server each time. Syntax: scgi\_upstream\_tries num Default: - Context: http, server, locatioon Limit the maximum number of tries for scgi proxy. Nginx tries to connect different server each time. Syntax: uwsgi\_upstream\_tries num Default: - Context: http, server, locatioon Limit the maximum number of tries for uwsgi proxy. Nginx tries to connect different server each time.
Project: Flomesh Service Mesh (FSM) (Orchestration & Management / Service Mesh)
File: release_pull_request_template.md

<!-- Use the checklist below to ensure your release PR is complete before marking it ready for review. --> `needs-cherry-pick-vX.Y.Z` [ ] I have made all of the following version and patch updates: Updated the container image tag in charts/fsm/values.yaml Updated the chart and app version in charts/fsm/Chart.yaml Updated the image tags used in the automated demo Regenerated the Helm chart README.md [ ] I have checked that the base branch for this PR is correct as defined by the release guide <!-- If this PR is for updating the release branch, ensure the base branch is `release-vX.Y`. If this PR is for making changes on the main branch, ensure the base branch is `main`. --> Is this a release candidate?
Project: Open Cluster Management (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: Gloo (Orchestration & Management / API Gateway)
File: glooctl_create_upstream_aws.md

title: "glooctl create upstream aws" weight: 5 Create an Aws Upstream AWS Upstreams represent a set of AWS Lambda Functions for a Region that can be routed to with Gloo. AWS Upstreams require a valid set of AWS Credentials to be provided. These should be uploaded to Gloo using `glooctl create secret aws` ``` glooctl create upstream aws [flags] ``` ``` --aws-region string region for AWS services this upstream utilize (default "us-east-1") --aws-secret-name glooctl create secret aws --help name of a secret containing AWS credentials created with glooctl. See glooctl create secret aws --help for help creating secrets --aws-secret-namespace glooctl create secret aws --help namespace where the AWS secret lives. See glooctl create secret aws --help for help creating secrets (default "gloo-system") -h, --help help for aws ``` ``` -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 --dry-run print kubernetes-formatted yaml rather than creating or updating a resource -i, --interactive use interactive mode --kube-context string kube context to use when interacting with kubernetes --kubeconfig string kubeconfig to use, if not standard one --name string name of the resource to read or write -n, --namespace string namespace for reading or writing resources (default "gloo-system") -o, --output OutputType output format: (yaml, json, table, kube-yaml, wide) (default table) --use-consul use Consul Key-Value storage as the backend for reading and writing config (VirtualServices, Upstreams, and Proxies) ``` - Create an Upstream
Project: Docker Swarm (Orchestration & Management / Scheduling & Orchestration)
File: CONTRIBUTING.md

Welcome to Kubernetes. We are excited about the prospect of you joining our ! The Kubernetes community abides by the CNCF . Here is an excerpt: As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities. We have full documentation on how to get started contributing here: Kubernetes projects require that you sign a Contributor License Agreement (CLA) before we can accept your pull requests - Main contributor documentation, or you can just jump directly to the - Common resources for existing developers - We have a diverse set of mentorship programs available that are always looking for volunteers!
Project: Avro (Orchestration & Management / Remote Procedure Call)
File: api-java.md

title: "Java API" linkTitle: "Java API" weight: 100 manualLink: /docs/++version++/api/java/ <!-- 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. --> The Javadocs can be found <a href="/docs/++version++/api/java/">here</a>.
Project: Karmada (Orchestration & Management / Scheduling & Orchestration)
File: ADMINS.md

This document explains who the admins are (see below), what they do in this repo, and how they should be doing it. If you're interested in becoming a maintainer, see . If you're interested in contributing, see . | Admin | GitHub ID | Affiliation | | -| | -- | | Charlotte | | Amazon | | Henri Yandell | | Amazon | | Jack Mazanec | | Amazon | | Vamshi Vijay Nakkirtha | | Amazon | | Vijayan Balasubramanian | | Amazon | As an admin you own stewartship of the repository and its settings. Admins have . Use those privileges to serve the community and protect the repository as follows. Security is your number one priority. Manage security keys and safeguard access to the repository. Note that this repository is monitored and supported 24/7 by Amazon Security, see for details. Act on violations by revoking access, and blocking malicious actors. Adopt organizational best practices, work in the open, and collaborate with other admins by opening issues before making process changes. Prefer consistency, and avoid diverging from practices in the opensearch-project organization.
Project: BFE (Orchestration & Management / Service Proxy)
File: write_doc_guide.md

BFE encourages you to contribute documentation. If your written or translated documents meet our requirements, your documents will be available on the bfe-networks.com website and on Github for BFE users. BFE's documentation is mainly divided into the following categories: Beginner's Guide: to help users get started and inspired; User Guides: to provide users with a tutorial of basic operations in BFE; Developer Guides: to meet the needs of developers; Our documentation supports contributions in format of (GitHub style) . Once the document is written, you can use the preview tool to check how the document appears to verify that your document is displayed correctly on the official website. Before doing this, please make sure your operating system has gitbook installed. Take the ubuntu system as an example, run: ```bash $ sudo apt-get update && apt-get install -y npm $ sudo npm install -g gitbook-cli ``` First download the full repository: ```bash $ git clone https://github.com/bfenetworks/bfe ``` Change to base directory of documents which you want to load and build(docs/LANG), run: ```bash $ cd docs/en_us/ $ gitbook serve --port 8000 ... Serving book on http://localhost:8000 ``` Then: open your browser and navigate to http://localhost:8000. The site may take a few seconds to load because the building takes a certain amount of time All content should be written in (GitHub style). Create a new `.md` file or modify an existing article in the repository you are currently working on Add the new document name to the corresponding index file (SUMMARY.md) Run the preview tool in base directory of documents (docs/LANG) ```bash $ cd docs/en_us/ $ gitbook serve --port 8000 ``` Open your browser and navigate to http://localhost:8000 . On the page to be updated, click Refresh Content at the top right corner. The steps to submit changes and PR can refer to We encourage your contributions to all aspects of the platform and supportive contents. You can Fork or Clone repository, ask questions and feedback, or submit bugs on issues. For details, please refer to the .
Project: Contour (Orchestration & Management / Service Proxy)
File: ip-filtering.md

Contour supports filtering requests based on the incoming ip address using Envoy's . Requests can be either allowed or denied based on a CIDR range specified on the virtual host and/or individual routes. If the request's IP address is allowed, the request will be proxied to the appropriate upstream. If the request's IP address is denied, an HTTP 403 (Forbidden) will be returned to the client. Rules are specified with the `ipAllowPolicy` and `ipDenyPolicy` fields on `virtualhost` and `route`: ```yaml apiVersion: projectcontour.io/v1 kind: HTTPProxy metadata: name: basic spec: virtualhost: fqdn: foo-basic.bar.com ipAllowPolicy: cidr: 127.0.0.1/32 source: Peer routes: conditions: prefix: / services: name: s1 port: 80 ipAllowPolicy: cidr: 127.0.0.1/32 source: Peer cidr: 99.99.0.0/16 source: Remote ``` CIDR ranges may be ipv4 or ipv6. Bare IP addresses are interpreted as the CIDR range containing that one ip address only. Examples: `1.1.1.1/24` `127.0.0.1` `2001:db8::68/24` `2001:db8::68` Filters are specified as either allow or deny: `ipAllowPolicy` only allows requests that match the ip filters. `ipDenyPolicy` denies all requests unless they match the ip filters. Allow and deny policies cannot both be specified at the same time for a virtual host or route. The `source` field controls how the ip address is selected from the request for filtering. `source: Peer` filter rules will filter using Envoy's , which is always the physical peer. `source: Remote` filter rules will filter using Envoy's , which may be inferred from the X-Forwarded-For header or proxy protocol. If using `source: Remote` with `X-Forwarded-For`, it may be necessary to configure Contour's `numTrustedHops` in . IP filters on the virtual host apply to all routes included in the virtual host, unless the route specifies its own rules. Rules specified on a route override any rules defined on the virtual host, they are not additive.
Project: Traefik Mesh (Orchestration & Management / Service Mesh)
File: maintainers.md

title: "Traefik Mesh Maintainers" description: "In this article, you can find the list of Traefik Mesh maintainers." Daniel Tomcej Manuel Zapf Michal Matur Landry Benguigui Harold Ozouf Julien Levesy Brendan Le Glaunec Kevin Pollet
Project: BFE (Orchestration & Management / Service Proxy)
File: redirect.md

Redirect HTTP to HTTPS for requests visiting example.org Modify the example configurations (conf/) as the following steps: Step 1. modify conf/bfe.conf and enable mod_redirect ```ini Modules = mod_redirect ``` Step 2. modify modredirect basic configuration (conf/modredirect/mod_redirect.conf) ```ini [basic] DataPath = mod_redirect/redirect.data ``` Step 3. modify redirect rule configuration (conf/mod_redirect/redirect.data), and add following rules. ```json { "Version": "init version", "Config": { "example_product": [{ "Cond": "!reqprotosecure() && reqhostin(\"example.org\")", "Actions": [{ "Cmd": "SCHEME_SET", "Params": [ "https" ] }], "Status": 301 }] } } ``` Step 4. Verify configured rules ```bash curl -H "host: example.org" "http://127.1:8080/test" ``` The response stuatus code should be 301, and the value of Location response Header should be "https://example.org/test".
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2015-09-24-mesos-0-24-1-and-more-released.md

layout: post title: Apache Mesos 0.24.1 and More Released permalink: /blog/mesos-0-24-1-and-more-released/ published: true post_author: display_name: Adam B tags: Release The latest Mesos 0.24.1 is now available for . This release includes a fix for version parsing for Docker 1.8 and 1.7.0.fc22, as well as a fix for Docker command health checks. These same fixes were backported onto 0.23.0 to produce a new Mesos 0.23.1 release. MESOS-2986 was also backported to 0.21 and 0.22 to produce Mesos 0.21.2 and 0.22.2 (still VOTING). All of these releases are (or will be) available on the page. - Docker version output is not compatible with Mesos - COMMAND health checks with Marathon 0.10.0 are broken Full release notes are available in the release . Upgrading to 0.24.1 can be done seamlessly on a 0.24.0 cluster. In fact, only the slaves need to be upgraded. If upgrading from an earlier version, please refer to the documentation. Special thanks to the lone code contributor for 0.24.1, 0.23.1, 0.22.2, and 0.21.2: haosdent huang. Our hero.
Project: gRPC (Orchestration & Management / Remote Procedure Call)
File: server_reflection.md

This document shows how to use gRPC Server Reflection in gRPC Python. Please see [C++ Server Reflection Tutorial] for general information and more examples how to use server reflection. gRPC Python Server Reflection is an add-on library. To use it, first install the [grpcio-reflection] PyPI package into your project. Note that with Python you need to manually register the service descriptors with the reflection service implementation when creating a server (this isn't necessary with e.g. C++ or Java) ```python from grpc_reflection.v1alpha import reflection def serve(): server = grpc.server(futures.ThreadPoolExecutor(max_workers=10)) helloworldpb2grpc.addGreeterServicerto_server(Greeter(), server) SERVICE_NAMES = ( helloworldpb2.DESCRIPTOR.servicesbyname['Greeter'].fullname, reflection.SERVICE_NAME, ) reflection.enableserverreflection(SERVICE_NAMES, server) server.addinsecureport('[::]:50051') server.start() ``` Please see [greeterserverwith_reflection.py] in the examples directory for the full example, which extends the gRPC [Python `Greeter` example] on a reflection-enabled server. After starting the server, you can verify that the server reflection is working properly by using the [`grpc_cli` command line tool]: ```sh $ grpc_cli ls localhost:50051 ``` output: ```sh grpc.reflection.v1alpha.ServerReflection helloworld.Greeter ``` For more examples and instructions how to use the `grpc_cli` tool, please refer to the [`grpc_cli` documentation] and the [C++ Server Reflection Tutorial]. Server Reflection can be used by clients to get information about gRPC services at runtime. We've provided a descriptor database called which implements the interface. It manages the communication between clients and reflection services and the storage of received information. Clients can use it as using a local descriptor database. To use Server Reflection with ProtoReflectionDescriptorDatabase, first initialize an instance with a channel. ```Python import grpc from grpcreflection.v1alpha.protoreflectiondescriptordatabase import ProtoReflectionDescriptorDatabase channel = grpc.securechannel(serveraddress, creds) reflection_db = ProtoReflectionDescriptorDatabase(channel) ``` Then use this instance to feed a . ```Python from google.protobuf.descriptor_pool import DescriptorPool descpool = DescriptorPool(reflectiondb) ``` Example usage of this descriptor pool: Get Service/method descriptors. ```Python servicedesc = descpool.FindServiceByName("helloworld.Greeter") methoddesc = servicedesc.FindMethodByName("helloworld.Greeter.SayHello") ``` Get message type descriptors and create messages dynamically. ```Python requestdesc = descpool.FindMessageTypeByName("helloworld.HelloRequest") request = MessageFactory(descpool).GetPrototype(requestdesc)() ``` You can also use the Reflection Database to list all the services: ```Python services = reflectiondb.getservices() ``` The [Server Reflection Protocol] provides detailed information about how the server reflection works and describes the server reflection protocol in detail.