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

title: kbcli cluster delete Delete clusters. ``` kbcli cluster delete NAME [flags] ``` ``` kbcli cluster delete mycluster kbcli cluster delete --selector clusterdefinition.kubeblocks.io/name=apecloud-mysql ``` ``` -A, --all-namespaces If present, list the requested object(s) across all namespaces. Namespace in current context is ignored even if specified with --namespace. --auto-approve Skip interactive approval before deleting --force If true, immediately remove resources from API and bypass graceful deletion. Note that immediate deletion of some resources may result in inconsistency or data loss and requires confirmation. --grace-period int Period of time in seconds given to the resource to terminate gracefully. Ignored if negative. Set to 1 for immediate shutdown. Can only be set to 0 when --force is true (force deletion). (default -1) -h, --help help for delete --now If true, resources are signaled for immediate shutdown (same as --grace-period=1). --rbac-enabled Specify whether rbac resources will be deleted by kbcli -l, --selector string Selector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints. ``` ``` --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 ``` - Cluster command.
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-pod-restart.1.md

% podman-pod-restart 1 podman\-pod\-restart - Restart one or more pods podman pod restart [options] pod ... Restart containers in one or more pods. Running containers are stopped and restarted. Stopped containers are started. You may use pod IDs or names as input. The pod ID is printed upon successful restart. When restarting multiple pods, an error from restarting one pod does not effect restarting other pods. Restarts all pods Instead of providing the pod name or ID, restart the last created pod. (This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines) Restart pod with a given name: ``` podman pod restart mywebserverpod cc8f0bea67b1a1a11aec1ecd38102a1be4b145577f21fc843c7c83b77fc28907 ``` Restart multiple pods with given IDs: ``` podman pod restart 490eb 3557fb 490eb241aaf704d4dd2629904410fe4aa31965d9310a735f8755267f4ded1de5 3557fbea6ad61569de0506fe037479bd9896603c31d3069a6677f23833916fab ``` Restart the last created pod: ``` podman pod restart --latest 3557fbea6ad61569de0506fe037479bd9896603c31d3069a6677f23833916fab ``` Restart all pods: ``` podman pod restart --all 19456b4cd557eaf9629825113a552681a6013f8c8cad258e36ab825ef536e818 3557fbea6ad61569de0506fe037479bd9896603c31d3069a6677f23833916fab 490eb241aaf704d4dd2629904410fe4aa31965d9310a735f8755267f4ded1de5 70c358daecf71ef9be8f62404f926080ca0133277ef7ce4f6aa2d5af6bb2d3e9 cc8f0bea67b1a1a11aec1ecd38102a1be4b145577f21fc843c7c83b77fc28907 ``` , , July 2018, Originally compiled by Peter Hunt <pehunt@redhat.com>
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_dashboard.md

