cwielenb/CNCF-Dataset huggingface dataset:
Project: Kata Containers (Runtime / Container Runtime)
File: DeviceConfig.md

Name | Type | Description | Notes | - | - | - Path | string | | Iommu | Pointer to bool | | [optional] [default to false] PciSegment | Pointer to int32 | | [optional] Id | Pointer to string | | [optional] `func NewDeviceConfig(path string, ) *DeviceConfig` NewDeviceConfig instantiates a new DeviceConfig object This constructor will assign default values to properties that have it defined, and makes sure properties required by API are set, but the set of arguments will change when the set of required properties is changed `func NewDeviceConfigWithDefaults() *DeviceConfig` NewDeviceConfigWithDefaults instantiates a new DeviceConfig object This constructor will only assign default values to properties that have it defined, but it doesn't guarantee that properties required by API are set `func (o *DeviceConfig) GetPath() string` GetPath returns the Path field if non-nil, zero value otherwise. `func (o DeviceConfig) GetPathOk() (string, bool)` GetPathOk returns a tuple with the Path field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *DeviceConfig) SetPath(v string)` SetPath sets Path field to given value. `func (o *DeviceConfig) GetIommu() bool` GetIommu returns the Iommu field if non-nil, zero value otherwise. `func (o DeviceConfig) GetIommuOk() (bool, bool)` GetIommuOk returns a tuple with the Iommu field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *DeviceConfig) SetIommu(v bool)` SetIommu sets Iommu field to given value. `func (o *DeviceConfig) HasIommu() bool` HasIommu returns a boolean if a field has been set. `func (o *DeviceConfig) GetPciSegment() int32` GetPciSegment returns the PciSegment field if non-nil, zero value otherwise. `func (o DeviceConfig) GetPciSegmentOk() (int32, bool)` GetPciSegmentOk returns a tuple with the PciSegment field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *DeviceConfig) SetPciSegment(v int32)` SetPciSegment sets PciSegment field to given value. `func (o *DeviceConfig) HasPciSegment() bool` HasPciSegment returns a boolean if a field has been set. `func (o *DeviceConfig) GetId() string` GetId returns the Id field if non-nil, zero value otherwise. `func (o DeviceConfig) GetIdOk() (string, bool)` GetIdOk returns a tuple with the Id field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *DeviceConfig) SetId(v string)` SetId sets Id field to given value. `func (o *DeviceConfig) HasId() bool` HasId returns a boolean if a field has been set.
Project: rkt (Runtime / Container Runtime)
File: packaging.md

This document aims to provide information about packaging rkt in Linux distributions. It covers dependencies, file ownership and permissions, and tips to observe packaging policies. Please see . By default, the rkt build will download a CoreOS Container Linux PXE image from the internet and extract some binaries, such as `systemd-nspawn` and `bash`. However, some packaging environments don't allow internet access during the build. To work around this, download the Container Linux PXE image before starting the build process, and use the `--with-coreos-local-pxe-image-path` and `--with-coreos-local-pxe-image-systemd-version` parameters. For more details, see the . Most Linux distributions don't allow the use of prebuilt binaries, or reuse of code that is already otherwise packaged. systemd falls in this category, as Debian and Fedora already package systemd, and rkt needs systemd. The configure script's `--with-stage1-flavors` option can be set to `host` to avoid rkt's dependency on systemd in these environments: ``` ./configure --with-stage1-flavors=host ``` The `stage1-host.aci` archive generated by this build will not contain bash, systemd, or any other binaries from external sources. The binaries embedded in the stage1 archive are all built from the sources in the rkt git repository. The external binaries needed by this `stage1-host.aci` are copied from the host at run time. Packages using the `--with-stage1-flavors=host` option must therefore add a run-time dependency on systemd and bash. Whenever systemd and bash are upgraded on the host, rkt will use the new version at run time. It becomes the packager's responsibility to test the rkt package whenever a new version of systemd is packaged. For more details, see the . rkt uses to maintain . Please see . In general, subdirectories of `/var/lib/rkt`, and `/etc/rkt` should be created with the same ownership and permissions as described in the . Any rkt package should create a system group `rkt`, and `rkt-admin`. The directory `/var/lib/rkt` should belong to group `rkt` with the `setgid` bit set (`chmod g+s`). The directory `/etc/rkt` should belong to group `rkt-admin` with the `setgid` bit set (`chmod g+s`). When the ownership and permissions of `/var/lib/rkt` are set up correctly, members of group `rkt` should be able to fetch ACIs. Members of group `rkt-admin` should be able to trust GPG keys, and add additional configurations in `/etc/rkt`. Root privilege is still required to run pods. The motivation to have separate `rkt`, and `rkt-admin` groups is that the person who makes administrative changes would likely be different than the unprivileged user who is able to fetch. A few are included in the rkt sources. These units demonstrate systemd-managed units to run the rkt with socket-activation, the rkt , and a periodic service invoked at 12-hour intervals to purge dead pods.
Project: containerd (Runtime / Container Runtime)
File: LICENSE.md

