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

title: kbcli dashboard open Open one dashboard. ``` kbcli dashboard open NAME [DASHBOARD-TYPE] [--port PORT] [flags] ``` ``` kbcli dashboard open kubeblocks-grafana kbcli dashboard open kubeblocks-grafana --port 8080 kbcli dashboard open kubeblocks-grafana mysql ``` ``` -h, --help help for open --pod-running-timeout duration The time (like 5s, 2m, or 3h, higher than zero) to wait for at least one pod is running (default 1m0s) --port string dashboard local port ``` ``` --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 ``` - List and open the KubeBlocks dashboards.
Project: LinuxKit (Provisioning / Automation & Configuration)
File: 2017-08-02.md

Time: 9am PDT (12pm EDT, 5pm BST) Meeting location: https://docker.zoom.us/j/779801882 Announcement: Moby project forum post - coming soon Video recording: https://www.youtube.com/watch?v=5FHYdwQlAMs Previous meeting notes: Introductions & Administrivia (5 min) Alpine Linux - security deep dive - @ncopa (45 min) Project updates (10 min) Next meeting: 2017-08-16 deep dive TBD please feel free to propose additional deep dives and discussion topics! Alpine Linux intro Question: what's the strategy for getting rid of SUID? File capabilities? Answer: no real plan Question: what's the strategy in the face of no more public GRSecurity patches? Answer: Currently forward porting last test patch, slightly risky, not a good solution. May discontinue use at some point. Question: Thoughts on capabilities? Answer: fs-caps sound like a nice way to get rid of SUID bits, since they're uid-independent. Question: Thoughts on LSMs? Answer: SELinux is complicated, AppArmor is simpler and perhaps better in that sense, not on the roadmap currently for Alpine to implement default profiles (but may be in the future) Question: What exactly is the deal with TLS? glibc does lazy allocation, so after pthread_create(), at some later point, the actual allocation for TLS may fail, and glibc simply aborts(). This is one reason dlopen is a noop, but not the only reason.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_dataprotection_backup.md

title: kbcli dataprotection backup Create a backup for the cluster. ``` kbcli dataprotection backup NAME [flags] ``` ``` kbcli dp backup mybackup --cluster mycluster kbcli dp backup mybackup --cluster mycluster --method mymethod kbcli dp backup mybackup --cluster mycluster --policy mypolicy kbcli dp backup mybackup --cluster mycluster --parent-backup myparentbackup ``` ``` --cluster string Cluster name --deletion-policy string Deletion policy for backup, determine whether the backup content in backup repo will be deleted after the backup is deleted, supported values: [Delete, Retain] (default "Delete") -h, --help help for backup --method string Backup methods are defined in backup policy (required), if only one backup method in backup policy, use it as default backup method, if multiple backup methods in backup policy, use method which volume snapshot is true as default backup method --parent-backup string Parent backup name, used for incremental backup --policy string Backup policy name, if not specified, use the cluster default backup policy --retention-period string Retention period for backup, supported values: [1y, 1mo, 1d, 1h, 1m] or combine them [1y1mo1d1h1m], if not specified, the backup will not be automatically deleted, you need to manually delete it. ``` ``` --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 --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 ``` - Data protection command.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.8.29.md

RabbitMQ `3.8.29` is a maintenance release. All users are recommended to upgrade to this release. RabbitMQ releases are distributed via , , and . This release and . explains what package repositories and tools can be used to provision modern Erlang versions. See the for general documentation on upgrades and for release notes of other releases. If upgrading from a `3.7.x` release, see upgrade and compatibility notes first. If upgrading from a `3.6.x` or older , first upgrade to and then to this version. Any questions about this release, upgrades or RabbitMQ in general are welcome on the and . Release notes are kept under . Contributors are encouraged to update them together with their changes. This helps with release automation and more consistent release schedule. Significantly faster queue re-import from on subsequent node restarts. Initial definition import still takes the same amount of time as before. GitHub issue: Maintenance mode could run into a timeout during queue leadership transfer. Contributed by @felixhuettner. GitHub issue: Connection data transfer rate units were incorrectly displayed when rate was less than 1 kiB per second. Contributed by @zgabi. GitHub issue: Corrected a help message for node memory usage tool tip. Contributed by @etc-crontab. GitHub issue: More Erlang 24.3's `eldap` library compatibility improvements. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.8.29.tar.xz` instead of the source tarball produced by GitHub.
Project: ArangoDB (App Definition and Development / Database)
File: checked.md

