cwielenb/CNCF-Dataset huggingface dataset:
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2015-09-17-mesoscon-europe-2015-schedule-announced.md

layout: post title: MesosCon Europe Schedule and Diversity Scholarship Available permalink: /blog/mesoscon-europe-2015-schedule-announced/ published: true post_author: display_name: Michael Hausenblas twitter: mhausenblas tags: MesosCon will take place in Dublin, Ireland in three weeks, and were excited to announce the event schedule and availability of a diversity scholarship program. The program committee was overwhelmed by the number of submissions to the first European edition of MesosCon 65 talks and tutorials have been submitted, you all rock , the community to help us select the most interesting and relevant talks. Given we had hard constraints concerning time and space we ended up selecting 14 talks and four lightning talks based on your overall ranking. The talks range from introductory presentations that aim helping the onboarding of new Mesos community members to deep dives: in the afternoon we will split into two tracks to be able to accommodate more topics. Sessions will take place on Thursday, October 8th 2015. Check out the yourself! We'll also be holding a Mesos hackathon on Friday October 9th, and look forward to seeing what members of the community build and dream up. As important as the schedule might be, if you cant be there in person, what gives? So, we're repeating the successful offering of a : it provides support to women, people of color, and people with disabilities who may not otherwise have the opportunity to attend MesosCon for financial reasons. today and hope to see you in Dublin.
Project: kcp (Orchestration & Management / Scheduling & Orchestration)
File: CONTRIBUTING.md

We're thrilled that you're interested in contributing to kcp! Please visit our on our documentation site. Beside that, what coverns the project and all contributions to it must follow the . From the KCP Project Governance, the following manifesto should guide the technical decisions through-out all contributions: kcp maintainers strive to be good citizens in the Kubernetes project. kcp maintainers see kcp always as part of the Kubernetes ecosystem and always strive to keep that ecosystem united. In particular, this means: kcp strives to not divert from Kubernetes, but strives to extend its use-cases to non-container control planes while keeping the ecosystems of libraries and tooling united. kcp as a consumer of Kubernetes API Machinery will strive to stay 100% compatible with the semantics of Kubernetes APIs, while removing container orchestration specific functionality. kcp strives to upstream changes to Kubernetes code as much as possible.
Project: Kubeflow (Orchestration & Management / Scheduling & Orchestration)
File: README.md

This folder contains information reguarding the newly formed (January 2023) Kubeflow Security Team. Since this team is just beginning, there is a lot of work to be done. If you are a security professional and you are a Kubeflow User we encourage you to get involved with the Kubeflow Security Team. Meetings* We meet bi-weekly on Wednesdays at 8:00am PT/10am CT. You can find out what that is in your timezone at Join* the the join the #security channel. Attend* the via Zoom (This meeting is also on the Kubeflow Community Calendar as well) Collaborate and Contribute* on what is currently being discussed actively in-progress. Change directories to `components/tensorboard-controller` Generate and install manifests and build the controller: `make install` Run the controller locally: `make run` If you want to enable the scheduling functionality for Tensorboard servers that use ReadWriteOnce PVCs as log storages, then set the `RWOPVCSCHEDULING` to `true` and run: `RWOPVCSCHEDULING="true" make run` Clone the repository Change directories to `components/tensorboard-controller` Generate and install manifests and build the controller: `make manifests` Build and push the docker image: `make docker-build docker-push IMG=YOURIMAGENAME` Deploy the Tensorboard controller: `make deploy IMG=YOURIMAGENAME` If you want to enable the scheduling functionality for Tensorboard servers that use ReadWriteOnce PVCs as log storages, then: Change directories to `components/tensorboard-controller/config/manager` Modify the `manager.yaml` file by navigating to the `deployment.spec.template.spec` field and manually setting the value of the `RWOPVCSCHEDULING` env var to `"true"` in the manager container. Run: `make deploy IMG=YOURIMAGENAME`
Project: Contour (Orchestration & Management / Service Proxy)
File: ingressroute.md

