cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_class.md

title: kbcli class Manage classes ``` -h, --help help for class ``` ``` --as string Username to impersonate for the operation. User could be a regular user or a service account in a namespace. --as-group stringArray Group to impersonate for the operation, this flag can be repeated to specify multiple groups. --as-uid string UID to impersonate for the operation. --cache-dir string Default cache directory (default "$HOME/.kube/cache") --certificate-authority string Path to a cert file for the certificate authority --client-certificate string Path to a client certificate file for TLS --client-key string Path to a client key file for TLS --cluster string The name of the kubeconfig cluster to use --context string The name of the kubeconfig context to use --disable-compression If true, opt-out of response compression for all requests to the server --insecure-skip-tls-verify If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure --kubeconfig string Path to the kubeconfig file to use for CLI requests. --match-server-version Require server version to match client version -n, --namespace string If present, the namespace scope for this CLI request --request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0") -s, --server string The address and port of the Kubernetes API server --tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used --token string Bearer token for authentication to the API server --user string The name of the kubeconfig user to use ``` - Create a class - List classes - Generate class definition template
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: device-write-iops.md

Limit write rate (in IO operations per second) to a device (e.g. --device-write-iops=/dev/sda:1000). On some systems, changing the resource limits may not be allowed for non-root users. For more details, see https://github.com/containers/podman/blob/main/troubleshooting.md#26-running-containers-with-resource-limits-fails-with-a-permissions-error This option is not supported on cgroups V1 rootless systems.
Project: Devfile (App Definition and Development / Application Definition & Image Build)
File: SHOULDERS.md

github.com/gobuffalo/flect does not try to reinvent the wheel! Instead, it uses the already great wheels developed by the Go community and puts them all together in the best way possible. Without these giants, this project would not be possible. Please make sure to check them out and thank them for all of their hard work. Thank you to the following GIANTS:
Project: ClickHouse (App Definition and Development / Database)
File: distributed_ddl_queue.md

slug: /en/operations/system-tables/distributedddlqueue Contains information about that were executed on a cluster. Columns: `entry` () Query id. `entry_version` () - Version of the entry `initiator_host` () - Host that initiated the DDL operation `initiator_port` () - Port used by the initiator `cluster` () Cluster name. `query` () Query executed. `settings` () - Settings used in the DDL operation `querycreatetime` () Query created time. `host` () Hostname `port` () Host Port. `status` () Status of the query. `exception_code` () Exception code. `exception_text` () - Exception message `queryfinishtime` () Query finish time. `querydurationms` () Duration of query execution (in milliseconds). Example ``` sql SELECT * FROM system.distributedddlqueue WHERE cluster = 'test_cluster' LIMIT 2 FORMAT Vertical Query id: f544e72a-6641-43f1-836b-24baa1c9632a Row 1: entry: query-0000000000 entry_version: 5 initiator_host: clickhouse01 initiator_port: 9000 cluster: test_cluster query: CREATE DATABASE testdb UUID '4a82697e-c85e-4e5b-a01e-a36f2a758456' ON CLUSTER testcluster settings: {'maxthreads':'16','useuncompressed_cache':'0'} querycreatetime: 2023-09-01 16:15:14 host: clickhouse-01 port: 9000 status: Finished exception_code: 0 exception_text: queryfinishtime: 2023-09-01 16:15:14 querydurationms: 154 Row 2: entry: query-0000000001 entry_version: 5 initiator_host: clickhouse01 initiator_port: 9000 cluster: test_cluster query: CREATE DATABASE testdb UUID '4a82697e-c85e-4e5b-a01e-a36f2a758456' ON CLUSTER testcluster settings: {'maxthreads':'16','useuncompressed_cache':'0'} querycreatetime: 2023-09-01 16:15:14 host: clickhouse-01 port: 9000 status: Finished exception_code: 630 exceptiontext: Code: 630. DB::Exception: Cannot drop or rename testdb, because some tables depend on it: queryfinishtime: 2023-09-01 16:15:14 querydurationms: 154 2 rows in set. Elapsed: 0.025 sec. ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: integrations.md

title: "Integrations" <!-- Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> The following external projects integrate with Apache Beam: Kettle is a tool for desinging data pipelines using a graphical user interface. The resulting pipelines can be translated to Beam pipelines. Kettle License: Apache 2.0
Project: TiKV (App Definition and Development / Database)
File: bug-report.md

name: "\U0001F41B Bug Report" about: Something isn't working as expected labels: type/bug <!-- Thanks for your bug report! Don't worry if you can't fill out all the sections. --> <!-- You can run `tikv-server --version` --> <!-- If you're using Linux, you can run `cat /proc/cpuinfo` --> <!-- If possible, provide a recipe for reproducing the error. A complete runnable program is good. -->
Project: KICS (Provisioning / Security & Compliance)
File: 24b132df-5cc7-4823-8029-f898e1c50b72.md

title: Service Account Name Undefined Or Empty hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 24b132df-5cc7-4823-8029-f898e1c50b72 Query name: Service Account Name Undefined Or Empty Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Defaults URL: A Kubernetes Pod should have a Service Account defined so to restrict Kubernetes API access, which means the attribute 'serviceaccountname' should be defined and not empty.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="6" resource "kubernetes_pod" "test1" { metadata { name = "terraform-example" } spec { container { image = "nginx:1.7.9" name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="6" resource "kubernetes_pod" "test2" { metadata { name = "terraform-example" } spec { container { image = "nginx:1.7.9" name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } serviceaccountname = null } } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="36" resource "kubernetes_pod" "test3" { metadata { name = "terraform-example" } spec { container { image = "nginx:1.7.9" name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } serviceaccountname = "" } } ``` ```tf title="Negative test num. 1 - tf file" resource "kubernetes_pod" "test" { metadata { name = "terraform-example" } spec { container { image = "nginx:1.7.9" name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } serviceaccountname = "service_name" dns_config { nameservers = ["1.1.1.1", "8.8.8.8", "9.9.9.9"] searches = ["example.com"] option { name = "ndots" value = 1 } option { name = "use-vc" } } dns_policy = "None" } } ```
Project: Harbor (Provisioning / Container Registry)
File: 6-03-OVA-patching.md