+++ title = "`checked<T, E = varies>`" description = "A type alias to a `stdchecked<T, E>` (standalone edition) or `boostchecked<T, E>` (Boost edition)." +++ A type alias to either {{% api "stdchecked<T, E = std::errorcode>" %}} (standalone edition) or {{% api "boostchecked<T, E = boost::system::errorcode>" %}} (Boost edition). This means that `checked<T>` uses the appropriate default alias depending on which edition of Outcome is in use. Namespace: `BOOSTOUTCOMEV2_NAMESPACE` Header: `<boost/outcome/result.hpp>`
Project: YugabyteDB (App Definition and Development / Database)
File: ta-20864.md

title: TA-20864 headerTitle: Failure of foreign key checks headcontent: 27 Feb 2024 type: docs showRightNav: true cascade: unversioned: true menu: preview_releases: identifier: ta-20864 weight: 1 rightNav: hideH2: true type: docs | Product | Affected Versions | Related Issues | Fixed In | | :- | : | :- | :- | | {{<product "ysql">}} | {{<release "All">}} | {{<issue 20864>}} | N/A | Foreign key checks may erroneously fail when writes impacting the foreign key check are done in the same statement. Upgrade to a release with the fix. To enhance YugabyteDB's performance, optimization occurs in the buffering of reads and writes in the PostgreSQL layer before sending them to DocDB in a single request. This reduces the number of round trips between PostgreSQL and DocDB, resulting in improved efficiency. The table contains multiple foreign keys, with one of them being self-referencing. During write operations, there are typically at least two statements. One of these writes impacts the foreign key check for another write operation. An example schema on the database is as follows: ```sql CREATE TABLE company(k INT PRIMARY KEY)")); CREATE TABLE employee( k INT PRIMARY KEY, companyfk INT, managerfk INT, UNIQUE(k, company_fk), FOREIGN KEY (company_fk) REFERENCES company(k), FOREIGN KEY (managerfk, companyfk) REFERENCES employee(company_fk, k))) ); Query Which will provide an error: INSERT INTO employee VALUES (1, 1, NULL), (2, 1, 1), (3, 1, 1)); ``` Query that results in an error: ```sql INSERT INTO employee VALUES (1, 1, NULL), (2, 1, 1), (3, 1, 1)); ``` List example on
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.8.md

