cwielenb/CNCF-Dataset huggingface dataset:
Project: Antrea (Runtime / Cloud Native Network)
File: network-requirements.md

Antrea has a few network requirements to get started, ensure that your hosts and firewalls allow the necessary traffic based on your configuration. | Configuration | Host(s) | ports/protocols | Other | ||-|--|| | Antrea with VXLAN enabled | All | UDP 4789 | | | Antrea with Geneve enabled | All | UDP 6081 | | | Antrea with STT enabled | All | TCP 7471 | | | Antrea with GRE enabled | All | IP Protocol ID 47 | No support for IPv6 clusters | | Antrea with IPsec ESP enabled | All | IP protocol ID 50 and 51, UDP 500 and 4500 | | | Antrea with WireGuard enabled | All | UDP 51820 | | | Antrea Multi-cluster with WireGuard encryption | Multi-cluster Gateway Node | UDP 51821 | | | All | kube-apiserver host | TCP 443 or 6443\* | | | All | All | TCP 10349, 10350, 10351, UDP 10351 | | \* _The value passed to kube-apiserver using the --secure-port flag. If you cannot locate this, check the targetPort value returned by kubectl get svc kubernetes -o yaml._
Project: rkt (Runtime / Container Runtime)
File: gc.md

rkt has a built-in garbage collection command that is designed to be run periodically from a timer or cron job. Stopped pods are moved to the garbage and cleaned up during a subsequent garbage collection pass. Each `gc` pass removes any pods remaining in the garbage past the grace period. . ``` Moving pod "21b1cb32-c156-4d26-82ae-eda1ab60f595" to garbage Moving pod "5dd42e9c-7413-49a9-9113-c2a8327d08ab" to garbage Moving pod "f07a4070-79a9-4db0-ae65-a090c9c393a3" to garbage ``` On the next pass, the pods are removed: ``` Garbage collecting pod "21b1cb32-c156-4d26-82ae-eda1ab60f595" Garbage collecting pod "5dd42e9c-7413-49a9-9113-c2a8327d08ab" Garbage collecting pod "f07a4070-79a9-4db0-ae65-a090c9c393a3" ``` | Flag | Default | Options | Description | | | | | | | `--expire-prepared` | `24h0m0s` | A time | Duration to wait before expiring prepared pods | | `--grace-period` | `30m0s` | A time | Duration to wait before discarding inactive pods from garbage | | `--mark-only` | `false` | `true` or `false` | If set to true, only the "mark" phase of the garbage collection process will be formed (i.e., exited/aborted pods will be moved to the garbage, but nothing will be deleted) | See the table with .
Project: Velero (Runtime / Cloud Native Storage)
File: _index.md

title: Resources description: Velero Resources id: resources Here you will find external resources about Velero, such as videos, podcasts, and community articles. Community Meetings Playlist {{< youtube "videoseries?list=PL7bmigfV0EqQRysvqvqOtRNk4L5S7uqwM" >}} Velero Demo and Deep Dives Playlist {{< youtube "videoseries?list=PL7bmigfV0EqT82eQaVCslWWM4k4d63KyK" >}} Kubecon NA 2019 - How to Backup and Restore Your Kubernetes Cluster - Annette Clewett & Dylan Murray, Red Hat: {{< youtube JyzgS-KKuoo >}} Kubernetes Back Up, Restore and Migration with Velero - A NewStack interview, with guests: Carlisia Thompson, Tom Spoonemore, and Efri Nattel-Shayo: {{< youtube 71NoY5CIcQ8 >}} How to migrate applications between Kubernetes clusters using Velero: {{< youtube IZlwKMoqBqE >}} TGIK 080: Velero 1.0: {{< youtube tj5Ey2bHsfM >}} Watch our recent webinar on backup and migration strategies: {{< youtube csrSPt3HFtg >}} Velero demo by Just me and Opensource - [ Kube 45 ] Velero - Backup & Restore Kubernetes Cluster: {{< youtube C9hzrexaIDA >}}
Project: Soda Foundation (Runtime / Cloud Native Storage)
File: MAINTAINERS.md

This page lists all active maintainers of this repository. If you were a maintainer and would like to add your name to the Emeritus list, please send us a PR. See for governance guidelines and how to become a maintainer. See for general contribution guidelines. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-dbg_kvstore_get.md

