cwielenb/CNCF-Dataset huggingface dataset:
Project: GreptimeDB (App Definition and Development / Database)
File: v0.7.0.md

| | | | | - | | CPU | AMD Ryzen 7 7735HS (8 core 3.2GHz) | | Memory | 32GB | | Disk | SOLIDIGM SSDPFKNU010TZ | | OS | Ubuntu 22.04.2 LTS | | | | | - | -- | | Machine | c5d.2xlarge | | CPU | 8 core | | Memory | 16GB | | Disk | 50GB (GP3) | | OS | Ubuntu 22.04.1 | | Environment | Ingest rate (rows/s) | | | -- | | Local | 369581.464 | | EC2 c5d.2xlarge | 298716.664 | | Query type | Local (ms) | EC2 c5d.2xlarge (ms) | | | - | -- | | cpu-max-all-1 | 30.56 | 54.74 | | cpu-max-all-8 | 52.69 | 70.50 | | double-groupby-1 | 664.30 | 1366.63 | | double-groupby-5 | 1391.26 | 2141.71 | | double-groupby-all | 2828.94 | 3389.59 | | groupby-orderby-limit | 718.92 | 1213.90 | | high-cpu-1 | 29.21 | 52.98 | | high-cpu-all | 5514.12 | 7194.91 | | lastpoint | 7571.40 | 9423.41 | | single-groupby-1-1-1 | 19.09 | 7.77 | | single-groupby-1-1-12 | 27.28 | 51.64 | | single-groupby-1-8-1 | 31.85 | 11.64 | | single-groupby-5-1-1 | 16.14 | 9.67 | | single-groupby-5-1-12 | 27.21 | 53.62 | | single-groupby-5-8-1 | 39.62 | 14.96 |
Project: CockroachDB (App Definition and Development / Database)
File: vsc-extension-quickstart.md

This folder contains all of the files necessary for your extension. `package.json` - this is the manifest file in which you declare your language support and define the location of the grammar file that has been copied into your extension. `syntaxes/optgen.tmLanguage` - this is the Text mate grammar file that is used for tokenization. `language-configuration.json` - this the language configuration, defining the tokens that are used for comments and brackets. Make sure the language configuration settings in `language-configuration.json` are accurate. Press `F5` to open a new window with your extension loaded. Create a new file with a file name suffix matching your language. Verify that syntax highlighting works and that the language configuration settings are working. You can relaunch the extension from the debug toolbar after making changes to the files listed above. You can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with your extension to load your changes. To add features such as intellisense, hovers and validators check out the VS Code extenders documentation at https://code.visualstudio.com/docs To start using your extension with Visual Studio Code copy it into the `<user home>/.vscode/extensions` folder and restart Code. To share your extension with the world, read on https://code.visualstudio.com/docs about publishing an extension.
Project: Meshery (Provisioning / Automation & Configuration)
File: brigade.md

layout: integration title: Brigade subtitle: Collaborative and visual infrastructure as code for Brigade image: /assets/img/integrations/brigade/icons/color/brigade-color.svg permalink: extensibility/integrations/brigade docURL: https://docs.meshery.io/extensibility/integrations/brigade description: integrations-category: App Definition and Development integrations-subcategory: Continuous Integration & Delivery registrant: Artifact Hub components: featureList: [ "Designed to quickly and efficently handle large volumes of events.", "Offers full management of user and service account authorization/authentication.", "Enables high event throughput via its backing message queue." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: Artifact Hub (App Definition and Development / Application Definition & Image Build)
File: keptn_annotations.md

You can provide some extra information about your Keptn integrations by using the `annotations` field in the . keptn/kind (string) This annotation allows providing the kind of the integration. Supported values: webhook, testing, deployment, notification, observability, remediation, sli-provider, finops and security. It's possible to add multiple kinds by using a comma separated list, like shown in the example below. keptn/version (string) Use this annotation to provide the Keptn version(s) your integration is compatible with. ```yaml ... annotations: keptn/kind: "webhook,testing" keptn/version: "0.10.0-0.12.0" ```
Project: Pluto (Provisioning / Security & Compliance)
File: installation.md

