cwielenb/CNCF-Dataset huggingface dataset:
Project: Alluxio (Runtime / Cloud Native Storage)
File: Azure-Data-Lake-Gen2.md

layout: global title: Azure Data Lake Storage Gen2 This guide describes how to configure Alluxio with {:target="_blank"} as the under storage system. Azure Data Lake Storage Gen2 is a set of capabilities dedicated to big data analytics, built on Azure Blob Storage. It converges the capabilities of Azure Data Lake Storage Gen1 with Azure Blob Storage. For more information about Azure Data Lake Storage Gen1, please read its {:target="_blank"}. If you haven't already, please see before you get started. In preparation for using Azure Data Lake Storage Gen2 with Alluxio, {:target="_blank"} or use an existing Data Lake storage. <table class="table table-striped"> <tr> <td markdown="span" style="width:30%">`<AZURE_CONTAINER>`</td> <td markdown="span">The container you want to use</td> </tr> <tr> <td markdown="span" style="width:30%">`<AZURE_DIRECTORY>`</td> <td markdown="span">The directory you want to use in the container, either by creating a new directory or using an existing one</td> </tr> <tr> <td markdown="span" style="width:30%">`<AZURE_ACCOUNT>`</td> <td markdown="span">Your Azure storage account</td> </tr> </table> You also need a {:target="_blank"} to authorize requests. To use Azure Data Lake Storage Gen2 as the UFS of Alluxio root mount point, you need to configure Alluxio to use under storage systems by modifying `conf/alluxio-site.properties`. If it does not exist, create the configuration file from the template. ```shell $ cp conf/alluxio-site.properties.template conf/alluxio-site.properties ``` Specify the underfs address by modifying `conf/alluxio-site.properties` to include: ```properties alluxio.dora.client.ufs.root=abfs://<AZURECONTAINER>@<AZUREACCOUNT>.dfs.core.windows.net/<AZURE_DIRECTORY>/ ``` Specify the Shared Key by adding the following property in `conf/alluxio-site.properties`: ```properties fs.azure.account.key.<AZUREACCOUNT>.dfs.core.windows.net=<AZURESHARED_KEY> ``` Specify the OAuth 2.0 Client Credentials by adding the following property in `conf/alluxio-site.properties`: (Please note that for URL Endpoint, use the V1 token endpoint) ```properties fs.azure.account.oauth2.client.endpoint=<OAUTH_ENDPOINT> fs.azure.account.oauth2.client.id=<CLIENT_ID> fs.azure.account.oauth2.client.secret=<CLIENT_SECRET> ``` Specify the Azure Managed Identities by adding the following property in `conf/alluxio-site.properties`: ```properties fs.azure.account.oauth2.msi.endpoint=<MSI_ENDPOINT> fs.azure.account.oauth2.client.id=<CLIENT_ID> fs.azure.account.oauth2.msi.tenant=<MSI_TENANT> ``` Once you have configured Alluxio to Azure Data Lake Storage Gen2, try to see that everything works.
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-dbg_bpf_metrics.md