layout: release date: 2022-09-20 tag: v0.6.8 language: en Implement `app import` subcommand and refactor `app onboard` @alphaX86 (#6061) [Performance] Make performance tests consistent with multi-cluster @gr455 (#6186) [UI] Remote config icon update @Chadha93 (#6221) [rjsf] text field validation @harkiratsm (#6218) New Svg for designer drawer @Harshit-Dandriyal (#6217) [bug] Fix Validation of PatternFile @theBeginner86 (#6223) [bug] Fix Validation of PatternFile @theBeginner86 (#6223) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Chadha93, @Harshit-Dandriyal, @Revolyssup, @alphaX86, @gr455, @harkiratsm, @leecalcote and @theBeginner86
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: developer-guide.md

title: Development linkTitle: Development weight: 1 version 1.21 Go to the and follow the to fork and set up a local repository. Build the Operator SDK CLI `operator-sdk` binary: ```sh make install ``` See the and guides for more information. See the for more information. The operator-sdk repo uses to test each pull request and build images for both master commits and release tags. You can alter these processes by modifying the appropriate . The operator-sdk project builds binaries for . If you wish to add support for a new one, please create a feature request issue before implementing support for that platform and submitting a PR. If you'd like to implement support yourself, you can test a new architecture by enabling Actions in your repository, add a platform pair to the workflow's `build and push` step, and push to your main branch. Once the updated Action passes, submit a PR linking the passing Action run.
Project: StarRocks (App Definition and Development / Database)
File: loadMethodIntro.md

Synchronous loading using + Asynchronous loading using Continuous asynchronous loading using Each of these options has its own advantages, which are detailed in the following sections. In most cases, we recommend that you use the INSERT+`FILES()` method, which is much easier to use. However, the INSERT+`FILES()` method currently supports only the Parquet, ORC, and CSV file formats. Therefore, if you need to load data of other file formats such as JSON, or , you can resort to Broker Load. If you need to load a large number of data files with a significant data volume in total (for example, more than 100 GB or even 1 TB), we recommend that you use the Pipe method. Pipe can split the files based on their number or size, breaking down the load job into smaller, sequential tasks. This approach ensures that errors in one file do not impact the entire load job and minimizes the need for retries due to data errors.
Project: KubeArmor (Provisioning / Security & Compliance)
File: res-cap.md

```sh root@ubuntu-1-deployment-f987bd4d6-xzcb8:/# tcpdump tcpdump: eth0: You don't have permission to capture on that device (socket: Operation not permitted) root@ubuntu-1-deployment-f987bd4d6-xzcb8:/# ``` ``` { "Action":"Block", "ClusterName":"k3sn0d3", "ContainerID":"aaf2118edcc20b3b04a0fae6164f957993bf3c047fd8cb33bc37ac7d0175e848", "ContainerImage":"docker.io/kubearmor/ubuntu-w-utils:0.1@sha256:b4693b003ed1fbf7f5ef2c8b9b3f96fd853c30e1b39549cf98bd772fbd99e260", "ContainerName":"ubuntu-1-container", "Data":"syscall=SYS_SOCKET", "Enforcer":"AppArmor", "HashID":"dd12f0f12a75b30d47c5815f93412f51b259b74ac0eccc9781b6843550f694a3", "HostName":"worker-node02", "HostPID":38077, "HostPPID":38065, "Labels":"container=ubuntu-1 group=group-1", "Message":"", "NamespaceName":"multiubuntu", "Operation":"Network", "Owner":{ "Name":"ubuntu-1-deployment", "Namespace":"multiubuntu", "Ref":"Deployment" }, "PID":124, "PPID":114, "PodName":"ubuntu-1-deployment-f987bd4d6-xzcb8", "PolicyName":"ksp-ubuntu-1-cap-net-raw-block", "ProcessName":"/usr/sbin/tcpdump", "Resource":"domain=AFPACKET type=SOCKRAW protocol=768", "Result":"Operation not permitted", "Severity":"1", "Source":"/usr/sbin/tcpdump", "Tags":"", "Timestamp":1705405378, "Type":"MatchedPolicy", "UID":0, "UpdatedTime":"2024-01-16T11:42:58.662928Z", "UpdatedTimeISO":"2024-01-16T11:42:58.662Z", "cluster_id":"16402", "component_name":"kubearmor", "instanceGroup":"0", "instanceID":"0", "workload":"1" } ```
Project: YugabyteDB (App Definition and Development / Database)
File: gcp-deployment-manager.md

title: Deploy YugabyteDB in Google Cloud Platform with GCP Deployment Manager headerTitle: Google Cloud Platform linkTitle: Google Cloud Platform description: Use the GCP Deployment Manager to deploy a YugabyteDB cluster in Google Cloud Platform. menu: v2.18: identifier: deploy-in-gcp-1-deployment-manager parent: public-clouds weight: 640 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li > <a href="../gcp-deployment-manager/" class="nav-link active"> <i class="icon-shell"></i> Google Cloud Deployment Manager </a> </li> <li> <a href="../gke/" class="nav-link"> <i class="fa-regular fa-dharmachakra" aria-hidden="true"></i> Google Kubernetes Engine (GKE) </a> </li> <li > <a href="../terraform/" class="nav-link"> <i class="icon-shell"></i> Terraform </a> </li> </ul> Download and Install . Clone the repository. ](https://console.cloud.google.com/cloudshell/editor?cloudshellgitrepo=https%3A%2F%2Fgithub.com%2Fyugabyte%2Fgcp-deployment-manager.git) To deploy using Google Cloud Deployment Manager: Change the current directory to the cloned repository. Use the following `gcloud` command to create the deployment-manager deployment: ```sh $ gcloud deployment-manager deployments create <your-deployment-name> --config=yugabyte-deployment.yaml ``` Wait 5-10 minutes for the creation of all resources to complete. After the deployment creation is complete, you can describe it as follows: ```sh $ gcloud deployment-manager deployments describe <your-deployment-name> ``` The output includes the YugabyteDB Admin URL, JDBC URL, and YSQL, YCQL, and YEDIS connection strings. You can use the YugabyteDB Admin URL to access the Admin portal.
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_fault_io.md

title: kbcli fault io IO chaos. ``` -h, --help help for io ``` ``` --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 ``` - Inject faults to pod. - Override the attributes of the file. - Causes IO operations to return specific errors. - Delayed IO operations. - Alters the contents of the file, distorting the contents of the file.
Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: fix-11623.en.md

Upgrade library `esockd` from 5.9.6 to 5.9.7 This upgrade included Enhancements regarding proxy protocol error and timeout. Lowered `ssl_error` exceptions to info level logging. Malformed MQTT packet parsing exception log level is lowered from `error` to `info`. In command `emqx ctl listeners` output, the `shutdown_count` counter is incremented when TLS handshake failure (`sslerror`) or Malformed packet (`frameerror`) happens.
Project: KICS (Provisioning / Security & Compliance)
File: e576ce44-dd03-4022-a8c0-3906acca2ab4.md

title: BigQuery Dataset Is Public hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e576ce44-dd03-4022-a8c0-3906acca2ab4 Query name: BigQuery Dataset Is Public Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Access Control URL: BigQuery dataset is anonymously or publicly accessible<br> ```tf title="Positive test num. 1 - tf file" hl_lines="14" resource "googlebigquerydataset" "positive1" { datasetid = "exampledataset" friendly_name = "test" description = "This is a test description" location = "EU" defaulttableexpiration_ms = 3600000 labels = { env = "default" } access { role = "OWNER" special_group = "allAuthenticatedUsers" } } ``` ```tf title="Negative test num. 1 - tf file" resource "googlebigquerydataset" "negative1" { datasetid = "exampledataset" friendly_name = "test" description = "This is a test description" location = "EU" defaulttableexpiration_ms = 3600000 labels = { env = "default" } access { role = "OWNER" userbyemail = googleserviceaccount.bqowner.email } access { role = "READER" domain = "hashicorp.com" } } ```
Project: Metal³ (Provisioning / Automation & Configuration)
File: inspectAnnotation.md

Baremetalhost's(BMH) Status sub-resource contains a hardware key which contains the result of introspection which is carried out during BMH registration. In some circumstances it may be desirable to disable this inspection process, and provide data from external source. The Inspect Annotation provides some interfaces to enable this. Note the `inspect.metal3.io/hardwaredetails` annotation is consumed: At any time when `inspect.metal3.io: disabled` is specified When there is no existing HardwareDetails data in the Status The `inspect.metal3.io/hardwaredetails` annotation will be removed when successfully processed or when the status is already set, generating an event in each case. The structure of the annotation's value should match the hardware status field schema, or a subset of that schema, for example: ```yaml inspect.metal3.io: disabled inspect.metal3.io/hardwaredetails: '{"systemVendor":{"manufacturer":"QEMU", "productName":"Standard PC (Q35 + ICH9, 2009)","serialNumber":""}, "firmware":{"bios":{"date":"","vendor":"","version":""}},"ramMebibytes":4096, "nics":[{"name":"eth0","model":"0x1af4 0x0001","mac":"00:b7:8b:bb:3d:f6", "ip":"172.22.0.64","speedGbps":0,"vlanId":0,"pxe":true}], "storage":[{"name":"/dev/sda","rotational":true,"sizeBytes":53687091200, "vendor":"QEMU","model":"QEMU HARDDISK","serialNumber":"drive-scsi0-0-0-0", "hctl":"6:0:0:0"}],"cpu":{"arch":"x86_64", "model":"Intel Xeon E3-12xx v2 (IvyBridge)","clockMegahertz":2494.224, "flags":["foo"],"count":4},"hostname":"hwdAnnotation-0"}' ``` Apart from that, sometimes you might want to request re-inspection for an already inspected host. This might be necessary when there was a hardware change on the host and you want to ensure that BMH status contains the latest inspection data about your host. To request a new inspection, simply annotating the host with `inspect.metal3.io` is enough. Once inspection is requested, you should see the BMH in `inspecting` state until inspection is completed and by the end of inspection the `inspect.metal3.io` annotation will be removed by Baremetal Operator. Note that, inspection can be requested only when BMH is in `Ready` state (i.e. before it is provisioned). The reason for this limitation is because requesting an inspection for provisioned BMH will result in rebooting the host, which will result in application downtime running on that host.