<!-- This file was autogenerated via cilium cmdref, do not edit manually--> Retrieve a key ``` cilium-dbg kvstore get [options] <key> [flags] ``` ``` cilium kvstore get --recursive foo ``` ``` -h, --help help for get -o, --output string json| yaml| jsonpath='{}' --recursive Recursive lookup ``` ``` --config string Config file (default is $HOME/.cilium.yaml) -D, --debug Enable debug messages -H, --host string URI to server-side API --kvstore string Key-Value Store type --kvstore-opt map Key-Value Store options ``` - Direct access to the kvstore
Project: MinIO (Runtime / Cloud Native Storage)
File: VULNERABILITY_REPORT.md

This document formally describes the process of addressing and managing a reported vulnerability that has been found in the MinIO server code base, any directly connected ecosystem component or a direct / indirect dependency of the code base. The vulnerability management policy described in this document covers the process of investigating, assessing and resolving a vulnerability report opened by a MinIO employee or an external third party. Therefore, it lists pre-conditions and actions that should be performed to resolve and fix a reported vulnerability. The vulnerability management process requires that the vulnerability report contains the following information: The project / component that contains the reported vulnerability. A description of the vulnerability. In particular, the type of the reported vulnerability and how it might be exploited. Alternatively, a well-established vulnerability identifier, e.g. CVE number, can be used instead. Based on the description mentioned above, a MinIO engineer or security team member investigates: Whether the reported vulnerability exists. The conditions that are required such that the vulnerability can be exploited. The steps required to fix the vulnerability. In general, if the vulnerability exists in one of the MinIO code bases itself - not in a code dependency - then MinIO will, if possible, fix the vulnerability or implement reasonable countermeasures such that the vulnerability cannot be exploited anymore.
Project: Spiderpool (Runtime / Cloud Native Network)
File: ippoolcr.md

| Case ID | Title | Priority | Smoke | Status | Other | | - |-|-|-|--| -- | | D00001 | An IPPool fails to add an IP that already exists in an other IPPool | p2 | | done | | | D00002 | Add a route with `routes` and `gateway` fields in the ippool spec, which only takes effect on the new pod and does not on the old pods | p2 | smoke | done | | | D00003 | Failed to add wrong IPPool gateway and route to an IPPool CR | p2 | | done | | | D00004 | Failed to delete an IPPool whose IP is not de-allocated at all | p2 | | done | | | D00005 | A "true" value of IPPool/Spec/disabled should forbid IP allocation, but still allow ip de-allocation | p2 | | done | | | D00006 | Successfully create and delete IPPools in batch | p2 | | done | | | D00007 | Add, delete, modify, and query ippools that are created manually | p1 | | done | | | D00008 | Manually ippool inherits subnet attributes (including gateway,routes, etc.) | p3 | | done | | | D00009 | multusName matches, IP can be assigned | p2 | | done | | | D00010 | multusName mismatch, unable to assign IP | p3 | | done | | | D00011 | The node where the pod is located matches the nodeName, and the IP can be assigned | p2 | | done | | | D00012 | The node where the pod resides does not match the nodeName, and the IP cannot be assigned | p3 | | done | | | D00013 | nodeName has higher priority than nodeAffinity | p3 | | done | | | D00014 | The namespace where the pod is located matches the namespaceName, and the IP can be assigned | p2 | | done | | | D00015 | The namespace where the pod resides does not match the namespaceName, and the IP cannot be assigned | p2 | | done | | | D00016 | namespaceName has higher priority than namespaceAffinity | p3 | | done | |
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-bugtool_completion_bash.md

<!-- This file was autogenerated via cilium cmdref, do not edit manually--> Generate the autocompletion script for bash Generate the autocompletion script for the bash shell. This script depends on the 'bash-completion' package. If it is not installed already, you can install it via your OS's package manager. To load completions in your current shell session: source <(cilium-bugtool completion bash) To load completions for every new session, execute once: cilium-bugtool completion bash > /etc/bash_completion.d/cilium-bugtool cilium-bugtool completion bash > $(brew --prefix)/etc/bash_completion.d/cilium-bugtool You will need to start a new shell for this setup to take effect. ``` cilium-bugtool completion bash ``` ``` -h, --help help for bash --no-descriptions disable completion descriptions ``` - Generate the autocompletion script for the specified shell
Project: Zenko (Runtime / Cloud Native Storage)
File: release.md