meta: name: description content: "Fairwinds Pluto | Installation documentation" We have an plugin . You can install with: ``` asdf plugin-add pluto asdf list-all pluto asdf install pluto <latest version> asdf local pluto <latest version> ``` Install the binary from our page. ``` brew install FairwindsOps/tap/pluto ``` Note: This is not maintained by Fairwinds, but should stay up to date with future releases. ``` scoop install pluto ``` Fairwinds signs the Pluto docker image and the checksums file with . Our public key is available at https://artifacts.fairwinds.com/cosign.pub You can verify the checksums file from the page with the following command: ``` cosign verify-blob checksums.txt --signature=checksums.txt.sig --key https://artifacts.fairwinds.com/cosign.pub ``` Verifying docker images is even easier: ``` cosign verify us-docker.pkg.dev/fairwinds-ops/oss/pluto:v5 --key https://artifacts.fairwinds.com/cosign.pub ```
Project: SpiceDB (App Definition and Development / Database)
File: TELEMETRY.md

SpiceDB reports metrics that are used to understand how clusters are being configured and the performance they are experiencing. The intent of collecting this information is to prioritize development that will have the most impact on the community. Telemetry can always be disabled by providing the flag `--telemetry-endpoint=""`. Telemetry is reported via the Prometheus Remote Write protocol. Any metrics prefixed with `spicedb_telemetry` are reported hourly to `telemetry.authzed.com`. You can find all of the code in . Information about the SpiceDB environment. CPU Architecture: architecture of the CPU vCPUs: number of CPUs reported by the Go runtime OS: operating system family as reported by the Go Runtime Datastore Engine: datastore engine configured Cluster ID: unique identifier for a cluster's datastore NodeID: unique identifier for the node, usually the hostname Count of the number of objects defined by the schema. Cluster ID: unique identifier for a cluster's datastore NodeID: unique identifier for the node, usually the hostname Rough estimate of the number of relationships stored in the datastore. Cluster ID: unique identifier for a cluster's datastore NodeID: unique identifier for the node, usually the hostname Histogram of cluster dispatches performed by the instance. Method: gRPC method of the dispatch request Cached: boolean of whether or not the dispatch was a cache hit Cluster ID: unique identifier for a cluster's datastore NodeID: unique identifier for the node, usually the hostname
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-provider-switch.md

layout: default title: mesheryctl-system-provider-switch permalink: reference/mesheryctl/system/provider/switch redirect_from: reference/mesheryctl/system/provider/switch/ type: reference display-title: "false" language: en command: system subcommand: provider switch provider and redeploy Switch provider of context in focus and redeploy Meshery. Run `mesheryctl system provider list` to see the available providers. <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system provider switch [provider] [flags] </div> </pre> Switch provider and redeploy Meshery <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system provider switch [provider] </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for switch </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> --config string path to config file (default "/home/runner/.meshery/config.yaml") -c, --context string (optional) temporarily change the current context. -v, --verbose verbose output -y, --yes (optional) assume yes for user interactive prompts. </div> </pre> Go back to , if you want to add content manually to the CLI documentation, please refer to the for guidance.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_iam_custom_role.md

+++ title = "googleiamcustom_role resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleiamcustom_role" identifier = "inspec/resources/gcp/googleiamcustomrole.md googleiamcustomrole resource" parent = "inspec/resources/gcp" +++ A `googleiamcustom_role` is used to test a Google CustomRole resource ```ruby describe googleiamcustom_role(project: 'chef-gcp-inspec', name: 'admin-role') do it { should exist } its('stage') { should eq 'GA' } its('included_permissions') { should eq ["iam.roles.list"] } end describe googleiamcustom_role(project: 'chef-gcp-inspec', name: 'nonexistent') do it { should_not exist } end ``` Properties that can be accessed from the `googleiamcustom_role` resource: `name` : The name of the role. `title` : A human-readable title for the role. Typically this is limited to 100 UTF-8 bytes. `description` : Human-readable description for the role `included_permissions` : Names of permissions this role grants when bound in an IAM policy. `stage` : The current launch stage of the role. `deleted` : The current deleted state of the role Ensure the is enabled for the current project.
Project: MongoDB (App Definition and Development / Database)
File: ppc64le_build_from_source.md