<div id="toc" class="navigation"></div> The object was added to Kubernetes in version 1.1 to describe properties of a cluster-wide reverse HTTP proxy. Since that time, the Ingress object has not progressed beyond the beta stage, and its stagnation inspired an to express missing properties of HTTP routing. The goal of the `IngressRoute` Custom Resource Definition (CRD) was to expand upon the functionality of the Ingress API to allow for a richer user experience as well as solve shortcomings in the original design. <p class="alert-deprecation"> <b>Removal Notice</b><br> The <code>IngressRoute</code> CRD has been removed from Contour. Please see the documentation for <a href="{% link docs/{{page.version}}/httpproxy.md %}"><code>HTTPProxy</code></a>, which is the successor to <code>IngressRoute</code>. You can also read the <a href="{% link _guides/ingressroute-to-httpproxy.md %}">IngressRoute to HTTPProxy upgrade</a> guide. </p>
Project: Gloo (Orchestration & Management / API Gateway)
File: migrate.proto.sk.md

title: "migrate.proto" weight: 5 <!-- Code generated by solo-kit. DO NOT EDIT. --> ```yaml "rename": string ``` | Field | Type | Description | | -- | - | -- | | `rename` | `string` | Rename the message/enum/enum value in next version. | ```yaml "rename": string "oneofPromotion": string ``` | Field | Type | Description | | -- | - | -- | | `rename` | `string` | Rename the field in next version. | | `oneofPromotion` | `string` | Add the field to a named oneof in next version. If this already exists, the field will join its siblings under the oneof, otherwise a new oneof will be created with the given name. | ```yaml "moveToPackage": string ``` | Field | Type | Description | | -- | - | -- | | `moveToPackage` | `string` | Move all types in the file to another package, this implies changing proto file path. | <!-- 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: Easegress (Orchestration & Management / API Gateway)
File: 1.2.Install.md

Instructions for installing Easegress from pre-built binaries or from source. The easiest way to install Easegress is by using pre-built binaries: Download the appropriate compressed archive file for your platform from . Extract the contents of the archive, which will create a directory containing the binaries. Add the extracted binaries to your system's path. You can either move and/or rename the binaries to a directory already in your path (such as /usr/local/bin), or add the newly created directory to your path. From a shell, test that Easegress is in your path: ```bash $ easegress-server --version Easegress v2.6.1 ``` Either download the Easegress repo as a ZIP file from , or clone the repo with the following command: ```bash $ git clone https://github.com/megaease/easegress.git ``` Navigate to the Easegress directory: ```bash $ cd easegress ``` Execute the build script to generate the binaries, which will be placed in the `bin` directory: ```bash $ make ``` Add the `bin` directory to your system's path: ```bash $ export PATH="$PATH:`pwd`/bin" ``` Verify that `easegress-server` has been successfully added to your path: ```bash $ easegress-server --version ``` Note: This repo requires Go 1.20+ compiler for the build. If you need the WebAssembly feature, please run `make wasm`. To install the Systemd service, execute the following command: ```bash $ /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/megaease/easegress/main/scripts/install.sh)" ``` Pull the latest image from Docker Hub: ```bash $ docker pull megaease/easegress:latest ``` Run the pulled image: ```bash $ docker run megaease/easegress ```
Project: APISIX (Orchestration & Management / API Gateway)
File: referer-restriction.md