Test 6-03 - OVA Patching ======= To verify that an OVA version of Harbor can be patching. User guide, installation guide of Harbor OVA version. This test requires an upgrade binary of Harbor. A running version of older version of Harbor OVA version. A vCenter, at least an ESX host. A linux host with Docker CLI installed (Docker client). TBD TBD None
Project: Meshery (Provisioning / Automation & Configuration)
File: 10-04-2022-19-56-10_fc5847eb.md

timestamp: "2022-10-04 19:55:45 UTC Tue" meshery-component: meshery-consul meshery-component-version: edge meshery-server-version: "v0.6.10" k8s-distro: minikube k8s-version: "v1.20.11" service-mesh: Consul service-mesh-version: "v0.49.0" tests: consul-client: null consul-server: null overall-status: "failing"
Project: Meshery (Provisioning / Automation & Configuration)
File: archived- news.md

title: News abstract: Subscribe with RSS to keep up with the latest news. permalink: /news/ excludedinsearch: true language: en display-title: "false" suggested-reading: false list: exclude <p>Subscribe with <a href="{{ site.baseurl }}/feed.xml">RSS</a> to keep up with the latest news. For site changes, see the <a href="https://github.com/{{ site.githubuser }}/{{ site.githubrepo }}/blob/master/CHANGELOG.md">changelog</a> kept with the code base.</p> <br> {% for post in site.posts limit:10 %} <div class="post-preview"> <h2><a href="{{ site.baseurl }}{{ post.url }}">{{ post.title }}</a></h2> <span class="post-date">{{ post.date | date: "%B %d, %Y" }}</span><br> {% if post.badges %}{% for badge in post.badges %}<span class="badge badge-{{ badge.type }}">{{ badge.tag }}</span>{% endfor %}{% endif %} {{ post.content | split:'<!--more-->' | first }} {% if post.content contains '<!--more-->' %} <a href="{{ site.baseurl }}{{ post.url }}">read more</a> {% endif %} </div> <hr> {% endfor %} Want to see more? See the <a href="{{ site.baseurl }}/archive/">News Archive</a>.
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: SECURITY.md

| Version | Supported | | - | | | 2.x | :whitecheckmark: | | 1.x | :x: | We ask that all suspected vulnerabilities be privately and responsibly disclosed by . will be used to communicate during the process of identifying and resolving the vulnerability. The advisory will only be made public when the patched version is released to inform the community of the vulnerability and its potential security impact.
Project: kube-hunter (Provisioning / Security & Compliance)
File: KHV034.md

vid: KHV034 title: Etcd is accessible using insecure connection (HTTP) categories: [Unauthenticated Access] severity: high The etcd server (Kubernetes database) port is accessible over plain HTTP, and therefore unencrypted and potentially insecured. Ensure your setup is exposing etcd only on an HTTPS port by using the etcd flags `--key-file` and `--cert-file`.
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: create-a-plugin.md