Bazel doesn't release to the PPC64LE architecture. To address this, MongoDB maintains our own Bazel build that we perform on our PPC64LE development systems. Bazel usually comes with a built-in JDK. However, the tooling used to build the built-in JDK doesn't support PPC64LE. To get around this, an external JDK must be present on both the system compiling the Bazel executable itself as well as the host running Bazel as a build system. On the MongoDB PPC64LE Evergreen static hosts and dev hosts, the OpenJDK 11 installation exists at: /usr/lib/jvm/java-11-openjdk-11.0.4.11-2.el8.ppc64le To compile with on these platforms, the developer must set JAVA_HOME before invoking Bazel. curl -O -L https://github.com/bazelbuild/bazel/releases/download/6.4.0/bazel-6.4.0-dist.zip unzip bazel-6.4.0-dist.zip JAVA_HOME=/usr/lib/jvm/java-11-openjdk-11.0.4.11-2.el8.ppc64le ./compile.sh
Project: Druid (App Definition and Development / Database)
File: azure.md

id: azure title: "Microsoft Azure" <!-- ~ Licensed to the Apache Software Foundation (ASF) under one ~ or more contributor license agreements. See the NOTICE file ~ distributed with this work for additional information ~ regarding copyright ownership. The ASF licenses this file ~ to you 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. --> To use this Apache Druid extension, `druid-azure-extensions` in the extensions load list. is another option for deep storage. This requires some additional Druid configuration. |Property|Description|Possible Values|Default| |--||--|-| |`druid.storage.type`|azure||Must be set.| |`druid.azure.account`||Azure Storage account name.|Must be set.| |`druid.azure.key`||Azure Storage account key.|Optional. Set one of key, sharedAccessStorageToken or useAzureCredentialsChain.| |`druid.azure.sharedAccessStorageToken`||Azure Shared Storage access token|Optional. Set one of key, sharedAccessStorageToken or useAzureCredentialsChain..| |`druid.azure.useAzureCredentialsChain`|Use for authentication|Optional. Set one of key, sharedAccessStorageToken or useAzureCredentialsChain.|False| |`druid.azure.managedIdentityClientId`|If you want to use managed identity authentication in the `DefaultAzureCredential`, `useAzureCredentialsChain` must be true.||Optional.| |`druid.azure.container`||Azure Storage container name.|Must be set.| |`druid.azure.prefix`|A prefix string that will be prepended to the blob names for the segments published to Azure deep storage| |""| |`druid.azure.protocol`|the protocol to use|http or https|https| |`druid.azure.maxTries`|Number of tries before canceling an Azure operation.| |3| |`druid.azure.maxListingLength`|maximum number of input files matching a given prefix to retrieve at a time| |1024| |`druid.azure.storageAccountEndpointSuffix`| The endpoint suffix to use. Use this config instead of `druid.azure.endpointSuffix`. Override the default value to connect to . This config supports storage accounts enabled for . Note: do not include the storage account name prefix in this config value. | Examples: `ABCD1234.blob.storage.azure.net`, `blob.core.usgovcloudapi.net`| `blob.core.windows.net`| See for more information.
Project: KubeMQ (App Definition and Development / Streaming & Messaging)
File: kubemq_events.md

Execute Kubemq 'events' Pub/Sub commands Execute Kubemq 'events' Pub/Sub commands ``` kubemq events [flags] ``` ``` kubemq events send kubemq events receive kubemq events attach ``` ``` -h, --help help for events ``` - - Events attach to 'events' channels command - Events receive a body from 'events' channel command - Events send messages to an 'events' channel command
Project: Beam (App Definition and Development / Streaming & Messaging)
File: nokia.md

title: "Nokia" icon: /images/logos/powered-by/nokia.png hasLink: "https://www.nokia.com/" <!-- 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. -->
Project: KubeVirt (App Definition and Development / Application Definition & Image Build)
File: discard-passthrough.md