Copyright (C) 2021 Matt Layher 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. ARE.
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-dbg_prefilter.md

<!-- This file was autogenerated via cilium cmdref, do not edit manually--> Manage XDP CIDR filters ``` -h, --help help for prefilter ``` ``` --config string Config file (default is $HOME/.cilium.yaml) -D, --debug Enable debug messages -H, --host string URI to server-side API ``` - CLI - Delete CIDR filters - List CIDR filters - Update CIDR filters
Project: ORAS (Runtime / Cloud Native Storage)
File: PULL_REQUEST_TEMPLATE.md

What this PR does / why we need it: Which issue(s) this PR fixes (optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged): Fixes # Please check the following list: [ ] Does the affected code have corresponding tests, e.g. unit test, E2E test? [ ] Does this change require a documentation update? [ ] Does this introduce breaking changes that would require an announcement or bumping the major version? [ ] Do all new files have an appropriate license header? <!-- If this is a security issue, please do not discuss on GitHub. Please report any suspected or confirmed security issues directly to https://github.com/oras-project/oras/blob/main/OWNERS.md. -->
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-dbg_bpf_nodeid_list.md

<!-- This file was autogenerated via cilium cmdref, do not edit manually--> List node IDs and their IP addresses List node IDs and their IP addresses. ``` cilium-dbg bpf nodeid list [flags] ``` ``` -h, --help help for list -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 the node IDs
Project: Velero (Runtime / Cloud Native Storage)
File: ark_client.md

title: "ark client" layout: docs Ark client related commands Ark client related commands ``` -h, --help help for client ``` ``` --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 ``` - Back up and restore Kubernetes cluster resources. - Get and set client configuration file values
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-dbg_map_get.md

<!-- This file was autogenerated via cilium cmdref, do not edit manually--> Display cached content of given BPF map ``` cilium-dbg map get <name> [flags] ``` ``` cilium map get cilium_ipcache ``` ``` -h, --help help for get -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 ``` - Access userspace cached content of BPF maps
Project: Spiderpool (Runtime / Cloud Native Network)
File: plugin-ifacer.md

When Pods use VLAN networks, network administrators may need to manually configure various VLAN or Bond interfaces on the nodes in advance. This process can be tedious and error-prone. Spiderpool provides a CNI meta-plugin called `ifacer`. This plugin dynamically creates VLAN sub-interfaces or Bond interfaces on the nodes during Pod creation, based on the provided `ifacer` configuration, greatly simplifying the configuration workload. In the following sections, we will delve into this plugin. Support dynamic creation of VLAN sub-interfaces Support dynamic creation of Bond interfaces The VLAN/Bond interfaces created by this plugin will be lost when the node restarts, but they will be automatically recreated upon the Pod restarts. Deleting existed VLAN/Bond interfaces is not supported. Configuring the address of VLAN/Bond interfaces during creation is not supported. If your OS(such as Fedora, CentOS, etc.) uses NetworkManager, Highly recommend configuring following configuration file at `/etc/NetworkManager/conf.d/spidernet.conf` to prevent interference from NetworkManager with Vlan and Bond interfaces created by `Ifacer`: ```shell ~# INTERFACE=<yourinterfacename> ~# cat > /etc/NetworkManager/conf.d/spidernet.conf <<EOF [keyfile] unmanaged-devices=interface-name:^veth*;interface-name:${IFACER_INTERFACE} EOF ~# systemctl restart NetworkManager ``` There are no specific requirements including Kubernetes or Kernel versions for using this plugin. During the installation of Spiderpool, the plugin will be automatically installed in the `/opt/cni/bin/` directory on each host. You can verify by checking for the presence of the `ifacer` binary in that directory on each host. Examples please see
Project: CubeFS (Runtime / Cloud Native Storage)
File: quota.md

