cwielenb/CNCF-Dataset huggingface dataset:
Project: lxd (Runtime / Container Runtime)
File: requirements.md

(requirements-go)= Incus requires Go 1.21 or higher and is only tested with the Golang compiler. We recommend having at least 2GiB of RAM to allow the build to complete. The minimum supported kernel version is 5.4. Incus requires a kernel with support for: Namespaces (`pid`, `net`, `uts`, `ipc` and `mount`) Seccomp Native Linux AIO (, etc.) The following optional features also require extra kernel options: Namespaces (`user` and `cgroup`) AppArmor (including Ubuntu patch for mount mediation) Control Groups (`blkio`, `cpuset`, `devices`, `memory` and `pids`) CRIU (exact details to be found with CRIU upstream) As well as any other kernel feature required by the LXC version in use. Incus requires LXC 5.0.0 or higher with the following build options: `apparmor` (if using Incus' AppArmor support) `seccomp` To run recent version of various distributions, including Ubuntu, LXCFS should also be installed. For virtual machines, QEMU 6.0 or higher is required. Incus uses `cowsql` for its database, to build and set it up, you can run `make deps`. Incus itself also uses a number of (usually packaged) C libraries: `libacl1` `libcap2` `libuv1` (for `cowsql`) `libsqlite3` >= 3.25.0 (for `cowsql`) Make sure you have all these libraries themselves and their development headers (`-dev` packages) installed.
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-bugtool_completion_fish.md

<!-- This file was autogenerated via cilium cmdref, do not edit manually--> Generate the autocompletion script for fish Generate the autocompletion script for the fish shell. To load completions in your current shell session: cilium-bugtool completion fish | source To load completions for every new session, execute once: cilium-bugtool completion fish > ~/.config/fish/completions/cilium-bugtool.fish You will need to start a new shell for this setup to take effect. ``` cilium-bugtool completion fish [flags] ``` ``` -h, --help help for fish --no-descriptions disable completion descriptions ``` - Generate the autocompletion script for the specified shell
Project: Inclavare Containers (Runtime / Container Runtime)
File: README-zh_CN.md

containerd-shim-rune-v2 is a shim for Inclavare Containers(runE). Carrier is a abstract framework to build an enclave for the specified enclave runtime (OcclumGraphene ..) . Go 1.13.x or above. ```bash mkdir -p $GOPATH/src/github.com/alibaba cd $GOPATH/src/github.com/alibaba git clone https://github.com/alibaba/inclavare-containers.git cd shim GOOS=linux make binaries make install ls -l /usr/local/bin/containerd-shim-rune-v2 ``` The Configuration file of Inclavare Containers MUST BE placed into `/etc/inclavare-containers/config.toml` ```toml log_level = "info" # "debug" "info" "warn" "error" sgxtoolsign = "/opt/intel/sgxsdk/bin/x64/sgx_sign" [containerd] socket = "/run/containerd/containerd.sock" [epm] socket = "/var/run/epm/epm.sock" [enclave_runtime] signature_method = "server" [enclave_runtime.occlum] enclaveruntimepath = "/opt/occlum/build/lib/libocclum-pal.so" enclavelibospath = "/opt/occlum/build/lib/libocclum-libos.so" [enclave_runtime.graphene] ``` Modify containerd configuration file(/etc/containerd/config.toml) and add runtimes rune into it. ```toml [plugins.cri.containerd.runtimes.rune] runtime_type = "io.containerd.rune.v2" ``` Add RuntimeClass rune into your kubernetes cluster. ```bash cat <<EOF | kubectl create -f - apiVersion: node.k8s.io/v1beta1 kind: RuntimeClass metadata: name: rune handler: rune scheduling: nodeSelector: EOF ``` ```bash cat <<EOF | kubectl create -f - apiVersion: v1 kind: Pod metadata: labels: run: helloworld-in-tee name: helloworld-in-tee spec: runtimeClassName: rune containers: command: /bin/hello_world env: name: RUNE_CARRIER value: occlum image: registry.cn-shanghai.aliyuncs.com/larus-test/hello-world:v2 imagePullPolicy: IfNotPresent name: helloworld workingDir: /var/run/rune EOF ```
Project: Velero (Runtime / Cloud Native Storage)
File: ark_restore_delete.md

title: "ark restore delete" layout: docs Delete a restore Delete a restore ``` ark restore delete NAME [flags] ``` ``` -h, --help help for delete ``` ``` --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 restores
Project: Rook (Runtime / Cloud Native Storage)
File: ceph-object-zone-crd.md

title: CephObjectZone CRD Rook allows creation of zones in a ceph cluster for a configuration through a CRD. The following settings are available for Ceph object store zones. ```yaml apiVersion: ceph.rook.io/v1 kind: CephObjectZone metadata: name: zone-a namespace: rook-ceph spec: zoneGroup: zonegroup-a metadataPool: failureDomain: host replicated: size: 3 dataPool: failureDomain: osd erasureCoded: dataChunks: 2 codingChunks: 1 customEndpoints: "http://rgw-a.fqdn" preservePoolsOnDelete: true ``` `name`: The name of the object zone to create `namespace`: The namespace of the Rook cluster where the object zone is created. The pools allow all of the settings defined in the Pool CRD spec. For more details, see the settings. In the example above, there must be at least three hosts (size 3) and at least three devices (2 data + 1 coding chunks) in the cluster. `zonegroup`: The object zonegroup in which the zone will be created. This matches the name of the object zone group CRD. `metadataPool`: The settings used to create all of the object store metadata pools. Must use replication. `dataPool`: The settings to create the object store data pool. Can use replication or erasure coding. `customEndpoints`: Specify the endpoint(s) that will accept multisite replication traffic for this zone. You may include the port in the definition if necessary. For example: "https://my-object-store.my-domain.net:443". By default, Rook will set this to the DNS name of the ClusterIP Service created for the CephObjectStore that corresponds to this zone. Most multisite configurations will not exist within the same Kubernetes cluster, meaning the default value will not be useful. In these cases, you will be required to create your own custom ingress resource for the CephObjectStore in order to make the zone available for replication. You must add the endpoint for your custom ingress resource to this list to allow the store to accept replication traffic. In the case of multiple stores (or multiple endpoints for a single store), you are not required to put all endpoints in this list. Only specify the endpoints that should be used for replication traffic. If you update `customEndpoints` to return to an empty list, you must the Rook operator to automatically add the CephObjectStore service endpoint to Ceph's internal configuration. `preservePoolsOnDelete`: If it is set to 'true' the pools used to support the CephObjectZone will remain when it is deleted. This is a security measure to avoid accidental loss of data. It is set to 'true' by default. It is better to check whether data synced with other peer zones before triggering the deletion to avoid accidental loss of data via steps mentioned When deleting a CephObjectZone, deletion will be blocked until all `CephObjectStores` belonging to the zone are removed.
Project: rkt (Runtime / Container Runtime)
File: quickstart-dev.md

This is an example configuration and quick start guide for the installation of rkt from source on Ubuntu 16.04 GNOME. For a detailed developer's reference, see . In this example ~/Repos is a personal workspace where all repos are stored ```sh $ mkdir ~/Repos && cd ~/Repos $ mkdir -p ~/.local/gopath/src/github.com/rkt $ sudo apt-get install git $ git -C ~/.local/gopath/src/github.com/rkt clone https://github.com/rkt/rkt.git $ ln -s ~/.local/gopath/src/github.com/rkt/rkt rkt ``` On a fresh system installation, few additional software packages are needed to correctly build rkt: ```sh $ sudo ~/Repos/rkt/scripts/install-deps-debian-sid.sh ``` See also . ``` $ cd ~/Downloads $ wget https://storage.googleapis.com/golang/go1.6.1.linux-amd64.tar.gz $ tar -xvf go1.6.1.linux-amd64.tar.gz $ mv go ~/.local ``` Add GO variables to .bashrc file: ```sh export PATH=~/.local/bin:~/.local/go/bin:$PATH export GOPATH=~/.local/gopath export GOROOT=~/.local/go ``` Ccache can save a lot of time. If you build a kernel once, most of the compiled code can just be taken from the cache. Ccache can be configured in a few easy steps: ```sh $ sudo apt-get install ccache $ ccache --max-size=10G $ sudo ln -s /usr/bin/ccache /usr/local/bin/gcc ``` The maximum cache size is 10GB now (the default value is too small to cache kernel compilation). Run the autogen and configure commands with the relevant arguments, for example (kvm as flavor): ```sh $ cd ~/Repos/rkt $ ./autogen.sh && ./configure --enable-functional-tests --enable-incremental-build --with-stage1-flavors=kvm ``` Now build rkt with: ```sh $ make V=2 -j ``` REMEMBER: If you want to test somebody else's changes: ```sh $ git checkout <branch> $ make clean $ ./autogen.sh && ./configure <proper arguments> ``` ```sh $ ./tests/build-and-run-tests.sh -f kvm ``` ```sh $ make functional-check ``` ```sh $ make functional-check GOTESTFUNCARGS='-run TESTNAME_HERE' ``` See more in page. ```sh $ sudo ./build-rkt-*/bin/rkt run --insecure-options=image --interactive docker://busybox $ exit $ sudo ./build-rkt-*/bin/rkt gc --grace-period=0 ``` ```sh for link in $(ip link | grep rkt | cut -d':' -f2 | cut -d'@' -f1); sudo ip link del "${link}" done ``` ```sh gofmt -s -w file.go ```
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-health.md

<!-- This file was autogenerated via cilium-agent --cmdref, do not edit manually--> Cilium Health Client Client for querying the Cilium health status API ``` cilium-health [flags] ``` ``` -D, --debug Enable debug messages -h, --help help for cilium-health -H, --host string URI to cilium-health server API --log-driver strings Logging endpoints to use for example syslog --log-opt map Log driver options for cilium-health e.g. syslog.level=info,syslog.facility=local5,syslog.tag=cilium-agent ``` - Generate the autocompletion script for the specified shell - Display local cilium agent status - Check whether the cilium-health API is up - Display cilium connectivity to other nodes
Project: Flannel (Runtime / Cloud Native Network)
File: extension.md

The `extension` backend provides an easy way for prototyping new backend types for flannel. It is not recommended for production use, for example it doesn't have a built in retry mechanism. This backend has the following configuration `Type` (string): `extension` `PreStartupCommand` (string): Command to run before allocating a network to this host The stdout of the process is captured and passed to the stdin of the SubnetAdd/Remove commands. `PostStartupCommand` (string): Command to run after allocating a network to this host The following environment variable is set SUBNET - The subnet of the remote host that was added. `SubnetAddCommand` (string): Command to run when a subnet is added stdin - The output from `PreStartupCommand` is passed in. The following environment variables are set SUBNET - The ipv4 subnet of the remote host that was added. IPV6SUBNET - The ipv6 subnet of the remote host that was added. PUBLIC_IP - The public IP of the remote host. PUBLIC_IPV6 - The public IPv6 of the remote host. `SubnetRemoveCommand`(string): Command to run when a subnet is removed stdin - The output from `PreStartupCommand` is passed in. The following environment variables are set SUBNET - The ipv4 subnet of the remote host that was removed. IPV6SUBNET - The ipv6 subnet of the remote host that was removed. PUBLIC_IP - The public IP of the remote host. PUBLIC_IPV6 - The public IPv6 of the remote host. All commands are run through the `sh` shell and are run with the same permissions as the flannel daemon. To replicate the functionality of the host-gw plugin, there's no need for a startup command. The backend just needs to manage the route to subnets when they are added or removed. An example ```json { "Network": "10.0.0.0/16", "Backend": { "Type": "extension", "SubnetAddCommand": "ip route add $SUBNET via $PUBLIC_IP", "SubnetRemoveCommand": "ip route del $SUBNET via $PUBLIC_IP" } } ``` VXLAN is more complex. It needs to store the MAC address of the vxlan device when it's created and to make it available to the flannel daemon running on other hosts. The address of the vxlan device also needs to be set after the subnet has been allocated. An example ```json { "Network": "10.50.0.0/16", "Backend": { "Type": "extension", "PreStartupCommand": "export VNI=1; export IFNAME=flannel-vxlan; ip link del $IFNAME 2>/dev/null; ip link add $IFNAME type vxlan id $VNI dstport 8472 && cat /sys/class/net/$IFNAME/address", "PostStartupCommand": "export IFNAME=flannel-vxlan; export SUBNETIP=`echo $SUBNET | cut -d'/' -f 1`; ip addr add $SUBNETIP/32 dev $IFNAME && ip link set $IF_NAME up", "SubnetAddCommand": "export SUBNETIP=`echo $SUBNET | cut -d'/' -f 1`; export IFNAME=flannel-vxlan; read VTEP; ip route add $SUBNET nexthop via $SUBNETIP dev $IFNAME onlink && ip neigh replace $SUBNETIP dev $IFNAME lladdr $VTEP && bridge fdb add $VTEP dev $IFNAME self dst $PUBLICIP" } } ```
Project: CubeFS (Runtime / Cloud Native Storage)
File: development.md

In July 2022, CubeFS was successfully promoted to a CNCF incubation project. In March 2022, an incubation application was submitted to CNCF. It was discovered that ChubaoFS was difficult to pronounce in English, so it was renamed CubeFS. In August 2020, OPPO joined the open-source project and became a core contributor and main promoter. In June 2019, JD.com donated ChubaoFS to the Cloud Native Computing Foundation (CNCF) and entered the CNCF sandbox project in December 2019.
Project: Project Calico (Runtime / Cloud Native Network)
File: command-line-flags.md

Command line flags override the confd . ``` confd -h ``` ```Text Usage of confd: -app-id string Vault app-id to use with the app-id backend (only used with -backend=vault and auth-type=app-id) -auth-token string Auth bearer token to use -auth-type string Vault auth backend type to use (only used with -backend=vault) -backend string backend to use (default "etcd") -basic-auth Use Basic Auth to authenticate (only used with -backend=etcd) -client-ca-keys string client ca keys -client-cert string the client cert -client-key string the client key -confdir string confd conf directory (default "/etc/confd") -config-file string the confd config file -interval int backend polling interval (default 600) -keep-stage-file keep staged files -log-level string level which confd should log messages -node value list of backend nodes (default []) -noop only show pending changes -onetime run once and exit -password string the password to authenticate with (only used with vault and etcd backends) -prefix string key path prefix (default "/") -scheme string the backend URI scheme for nodes retrieved from DNS SRV records (http or https) (default "http") -srv-domain string the name of the resource record -srv-record string the SRV record to search for backends nodes. Example: etcd-client.tcp.example.com -sync-only sync without checkcmd and reloadcmd -table string the name of the DynamoDB table (only used with -backend=dynamodb) -user-id string Vault user-id to use with the app-id backend (only used with -backend=value and auth-type=app-id) -username string the username to authenticate as (only used with vault and etcd backends) -version print version and exit -watch enable watch support ``` The -scheme flag is only used to set the URL scheme for nodes retrieved from DNS SRV records.
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-dbg_endpoint.md

<!-- This file was autogenerated via cilium cmdref, do not edit manually--> Manage endpoints ``` -h, --help help for endpoint ``` ``` --config string Config file (default is $HOME/.cilium.yaml) -D, --debug Enable debug messages -H, --host string URI to server-side API ``` - CLI - View & modify endpoint configuration - Disconnect an endpoint from the network - Display endpoint information - View endpoint health - Manage label configuration of endpoint - List all endpoints - View endpoint status log
Project: Kata Containers (Runtime / Container Runtime)
File: VmmPingResponse.md

Name | Type | Description | Notes | - | - | - BuildVersion | Pointer to string | | [optional] Version | string | | Pid | Pointer to int64 | | [optional] Features | Pointer to []string | | [optional] `func NewVmmPingResponse(version string, ) *VmmPingResponse` NewVmmPingResponse instantiates a new VmmPingResponse 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 NewVmmPingResponseWithDefaults() *VmmPingResponse` NewVmmPingResponseWithDefaults instantiates a new VmmPingResponse 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 *VmmPingResponse) GetBuildVersion() string` GetBuildVersion returns the BuildVersion field if non-nil, zero value otherwise. `func (o VmmPingResponse) GetBuildVersionOk() (string, bool)` GetBuildVersionOk returns a tuple with the BuildVersion field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *VmmPingResponse) SetBuildVersion(v string)` SetBuildVersion sets BuildVersion field to given value. `func (o *VmmPingResponse) HasBuildVersion() bool` HasBuildVersion returns a boolean if a field has been set. `func (o *VmmPingResponse) GetVersion() string` GetVersion returns the Version field if non-nil, zero value otherwise. `func (o VmmPingResponse) GetVersionOk() (string, bool)` GetVersionOk returns a tuple with the Version field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *VmmPingResponse) SetVersion(v string)` SetVersion sets Version field to given value. `func (o *VmmPingResponse) GetPid() int64` GetPid returns the Pid field if non-nil, zero value otherwise. `func (o VmmPingResponse) GetPidOk() (int64, bool)` GetPidOk returns a tuple with the Pid field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *VmmPingResponse) SetPid(v int64)` SetPid sets Pid field to given value. `func (o *VmmPingResponse) HasPid() bool` HasPid returns a boolean if a field has been set. `func (o *VmmPingResponse) GetFeatures() []string` GetFeatures returns the Features field if non-nil, zero value otherwise. `func (o VmmPingResponse) GetFeaturesOk() ([]string, bool)` GetFeaturesOk returns a tuple with the Features field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *VmmPingResponse) SetFeatures(v []string)` SetFeatures sets Features field to given value. `func (o *VmmPingResponse) HasFeatures() bool` HasFeatures returns a boolean if a field has been set.
Project: Weave Net (Runtime / Cloud Native Network)
File: benchmarks.md

