cwielenb/CNCF-Dataset huggingface dataset:
Project: YugabyteDB (App Definition and Development / Database)
File: managed-cli-usage.md

title: ybm CLI usage resource headerTitle: ybm usage linkTitle: usage description: YugabyteDB Managed CLI reference usage resource. headcontent: Output cluster usage menu: preview_yugabyte-cloud: identifier: managed-cli-usage parent: managed-cli-reference weight: 20 type: docs Use the `usage` resource to output billing usage data for your account. ```text Usage: ybm usage get [flags] ``` Output usage for clusters `my-cluster` and `your-cluster` for September 2023: ```sh ybm usage get \ --cluster-name my-cluster \ --cluster-name your-cluster \ --start 2023-09-01 \ --end 2023-09-30 ``` Retrieve usage data for specified clusters in a specified date range. | Flag | Description | | : | : | | --cluster-name | Name of the cluster to get usage data. You can retrieve usage data for multiple clusters by specifying multiple `--cluster-name` arguments. | | --end | Required. End date in RFC3339 format (for example, '2023-09-30T23:59:59.999Z') or 'yyyy-MM-dd' format (for example, '2023-09-30'). | | --output-file | Output filename. | | --output-format | Output format. Options: csv, json. | | --start | Required. Start date in RFC3339 format (for example, '2023-09-30T23:59:59.999Z') or 'yyyy-MM-dd' format (for example, '2023-09-30'). |
Project: ArangoDB (App Definition and Development / Database)
File: is_exception_ptr_available.md

+++ title = "`isexceptionptr_available<T>`" description = "True if an exception ptr can be constructed from a `T`." +++ `::value` is true if an exception ptr can be constructed from a `T` e.g. if there exists an ADL discovered free function `makeexceptionptr(T)`. `::type` is the type that would result if `::value` is true, else `void`. Overridable: By template specialisation into the `trait` namespace. Default: True if `T` is an exception ptr, else to metaprogramming which performs the ADL discovery of `makeexceptionptr(T)`. Note that the STL defines an ADL discovered free function {{% api "std::makeexceptionptr(T)" %}}. Thus this trait will pick up that free function. Namespace: `BOOSTOUTCOMEV2_NAMESPACE::trait` Header: `<boost/outcome/trait.hpp>` Variable alias: `isexceptionptravailablev<T>`
Project: ShardingSphere (App Definition and Development / Database)
File: migrate-table-into.en.md

+++ title = "MIGRATE TABLE INTO" weight = 6 +++ `MIGRATE TABLE INTO` syntax is used to migration table from source to target {{< tabs >}} {{% tab name="Grammar" %}} ```sql MigrateTableInto ::= 'MIGRATE' 'TABLE' migrationSource '.' tableName 'INTO' (databaseName '.')? tableName migrationSource ::= identifier databaseName ::= identifier tableName ::= identifier ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When `databaseName` is not specified, the default is the currently used `DATABASE`. If `DATABASE` is not used, `No database selected` will be prompted. Migrate table from source to current database ```sql MIGRATE TABLE ds0.torder INTO t_order; ``` Migrate table from source to specified database ```sql UNREGISTER MIGRATION SOURCE STORAGE UNIT ds1, ds2; ``` `MIGRATE`, `TABLE`, `INTO`
Project: StarRocks (App Definition and Development / Database)
File: ucase.md

displayed_sidebar: "English" This function converts a string to upper-case. It is analogous to the function upper. ```Haskell VARCHAR ucase(VARCHAR str) ``` ```Plain Text mysql> SELECT ucase("AbC123"); +--+ |ucase('AbC123') | +--+ |ABC123 | +--+ ``` UCASE
Project: Polaris (Provisioning / Security & Compliance)
File: exemptions.md

meta: name: description content: "Fairwinds Polaris | Exemptions" Sometimes a workload really does need to do things that Polaris considers insecure. For instance, many of the `kube-system` workloads need to run as root, or need access to the host network. In these cases, we can add exemptions to allow the workload to pass Polaris checks. Exemptions can be added in a few different ways: Namespace: By editing the Polaris config. Controller: By annotating a controller, or editing the Polaris config. Container: By editing the Polaris config. To exempt a controller from all checks via annotations, use the annotation `polaris.fairwinds.com/exempt=true`, e.g. ``` kubectl annotate deployment my-deployment polaris.fairwinds.com/exempt=true ``` To exempt a controller from a particular check via annotations, use an annotation in the form of `polaris.fairwinds.com/<check>-exempt=true`, e.g. ``` kubectl annotate deployment my-deployment polaris.fairwinds.com/cpuRequestsMissing-exempt=true ``` To add exemptions via the config, you have to specify at least one or more of the following: A namespace A list of controller names A list of container names You can also specify a list of particular rules. If no rules are specified then every rule is exempted. Controller names and container names are matched as a prefix, so an empty string will match every controller or container respectively. For example: ```yaml exemptions: namespace: default namespace: kube-system controllerNames: dns-controller rules: hostNetworkSet controllerNames: dns-controller rules: hostNetworkSet namespace: kube-system containerNames: coredns rules: hostNetworkSet ```
Project: Druid (App Definition and Development / Database)
File: middlemanager.md

id: middlemanager title: "MiddleManager service" sidebar_label: "MiddleManager" <!-- ~ 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. --> The MiddleManager service is a worker service that executes submitted tasks. MiddleManagers forward tasks to that run in separate JVMs. Druid uses separate JVMs for tasks to isolate resources and logs. Each Peon is capable of running only one task at a time, wheres a MiddleManager may have multiple Peons. For Apache Druid MiddleManager service configuration, see . For basic tuning guidance for the MiddleManager service, see . For a list of API endpoints supported by the MiddleManager, see the . ``` org.apache.druid.cli.Main server middleManager ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.13.md