To release the Zenko and Zenko-base ISOs: Update the version in the `VERSION` file and merge the changes (e.g., `2.4.15`). Start a new promotion using the Select the branch to release. Specify the tag from the step 1 (e.g., `2.4.15`). Specify the artifacts name to promote. The artifact URL can be found in the commit build you want to promote, under `Annotations`. For example, given `https://artifacts.scality.net/builds/github:scality:Zenko:staging-d13ed9e848.build-iso-and-end2end-test.230` the name will be `github:scality:Zenko:staging-d13ed9e848.build-iso-and-end2end-test.230` The workflow will automatically create a new GitHub release.
Project: Inclavare Containers (Runtime / Container Runtime)
File: running_skeleton_with_rune_attest_command.md

This guide will guide you how to use remote attestation based on SGX in skeleton with rune. Currently `rune attest` can only run on the machines with , we will support as soon as possible. Build a skeleton bundle according to from scratch. Build rune according to . Register a `SPID` and `Subscription Key` of to get IAS report(optional). After the registration, Intel will respond with a SPID which is needed to communicate with IAS. Before using `rune attest` command, you must ensure your skeleton container/bundles(such as skeleton-enclave-container) running by setting `"wait_timeout","100"` of `process.args` in config.json as following: ```json "process": { "args": [ "${YOURPROGRAM}","waittimeout","100" ], } ``` Only `liberpal-skeleton-v3.so` supports `rune attest` command. So you also need to configure enclave runtime as following: ```json "annotations": { "enclave.type": "intelSgx", "enclave.runtime.path": "/usr/lib/liberpal-skeleton-v3.so", "enclave.runtime.args": "debug" } ``` If you want to use `rune attest` command to get IAS report, you also need to `delete` the `network` namespace configuration in your `config.json` to ensure you run skeleton in host network mode. After doing this, your `namespaces` is as following without the `network` type namespace: ```json "namespaces": [ { "type": "pid" }, { "type": "ipc" }, { "type": "uts" }, { "type": "mount" } ], ``` Then you can run your skeleton containers by typing the following commands: ```shell cd "$HOME/rune_workdir/rune-container" cp /etc/resolv.conf rootfs/etc/resolv.conf sudo rune --debug run skeleton-enclave-container ``` You can type the following command to use `rune attest` command with skeleton in another shell to get local report: ```shell rune --debug attest --quote-type={SGXQUOTETYPE} skeleton-enclave-container ``` where: @quote-type: specify the quote types of sgx, such as, `epidUnlinkable`: `epidLinkable`: `ecdsa`: . Note `rune attest` currently doesn't support the ecdsa quote type, and we will support it soon. You can type the following command to use `rune attest` command with skeleton in another shell to get IAS report: ```shell rune --debug attest --isRA \ --quote-type={SGXQUOTETYPE} \ --spid=${EPID_SPID} \ --subscription-key=${EPIDSUBSCRIPTIONKEY} \ skeleton-enclave-container ``` where: @isRA: specify the type of report is local or remote report. @quote-type: specify the quote types of sgx which is the same as the parameters of . @spid: specify the `SPID`. @subscription-key: specify the `Subscription Key`.
Project: Soda Foundation (Runtime / Cloud Native Storage)
File: Community-Contributing.md

](https://goreportcard.com/report/github.com/sodafoundation/api) ](https://travis-ci.org/sodafoundation/api) ](https://coveralls.io/github/sodafoundation/api?branch=master) <img src="https://www.opensds.io/wp-content/uploads/sites/18/2016/11/logo_opensds.png" width="100"> opensds is Apache 2.0 licensed and accepts contributions via GitHub pull requests. This document outlines some of the conventions on commit message formatting, contact points for developers and other resources to make getting your contribution into opensds easier. Email: Slack: # Before you start, NOTICE that ```master``` branch is the relatively stable version provided for customers and users. So all code modifications SHOULD be submitted to ```development``` branch. Fork the repository on GitHub. Read the README.md and INSTALL.md for project information and build instructions. For those who just get in touch with this project recently, here is a proposed contributing . The coding style suggested by the Golang community is used in opensds. See the for more details. Please follow this style to make opensds easy to review, maintain and develop. A great way to contribute to the project is to send a detailed report when you encounter an issue. We always appreciate a well-written, thorough bug report, and will thank you for it! When reporting issues, refer to this format: What version of env (opensds, os, golang etc) are you using? Is this a BUG REPORT or FEATURE REQUEST? What happened? What you expected to happen? How to reproduce it?(as minimally and precisely as possible) Raise your idea as an If it is a new feature that needs lots of design details, a design proposal should also be submitted . After reaching consensus in the issue discussions and design proposal reviews, complete the development on the forked repo and submit a PR. Here are the that are already closed. If a PR is submitted by one of the core members, it has to be merged by a different core member. After PR is sufficiently discussed, it will get merged, abondoned or rejected depending on the outcome of the discussion. Thank you for your contribution !
Project: CubeFS (Runtime / Cloud Native Storage)
File: build.md

First, please confirm that you use the command `PORTABLE=1 make static_lib` to compile rocksdb. Then use the `ldd` command to check if the dependent libraries are installed on the machine. After installing the missing libraries, execute the `ldconfig` command. There are two ways to solve this problem: Add the specified library to `CGOLDFLAGS` to compile, for example: `CGOLDFLAGS="-L/usr/local/lib -lrocksdb -lzstd"`. This method requires that the zstd library is also installed on other deployment machines. Delete the script that automatically detects whether the zstd library is installed. The file location is an example: `rockdb-5.9.2/buildtools/builddetect_platform`. Delete the following content: ```bash $CXX $CFLAGS $COMMON_FLAGS -x c++ - -o /dev/null 2>/dev/null <<EOF int main() {} EOF if [ "$?" = 0 ]; then COMMONFLAGS="$COMMONFLAGS -DZSTD" PLATFORMLDFLAGS="$PLATFORMLDFLAGS -lzstd" JAVALDFLAGS="$JAVALDFLAGS -lzstd" fi ``` When compiling the erasure coding subsystem, an error message is displayed: `fatal error: rocksdb/c.h: no such file or directory...` First, confirm whether the file pointed to by the error message exists in the `.deps/include/rocksdb` directory. If it exists, try `source env.sh` and try again. If the file does not exist or the error still occurs, you can delete all the rocksdb-related files in the `.deps` directory and then recompile. To resolve the error message "/usr/bin/ld: cannot find -lbz2" during compilation, you should check if the "bzip2-devel" package is installed with a version of 1.0.6 or higher. To resolve the error message "/usr/bin/ld: cannot find -lz" during compilation, you should check if the "zlib-devel" package is installed with a version of 1.2.7 or higher. when building `blobstore`, just enter sub-folder `blobstore` and add following content to the end of `blobstore/env.sh` before executing `source env.sh`: ```bash export DISABLEWARNINGAS_ERROR=true ``` when building `cubefs` itself, just add following content at the end of `env.sh` before executing `source env.sh`: NOTE: Options might be different according to different gcc versions. Following option has been tested on `gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0` ```bash export CXXFLAGS=-Wno-error=xxx # optional, developers can change accordingly or comment out or delete it safely ```
Project: Velero (Runtime / Cloud Native Storage)
File: ark_restic_repo_get.md

title: "ark restic repo get" layout: docs Get restic repositories Get restic repositories ``` ark restic repo get [flags] ``` ``` -h, --help help for get --label-columns stringArray a comma-separated list of labels to be displayed as columns -o, --output string Output display format. For create commands, display the object but do not send it to the server. Valid formats are 'table', 'json', and 'yaml'. (default "table") -l, --selector string only show items matching this label selector --show-labels show labels in the last column ``` ``` --alsologtostderr log to standard error as well as files --kubeconfig string Path to the kubeconfig file to use to talk to the Kubernetes apiserver. If unset, try the environment variable KUBECONFIG, as well as in-cluster configuration --kubecontext string The context to use to talk to the Kubernetes apiserver. If unset defaults to whatever your current-context is (kubectl config current-context) --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 --logtostderr log to standard error instead of files -n, --namespace string The namespace in which Ark should operate (default "heptio-ark") --stderrthreshold severity logs at or above this threshold go to stderr (default 2) -v, --v Level log level for V logs --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging ``` - Work with restic repositories
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-dbg_bpf_policy_get.md

<!-- This file was autogenerated via cilium cmdref, do not edit manually--> Get contents of a policy BPF map ``` cilium-dbg bpf policy get [flags] ``` ``` --all Dump all policy maps -h, --help help for get -n, --numeric Do not resolve IDs -o, --output string json| yaml| jsonpath='{}' ``` ``` --config string Config file (default is $HOME/.cilium.yaml) -D, --debug Enable debug messages -H, --host string URI to server-side API ``` - Manage policy related BPF maps
Project: CRI-O (Runtime / Container Runtime)
File: MAINTAINERS.md

This page lists all active maintainers of this repository. If you were a maintainer and would like to add your name to the Emeritus list, please send us a PR. See for governance guidelines and how to become a maintainer. See for general contribution guidelines. , Datadog, Inc. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC
Project: Submariner (Runtime / Cloud Native Network)
File: flaking-test.md

name: Flaking Test about: Report flaky tests or jobs in Submariner CI labels: flake <!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Submariner CI --> Which jobs are flaking: Which test(s) are flaking: Testgrid link: Reason for failure: Anything else we need to know:
Project: Antrea (Runtime / Cloud Native Network)
File: api.md

This document lists all the API resource versions currently supported by Antrea Mulit-cluster. Antrea Multi-cluster is supported since v1.5.0. Most Custom Resource Definitions (CRDs) used by Antrea Multi-cluster are in the API group `multicluster.crd.antrea.io`, and two CRDs from are in group `multicluster.x-k8s.io` which is defined by Kubernetes upstream . | CRD | CRD version | Introduced in | Deprecated in / Planned Deprecation | Planned Removal | | | -- | - | -- | | | `ClusterSets` | v1alpha2 | v1.13.0 | N/A | N/A | | `MemberClusterAnnounces` | v1alpha1 | v1.5.0 | N/A | N/A | | `ResourceExports` | v1alpha1 | v1.5.0 | N/A | N/A | | `ResourceImports` | v1alpha1 | v1.5.0 | N/A | N/A | | `Gateway` | v1alpha1 | v1.7.0 | N/A | N/A | | `ClusterInfoImport` | v1alpha1 | v1.7.0 | N/A | N/A | | CRD | CRD version | Introduced in | Deprecated in / Planned Deprecation | Planned Removal | | - | -- | - | -- | | | `ServiceExports` | v1alpha1 | v1.5.0 | N/A | N/A | | `ServiceImports` | v1alpha1 | v1.5.0 | N/A | N/A | | CRD | API group | CRD version | Introduced in | Deprecated in | Removed in | | | - | -- | - | - | - | | `ClusterClaims` | `multicluster.crd.antrea.io` | v1alpha1 | v1.5.0 | v1.8.0 | v1.8.0 | | `ClusterClaims` | `multicluster.crd.antrea.io` | v1alpha2 | v1.8.0 | v1.13.0 | v1.13.0 | | `ClusterSets` | `multicluster.crd.antrea.io` | v1alpha1 | v1.5.0 | v1.13.0 | N/A |
Project: OpenEBS (Runtime / Cloud Native Storage)
File: features.md

<!-- This is for pull requesting new features, improvements and changes! For fixing bugs use https://github.com/openebs/openebs/compare/?template=bugs.md --> <!-- Don't forget to follow code style, and update documentation and tests if needed --> <!-- If you can't answer some sections, please delete them --> <!-- Describe your changes in detail --> <!-- Why is this change required? How can it benefit other users? --> <!-- If it is from an open issue, please link to the issue here --> <!-- Please describe in detail how you tested your changes --> <!-- Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc <!-- Will your changes brake backward compatibility or not? --> <!-- Add screenshots of your changes -->
Project: Antrea (Runtime / Cloud Native Network)
File: code-generation.md

Antrea uses , and to generate CNI gRPC service code. If you make any change to , you can re-generate the code by invoking `make codegen`. Antrea extends Kubernetes API with an extension APIServer and Custom Resource Definitions, and uses [k8s.io/code-generator (release-1.18)](https://github.com/kubernetes/code-generator/tree/release-1.18) to generate clients, informers, conversions, protobuf codecs and other helpers. The resource definitions and their generated codes are located in the conventional paths: `pkg/apis/<resource group>` for internal types and `pkg/apis/<resource group>/<version>` for versioned types and `pkg/client/clientset` for clients. If you make any change to any `types.go`, you can re-generate the code by invoking `make codegen`. Antrea uses the framework for its unit tests. If you add or modify interfaces that need to be mocked, please add or update `MOCKGEN_TARGETS` in accordingly. All the mocks for a given package will typically be generated in a sub-package called `testing`. For example, the mock code for the interface `Baz` defined in the package `pkg/foo/bar` will be generated to `pkg/foo/bar/testing/mock_bar.go`, and you can import it via `pkg/foo/bar/testing`. Same as above, you can re-generate the mock source code (with `mockgen`) by invoking `make codegen`. contains a list of supported metrics, which could be affected by third party component changes. The collection of metrics is done from a running Kind deployment, in order to reflect the current list of metrics which is exposed by Antrea Controller and Agents. To regenerate the metrics list within the document, use with document location as a parameter.