::: warning Note Quota management is a new feature added in v3.2.1. ::: Limits the number of files or directories within a single directory to avoid the occurrence of excessively large directories, which could exhaust the resources of MP nodes. The default limit for the number of children in each directory is 20 million, which can be configured with a minimum value of 1 million and no upper limit. If the number of children created under a single directory exceeds the limit, the creation fails. The configured limit value takes effect on the entire cluster and is persisted on the master. Full support requires upgrading the client, metadata node, and master to version 3.2.1. ```bash curl -v "http://192.168.0.11:17010/setClusterInfo?dirQuota=20000000" ``` ::: tip Note `192.168.0.11` is the IP address of the master, and the same applies below. ::: | Parameter | Type | Description | |--|--|-| | dirQuota | uint32 | Quota value | ```bash curl -v "http://192.168.0.11:17010/admin/getIp" ``` The response is as follows: ```json { "code": 0, "data": { "Cluster": "test", "DataNodeAutoRepairLimitRate": 0, "DataNodeDeleteLimitRate": 0, "DirChildrenNumLimit": 20000000, "EbsAddr": "", "Ip": "192.168.0.1", "MetaNodeDeleteBatchCount": 0, "MetaNodeDeleteWorkerSleepMs": 0, "ServicePath": "" }, "msg": "success" } ``` The `DirChildrenNumLimit` field is the directory quota value for the current cluster.
Project: Flannel (Runtime / Cloud Native Network)
File: ISSUE_TEMPLATE.md

<! Provide a general summary of the issue in the Title above --> <! If you're describing a bug, tell us what should happen --> <! If you're suggesting a change/improvement, tell us how it should work --> <! If describing a bug, tell us what happens instead of the expected behavior --> <! If suggesting a change/improvement, explain the difference from current behavior --> <! Not obligatory, but suggest a fix/reason for the bug, --> <! or ideas how to implement the addition or change --> <! Provide a link to a live example, or an unambiguous set of steps to --> <! reproduce this bug. Include code to reproduce, if relevant --> <! How has this issue affected you? What are you trying to accomplish? --> <! Providing context helps us come up with a solution that is most useful in the real world --> <! Include as many relevant details about the environment you experienced the bug in --> Flannel version: Backend used (e.g. vxlan or udp): Etcd version: Kubernetes version (if used): Operating System and version: Link to your project (optional):
Project: Kata Containers (Runtime / Container Runtime)
File: Licensing-strategy.md

The license for the project is . All repositories in the project have a top level file called `LICENSE`. This file lists full details of all licences used by the repository. Where possible all files in all repositories also contain a license identifier. This provides fine-grained licensing and allows automated tooling to check the license of individual files. This SPDX licence identifier requirement is enforced by the .
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-dbg_bpf_recorder.md

<!-- This file was autogenerated via cilium cmdref, do not edit manually--> PCAP recorder ``` -h, --help help for recorder ``` ``` --config string Config file (default is $HOME/.cilium.yaml) -D, --debug Enable debug messages -H, --host string URI to server-side API ``` - Direct access to local BPF maps - List PCAP recorder entries
Project: FabEdge (Runtime / Cloud Native Network)
File: CHANGELOG-1.0.0.md

Added: Connector HA is implemented; More calico modes are supported; Flannel host-gw mode is supported; Fixed: Fix the bug that nodePort service doesn't work on cloud side; Fix the bug that cloud-agent lost connections to connector after connector reboot; Fix the bug that fabedge-agent can't initialize tunnels if strongswan container reboot;
Project: Firecracker (Runtime / Container Runtime)
File: network-performance.md

This document provides details about Firecracker network performance. The numbers presented are dependent on the hardware (CPU, networking card, etc.), OS version and settings. Scope of the measurements is to illustrate the limits for the emulation thread. | Segment size/ Direction | 1460bytes | 256bytes | 128bytes | 96bytes | | -- | | -- | -- | - | | Ingress | 25Gbps | 23Gbps | 20Gbps | 18Gbps | | Egress | 25Gbps | 23Gbps | 20Gbps | 18Gbps | | Bidirectional | 18Gbps | 18Gbps | 18Gbps | 18Gbps | Setup and test description Throughput measurements were done using . The target is to fully saturate the emulation thread and keep it at 100% utilization. No adjustments were done to socket buffer, or any other network related kernel parameters. To identify the limit of emulation thread, TCP throughput was measured between host and guest. An EC2 instance, running , was used as a host. For ingress or egress throughput measurements, a Firecracker microVM running Kernel 4.14 with 4GB of Ram, 8 vCPUs and one network interface was used. The measurements were taken using 6 iperf3 clients running on host and 6 iperf3 serves running on guest and vice versa. For bidirectional throughput measurements, a Firecracker microVM running Amazon Linux 2, Kernel 4.14 with 4GB of Ram, 12 vCPUs and one network interface was used. The measurements were taken using 4 iperf3 clients and 4 iperf3 servers running on both host and guest. The virtualization layer, Firecracker emulation thread plus host kernel stack, is responsible for adding on average 0.06ms of network latency. Setup and test description Latency measurements were done using ping round trip times. 2 x EC2 M5d.metal instances running Amazon Linux 2 within the same were used, with a security group configured so that it would allow traffic from instances using private IPs. A 10Mbps background traffic was running between instances. Round trip time between instances was measured. `rtt min/avg/max/mdev = 0.101/0.198/0.237/0.044 ms` On one of the instances, a Firecracker microVM running Kernel 4.14, with 1 GB of RAM, 2 vCPUs, one network interface running was used. Round trip between the microVM and the other instance was measured, while a 10Mbps background traffic was running. `rtt min/avg/max/mdev = 0.191/0.321/0.519/0.058 ms` From the difference between those we can conclude that ~0.06ms are the virtualization overhead.
Project: CNI-Genie (Runtime / Cloud Native Network)
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: <! If your repo has certain guidelines for contribution, put them here ahead of the general k8s resources --> 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! <! Custom Information - if you're copying this template for the first time you can add custom content here, for example: - Replace `kubernetes-users` with your slack channel string, this will send users directly to your channel. -->
Project: containerd (Runtime / Container Runtime)
File: fuzzy_mode_convert_table.md