Results: https://www.weave.works/weave-net-performance-fast-datapath/ Two `c3.8xlarge` instances running Ubuntu 16.04 LTS (`ami-d8f4deab`) in `eu-west-1` region of AWS. 10 Gigabit . `iperf 3.0.11`. Encrypted: ``` host1$ WEAVE_MTU=8916 weave launch --password=foobar host1$ docker $(weave config) run --rm -ti --name server networkstatic/iperf3 -s host2$ WEAVE_MTU=8916 weave launch --password=foobar host1 host2$ docker $(weave config) run --rm -ti networkstatic/iperf3 -c server ``` Non-encrypted: ``` host1$ WEAVE_MTU=8950 weave launch host1$ docker $(weave config) run --rm -ti --name server networkstatic/iperf3 -s host2$ WEAVE_MTU=8950 weave launch --password=foobar host1 host2$ docker $(weave config) run --rm -ti networkstatic/iperf3 -c server ``` Encrypted: ``` host1$ WEAVENOFASTDP=1 weave launch --password=foobar host1$ docker $(weave config) run --rm -ti --name server networkstatic/iperf3 -s host2$ WEAVENOFASTDP=1 weave launch --password=foobar host1 host2$ docker $(weave config) run --rm -ti networkstatic/iperf3 -c server ``` Non-encrypted: ``` host1$ WEAVENOFASTDP=1 weave launch host1$ docker $(weave config) run --rm -ti --name server networkstatic/iperf3 -s host2$ WEAVENOFASTDP=1 weave launch --password=foobar host1 host2$ docker $(weave config) run --rm -ti networkstatic/iperf3 -c server ``` Non-encrypted: ``` host1$ iperf -s host2$ iperf -c host1 ``` Encrypted: ``` host1$ export KEY1="0x466454f2b1a770f8f872f9afbc35ebeac57e00fc11ac86ed1f82716f010b20f0cf532274" host1$ export KEY2="0x3531151241a770f8f872f9afbc35ebeac57e00fc11ac86ed1f82716f010b20f0cf532274" host1# ip xfrm state add src ${IP1} dst ${IP2} proto esp spi 0x4c856ffc replay-window 256 flag esn reqid 0 mode transport aead 'rfc4106(gcm(aes))' ${KEY1} 128 host1# ip xfrm state add src ${IP2} dst ${IP1} proto esp spi 0x9b0830bc replay-window 256 flag esn reqid 0 mode transport aead 'rfc4106(gcm(aes))' ${KEY2} 128 host1# ip xfrm policy add src ${IP1}/32 dst ${IP2}/32 dir out tmpl src ${IP1} dst ${IP2} proto esp spi 0x4c856ffc reqid 0 mode transport host1$ iperf -s host2$ export KEY1="0x466454f2b1a770f8f872f9afbc35ebeac57e00fc11ac86ed1f82716f010b20f0cf532274" host2$ export KEY2="0x3531151241a770f8f872f9afbc35ebeac57e00fc11ac86ed1f82716f010b20f0cf532274" host2# ip xfrm state add src ${IP2} dst ${IP1} proto esp spi 0x9b0830bc reqid 0 replay-window 256 flag esn mode transport aead 'rfc4106(gcm(aes))' ${KEY2} 128 host2# ip xfrm state add src ${IP1} dst ${IP2} proto esp spi 0x4c856ffc reqid 0 replay-window 256 flag esn mode transport aead 'rfc4106(gcm(aes))' ${KEY1} 128 host2# ip xfrm policy add src ${IP2}/32 dst ${IP1}/32 dir out tmpl src ${IP1} dst ${IP2} proto esp spi 0x9b0830bc reqid 0 mode transport host2$ iperf -c host1 ```