Sparsification can make a disk thin-provisioned, in other words it allows to convert the freed space within the disk image into free space back on the host. The utility can be used on a mounted filesystem to discard the blocks not used by the filesystem. In order to be able to sparsify a disk inside the guest, the disk needs to be configured in the with the option `discard=unmap`. In KubeVirt, every disk is passed as default with this option enabled. It is possible to check if the trim configuration is supported in the guest by running`lsblk -D`, and check the discard options supported on every disk. Example: ```bash $ lsblk -D NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO loop0 0 4K 4G 0 loop1 0 64K 4M 0 sr0 0 0B 0B 0 rbd0 0 64K 4M 0 vda 512 512B 2G 0 vda1 0 512B 2G 0 ``` However, in certain cases like preallocaton or when the disk is thick provisioned, the option needs to be disabled. The disk's PVC has to be marked with an annotation that contains `/storage.preallocation` or `/storage.thick-provisioned`, and set to true. If the volume is preprovisioned using and the is enabled, then the PVC is automatically annotated with: `cdi.kubevirt.io/storage.preallocation: true` and the discard passthrough option is disabled. Example of a PVC definition with the annotation to disable discard passthrough: ```yaml apiVersion: v1 kind: PersistentVolumeClaim metadata: name: pvc annotations: user.custom.annotation/storage.thick-provisioned: "true" spec: storageClassName: local accessModes: ReadWriteOnce volumeMode: Filesystem resources: requests: storage: 1Gi ```
Project: YDB (App Definition and Development / Database)
File: with.md

It's set after the data source in `FROM` and is used for additional hints for tables. You can't use hints for subqueries and . The following values are supported: `INFER_SCHEMA`: Sets the flag for output of the table schema. The behavior is similar to the , but for a specific data source. You can specify the number of rows to output (from 1 to 1000). `FORCEINFERSCHEMA`: Sets the flag for table schema output. The behavior is similar to the , but for a specific data source. You can specify the number of rows to output (from 1 to 1000). `DIRECT_READ`: Suppresses certain optimizers and enforces accessing table contents as is. The behavior is similar to the debug , but for a specific data source. `INLINE`: Hints that the table contents is small and you need to use its in-memory view to process the query. The actual size of the table is not controlled in this case, and if it's large, the query might fail with an out-of-memory error. `UNORDERED`: Suppresses original table sorting. `XLOCK`: Hints that you need to lock the table exclusively. It's useful when you read a table at the stage of processing the , and then update its contents in the main query. Avoids data loss if an external process managed to change the table between executing a metaprogram phase and the main part of the query. `SCHEMA` type: Hints that the specified table schema must be used entirely, ignoring the schema in the metadata. `COLUMNS` type: Hints that the specified types should be used for columns whose names match the table's column names in the metadata, as well as which columns are additionally present in the table. `IGNORETYPEV3`, `IGNORETYPEV3`: Sets the flag to ignore type_v3 types in the table. The behavior is similar to the , but for a specific data source. When setting the `SCHEMA` and `COLUMNS` hints, the type must be a . {% if featurebulktables %} If you use the `SCHEMA` hint, then with the table functions , , , , you can use an empty list of tables that is treated as an empty table with columns defined in the `SCHEMA`. {% endif %} Examples: ```yql SELECT key FROM mytable WITH INFERSCHEMA; SELECT key FROM mytable WITH FORCEINFER_SCHEMA="42"; ``` ```yql $s = (SELECT COUNT(*) FROM my_table WITH XLOCK); INSERT INTO my_table WITH TRUNCATE SELECT EvaluateExpr($s) AS a; ``` ```yql SELECT key, value FROM my_table WITH SCHEMA Struct<key:String, value:Int32>; ``` ```yql SELECT key, value FROM my_table WITH COLUMNS Struct<value:Int32?>; ``` ```yql SELECT key, value FROM EACH($my_tables) WITH SCHEMA Struct<key:String, value:List<Int32>>; ```
Project: ThreatMapper (Provisioning / Security & Compliance)
File: installation.md

title: Installing ThreatMapper The ThreatMapper product consists of a Management Console, and multiple Sensor Agents and Cloud Scanner tasks that are deployed within your production platform(s). The Management Console is deployed first. The Management console generates an API key and a URL which you will need when you install the Cloud Scanner tasks and Sensor Agents. ```mdx-code-block import DocCardList from '@theme/DocCardList'; import {useCurrentSidebarCategory} from '@docusaurus/theme-common'; <DocCardList items={useCurrentSidebarCategory().items}/> ```
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: lagoon-logging.md