| json type \ dest type | bool | int | uint | float |string| | | | | |--|--| | number | positive => true <br/> negative => true <br/> zero => false| 23.2 => 23 <br/> -32.1 => -32| 12.1 => 12 <br/> -12.1 => 0|as normal|same as origin| | string | empty string => false <br/> string "0" => false <br/> other strings => true | "123.32" => 123 <br/> "-123.4" => -123 <br/> "123.23xxxw" => 123 <br/> "abcde12" => 0 <br/> "-32.1" => -32| 13.2 => 13 <br/> -1.1 => 0 |12.1 => 12.1 <br/> -12.3 => -12.3<br/> 12.4xxa => 12.4 <br/> +1.1e2 =>110 |same as origin| | bool | true => true <br/> false => false| true => 1 <br/> false => 0 | true => 1 <br/> false => 0 |true => 1 <br/>false => 0|true => "true" <br/> false => "false"| | object | true | 0 | 0 |0|originnal json| | array | empty array => false <br/> nonempty array => true| [] => 0 <br/> [1,2] => 1 | [] => 0 <br/> [1,2] => 1 |[] => 0<br/>[1,2] => 1|original json|
Project: Antrea (Runtime / Cloud Native Network)
File: getting-started-gif.md

To refresh the gif image included in , follow these steps: install set `PS1="> "` in your bash profile file (e.g. `.bashrc`, `zshrc`, ...) to simplify the prompt record the cast with the correct shell, e.g. `SHELL=zsh asciinema rec my.cast` convert the cast file to a gif file: `docker run --rm -v $PWD:/data -w /data asciinema/asciicast2gif -s 3 -w 120 -h 20 my.cast my.gif` upload the gif file to Github's CDN by following these update the link in by opening a PR
Project: Carina (Runtime / Cloud Native Storage)
File: install.md

Kubernetes cluster with CSI_VERSION = 1.5.0 If running kubelet in docker containerit should mount host 's `/dev:/dev` directory. Linux Kernel 3.10.0-1160.11.1.el7.x86_64 Each node should have multiple raw disks. Carina will ignore nodes with no empty disks. Using `kubectl get pods -n kube-system | grep carina` to check installation status. ```shell $ cd deploy/kubernetes $ ./deploy.sh $ kubectl get pods -n kube-system |grep carina carina-scheduler-6cc9cddb4b-jdt68 0/1 ContainerCreating 0 3s csi-carina-node-6bzfn 0/2 ContainerCreating 0 6s csi-carina-node-flqtk 0/2 ContainerCreating 0 6s csi-carina-provisioner-7df5d47dff-7246v 0/4 ContainerCreating 0 12s ``` Uninstallation ```shell $ cd deploy/kubernetes $ ./deploy.sh uninstall ``` The uninstallation will leave the pod still using carina PV untouched. ``` helm repo add carina-csi-driver https://carina-io.github.io helm search repo -l carina-csi-driver helm install carina-csi-driver carina-csi-driver/carina-csi-driver --namespace kube-system --version v0.9.0 ``` ``` helm uninstall carina-csi-driver helm pull carina-csi-driver/carina-csi-driver --version v0.9.1 tar -zxvf carina-csi-driver-v0.9.1.tgz helm install carina-csi-driver carina-csi-driver/ ```
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-operator_completion.md

<!-- This file was autogenerated via cilium-operator --cmdref, do not edit manually--> Generate the autocompletion script for the specified shell Generate the autocompletion script for cilium-operator for the specified shell. See each sub-command's help for details on how to use the generated script. ``` -h, --help help for completion ``` - Run cilium-operator - Generate the autocompletion script for bash - Generate the autocompletion script for fish - Generate the autocompletion script for powershell - Generate the autocompletion script for zsh