id: create-a-plugin title: Create a Backstage Plugin description: Documentation on How to Create a Backstage Plugin A Backstage Plugin adds functionality to Backstage. To create a new frontend plugin, make sure you've run `yarn install` and installed dependencies, then run the following on your command line (a shortcut to invoking the ) from the root of your project. ```bash yarn new --select plugin ``` This will create a new Backstage Plugin based on the ID that was provided. It will be built and added to the Backstage App automatically. If the Backstage App is already running (with `yarn start` or `yarn dev`) you should be able to see the default page for your new plugin directly by navigating to `http://localhost:3000/my-plugin`. You can also serve the plugin in isolation by running `yarn start` in the plugin directory. Or by using the yarn workspace command, for example: ```bash yarn workspace @backstage/plugin-my-plugin start # Also supports --check ``` This method of serving the plugin provides quicker iteration speed and a faster startup and hot reloads. It is only meant for local development, and the setup for it can be found inside the plugin's `dev/` directory. There are other plugin library package types that you can chose from. To be able to select the type when you create a new plugin just run: `yarn new`. You'll then be asked what type of plugin you wish to create like this:
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.8.11.md

RabbitMQ `3.8.11` is a maintenance release that contains bug fixes. This release . This release or . Erlang 21.3 . `22.3` or `23.2` releases are recommended. explains what package repositories and tools can be used to provision latest patch versions of Erlang `22.3.x`. See upgrade and compatibility notes first if upgrading from an earlier release series (e.g. `3.7.x`). See the for general documentation on upgrades and for release notes of other releases. When upgrading to this release from `3.7.15` or an older version, extra care has to be taken. Because older RabbitMQ CLI tools can be incompatible with Erlang 22+ releases, RabbitMQ must be upgraded at the same time as Erlang. Alternatively the node can be upgraded to `3.7.18` on Erlang 21.3 first, then Erlang 22.x or 23.x, then RabbitMQ to the most recent 3.8.x release. Any questions about this release, upgrades or RabbitMQ in general are welcome on the and . Quorum queues that had active consumers during a rolling cluster upgrade could run into an exception and restart loop. This issue is specific to . GitHub issue: Nodes that had `reversednslookup` set to `true` could not accept client connections. This issue is specific to . GitHub issue: No dependency changes. Warning: The source code archive provided by GitHub only contains the source of the broker, not the plugins or the client libraries. Please download the archive named `rabbitmq-server-3.8.11.tar.xz`.
Project: Copa (Provisioning / Security & Compliance)
File: faq.md

title: FAQ Copa is capable of patching "OS level" vulnerabilities. This includes packages (like `openssl`) in the image that are managed by a package manager such as `apt` or `yum`. Copa is not currently capable of patching vulnerabilities at the "application level" such as Python packages or Go modules (see for more details). Copa is not capable of patching vulnerabilities for compiled languages, like Go, at the "application level", for instance, Go modules. If your application uses a vulnerable version of the `golang.org/x/net` module, Copa will be unable to patch it. This is because Copa doesn't have access to the application's source code or the knowledge of how to build it, such as compiler flags, preventing it from patching vulnerabilities at the application level. To patch vulnerabilities for applications, you can package these applications and consume them from package repositories, like `http://archive.ubuntu.com/ubuntu/` for Ubuntu, and ensure Trivy can scan and report vulnerabilities for these packages. This way, Copa can patch the applications as a whole, though it cannot patch specific modules within the applications. :::caution Experimental: This feature might change without preserving backwards compatibility. ::: Copa does not support replacing the repositories in the package managers with alternatives. Images must already use the intended package repositories. For example, for debian, updating `/etc/apt/sources.list` from `http://archive.ubuntu.com/ubuntu/` to a mirror, such as `https://mirrors.wikimedia.org/ubuntu/`. If you need the tooling image to use a different package repository, you can create a source policy to define a replacement image and/or pin to a digest. For example, the following source policy replaces `docker.io/library/debian:11-slim` image with `foo.io/bar/baz:latest@sha256:42d3e6bc186572245aded5a0be381012adba6d89355fa9486dd81b0c634695b5`: ```shell cat <<EOF > source-policy.json { "rules": [ { "action": "CONVERT", "selector": { "identifier": "docker-image://docker.io/library/debian:11-slim" }, "updates": { "identifier": "docker-image://foo.io/bar/baz:latest@sha256:42d3e6bc186572245aded5a0be381012adba6d89355fa9486dd81b0c634695b5" } } ] } EOF export EXPERIMENTALBUILDKITSOURCE_POLICY=source-policy.json ``` Tooling image for Debian-based images are `docker.io/library/debian:11-slim` and RPM-based repos are `mcr.microsoft.com/cbl-mariner/base/core:2.0`. For more information on source policies, see .
Project: OpenAPI (App Definition and Development / Application Definition & Image Build)
File: GOVERNANCE.md

