content listlengths 1 171 | tag dict |
|---|---|
[
{
"data": "rkt can run multiple applications in a pod, under a supervising process and alongside with a sidecar service which takes care of multiplexing its I/O toward the outside world. Historically this has been done via systemd-journald only, meaning that all logging was handled via journald and interactive ... | {
"category": "Runtime",
"file_name": "log-attach-design.md",
"project_name": "rkt",
"subcategory": "Container Runtime"
} |
[
{
"data": "`ScaleWorkload` function can be used to scale a workload to specified replicas. It automatically sets the original replica count of the workload as output artifact, which makes using `ScaleWorkload` function in blueprints a lot easier. Below is an example of how this function can be used ``` yaml api... | {
"category": "Runtime",
"file_name": "scaleworkload.md",
"project_name": "Kanister",
"subcategory": "Cloud Native Storage"
} |
[
{
"data": "CURVE client serves as the entrance of the services provided by CURVE, providing dynamic link library for QEMU/CURVE-NBD. As a result, restarting QEMU/CURVE-NBD is necessary when CURVE Client needs to be updated. In order to relief the impact of updating on applications based on CURVE, we decoupled C... | {
"category": "Runtime",
"file_name": "nebd_en.md",
"project_name": "Curve",
"subcategory": "Cloud Native Storage"
} |
[
{
"data": "All notable changes to this project will be documented in this file. This project adheres to . Enhancements: : Add `WithLazy` method for `SugaredLogger`. : zaptest: Add `NewTestingWriter` for customizing TestingWriter with more flexibility than `NewLogger`. : Add `Log`, `Logw`, `Logln` methods for `S... | {
"category": "Runtime",
"file_name": "CHANGELOG.md",
"project_name": "Cilium",
"subcategory": "Cloud Native Network"
} |
[
{
"data": "This is a small experiment to have a wrapper CLI which can call both API functions as well as debug CLI. To facilitate tab completion and help, the API call names are broken up with spaces replacing the underscores."
}
] | {
"category": "Runtime",
"file_name": "README.md",
"project_name": "FD.io",
"subcategory": "Cloud Native Network"
} |
[
{
"data": "Microsoft Azure AWS Alibaba VMWare Netflix Hashi Corp Admiralty Elotl Tencent Games Since end-users are specific per provider within VK we have many end-user customers that we don't have permission to list publically. Please contact ribhatia@microsoft.com for more informtation. Are you currently usin... | {
"category": "Runtime",
"file_name": "ADOPTERS.md",
"project_name": "Virtual Kubelet",
"subcategory": "Container Runtime"
} |
[
{
"data": "Firecracker uses a to standardize the build process. This also fixes the build tools and dependencies to specific versions. Every once in a while, something needs to be updated. To do this, a new container image needs to be built locally, then published to the registry. The Firecracker CI suite must ... | {
"category": "Runtime",
"file_name": "devctr-image.md",
"project_name": "Firecracker",
"subcategory": "Container Runtime"
} |
[
{
"data": "<!-- This file was autogenerated via cilium cmdref, do not edit manually--> Manage compiled BPF template objects ``` -h, --help help for sha ``` ``` --config string Config file (default is $HOME/.cilium.yaml) -D, --debug Enable debug messages -H, --host string URI to server-side API ``` - Direct acce... | {
"category": "Runtime",
"file_name": "cilium-dbg_bpf_sha.md",
"project_name": "Cilium",
"subcategory": "Cloud Native Network"
} |
[
{
"data": "To simplify the communication between velero users and developers, this document proposes the `velero debug` command to generate a tarball including the logs needed for debugging. Github issue: https://github.com/vmware-tanzu/velero/issues/675 Gathering information to troubleshoot a Velero deployment... | {
"category": "Runtime",
"file_name": "velero-debug.md",
"project_name": "Velero",
"subcategory": "Cloud Native Storage"
} |
[
{
"data": "OpenEBS is the most widely deployed open source example of a category of storage solutions sometimes called . OpenEBS is itself deployed as a set of containers on Kubernetes worker nodes. This document describes the high level architecture of OpenEBS and the links to the Source Code and its Dependenc... | {
"category": "Runtime",
"file_name": "README.md",
"project_name": "OpenEBS",
"subcategory": "Cloud Native Storage"
} |
[
{
"data": "Libvirt is one of manager for StratoVirt, it manages StratoVirt by creating cmdlines to launch StratoVirt and giving commands via QMP. Currently, five virsh commands are supported to manage StratoVirt: `virsh create`, `virsh destroy`, `virsh suspend`, `virsh resume` and `virsh console`. StratoVirt ca... | {
"category": "Runtime",
"file_name": "interconnect_with_libvirt.md",
"project_name": "StratoVirt",
"subcategory": "Container Runtime"
} |
[
{
"data": "title: Prerequisites Rook can be installed on any existing Kubernetes cluster as long as it meets the minimum version and Rook is granted the required privileges (see below for more information). Kubernetes versions v1.25 through v1.30 are supported. Architectures supported are `amd64 / x86_64` and `... | {
"category": "Runtime",
"file_name": "prerequisites.md",
"project_name": "Rook",
"subcategory": "Cloud Native Storage"
} |
[
{
"data": "Prerequisites: Tests must be run on a Linux OS Docker installed with IPv6 enabled You will need to restart your Docker engine after updating the config Target kube-vip Docker image exists locally. Either build the image locally with `make dockerx86Local` or `docker pull` the image from a registry. Ru... | {
"category": "Runtime",
"file_name": "README.md",
"project_name": "kube-vip",
"subcategory": "Cloud Native Network"
} |
[
{
"data": "Architecture of the library === ELF -> Specifications -> Objects -> Links ELF BPF is usually produced by using Clang to compile a subset of C. Clang outputs an ELF file which contains program byte code (aka BPF), but also metadata for maps used by the program. The metadata follows the conventions set... | {
"category": "Runtime",
"file_name": "ARCHITECTURE.md",
"project_name": "Inclavare Containers",
"subcategory": "Container Runtime"
} |
[
{
"data": "title: \"Cluster migration\" layout: docs Velero's backup and restore capabilities make it a valuable tool for migrating your data between clusters. Cluster migration with Velero is based on Velero's functionality, which is responsible for syncing Velero resources from your designated object storage ... | {
"category": "Runtime",
"file_name": "migration-case.md",
"project_name": "Velero",
"subcategory": "Cloud Native Storage"
} |
[
{
"data": "<!-- toc --> - - - - - - - - <!-- /toc --> Antrea Multi-cluster implements , which allows users to create multi-cluster Services that can be accessed cross clusters in a ClusterSet. Antrea Multi-cluster also extends Antrea-native NetworkPolicy to support Multi-cluster NetworkPolicy rules that apply t... | {
"category": "Runtime",
"file_name": "user-guide.md",
"project_name": "Antrea",
"subcategory": "Cloud Native Network"
} |
[
{
"data": "name: Release task about: Create a release task title: \"[RELEASE]\" labels: release/task assignees: '' What's the task? Please describe. Action items for releasing v<x.y.z> Roles Release captain: <!--responsible for RD efforts of release development and coordinating with QA captain--> QA captain: <!... | {
"category": "Runtime",
"file_name": "release.md",
"project_name": "Longhorn",
"subcategory": "Cloud Native Storage"
} |
[
{
"data": "Describe the PR e.g. add cool parser. Relation issue e.g. https://github.com/swaggo/gin-swagger/pull/123/files Additional context Add any other context about the problem here."
}
] | {
"category": "Runtime",
"file_name": "pull_request_template.md",
"project_name": "HwameiStor",
"subcategory": "Cloud Native Storage"
} |
[
{
"data": "This document defines a high level roadmap for rkt development. The dates below should not be considered authoritative, but rather indicative of the projected timeline of the project. The represent the most up-to-date state of affairs. rkt's version 1.0 release marks the command line user interface a... | {
"category": "Runtime",
"file_name": "ROADMAP.md",
"project_name": "rkt",
"subcategory": "Container Runtime"
} |
[
{
"data": "We follow the , and use the corresponding tooling. For the purposes of the aforementioned guidelines, controller-runtime counts as a \"library project\", but otherwise follows the guidelines exactly. For release branches, we generally tend to support backporting one (1) major release (`release-{X-1}`... | {
"category": "Runtime",
"file_name": "VERSIONING.md",
"project_name": "Stash by AppsCode",
"subcategory": "Cloud Native Storage"
} |
[
{
"data": "The initial roadmap of CRI-O was lightweight and followed the main Kubernetes Container Runtime Interface (CRI) development lifecycle. This is partially because additional features on top of that are either integrated into a CRI-O release as soon as theyre ready, or are tracked through the Milestone ... | {
"category": "Runtime",
"file_name": "roadmap.md",
"project_name": "CRI-O",
"subcategory": "Container Runtime"
} |
[
{
"data": "<!-- Thank you for contributing to curve! --> Issue Number: #xxx <!-- replace xxx with issue number --> Problem Summary: What's Changed: How it Works: Side effects(Breaking backward compatibility? Performance regression?): [ ] Relevant documentation/comments is changed or added [ ] I acknowledge that... | {
"category": "Runtime",
"file_name": "pull_request_template.md",
"project_name": "Curve",
"subcategory": "Cloud Native Storage"
} |
[
{
"data": "| 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/>... | {
"category": "Runtime",
"file_name": "fuzzy_mode_convert_table.md",
"project_name": "Spiderpool",
"subcategory": "Cloud Native Network"
} |
End of preview. Expand in Data Studio
YAML Metadata Warning:empty or missing yaml metadata in repo card
Check out the documentation for more information.
CNCF Raw Data for LLM Training
Description
This dataset, named cncf-raw-data-for-llm-training, consists of markdown (MD) and PDF content extracted from various project repositories within the CNCF (Cloud Native Computing Foundation) landscape. The data was collected by fetching MD and PDF files from different CNCF project repositories and converting them into JSON format. This dataset is intended as raw data for training large language models (LLMs).
The dataset includes the following two columns:
Tag: A JSON object that categorizes the file. For example:
{ "category": "Runtime", "file_name": "log-attach-design.md", "project_name": "rkt", "subcategory": "Container Runtime" }- Category: A broad classification representing the main functional area of the project.
- File Name: The name of the file as it appears in the original repository.
- Project Name: The name of the specific project to which the file belongs.
- Subcategory: A more specific classification within the main category.
Content: The actual content of the file (MD or PDF) in Jason format.
License
This dataset is available under the MIT license.
Links
- Downloads last month
- 16