title: referer-restriction keywords: Apache APISIX API Gateway Referer restriction description: This document contains information about the Apache APISIX referer-restriction Plugin, which can be used to restrict access to a Service or a Route by whitelisting/blacklisting the Referer request header. <!-- --> The `referer-restriction` Plugin can be used to restrict access to a Service or a Route by whitelisting/blacklisting the `Referer` request header. | Name | Type | Required | Default | Valid values | Description | |-||-|-|--|| | whitelist | array[string] | False | | | List of hostnames to whitelist. A hostname can start with `*` for wildcard. | | blacklist | array[string] | False | | | List of hostnames to blacklist. A hostname can start with `*` for wildcard. | | message | string | False | "Your referer host is not allowed" | [1, 1024] | Message returned when access is not allowed. | | bypass_missing | boolean | False | false | | When set to `true`, bypasses the check when the `Referer` request header is missing or malformed. | :::info IMPORTANT Only one of `whitelist` or `blacklist` attribute must be specified. They cannot work together. ::: You can enable the Plugin on a specific Route or a Service as shown below: :::note You can fetch the `admin_key` from `config.yaml` and save to an environment variable with the following command: ```bash adminkey=$(yq '.deployment.admin.adminkey[0].key' conf/config.yaml | sed 's/"//g') ``` ::: ```shell curl http://127.0.0.1:9180/apisix/admin/routes/1 -H "X-API-KEY: $admin_key" -X PUT -d ' { "uri": "/index.html", "upstream": { "type": "roundrobin", "nodes": { "127.0.0.1:1980": 1 } }, "plugins": { "referer-restriction": { "bypass_missing": true, "whitelist": [ "xx.com", "*.xx.com" ] } } }' ``` Once you have configured the Plugin as shown above, you can test it by setting `Referer: http://xx.com/x`: ```shell curl http://127.0.0.1:9080/index.html -H 'Referer: http://xx.com/x' ``` ```shell HTTP/1.1 200 OK ... ``` Now, if you make a request with `Referer: http://yy.com/x`, the request will be blocked: ```shell curl http://127.0.0.1:9080/index.html -H 'Referer: http://yy.com/x' ``` ```shell HTTP/1.1 403 Forbidden ... {"message":"Your referer host is not allowed"} ``` Since we have set `bypass_missing` to `true`, a request without the `Referer` header will be successful as the check is skipped: ```shell curl http://127.0.0.1:9080/index.html ``` ```shell HTTP/1.1 200 OK ... ``` To remove the `referer-restriction` Plugin, you can delete the corresponding JSON configuration from the Plugin configuration. APISIX will automatically reload and you do not have to restart for this to take effect. ```shell curl http://127.0.0.1:9180/apisix/admin/routes/1 -H "X-API-KEY: $admin_key" -X PUT -d ' { "uri": "/index.html", "plugins": {}, "upstream": { "type": "roundrobin", "nodes": { "127.0.0.1:1980": 1 } } }' ```
Project: kcp (Orchestration & Management / Scheduling & Orchestration)
File: kubectl-plugin.md

description: > How to install and use the kubectl kcp plugin. kcp provides a kubectl plugin that simplifies the operations with the kcp server. You can install the plugin from the current repo: ```sh $ make install go install ./cmd/... ``` The plugin will be : ```sh $ kubectl-kcp KCP is the easiest way to manage Kubernetes applications against one or more clusters, by giving you a personal control plane that schedules your workloads onto one or many clusters, and making it simple to pick up and move. Advanced use cases including spreading your apps across clusters for resiliency, scheduling batch workloads onto clusters with free capacity, and enabling collaboration for individual teams without having access to the underlying clusters. This command provides KCP specific sub-command for kubectl. Usage: kcp [command] Available Commands: completion generate the autocompletion script for the specified shell help Help about any command workspace Manages KCP workspaces Flags: --adddirheader If true, adds the file directory to the header of the log messages --alsologtostderr log to standard error as well as files -h, --help help for kcp --logbacktraceat traceLocation when logging hits line file:N, emit a stack trace (default :0) --log_dir string If non-empty, write log files in this directory --log_file string If non-empty, use this log file --logfilemax_size uint Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800) --logtostderr log to standard error instead of files (default true) --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level) --skip_headers If true, avoid header prefixes in the log messages --skiplogheaders If true, avoid headers when opening log files --stderrthreshold severity logs at or above this threshold go to stderr (default 2) -v, --v Level number for the log level verbosity --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging Use "kcp [command] --help" for more information about a command. ```
Project: Traefik (Orchestration & Management / API Gateway)
File: addprefix.md

title: "Traefik AddPrefix Documentation" description: "Learn how to implement the HTTP AddPrefix middleware in Traefik Proxy to updates request paths before being forwarded. Read the technical documentation." Prefixing the Path {: .subtitle } The AddPrefix middleware updates the path of a request before forwarding it. ```yaml tab="Docker & Swarm" labels: "traefik.http.middlewares.add-foo.addprefix.prefix=/foo" ``` ```yaml tab="Kubernetes" apiVersion: traefik.io/v1alpha1 kind: Middleware metadata: name: add-foo spec: addPrefix: prefix: /foo ``` ```yaml tab="Consul Catalog" "traefik.http.middlewares.add-foo.addprefix.prefix=/foo" ``` ```yaml tab="File (YAML)" http: middlewares: add-foo: addPrefix: prefix: "/foo" ``` ```toml tab="File (TOML)" [http.middlewares] [http.middlewares.add-foo.addPrefix] prefix = "/foo" ``` `prefix` is the string to add before the current path in the requested URL. It should include a leading slash (`/`).
Project: DolphinScheduler (Orchestration & Management / Scheduling & Orchestration)
File: DSIP.md