Lagoon integrates with OpenSearch to store application, container and router logs. Lagoon Logging collects the application, router and container logs from Lagoon projects, and sends them to the logs concentrator. It needs to be installed onto each `lagoon-remote` instance. In addition, it should be installed in the `lagoon-core` cluster to collect logs from the `lagoon-core` service. This is configured in the `LagoonLogs` section. Logging Overview: See also: . Read more about Lagoon logging here: Create `lagoon-logging-values.yaml`: ```yaml title="lagoon-logging-values.yaml" tls: caCert: | << content of ca.pem from Logs-Concentrator>> clientCert: | << content of client.pem from Logs-Concentrator>> clientKey: | << content of client-key.pem from Logs-Concentrator>> forward: username: <<Username for Lagoon Remote 1>> password: <<Password for Lagoon Remote 1>> host: <<ExternalIP of Logs-Concentrator Service LoadBalancer>> hostName: <<Hostname in Server Cert of Logs-Concentrator>> hostPort: '24224' selfHostname: <<Hostname in Client Cert of Logs-Concentrator>> sharedKey: <<Generated ForwardSharedKey of Logs-Concentrator>> tlsVerifyHostname: false clusterName: <<Short Cluster Identifier>> logsDispatcher: serviceMonitor: enabled: false logging-operator: monitoring: serviceMonitor: enabled: false lagoonLogs: enabled: true rabbitMQHost: lagoon-core-broker.lagoon-core.svc.cluster.local rabbitMQUser: lagoon rabbitMQPassword: <<RabbitMQ Lagoon Password>> excludeNamespaces: {} ``` Install `lagoon-logging`: ```bash title="Install lagoon-logging" helm repo add banzaicloud-stable https://kubernetes-charts.banzaicloud.com helm upgrade --install --create-namespace \ --namespace lagoon-logging \ -f lagoon-logging-values.yaml \ lagoon-logging lagoon/lagoon-logging ``` If you'd like logs from `ingress-nginx` inside `lagoon-logging`: The ingress controller must be installed in the namespace `ingress-nginx` Add the content of this file to `ingress-nginx`: ```yaml title="ingress-nginx log-format-upstream" controller: config: log-format-upstream: >- { "time": "$time_iso8601", "remoteaddr": "$remoteaddr", "x-forwarded-for": "$httpxforwarded_for", "true-client-ip": "$httptrueclient_ip", "reqid": "$reqid", "remoteuser": "$remoteuser", "bytessent": $bytessent, "requesttime": $requesttime, "status": "$status", "host": "$host", "requestproto": "$serverprotocol", "request_uri": "$uri", "request_query": "$args", "requestlength": $requestlength, "requesttime": $requesttime, "requestmethod": "$requestmethod", "httpreferer": "$httpreferer", "httpuseragent": "$httpuseragent", "namespace": "$namespace", "ingressname": "$ingressname", "servicename": "$servicename", "serviceport": "$serviceport" } ``` Your logs should start flowing!
Project: ClickHouse (App Definition and Development / Database)
File: 70_performance-issue.md

name: Performance issue about: Report something working slower than expected title: '' labels: performance assignees: '' (you don't have to strictly follow this form) Describe the situation What exactly works slower than expected? How to reproduce Which ClickHouse server version to use Which interface to use, if matters Non-default settings, if any `CREATE TABLE` statements for all tables involved Sample data for all these tables, use if necessary Queries to run that lead to slow performance Expected performance What are your performance expectation, why do you think they are realistic? Has it been working faster in older ClickHouse releases? Is it working faster in some specific other system? Additional context Add any other context about the problem here.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.4.25.md

layout: release date: 2020-11-29 tag: v0.4.25 [ doc ] add completion doc @jiraguha (#1962) fixes #1954 @vineethvanga18 (#1958) Replace the chart icon @Aisuko (#1955) Reformat the rest of the adapter charts @Aisuko (#1917) fix: backend build for meshery @kushthedude (#1979) fix: docker builds failures in CI @kushthedude (#1959) fix: backend build for meshery @kushthedude (#1979) Bump start-server-and-test from 1.11.2 to 1.11.5 in /ui @dependabot-preview (#1939) Bump cypress from 5.5.0 to 5.6.0 in /ui @dependabot-preview (#1940) fix: docker builds failures in CI @kushthedude (#1959) Bump uuid from 8.3.0 to 8.3.1 in /ui @dependabot-preview (#1932) Bump husky from 4.2.5 to 4.3.0 in /ui @dependabot-preview (#1938)