layout: release date: 2021-05-17 tag: v0.5.13 [mesheryctl] Add skip-update flag on `system restart` cmd @alphaX86 (#2929) [UI] Icons scaled with all browser zoom in/out @Ayush-Khandelwal-007 (#2934) Updating table for docs @amino19 (#2950) Update system status and system logs @navendu-pottekkat (#2930) Fix system status and IsMesheryRunning @navendu-pottekkat (#2922) Fix system update for `platform: kubernetes` @navendu-pottekkat (#2926) Fix `system logs` @navendu-pottekkat (#2915) Apply operators conditionally based on commands @metonymic-smokey (#2916) Fixed bug with deploying Meshery operator on platform: Docker @navendu-pottekkat (#2914)
Project: Meshery (Provisioning / Automation & Configuration)
File: 10-04-2022-19-47-10_6221f429.md

timestamp: "2022-10-04 19:47:11 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: KICS (Provisioning / Security & Compliance)
File: 33fc6923-6553-4fe6-9d3a-4efa51eb874b.md

title: Node Restriction Admission Control Plugin Not Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 33fc6923-6553-4fe6-9d3a-4efa51eb874b Query name: Node Restriction Admission Control Plugin Not Set Platform: Kubernetes Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: When using kube-apiserver command, the --enable-admission-plugins flag should have 'NodeRestriction' plugin and the plugin should be correctly configured in AdmissionControl Config file<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--enable-admission-plugins=AlwaysAdmit"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver"] args: ["--enable-admission-plugins=NodeRestriction", "--admission-control-config-file=path/to/plugin/config/file.yaml"] restartPolicy: OnFailure ``` ```yaml title="Negative test num. 2 - yaml file" apiVersion: v1 kind: Pod metadata: name: command-demo labels: purpose: demonstrate-command spec: containers: name: command-demo-container image: gcr.io/google_containers/kube-apiserver-amd64:v1.6.0 command: ["kube-apiserver","--enable-admission-plugins=NodeRestriction", "--admission-control-config-file=path/to/plugin/config/file.yaml"] args: [] restartPolicy: OnFailure ```
Project: KICS (Provisioning / Security & Compliance)
File: bf9d42c7-c2f9-4dfe-942c-c8cc8249a081.md

title: User With Privilege Escalation By Actions 'iam:AddUserToGroup' hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: bf9d42c7-c2f9-4dfe-942c-c8cc8249a081 Query name: User With Privilege Escalation By Actions 'iam:AddUserToGroup' Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: User with privilege escalation by actions 'iam:AddUserToGroup' and Resource set to '*'. For more information see https://rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation/.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "awsiamuser" "cosmic" { name = "cosmic" } resource "awsiamuserpolicy" "testinline_policy" { name = "testinlinepolicy" user = awsiamuser.cosmic.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "iam:AddUserToGroup", ] Effect = "Allow" Resource = "*" }, ] }) } resource "awsiampolicy_attachment" "test-attach" { name = "test-attachment" users = [awsiamuser.cosmic.name] roles = [awsiamrole.role.name] groups = [awsiamgroup.group.name] } ``` ```tf title="Negative test num. 1 - tf file" resource "awsiamuser" "cosmic2" { name = "cosmic2" } resource "awsiamuserpolicy" "inlinepolicyruninstances2" { name = "inlinepolicyrun_instances" user = awsiamuser.cosmic2.name policy = jsonencode({ Version = "2012-10-17" Statement = [ { Action = [ "ec2:Describe*", ] Effect = "Allow" Resource = "*" }, ] }) } ```
Project: YugabyteDB (App Definition and Development / Database)
File: select.md