DolphinScheduler Improvement Proposal(DSIP) introduce major improvements to the Apache DolphinScheduler codebase. It is not for small incremental improvements, and the purpose of DSIP is to notice and inform community the finished or coming big feature for Apache DolphinScheduler. Any major new feature, major improvement, introduce or remove components Any major change of public interfaces, such as API endpoints, web ui huge change When the change in doubt and any committer thinks it should be DSIP, it does. We use GitHub Issue and Apache mail thread to record and hold DSIP, for more detail you could go to section and . As a DSIP, it should: Have a mail thread title started with ` Have a GitHub Issue labeled with `DSIP`, and including the mail thread link in the description. Current DSIPs including all DSIP still work-in-progress, you could see in Past DSIPs including all DSIP already done or retired for some reason, you could see in All DSIP should start with GitHub Issue If you pretty sure your issue is DSIP, you could click and choose "DSIP" in If you not sure about your issue is DSIP or not, you could click and choose "Feature request" in . DolphinScheduler maintainer team would add label `DSIP`, mention you in the issue and lead you to this document when they think it should be DSIP. You should add special prefix `[DSIP-XXX]`, `XXX` stand for the id DSIP. It's auto increment, and you could find the next integer in issues. After issue labeled with "DSIP", you should send an email to . Describe the purpose, and the draft design about your idea. Here is the template for mail Title: ` <CHANGE-TO-YOUR-LOVELY-PROPOSAL-TITLE>`, change `XXX` to special integer you just change in , and also change proposal title. Content: ```text Hi community, <CHANGE-TO-YOUR-PROPOSAL-DETAIL> I already add a GitHub Issue for my proposal, which you could see in <CHANGE-TO-YOUR-GITHUB-ISSUE-LINK>. Looking forward any feedback for this thread. ``` After community discuss and all of them think it worth as DSIP, you could . But if community think it should not be DSIP or even this change should not be included to DolphinScheduler, maintainers terminate mail thread and remove label "DSIP" for GitHub Issue, or even close issue if it should not change. When your proposal pass in the mail thread, you could make your hand dirty and start the work. You could submit related pull requests in GitHub if change should in one single commit. What's more, if proposal is too huge in single commit, you could create subtasks in GitHub Issue like , and separate into multiple commit. When DSIP is finished and all related PR were merged, you should reply the mail thread you created in to notice community the result of the DSIP. After that, this DSIP GitHub Issue would be closed and transfer from to , but you could still find it in : Have multiple subtasks and Projects on it.
Project: Pipy (Orchestration & Management / Service Proxy)
File: SUPPORT.md

OpenSSL User Support resources ============================== See the <https://www.openssl.org/support/contracts.html> for details on how to obtain commercial technical support. If you have general questions about using OpenSSL In this case the [openssl-users] mailing list is the right place for you. The list is not only watched by the OpenSSL team members, but also by many other OpenSSL users. Here you will most likely get the answer to your questions. An overview over the can be found below. If you think you found a Bug *NOTE: this section assumes that you want to report it or figure it out and fix it. What's written here is not to be taken as a recipe for how to get a working production installation* If you have any problems with OpenSSL then please take the following steps first: Search the mailing lists and/or the GitHub issues to find out whether the problem has already been reported. Download the latest version from the repository to see if the problem has already been addressed. Configure without assembler support (`no-asm`) and check whether the problem persists. Remove compiler optimization flags. Please keep in mind: Just because something doesn't work the way you expect does not mean it is necessarily a bug in OpenSSL. If you are not sure, consider searching the mail archives and posting a question to the [openssl-users] mailing list first. If you wish to report a bug, please open an on GitHub and include the following information: OpenSSL version: output of `openssl version -a` Configuration data: output of `perl configdata.pm --dump` OS Name, Version, Hardware platform Compiler Details (name, version) Application Details (name, version) Problem Description (steps that will reproduce the problem, if known) Stack Traceback (if the application dumps core) Not only errors in the software, also errors in the documentation, in particular the manual pages, can be reported as issues. The fastest way to get a bug fixed is to fix it yourself ;-). If you are experienced in programming and know how to fix the bug, you can open a pull request. The details are covered in the section. Don't hesitate to open a pull request, even if it's only a small change like a grammatical or typographical error in the documentation. Mailing Lists ============= The OpenSSL maintains a number of [mailing lists] for various purposes. The most important lists are: [openssl-users] for general questions about using the OpenSSL software and discussions between OpenSSL users. [openssl-announce] for official announcements to the OpenSSL community. [openssl-project] for discussion about the development roadmap and governance. Only subscribers can post to [openssl-users] or [openssl-project]. The archives are made public, however. For more information, see the [mailing lists] page. There was an [openssl-dev] list that has been discontinued since development is now taking place in the form of GitHub pull requests. Although not active anymore, the searchable archive may still contain useful information. <!-- Links -->
Project: Gloo (Orchestration & Management / API Gateway)
File: string.proto.sk.md

title: "string.proto" weight: 5 <!-- Code generated by solo-kit. DO NOT EDIT. --> Specifies the way to match a string. [#next-free-field: 8] ```yaml "exact": string "prefix": string "suffix": string "safeRegex": .xds.type.matcher.v3.RegexMatcher "contains": string "ignoreCase": bool ``` | Field | Type | Description | | -- | - | -- | | `exact` | `string` | The input string must match exactly the string specified here. Examples: abc only matches the value abc*. Only one of `exact`, `prefix`, `suffix`, `safeRegex`, or `contains` can be set. | | `prefix` | `string` | The input string must have the prefix specified here. Note: empty prefix is not allowed, please use regex instead. Examples: abc matches the value abc.xyz*. Only one of `prefix`, `exact`, `suffix`, `safeRegex`, or `contains` can be set. | | `suffix` | `string` | The input string must have the suffix specified here. Note: empty prefix is not allowed, please use regex instead. Examples: abc matches the value xyz.abc*. Only one of `suffix`, `exact`, `prefix`, `safeRegex`, or `contains` can be set. | | `safeRegex` | | The input string must match the regular expression specified here. Only one of `safeRegex`, `exact`, `prefix`, `suffix`, or `contains` can be set. | | `contains` | `string` | The input string must have the substring specified here. Note: empty contains match is not allowed, please use regex instead. Examples: abc matches the value xyz.abc.def*. Only one of `contains`, `exact`, `prefix`, `suffix`, or `safeRegex` can be set. | | `ignoreCase` | `bool` | If true, indicates the exact/prefix/suffix matching should be case insensitive. This has no effect for the safe_regex match. For example, the matcher data will match both input string Data and data if set to true. | Specifies a list of ways to match a string. ```yaml "patterns": []xds.type.matcher.v3.StringMatcher ``` | Field | Type | Description | | -- | - | -- | | `patterns` | | | <!-- 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: Armada (Orchestration & Management / Scheduling & Orchestration)
File: docs-readme.md

See Docs added to this directory are automatically copied into armadaproject.io. For example, if you wanted to document bananas, and you added `bananas.md`, once committed to master that would be published at `https://armadaproject.io/bananas/`. If you'd like to add a more complex page, such as one with images or other linked assets, you have to be very careful to ensure links will work both for people viewing in github and for those viewing via armadaproject.io. The easiest way to accomplish this is by using page bundles. See quickstart as as example: quickstart/index.md is the actual content, with links to various images using relative pathing; e.g. `./my-image.png`. This is considered a page bundle by jekyll (github pages) and are rendered as a single page at `quickstart/`. In order to get this page bundle pushed to gh-pages branch, you'll need to adjust the github workflow in `.github/workflows/pages.yml` to add your new page bundle as well. If you put a commit here to remove a page, you will need to also commit to the gh-pages branch to remove that page.