The OpenAPI Specification is a project of the OpenAPI Initiative (OAI), under the auspices of the Linux Foundation. For governance of the OAI, review the . The TSC is a self-organizing sub-group of the OAI. Herein are its principles and guidelines. Roles: Elected by TSC members in a plurality vote (oral count). Liaison represents the TSC to the OAI's Business Governing Board (BGB) at board meetings (though this itself does not confer voting rights) and is the public facing mouthpiece of the TSC. all and only members of the TSC are maintainers, and are responsible for approving proposed changes to the specification. If membership drops below 3, work is suspended until the BGB can re-establish the minimum. To maintain agility, the TSC should be capped at a maximum 9 members, though that number can be reconsidered by the TSC in the future. Past members will be noted as emeritus status once they are no longer members. responsible for onboarding of new contributors, dealing with antisocial behaviour before it becomes a code of conduct violation, and managing the issue triage team. Responsible for not giving up or letting down. Requires plurality vote of TSC members. A call-for-nominations period may be agreed upon by the TSC voting members and announced in a timely manner on a weekly TDC call (and documented on the agenda issue), assuming the TSC membership is not already at its maximum. A candidate may be nominated through a motion by a voting TSC member in a closed TSC meeting. A nominee must not receive opposition votes of more than 25% of the TSC voting membership via a confidential vote held electronically within a week following the nomination meeting. Approved nominees become provisional members and are expected to comport themselves as full members of the TSC during the provisional period of 6 months. The provisional period is concluded by a second, confidential vote similar to the nomination period's vote, after which newly confirmed members gain their voting rights. At most there are four voting periods per year (no more than one every three months), with a minimum of one per year. Occasionally it may be necessary to remove a TSC member, such as behavior that violates the code of conduct or prolonged absenteeism. A 66% vote (confidential, electronic) of the other TSC members is required to remove a member. Otherwise, TSC members are removed when they renounce their position by informing the TSC of their effective resignation date via email. The group will strive to achieve all decisions via unopposed consensus. When not possible, unresolved conflicts will be raised to the OAI's Technical Oversight Board (TOB). The TSC will maintain a publicly available document specifying the process in the contributor guidelines for how proposed changes are merged into the specification. The TSC will document and publicize the schedule of merge parties and release parties for the benefit of the developer community.
Project: StarRocks (App Definition and Development / Database)
File: key_column_usage.md

displayed_sidebar: "English" `keycolumnusage` identifies all columns that are restricted by some unique, primary key, or foreign key constraint. The following fields are provided in `keycolumnusage`: | Field | Description | | -- | | | CONSTRAINT_CATALOG | The name of the catalog to which the constraint belongs. This value is always `def`. | | CONSTRAINT_SCHEMA | The name of the database to which the constraint belongs. | | CONSTRAINT_NAME | The name of the constraint. | | TABLE_CATALOG | The name of the catalog to which the table belongs. This value is always `def`. | | TABLE_SCHEMA | The name of the database to which the table belongs. | | TABLE_NAME | The name of the table that has the constraint. | | COLUMN_NAME | The name of the column that has the constraint.If the constraint is a foreign key, then this is the column of the foreign key, not the column that the foreign key references. | | ORDINAL_POSITION | The column's position within the constraint, not the column's position within the table. Column positions are numbered beginning with 1. | | POSITIONINUNIQUE_CONSTRAINT | `NULL` for unique and primary-key constraints. For foreign-key constraints, this column is the ordinal position in key of the table that is being referenced. | | REFERENCEDTABLESCHEMA | The name of the schema referenced by the constraint. | | REFERENCEDTABLENAME | The name of the table referenced by the constraint. | | REFERENCEDCOLUMNNAME | The name of the column referenced by the constraint. |
Project: ContainerSSH (Provisioning / Security & Compliance)
File: CONTRIBUTING.md

Welcome! And a big thank you for wanting to contribute! Let's get you started. First of all, this project is licensed under the . This means that the code you submit will be usable for anyone for any purpose free of charge. Please submit code that you personally own or have permission to submit under this license, and only if you are ok with that. That's out of the way, let's focus on making your contribution happen. For the coding aspects we recommend reading the . It runs you through the nitty-gritty details of setting up the development environment.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: withkeys.md

title: "WithKeys" <!-- Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> Not available. See for updates.
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
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