title: SELECT linkTitle: "SELECT " description: SELECT menu: preview: parent: api-yedis weight: 2038 aliases: /preview/api/yedis/select type: docs `SELECT` is used to change the yedis database that the client is communicating with. By default, all client connections start off communicating with the default database ("0"). To start using a database, other than the default database ("0"), it needs to be pre-created using the `CREATEDB` command before use. Returns a status string if successful. Returns an error if the database is not already created. ```sh $ SET k1 v1 ``` ``` "OK" ``` ```sh $ GET k1 ``` ``` "v1" ``` ```sh $ LISTDB ``` ``` 1) "0" ``` ```sh $ CREATEDB "second" ``` ``` "OK" ``` ```sh $ SELECT "second" ``` ``` "OK" ``` ```sh $ SET k1 v2 ``` ``` "OK" ``` ```sh $ GET k1 ``` ``` "v2" ``` ```sh $ SELECT 0 ``` ``` "OK" ``` ```sh $ GET k1 ``` ``` "v1" ```
Project: StarRocks (App Definition and Development / Database)
File: percentile_disc.md

displayed_sidebar: "English" Returns a percentile value based on a discrete distribution of the input column `expr`. If the exact percentile value cannot be found, this function returns the larger value between the two closest values. This function is supported from v2.5 onwards. ```SQL PERCENTILE_DISC (expr, percentile) ``` `expr`: the column for which you want to calculate the percentile value. The column can be of any data type that is sortable. `percentile`: the percentile of the value you want to find. It must be a constant floating-point number between 0 and 1. For example, if you want to find the median value, set this parameter to `0.5`. If you want to find the value at the 70th percentile, specify 0.7. The data type of the return value is the same as `expr`. NULL values are ignored in the calculation. Create table `exam` and insert data into this table. ```sql CREATE TABLE exam ( subject STRING, score INT ) DISTRIBUTED BY HASH(`subject`); INSERT INTO exam VALUES ('chemistry',80), ('chemistry',100), ('chemistry',null), ('math',60), ('math',70), ('math',85), ('physics',75), ('physics',80), ('physics',85), ('physics',99); ``` ```Plain select * from exam order by subject; +--+-+ | subject | score | +--+-+ | chemistry | 80 | | chemistry | 100 | | chemistry | NULL | | math | 60 | | math | 70 | | math | 85 | | physics | 75 | | physics | 80 | | physics | 85 | | physics | 99 | +--+-+ ``` Calculate the median of each subject. ```SQL select subject, percentile_disc(score, 0.5) from exam group by subject; ``` Output ```Plain +--+--+ | subject | percentile_disc(score, 0.5) | +--+--+ | chemistry | 100 | | math | 70 | | physics | 85 | +--+--+ ```
Project: YugabyteDB (App Definition and Development / Database)
File: scaling-writes.md

title: Writes headerTitle: Writes linkTitle: Writes description: Writes in YugabyteDB. headcontent: Write performance when scaling out menu: v2.18: name: Writes identifier: scaling-writes parent: explore-scalability weight: 50 type: docs Writes scale linearly in YugabyteDB as more nodes are added to the cluster. In YugabyteDB, the rows are based on the primary key (or the row ID when a primary key is not defined), and these tablets are distributed across the nodes in the cluster. Because data is distributed across the different nodes in the cluster, YugabyteDB can perform parallel write operations, which results in linear scaling of performance when nodes are added to the cluster. YugabyteDB can clock more than 1 million writes/second in both and APIs. On a 100-node YugabyteDB cluster set up with c5.4xlarge instances (16 vCPUs at 3.3GHz) in a single zone, the cluster performed 1.26 million writes/second with 1.7ms latency. The cluster configuration is shown in the following illustration. On a 50-node YugabyteDB cluster on GCP using n1-standard-16 instances (16 vCPUs at 2.20GHz), YCQL clocked 1.2M writes/second with 3.1ms average latency. The cluster configuration is shown in the following illustration.
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: v1.10.0.md

title: v1.10.0 weight: 998990000 Ansible projects are now scaffolded with `Kustomize` version `3.8.7`. This version of kustomize requires that the path to patch file be provided with the `--path` flag in `add patch` command. In `molecule/default/prepare.yml` file, update the command under `Set pull policy`, to be: ```diff name: Set pull policy command: '{{ "{{ kustomize }}" }} edit add patch pullpolicy/{{ "{{ operatorpull_policy }}" }}.yaml' command: '{{ "{{ kustomize }}" }} edit add patch --path pullpolicy/{{ "{{ operatorpull_policy }}" }}.yaml' ``` See for more details.
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.16.0.md