title: kbcli dashboard List and open the KubeBlocks dashboards. ``` -h, --help help for dashboard ``` ``` --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 all dashboards. - Open one dashboard.
Project: Harbor (Provisioning / Container Registry)
File: 3-12-DB-admin-user-search-project-members.md

Test 3-12 - Admin Search Project Members (DB Mode) ======= To verify that an admin user can search members of a project when users are managed locally by Harbor (DB mode). User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against a local database. ( auth_mode is set to db_auth* .) The user data is stored in a local database. A linux host with Docker CLI installed (Docker client). At least five(5) non-admin users are in Harbor. At least 5 members in a project that admin user is not a member of. NOTE: In below test, user A, B are non system admin users. User A, B and project X should be replaced by longer and meaningful names. MUST use two kinds of browsers at the same time to ensure independent sessions. For example, use Chrome and Firefox, or Chrome and Safari. DO NOT use the same browser to log in two users at the same time in different windows(tabs). Log in to UI as admin. Look for an existing project X that admin is not a member of, project X should have at least 5 members. Search members of project X using different criteria (keywords). Step 3, admin should see results based on search keywords. None
Project: Timescale (App Definition and Development / Database)
File: SECURITY.md

We aim to keep TimescaleDB safe for everyone. Publicly disclosing security bugs in a public forum can put everyone in the Timescale community at risk, however. Therefore, we ask that people follow the below instructions to report security vulnerability. The entire Timescale community thanks you! The supported version is always the latest major release available in our repository. We also release regular minor versions with fixes and corrections alongside some new features as well as patchfix releases, that you should keep upgrading to. Vulnerability fixes are made available as part of these patchfix releases and you can read our list of . You can also take a look at our . If you find a vulnerability in our software, please email the Timescale Security Team at security@timescale.com. Please note that the e-mail address should only be used for reporting undisclosed security vulnerabilities in Timescale products and services. Regular bug reports should be submitted as GitHub issues, while other questions around security, compliance, or functionality can be made either through our support (for customers) or community channels (e.g., , , etc.)
Project: ClickHouse (App Definition and Development / Database)
File: v21.6.5.37-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Here will be listed all the bugs that I am gonna to fix in this PR. (). Backported in : Fix "Missing columns" exception when joining Distributed Materialized View. (). Backported in : Fix serialization of splitted nested messages in Protobuf format. This PR fixes . (). Backported in : Distinguish KILL MUTATION for different tables (fixes unexpected `Cancelled mutating parts` error). (). Backported in : Fixed an error which occurred while inserting a subset of columns using CSVWithNames format. Fixes . (). Backported in : Fix TOCTOU error in installation script. (). Backported in : Fix incorrect behaviour and UBSan report in big integers. In previous versions `CAST(1e19 AS UInt128)` returned zero. (). Backported in : Fix joinGetOrNull with not-nullable columns. This fixes . (). Backported in : Fix error `Bad cast from type DB::ColumnLowCardinality to DB::ColumnVector<char8_t>` for queries where `LowCardinality` argument was used for IN (this bug appeared in 21.6). Fixes . (). Backported in : Fix Logical Error Cannot sum Array/Tuple in min/maxMap. (). Backported in : Support `SimpleAggregateFunction(LowCardinality)` for `SummingMergeTree`. Fixes . (). Backported in : On ZooKeeper connection loss `ReplicatedMergeTree` table might wait for background operations to complete before trying to reconnect. It's fixed, now background operations are stopped forcefully. (). Backported in : Fix the possibility of non-deterministic behaviour of the `quantileDeterministic` function and similar. This closes . (). Backported in : Fix lost `WHERE` condition in expression-push-down optimization of query plan (setting `queryplanfilterpushdown = 1` by default). Fixes . (). Backported in : Fix `REPLACE` column transformer when used in DDL by correctly quoting the formated query. This fixes . (). ExpressionActions compile only necessary places (). odbc fix ().
Project: KICS (Provisioning / Security & Compliance)
File: 4ac0e2b7-d2d2-4af7-8799-e8de6721ccda.md

title: CPU Limits Not Set hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 4ac0e2b7-d2d2-4af7-8799-e8de6721ccda Query name: CPU Limits Not Set Platform: Kubernetes Severity: <span style="color:#edd57e">Low</span> Category: Resource Management URL: CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="10 35 14 31" apiVersion: v1 kind: Pod metadata: name: frontend spec: containers: name: app image: images.my-company.example/app:v4 resources: limits: memory: "64Mi" name: log-aggregator image: images.my-company.example/log-aggregator:v6 resources: requests: memory: "64Mi" cpu: "250m" apiVersion: serving.knative.dev/v1 kind: Configuration metadata: name: dummy-config namespace: knative-sequence spec: template: spec: containers: name: app image: images.my-company.example/app:v4 resources: limits: memory: "64Mi" name: log-aggregator image: images.my-company.example/log-aggregator:v6 resources: requests: memory: "64Mi" cpu: "250m" ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: frontend spec: containers: name: app image: images.my-company.example/app:v4 resources: limits: cpu: "500m" name: log-aggregator image: images.my-company.example/log-aggregator:v6 resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.83.md

layout: release date: 2023-04-20 tag: v0.6.83 Add "isNamespaced" to Meshmodel components(after meshkit change) @Revolyssup (#7501) Add prometheus deployment on playground @Revolyssup (#7565) [Design Configurator] Create design configurator with MeshModel support @Abhishek-kumar09 (#7578) Replace the Logo of Layer5 with Meshery in config.yml workflow @anshgoyalevil (#7568) Delete Layer5-celebration.png @souravpy (#7567) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Revolyssup, @anshgoyalevil, @leecalcote, @souravpy and l5io
Project: CloudTTY (App Definition and Development / Application Definition & Image Build)
File: readme.md

](https://travis-ci.org/kubernetes-sigs/yaml) kubernetes-sigs/yaml is a permanent fork of . A wrapper around designed to enable a better way of handling YAML when marshaling to and from structs. In short, this library first converts YAML to JSON using go-yaml and then uses `json.Marshal` and `json.Unmarshal` to convert to or from the struct. This means that it effectively reuses the JSON struct tags as well as the custom JSON methods `MarshalJSON` and `UnmarshalJSON` unlike go-yaml. For a detailed overview of the rationale behind this method, . This package uses and therefore supports . Caveat #1: When using `yaml.Marshal` and `yaml.Unmarshal`, binary data should NOT be preceded with the `!!binary` YAML tag. If you do, go-yaml will convert the binary data from base64 to native binary data, which is not compatible with JSON. You can still use binary in your YAML files though - just store them without the `!!binary` tag and decode the base64 in your code (e.g. in the custom JSON methods `MarshalJSON` and `UnmarshalJSON`). This also has the benefit that your YAML and your JSON binary data will be decoded exactly the same way. As an example: ``` BAD: exampleKey: !!binary gIGC GOOD: exampleKey: gIGC ... and decode the base64 data in your code. ``` Caveat #2: When using `YAMLToJSON` directly, maps with keys that are maps will result in an error since this is not supported by JSON. This error will occur in `Unmarshal` as well since you can't unmarshal map keys anyways since struct fields can't be keys. To install, run: ``` $ go get sigs.k8s.io/yaml ``` And import using: ``` import "sigs.k8s.io/yaml" ``` Usage is very similar to the JSON library: ```go package main import ( "fmt" "sigs.k8s.io/yaml" ) type Person struct { Name string `json:"name"` // Affects YAML field names too. Age int `json:"age"` } func main() { // Marshal a Person struct to YAML. p := Person{"John", 30} y, err := yaml.Marshal(p) if err != nil { fmt.Printf("err: %v\n", err) return } fmt.Println(string(y)) /* Output: age: 30 name: John */ // Unmarshal the YAML back into a Person struct. var p2 Person err = yaml.Unmarshal(y, &p2) if err != nil { fmt.Printf("err: %v\n", err) return } fmt.Println(p2) /* Output: {John 30} */ } ``` `yaml.YAMLToJSON` and `yaml.JSONToYAML` methods are also available: ```go package main import ( "fmt" "sigs.k8s.io/yaml" ) func main() { j := []byte(`{"name": "John", "age": 30}`) y, err := yaml.JSONToYAML(j) if err != nil { fmt.Printf("err: %v\n", err) return } fmt.Println(string(y)) /* Output: age: 30 name: John */ j2, err := yaml.YAMLToJSON(y) if err != nil { fmt.Printf("err: %v\n", err) return } fmt.Println(string(j2)) /* Output: {"age":30,"name":"John"} */ } ```
Project: TDengine (App Definition and Development / Database)
File: 20-keywords.md

title: Reserved Keywords sidebar_label: Reserved Keywords description: This document describes the reserved keywords in TDengine that cannot be used in object names. There are more than 200 keywords reserved by TDengine, they can't be used as the name of database, table, STable, subtable, column or tag with either upper case, lower case or mixed case. If you need to use these keywords, use the symbol `` ` `` to enclose the keywords, e.g. \`ADD\`. The following list shows all reserved keywords: ABORT ACCOUNT ACCOUNTS ADD AFTER AGGREGATE ALIVE ALL ALTER ANALYZE AND APPS AS ASC AT_ONCE ATTACH BALANCE BEFORE BEGIN BETWEEN BIGINT BINARY BITAND BITNOT BITOR BLOCKS BNODE BNODES BOOL BUFFER BUFSIZE BY CACHE CACHEMODEL CACHESIZE CASCADE CAST CHANGE CLIENT_VERSION CLUSTER COLON COLUMN COMMA COMMENT COMP COMPACT CONCAT CONFLICT CONNECTION CONNECTIONS CONNS CONSUMER CONSUMERS CONTAINS COPY COUNT CREATE CURRENT_USER DATABASE DATABASES DBS DEFERRED DELETE DELIMITERS DESC DESCRIBE DETACH DISTINCT DISTRIBUTED DIVIDE DNODE DNODES DOT DOUBLE DROP DURATION EACH ENABLE END EVERY EXISTS EXPIRED EXPLAIN FAIL FILE FILL FIRST FLOAT FLUSH FOR FROM FUNCTION FUNCTIONS GLOB GRANT GRANTS GROUP HAVING ID IF IGNORE IMMEDIATE IMPORT IN INDEX INDEXES INITIALLY INNER INSERT INSTEAD INT INTEGER INTERVAL INTO IS ISNULL JOIN JSON KEEP KEY KILL LAST LAST_ROW LICENCES LIKE LIMIT LINEAR LOCAL MATCH MAX_DELAY BWLIMIT MAXROWS MAX_SPEED MERGE META MINROWS MINUS MNODE MNODES MODIFY MODULES NCHAR NEXT NMATCH NONE NOT NOTNULL NOW NULL NULLS OF OFFSET ON OR ORDER OUTPUTTYPE PAGES PAGESIZE PARTITIONS PASS PLUS PORT PPS PRECISION PREV PRIVILEGE QNODE QNODES QTIME QUERIES QUERY RAISE RANGE RATIO READ REDISTRIBUTE RENAME REPLACE REPLICA RESET RESTRICT RETENTIONS REVOKE ROLLUP ROW SCHEMALESS SCORES SELECT SEMI SERVER_STATUS SERVER_VERSION SESSION SET SHOW SINGLE_STABLE SLIDING SLIMIT SMA SMALLINT SNODE SNODES SOFFSET SPLIT STABLE STABLES STAR STATE STATE_WINDOW STATEMENT STORAGE STREAM STREAMS STRICT STRING SUBSCRIPTIONS SYNCDB SYSINFO TABLE TABLES TAG TAGS TBNAME TIMES TIMESTAMP TIMEZONE TINYINT TO TODAY TOPIC TOPICS TRANSACTION TRANSACTIONS TRIGGER TRIM TSERIES TTL UNION UNSIGNED UPDATE USE USER USERS USING VALUE VALUES VARCHAR VARIABLE VARIABLES VERBOSE VGROUP VGROUPS VIEW VNODES WAL WALFSYNCPERIOD WAL_LEVEL WALRETENTIONPERIOD WALRETENTIONSIZE WATERMARK WHERE WINDOW_CLOSE WITH WRITE \_C0 \_IROWTS \_QDURATION \_QEND \_QSTART \_ROWTS \_WDURATION \_WEND \_WSTART
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: logs-concentrator.md

Logs-concentrator collects the logs being sent by Lagoon clusters and augments them with additional metadata before inserting them into Elasticsearch. Create certificates according to ReadMe: Create `logs-concentrator-values.yml`: ```yaml title="logs-concentrator-values.yml" tls: caCert: | <<contents of ca.pem>> serverCert: | <<contents of server.pem serverKey: | <<contents of server-key.pem>> elasticsearchHost: elasticsearch-opendistro-es-client-service.elasticsearch.svc.cluster.local elasticsearchAdminPassword: <<ElasticSearch Admin Password>> forwardSharedKey: <<Random 32 Character Password>> users: username: <<Username for Lagoon Remote 1>> password: <<Random Password for Lagoon Remote 1>> service: type: LoadBalancer serviceMonitor: enabled: false ``` Install logs-concentrator: ```bash title="Install logs-concentrator" helm upgrade --install --create-namespace \ --namespace lagoon-logs-concentrator \ -f logs-concentrator-values.yaml \ lagoon-logs-concentrator lagoon/lagoon-logs-concentrator ```
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: restart.md

Restart policy to follow when containers exit. Restart policy does not take effect if a container is stopped via the podman kill or podman stop commands. Valid policy values are: `no` : Do not restart containers on exit `never` : Synonym for no; do not restart containers on exit `on-failure[:maxretries]` : Restart containers when they exit with a non-zero exit code, retrying indefinitely or until the optional *maxretries* count is hit `always` : Restart containers when they exit, regardless of status, retrying indefinitely `unless-stopped` : Identical to always Podman provides a systemd unit file, podman-restart.service, which restarts containers after a system reboot. When running containers in systemd services, use the restart functionality provided by systemd. In other words, do not use this option in a container unit, instead set the `Restart=` systemd directive in the `[Service]` section. See podman-systemd.unit(5) and systemd.service(5).
Project: Meshery (Provisioning / Automation & Configuration)
File: mesheryctl-system-config-eks.md

layout: default title: mesheryctl-system-config-eks permalink: reference/mesheryctl/system/config/eks redirect_from: reference/mesheryctl/system/config/eks/ type: reference display-title: "false" language: en command: system subcommand: config Configure Meshery to use EKS cluster Configure Meshery to connect to EKS cluster <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system config eks [flags] </div> </pre> Configure Meshery to connect to EKS cluster using auth token <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system config eks --token auth.json </div> </pre> Configure Meshery to connect to EKS cluster (if session is logged in using login subcommand) <pre class='codeblock-pre'> <div class='codeblock'> mesheryctl system config eks </div> </pre> <pre class='codeblock-pre'> <div class='codeblock'> -h, --help help for eks -t, --token string Path to token for authenticating to Meshery API </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.