<!-- This file was autogenerated via cilium cmdref, do not edit manually--> BPF datapath traffic metrics ``` -h, --help help for metrics ``` ``` --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 BPF datapath traffic metrics
Project: runc (Runtime / Container Runtime)
File: runc-create.8.md

% runc-create "8" runc-create - create a container runc create [option ...] container-id The create command creates an instance of a container from a bundle. The bundle is a directory with a specification file named config.json, and a root filesystem. --bundle|-b path : Path to the root of the bundle directory. Default is current directory. --console-socket path : Path to an AF_UNIX socket which will receive a file descriptor referencing the master end of the console's pseudoterminal. See . --pid-file path : Specify the file to write the initial container process' PID to. --no-pivot : Do not use pivot root to jail process inside rootfs. This should not be used except in exceptional circumstances, and may be unsafe from the security standpoint. --no-new-keyring : Do not create a new session keyring for the container. This will cause the container to inherit the calling processes session key. --preserve-fds N : Pass N additional file descriptors to the container (stdio + $LISTEN_FDS + N in total). Default is 0. runc-spec(8), runc-start(8), runc(8).
Project: lxd (Runtime / Container Runtime)
File: network_ipam.md

(network-ipam)= {abbr}`IPAM (IP Address Management)` is a method used to plan, track, and manage the information associated with a computer network's IP address space. In essence, it's a way of organizing, monitoring, and manipulating the IP space in a network. Checking the IPAM information for your Incus setup can help you debug networking issues. You can see which IP addresses are used for instances, network interfaces, forwards, and load balancers and use this information to track down where traffic is lost. To display IPAM information, enter the following command: ```bash incus network list-allocations ``` By default, this command shows the IPAM information for the `default` project. You can select a different project with the `--project` flag, or specify `--all-projects` to display the information for all projects. The resulting output will look something like this: ``` ++--+-++-+ | USED BY | ADDRESS | TYPE | NAT | HARDWARE ADDRESS | ++--+-++-+ | /1.0/networks/incusbr0 | 192.0.2.0/24 | network | true | | ++--+-++-+ | /1.0/networks/incusbr0 | 2001:db8::/32 | network | true | | ++--+-++-+ | /1.0/instances/u1 | 2001:db8::1/128 | instance | true | 00:16:3e:04:f0:95 | ++--+-++-+ | /1.0/instances/u1 | 192.0.2.2/32 | instance | true | 00:16:3e:04:f0:95 | ++--+-++-+ ... ``` Each listed entry lists the IP address (in CIDR notation) of one of the following Incus entities: `network`, `network-forward`, `network-load-balancer`, and `instance`. An entry contains an IP address using the CIDR notation. It also contains an Incus resource URI, the type of the entity, whether it is in NAT mode, and the hardware address (only for the `instance` entity).
Project: Kube-OVN (Runtime / Cloud Native Network)
File: CODE_STYLE.md

The goal of this guide is to manage the complexity, keep a consistent code style and prevent common mistakes. New code should follow the guides below and reviewers should check if new PRs follow the rules. Always use camelcase to name variables and functions. <table> <thead><tr><th>Bad</th><th>Good</th></tr></thead> <tbody> <tr><td> ```go var command_line string ``` </td><td> ```go var commandLine string ``` </td></tr> </tbody></table> All error that not expected should be handled with error log. No error should be skipped silently. <table> <thead><tr><th>Bad</th><th>Good</th></tr></thead> <tbody> <tr><td> ```go kubeClient, _ := kubernetes.NewForConfig(cfg) ``` </td><td> ```go kubeClient, err := kubernetes.NewForConfig(cfg) if err != nil { klog.Errorf("init kubernetes client failed %v", err) return err } ``` </td></tr> </tbody></table> We prefer use `if err := somefunction(); err != nil {}` to check error in one line. <table> <thead><tr><th>Bad</th><th>Good</th></tr></thead> <tbody> <tr><td> ```go err := c.initNodeRoutes() if err != nil { klog.Fatalf("failed to initialize node routes: %v", err) } ``` </td><td> ```go if err := c.initNodeRoutes(); err != nil { klog.Fatalf("failed to initialize node routes: %v", err) } ``` </td></tr> </tbody></table> The length of one function should not exceed 100 lines. When err occurs in the function, it should be returned to the caller not skipped silently. <table> <thead><tr><th>Bad</th><th>Good</th></tr></thead> <tbody> <tr><td> ```go func startHandle() { if err = some(); err != nil { klog.Errorf(err) } return } ``` </td><td> ```go func startHandle() error { if err = some(); err != nil { klog.Errorf(err) return err } return nil } ``` </td></tr> </tbody></table> When adding a new CRD to Kube-OVN, you should consider things below to avoid common bugs. The new feature should be disabled for performance and stability reasons. The `install.sh`, `charts` and `yamls` should install the new CRD. The `cleanup.sh` should clean the CRD and all the related resources. The `gc.go` should check the inconsistent resource and do the cleanup. The add/update/delete event can be triggered many times during the lifecycle, the handler should be reentrant.
Project: Velero (Runtime / Cloud Native Storage)
File: ark_get_restores.md

title: "ark get restores" layout: docs Get restores Get restores ``` ark get restores [flags] ``` ``` -h, --help help for restores --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 ``` - Get ark resources
Project: JuiceFS (Runtime / Cloud Native Storage)
File: contributing_guide.md

title: Contributing Guide sidebar_position: 1 description: JuiceFS is open source software and the code is contributed and maintained by developers worldwide. Learn how to participate in this article. Before starting work on a feature or bug fix, search GitHub or reach out to us via GitHub or Slack, make sure no one else is already working on it and we'll ask you to open a GitHub issue if necessary. Before contributing, use the GitHub issue to discuss the feature and reach an agreement with the core developers. For major feature updates, write a design document to help the community understand your motivation and solution. Find issues with the label or . Read for important data structure references. We're following and . Use `go fmt` to format your code before committing. You can find information in editor support for Go tools in . Every new source file must begin with a license header. Install and use it to set up a pre-commit hook for static analysis. Just run `pre-commit install` in the root of the repo. Before you can contribute to JuiceFS, you will need to sign the . There're a CLA assistant to guide you when you first time submit a pull request. Presence of unit tests Adherence to the coding style Adequate in-line comments Explanatory commit message Create a topic branch from where to base the contribution. This is usually `main`. Make commits of logical units. Make sure commit messages are in the proper format. Push changes in a topic branch to a personal fork of the repository. Submit a pull request to . The PR should link to one issue which either created by you or others. The PR must receive approval from at least one maintainer before it be merged.
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-dbg_bpf_lb_maglev_get.md

<!-- This file was autogenerated via cilium cmdref, do not edit manually--> Get Maglev lookup table for given service by ID ``` cilium-dbg bpf lb maglev get <service id> [flags] ``` ``` -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 ``` - Maglev lookup table
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-operator_completion_fish.md

<!-- This file was autogenerated via cilium-operator --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-operator completion fish | source To load completions for every new session, execute once: cilium-operator completion fish > ~/.config/fish/completions/cilium-operator.fish You will need to start a new shell for this setup to take effect. ``` cilium-operator completion fish [flags] ``` ``` -h, --help help for fish --no-descriptions disable completion descriptions ``` - Generate the autocompletion script for the specified shell
Project: Soda Foundation (Runtime / Cloud Native Storage)
File: euac.md

OpenSDS End User Advisory Committee The End User Advisory Committee (EUAC) is to assist and support the OpenSDS community in its objectives by providing technical and strategic guidance real-world storage challenges Cosimo Rosetti (Vodafone) Kei Kusunoki (NTT Communications) Yusuke Sato (Yahoo Japan) Yuji Yazawa (Toyota) Wim Jacobs (KPN) Shinya Tsunematsu (GMO Pepabo) This meeting is hosted on zoom. Join the EUAC mailing list for info on meetings Zoom Meeting: https://zoom.us/j/477192859 Or iPhone one-tap : US: +19294362866,,477192859# or +16699006833,,477192859# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 669 900 6833 Meeting ID: 477 192 859 International numbers available: https://zoom.us/zoomconference?m=h0x5xsxAwYrgrrKRsEx7PLkOfvL3bm
Project: Firecracker (Runtime / Container Runtime)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '[Bug] Title' labels: 'Quality: Bug' assignees: '' `[Author TODO: A clear and concise description of what the bug is.]` `[Author TODO: Steps to reproduce the behaviour:]` Start Firecracker via.... Configure Firecracker via... ... `[Author TODO: A clear and concise description of what you expected to happen.]` `[Author TODO: Please supply the following information):]` Firecracker version: Host and guest kernel versions: Rootfs used: Architecture: Any other relevant software versions: `[Author TODO: How has this bug affected you?]` `[Author TODO: What are you trying to achieve?]` `[Author TODO: Do you have any idea of what the solution might be?]` [ ] Have you searched the Firecracker Issues database for similar problems? [ ] Have you read the existing relevant Firecracker documentation? [ ] Are you certain the bug being reported is a Firecracker issue?
Project: Spiderpool (Runtime / Cloud Native Network)
File: ifacer.md

| Case ID | Title | Priority | Smoke | Status | Other | | - | | -- | -- | | -- | | N00001 | Creating a VLAN interface should succeed | p1 | true | done | | | N00002 | VLAN interface already exists, skip creation | p2 | | done | | | N00003 | VLAN interface exists but state is down, set it up and exit | p2 | | done | | | N00004 | Different VLAN interfaces have the same VLAN id, an error is returned | p2 | | done | | | N00005 | The master interface is down, setting it up and creating VLAN interface | p2 | | done | | | N00006 | Restart the node vlan/bond will be lost, restart the pod they should be restored. | p3 | | done | |
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-dbg_encrypt_flush.md

<!-- This file was autogenerated via cilium cmdref, do not edit manually--> Flushes the current IPsec state Will cause a short connectivity disruption ``` cilium-dbg encrypt flush [flags] ``` ``` -f, --force Skip confirmation -h, --help help for flush --node-id string Only delete states and policies with this node ID. Decimal or hexadecimal (0x) format. If multiple filters are used, they all apply -o, --output string json| yaml| jsonpath='{}' --spi uint8 Only delete states and policies with this SPI. If multiple filters are used, they all apply --stale Delete stale states and policies based on the current node ID map content ``` ``` --config string Config file (default is $HOME/.cilium.yaml) -D, --debug Enable debug messages -H, --host string URI to server-side API ``` - Manage transparent encryption
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-dbg_bpf_ct_list.md

<!-- This file was autogenerated via cilium cmdref, do not edit manually--> List connection tracking entries ``` cilium-dbg bpf ct list ( global | endpoint | cluster ) [identifier] [flags] ``` ``` -h, --help help for list -o, --output string json| yaml| jsonpath='{}' -d, --time-diff print time difference for entries --time-diff-clocksource-hz int manually set clock source Hz (default 250) --time-diff-clocksource-mode string manually set clock source mode (instead of contacting the server) ``` ``` --config string Config file (default is $HOME/.cilium.yaml) -D, --debug Enable debug messages -H, --host string URI to server-side API ``` - Connection tracking tables
Project: Weave Net (Runtime / Cloud Native Network)
File: operational-guide.md

title: Operational Guide menu_order: 45 search_type: Documentation This operational guide is intended to give you an overview of how to operate and manage a Weave Network in production. It consists of three main parts: A with which you will need to be familiar Detailed instructions for safely bootstrapping, growing and shrinking Weave networks in a number of different deployment scenarios: An [interactive installation](/site/operational-guide/interactive.md), suitable for evaluation and development A [uniformly configured cluster](/site/operational-guide/uniform-fixed-cluster.md) with a fixed number of initial nodes, suitable for automated provisioning but requiring manual intervention for resizing A comprising fixed and autoscaling components, suitable for a base load with automated scale-out/scale-in A [uniformly configured cluster](/site/operational-guide/uniform-dynamic-cluster.md) with dynamic nodes, suitable for automated provisioning and resizing. A list of [common administrative tasks](/site/operational-guide/tasks.md), such as configuring Weave Net to start on boot, upgrading clusters, cleaning up peers and reclaiming IP address space
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-dbg_service_update.md

<!-- This file was autogenerated via cilium cmdref, do not edit manually--> Update a service ``` cilium-dbg service update [flags] ``` ``` --backend-weights uints Backend weights (100 default, 0 means maintenance state, only for maglev mode) (default []) --backends strings Backend address or addresses (<IP:Port>) --frontend string Frontend address -h, --help help for update --id uint Identifier --k8s-cluster-internal Set service as cluster-internal for externalTrafficPolicy=Local xor internalTrafficPolicy=Local --k8s-ext-traffic-policy string Set service with k8s externalTrafficPolicy as {Local,Cluster} (default "Cluster") --k8s-external Set service as a k8s ExternalIPs --k8s-host-port Set service as a k8s HostPort --k8s-int-traffic-policy string Set service with k8s internalTrafficPolicy as {Local,Cluster} (default "Cluster") --k8s-load-balancer Set service as a k8s LoadBalancer --k8s-node-port Set service as a k8s NodePort --local-redirect Set service as Local Redirect --states strings Backend state(s) as {active(default),terminating,quarantined,maintenance} ``` ``` --config string Config file (default is $HOME/.cilium.yaml) -D, --debug Enable debug messages -H, --host string URI to server-side API ``` - Manage services & loadbalancers
Project: Kata Containers (Runtime / Container Runtime)
File: TpmConfig.md

Name | Type | Description | Notes | - | - | - Socket | string | | `func NewTpmConfig(socket string, ) *TpmConfig` NewTpmConfig instantiates a new TpmConfig 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 NewTpmConfigWithDefaults() *TpmConfig` NewTpmConfigWithDefaults instantiates a new TpmConfig 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 *TpmConfig) GetSocket() string` GetSocket returns the Socket field if non-nil, zero value otherwise. `func (o TpmConfig) GetSocketOk() (string, bool)` GetSocketOk returns a tuple with the Socket field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. `func (o *TpmConfig) SetSocket(v string)` SetSocket sets Socket field to given value.
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-dbg_metrics.md

<!-- This file was autogenerated via cilium cmdref, do not edit manually--> Access metric status ``` -h, --help help for metrics ``` ``` --config string Config file (default is $HOME/.cilium.yaml) -D, --debug Enable debug messages -H, --host string URI to server-side API ``` - CLI - List all metrics
Project: Submariner (Runtime / Cloud Native Network)
File: PULL_REQUEST_TEMPLATE.md

<!-- Thanks for sending a pull request! Here are some tips for you: If this is your first time, please read our developer guide: https://submariner.io/development/ Ensure you have added the appropriate tests for your PR: https://submariner.io/development/code-review/#test-new-functionality Read the code review guide to ease the review process: https://submariner.io/development/code-review/ If the PR is unfinished, mark it as a draft: https://submariner.io/development/code-review/#mark-work-in-progress-prs-as-drafts If you are using CI to debug, use your private fork: https://submariner.io/development/code-review/#use-private-forks-for-debugging-prs-by-running-ci Add labels to the PR as appropriate. This template is based on the K8s/K8s template: https://github.com/kubernetes/kubernetes/blob/master/.github/PULLREQUESTTEMPLATE.md -->
Project: Weave Net (Runtime / Cloud Native Network)
File: managing-domains-weavedns.md

title: Managing Domains menu_order: 30 search_type: Documentation The following topics are discussed: If you don't supply a domain search path (with `--dns-search=`), Weave Net (via the or via `weave attach`) tells a container to look for "bare" hostnames, like `pingme`, in its own domain (or in `weave.local` if it has no domain). If you want to supply other entries for the domain search path, e.g. if you want containers in different sub-domains to resolve hostnames across all sub-domains plus some external domains, you need also to supply the `weave.local` domain to retain the above behaviour. ``` docker run -ti \ --dns-search=zone1.weave.local --dns-search=zone2.weave.local \ --dns-search=corp1.com --dns-search=corp2.com \ --dns-search=weave.local weaveworks/ubuntu ``` By default, weaveDNS uses `weave.local.` as the domain for names on the Weave network. In general users do not need to change this domain, but you can force weaveDNS to use a different domain by launching it with the `--dns-domain` argument. For example, ``` $ weave launch --dns-domain="mycompany.local." ``` The local domain should end with `local.`, since these names are link-local as per , (though this is not strictly necessary). *
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-operator-alibabacloud_completion_powershell.md

<!-- This file was autogenerated via cilium-operator --cmdref, do not edit manually--> Generate the autocompletion script for powershell Generate the autocompletion script for powershell. To load completions in your current shell session: cilium-operator-alibabacloud completion powershell | Out-String | Invoke-Expression To load completions for every new session, add the output of the above command to your powershell profile. ``` cilium-operator-alibabacloud completion powershell [flags] ``` ``` -h, --help help for powershell --no-descriptions disable completion descriptions ``` - Generate the autocompletion script for the specified shell