replace quay.io/brancz/kube-rbac-proxy with bitnami/kube-rbac-proxy by @tomqin93 in https://github.com/Edgenesis/shifu/pull/576 Newest readme by @rachelzhang0922 in https://github.com/Edgenesis/shifu/pull/557 Add link to cncf landscape by @saiyan86 in https://github.com/Edgenesis/shifu/pull/571 Bump sigs.k8s.io/controller-runtime from 0.14.5 to 0.14.6 by @dependabot in https://github.com/Edgenesis/shifu/pull/566 Bump golang.org/x/crypto from 0.7.0 to 0.8.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/575 Bump github.com/spf13/cobra from 1.6.1 to 1.7.0 by @dependabot in https://github.com/Edgenesis/shifu/pull/573 Bump github.com/onsi/gomega from 1.27.5 to 1.27.6 by @dependabot in https://github.com/Edgenesis/shifu/pull/570 Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.15.0...v0.16.0
Project: Confidential Containers (Provisioning / Security & Compliance)
File: v0.6.0.md

Release Date: June 7th, 2023 Please see the for details on how to try out Confidential Containers. Please refer to our and pages for a definition of the acronyms used in this document. Support for attesting pod VMs with Azure vTPMs on SEV-SNP Support for using Project Amber as an attestation service Support for Cosign signature validation with s390x Pulling guest images with many layers can no longer cause guest CPU starvation. Attestation Service upgraded to avoid several security issues in Go packages. CC-KBC & KBS support with SGX attester/verifier for Occlum and CI for enclave-cc Confidential Containers is tested with attestation on the following platforms: Intel TDX AMD SEV(-ES) Intel SGX The following platforms are untested or partially supported: IBM Secure Execution (SE) on IBM zSystems (s390x) running LinuxONE AMD SEV-SNP The following platforms are in development: ARM CCA The following are known limitations of this release: Platform support is rapidly changing Image signature validation with AMD SEV-ES is not covered by CI. SELinux is not supported on the host and must be set to permissive if in use. The generic KBS does not yet supported all platforms. The format of encrypted container images is still subject to change The container image format itself may still change The tools to generate images are not in their final form The image format itself is subject to change in upcoming releases Not all image repositories support encrypted container images. CoCo currently requires a custom build of `containerd`, which is installed by the operator. Codepath for pulling images will change significantly in future releases. `crio` is only supported with `cloud-api-adaptor`. Complete integration with Kubernetes is still in progress. OpenShift support is not yet complete. Existing APIs do not fully support the CoCo security and threat model. Some commands accessing confidential data, such as `kubectl exec`, may either fail to work, or incorrectly expose information to the host Container images must be downloaded separately (inside guest) for each pod. The CoCo community aspires to adopting open source security best practices, but not all practices are adopted yet. We track our status with the OpenSSF Best Practices Badge, which remained at 64% at the time of this release. Vulnerability reporting mechanisms still need to be created. Public github issues are still appropriate for this release until private reporting is established. None
Project: Chef InSpec (Provisioning / Security & Compliance)
File: ipfilter.md

+++ title = "ipfilter resource" draft = false gh_repo = "inspec" platform = "bsd" [menu] [menu.inspec] title = "ipfilter" identifier = "inspec/resources/os/ipfilter.md ipfilter resource" parent = "inspec/resources/os" +++ Use the `ipfilter` Chef InSpec audit resource to test rules defined for `ipfilter`. The `ipfstat` utility is used to report on packet filter statistics and filter list. `ipfstat -io` is used to view the active filtering rule set for the input and the output side of the kernel IP processing. The rule match is done against the output rules of `ipfstat -io`. {{< readfile file="content/inspec/reusable/md/inspec_installation.md" >}} An `ipfilter` resource block declares tests for rules defined for IP Filter: describe ipfilter do it { should have_rule("RULE") } end where `have_rule('RULE')` tests the active rule for ipfilter. This must match the entire line taken from `'ipfstat -io'`. The following examples show how to use this Chef InSpec audit resource. describe ipfilter do it { should have_rule("pass in quick on lo0 all") } it { should have_rule("pass out quick on lo0 all") } end describe ipfilter do it { should have_rule("pass in quick on xl0 all") } it { should have_rule("pass out quick on xl0 all") } end describe ipfilter do it { should have_rule("pass out quick on dc0 proto tcp from any to any port = ftp flags S/FSRPAU keep state") } end describe ipfilter do it { should have_rule("pass out quick on dc0 proto tcp from any to any port = ssh flags S/FSRPAU keep state") } end Note that the rule specification must exactly match what is in the output of `'ipfstat -io'`, which depends on how you have built your rules. {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} This resource has the following special matchers. The `have_rule` matcher tests the named rule against the information in the output rule of `'ipfstat -io'`: it { should have_rule("RULE") }
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_login.md

title: kbcli login Authenticate with the KubeBlocks Cloud ``` kbcli login [flags] ``` ``` -c, --context string Context name. -h, --help help for login --no-browser Do not open the browser for authentication. -o, --org string Organization name. -r, --region string Specify the region [jp] to log in. (default "jp") ``` ``` --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 --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 ```