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

title: kbcli cluster list-backups List backups. ``` kbcli cluster list-backups [flags] ``` ``` kbcli cluster list-backups ``` ``` -A, --all-namespaces If present, list the requested object(s) across all namespaces. Namespace in current context is ignored even if specified with --namespace. -h, --help help for list-backups --name string The backup name to get the details. -o, --output format prints the output in the specified format. Allowed values: table, json, yaml, wide (default table) -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. --show-labels When printing, show all labels as the last column (default hide labels column) ``` ``` --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: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.6.9.md

RabbitMQ `3.6.9` is a security and maintenance release. See the for general documentation on upgrades. This release has no incompatibilities with 3.6.7. See upgrade and compatibility notes if upgrading from an earlier release. Details for the CVEs below are pending publication. `CVE-2017-4965`: XSS vulnerabilities in management UI `CVE-2017-4966`: authentication details are stored in browser-local storage without expiration `CVE-2017-4967`: XSS vulnerabilities in management UI As part of the patch addressing `CVE-2017-4966` management UI sessions were limited to 8 hours. Certain TCP and TLS listener configuration settings could break JSON serialisation of `GET /api/overview` responses. GitHub issues: , , More numerical types are now handled for the "hops" property. GitHub issue: Calling ExchangeBind more than once with the same arguments threw an exception. GitHub issues: , To upgrade a non-clustered RabbitMQ simply install the new version. All configuration and persistent message data are retained. When upgrading using definitions export/import from versions earlier than 3.6.0, see http://rabbitmq.com/passwords.html. To upgrade a RabbitMQ cluster, follow the instructions . Warning: The source code archive provided by GitHub only contains the source of the broker, not the plugins or the client libraries. Please download the archive named `rabbitmq-3.6.9.tar.gz`.
Project: KICS (Provisioning / Security & Compliance)
File: e94d3121-c2d1-4e34-a295-139bfeb73ea3.md

title: Shared Host IPC Namespace hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: e94d3121-c2d1-4e34-a295-139bfeb73ea3 Query name: Shared Host IPC Namespace Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Resource Management URL: Container should not share the host IPC namespace<br> ```tf title="Positive test num. 1 - tf file" hl_lines="8" resource "kubernetes_pod" "positive1" { metadata { name = "terraform-example" } spec { host_ipc = true container { image = "nginx:1.7.9" name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } dns_config { nameservers = ["1.1.1.1", "8.8.8.8", "9.9.9.9"] searches = ["example.com"] option { name = "ndots" value = 1 } option { name = "use-vc" } } dns_policy = "None" } } ``` ```tf title="Negative test num. 1 - tf file" resource "kubernetes_pod" "negative1" { metadata { name = "terraform-example" } spec { host_ipc = false container { image = "nginx:1.7.9" name = "example" env { name = "environment" value = "test" } port { container_port = 8080 } liveness_probe { http_get { path = "/nginx_status" port = 80 http_header { name = "X-Custom-Header" value = "Awesome" } } initialdelayseconds = 3 period_seconds = 3 } } dns_config { nameservers = ["1.1.1.1", "8.8.8.8", "9.9.9.9"] searches = ["example.com"] option { name = "ndots" value = 1 } option { name = "use-vc" } } dns_policy = "None" } } ```
Project: StarRocks (App Definition and Development / Database)
File: array_position.md

displayed_sidebar: "English" Obtains the position of an element in an array. ```Haskell arrayposition(anyarray, any_element) ``` `any_array`: the array to be searched. `any_element`: an expression that matches the element in an array. Returns the position of the specified element if the element can be found in the specified array and returns 0 if the element cannot be found in the array. Example 1: Obtain the position of an element in an array. ```plaintext mysql> select array_position(["apple","orange","pear"], "orange"); +--+ | array_position(['apple','orange','pear'], 'orange') | +--+ | 2 | +--+ 1 row in set (0.01 sec) ``` Example 2: Obtain the position of `NULL` in an array. ```sql mysql> select array_position([1, NULL], NULL); ``` ```plaintext +--+ | array_position([1,NULL], NULL) | +--+ | 2 | +--+ 1 row in set (0.00 sec) ``` Example 3: Obtain the position of a sub-array in a multi-dimensional array. A position can be returned only when a sub-array that consists of the same elements in the same order as the specified sub-array can be found in the multi-dimensional array. ```Lua mysql> select array_position([[1,2,3], [4,5,6]], [4,5,6]); +--+ | array_position([[1,2,3],[4,5,6]], [4,5,6]) | +--+ | 2 | +--+ 1 row in set (0.00 sec) mysql> select array_position([[1,2,3], [4,5,6]], [4,6,5]); +--+ | array_position([[1,2,3],[4,5,6]], [4,6,5]) | +--+ | 0 | +--+ 1 row in set (0.00 sec) ``` ARRAY_POSITION, ARRAY
Project: Paladin Cloud (Provisioning / Security & Compliance)
File: code_of_conduct.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at Info@PaladinCloud.io. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
Project: KICS (Provisioning / Security & Compliance)
File: 227c2f58-70c6-4432-8e9a-a89c1a548cf5.md

title: Bucket Without Versioning hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 227c2f58-70c6-4432-8e9a-a89c1a548cf5 Query name: Bucket Without Versioning Platform: GoogleDeploymentManager Severity: <span style="color:#ff7213">Medium</span> Category: Observability URL: Bucket should have versioning enabled<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" resources: name: bucket type: storage.v1.bucket properties: name: my-bucket ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="7" resources: name: bucket type: storage.v1.bucket properties: name: my-bucket versioning: enabled: false ``` ```yaml title="Negative test num. 1 - yaml file" resources: name: bucket type: storage.v1.bucket properties: name: my-bucket versioning: enabled: true ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: cruise.md

title: "Cruise" icon: /images/logos/powered-by/cruise.png hasLink: "https://medium.com/cruise/introducing-terra-cruises-data-processing-platform-c6a476bb5b72" <!-- 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: KubeVela (App Definition and Development / Application Definition & Image Build)
File: labels.eg.md

```yaml apiVersion: core.oam.dev/v1beta1 kind: Application metadata: name: myapp spec: components: name: express-server type: webservice properties: image: crccheck/hello-world port: 8000 traits: type: labels properties: "release": "stable" type: annotations properties: "description": "web application" ```
Project: KubeClarity (Provisioning / Security & Compliance)
File: PULL_REQUEST_TEMPLATE.md

Please provide a meaningful description of what this change will do, or is for. Bonus points for including links to related issues, other PRs, or technical references. Note that by not including a description, you are asking reviewers to do extra work to understand the context of this change, which may lead to your PR taking much longer to review, or result in it not being reviewed at all. [ ] Bug Fix [ ] New Feature [ ] Breaking Change [ ] Refactor [ ] Documentation [ ] Other (please describe) [ ] Existing issues have been referenced (where applicable) [ ] I have verified this change is not present in other open pull requests [ ] Functionality is documented [ ] All code style checks pass [ ] New code contribution is covered by automated tests [ ] All new and existing tests pass
Project: Devfile (App Definition and Development / Application Definition & Image Build)
File: bug_report.md

name: Bug report about: Report a bug title: '' labels: '' assignees: '' /kind bug <!-- Welcome! - We kindly ask you to: Fill out the issue template below Use the Devfile Community Slack Channel: https://kubernetes.slack.com/archives/C02SX9E5B55 if you have a question rather than a bug or feature request. If you havent joined the Kubernetes workspace before, follow https://slack.k8s.io/. Thanks for understanding and for contributing to the project! --> <!-- Uncomment appropriate `/area` lines, and delete the rest. For example, `> /area api` would simply become: `/area api` --> /area ci /area api /area library /area registry /area alizer /area devworkspace /area integration-tests /area test-automation /area releng /area landing-page Operating System and version: Go Pkg Version: <!-- Please paste the text output of the console in the error output section with a screenshot --> Operating System and version: Node.js version: Yarn version: Project.json: <!-- Please paste the text output of the console in the error output section with a screenshot --> Operating System and version: Browser name and version: Describe the bug: <!-- A clear and concise description of what the bug is. --> To Reproduce: <!-- Steps to reproduce the behavior. --> <!-- A clear and concise description of what you expected to happen. --> <!-- To get logs: ci: please copy the github workflow output api: please copy the terminal output library: please copy the terminal output registry: follow instruction under "Collecting Logs" to find log: https://github.com/devfile/registry-support/blob/main/TROUBLESHOOTING.md devworkspace: copy the logs from the controller (kubectl logs deploy/devworkspace-controller -n $NAMESPACE) test-automation: api: follow instruction under "Running tests locally" to find test log: https://github.com/devfile/api/tree/main/test library: follow instruction under "Running the tests locally" to find test log: https://github.com/devfile/library/tree/main/tests devworkspace: copy the logs from the controller (kubectl logs deploy/devworkspace-controller -n $NAMESPACE) integration-tests: please copy the build log under prow ci result for QE ingetration tests --> <!-- Add any other context about the problem here. --> <!-- Describe the workaround if applicable. --> <!-- Provide suggestion on how to fix the bug upon your investigation, if applicable. -->
Project: Hazelcast Jet (App Definition and Development / Streaming & Messaging)
File: event-time-processing.md

title: Event Time-Based Processing description: How Jet deals with event-time disorder with techniques such as watermarks. id: version-4.0-event-time-processing original_id: event-time-processing In we introduced event time and, especially, event disorder. Here we'll present some of the tricks Jet uses to deal with it. The key event-time concept is the watermark which corresponds to the notion of now in the processing-time domain. It marks a position in the data stream and tells what time it is at that position. Check out this diagram: The user has configured the maximum tolerable lag as `0:02`. We can see that the watermark always reflects that and lags behind the event timestamps by at most `0:02`. When an event arrives out of order, the watermark lags behind it by less than `0:02` and, if the lag would be negative (watermark is already past the event's timestamp), Jet considers that event as a "fluke in the input" and ignores it. By this time Jet already emitted the aggregation result for the window where this event belongs so there's no point in dealing with it. The picture above is the simplest and a very straightforward aspect of dealing with event disorder. More serious problems start when we take into account that a Jet processing task doesn't receive a single data stream, but many streams from many parallel upstream tasks. We illustrated this fact in the page. Every such substream has its own watermark and we must find a way to combine (coalesce) all of them into a unified watermark value observed by the task. The invariant we want to protect is that an event that wasn't late within its substream, can't become late in the merged flow. This means that the coalesced watermark should be the lowest watermark of any substream: The overall result is that there is no upper bound anymore on how much the watermark can lag behind an event in the stream. The substream with the highest latency holds back all others, but not just that: since the watermark is purely data-driven, even a substream with no latency can cause unbounded watermark lag simply by having low activity &mdash; a lot of time passing between consecutive events. This can occur when substreams come from a partitioned source. Since partitioning is based on some key like user ID, it may happen that there are no users active on a partition. While on others there are millions of events, on one there is nothing for minutes. Hazelcast Jet mitigates this problem by tracking the watermark on each partition of a partitioned source, detecting when a partition has gone idle, and starting to advance the watermark even in the absence of data.
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.2.6.2.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs | Major | . | Jian He | Jian He | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | For better error recovery, check if the directory exists before using it for localization. | Major | nodemanager | zhihai xu | zhihai xu | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | RM should handle NMContainerStatuses sent by NM while registering if NM is Reconnected node | Blocker | resourcemanager | Rohith Sharma K S | Rohith Sharma K S | | | Fetcher#copyMapOutput is leaking usedMemory upon IOException during InMemoryMapOutput shuffle handler | Blocker | . | Eric Payne | Eric Payne | | | Default value for maximum nodemanager connect wait time is too high | Major | . | Jason Lowe | Naganarasimha G R | | | Should use equals when compare Resource in RMNodeImpl#ReconnectNodeTransition | Minor | resourcemanager | zhihai xu | zhihai xu | | | Two RMNodes for the same NodeId are used in RM sometimes after NM is reconnected. | Major | resourcemanager | zhihai xu | zhihai xu | | | Retrospect on decision of making RM crashed if any exception throw in ZKRMStateStore | Critical | . | Junping Du | Jian He | | | Completed container whose app is finished is not removed from NMStateStore | Major | . | Jun Gong | Jun Gong | | | MapReduce doesn't set the HADOOP\_CLASSPATH for jar lib in distributed cache. | Critical | . | Junping Du | Junping Du | | | RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset synchronously | Major | resourcemanager | Jun Gong | Jun Gong | | | Fix wrong value of JOB\_FINISHED event in JobHistoryEventHandler | Major | . | Shinichi Yamashita | Shinichi Yamashita | | | ZKRMStateStore shouldn't create new session without occurrance of SESSIONEXPIED | Blocker | resourcemanager | Bibin A Chundatt | Varun Saxena | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | RM HA UI redirection needs to be fixed when both RMs are in standby mode | Major | resourcemanager | Xuan Gong | Xuan Gong | | | RM should print alert messages if Zookeeper and Resourcemanager gets connection issue | Critical | yarn | Yesha Vora | Xuan Gong |
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: 03-consuming.md

id: consuming title: Consuming Utility APIs sidebar_label: Consuming APIs description: Consuming utility APIs NOTE: The new frontend system is in alpha and is only supported by a small number of plugins. All of the utility API extensions that were passed into your app through installed plugins, get instantiated and configured in the right order by the framework, and are then made available for consumption. You can interact with these instances in the following ways. The most common consumption pattern for utility APIs is to call the `useApi` hook inside React components to get an implementation via its API ref. This applies whether it was originally provided from the core framework or from a plugin. ```tsx import { useApi, configApiRef } from '@backstage/frontend-plugin-api'; const MyComponent = () => { const configApi = useApi(configApiRef); const title = configApi.getString('app.title'); // ... }; ``` The `useApi` hook always returns a value, or throws an exception if the API ref could not be resolved to a registered implementation. For advanced use cases, where you explicitly want to optionally request a utility API that may or may not have been provided at runtime, you can use the underlying `useApiHolder` hook instead. ```tsx import { useApiHolder, configApiRef } from '@backstage/frontend-plugin-api'; const MyComponent = () => { const apis = useApiHolder(); const configApi = apis.get(configApiRef); // may return undefined if (configApi) { const title = configApi.getString('app.title'); // ... } }; ``` Your utility APIs can depend on other utility APIs in their factories. You do this by declaring `deps` on your `createApiFactory`, and reading the outcome in your `factory`. ```tsx import { configApiRef, createApiExtension, createApiFactory, discoveryApiRef, } from '@backstage/frontend-plugin-api'; import { MyApiImpl } from './MyApiImpl'; const myApi = createApiExtension({ factory: createApiFactory({ api: myApiRef, deps: { configApi: configApiRef, discoveryApi: discoveryApiRef, }, factory: ({ configApi, discoveryApi }) => { return new MyApiImpl({ configApi, discoveryApi }); }, }), }); ``` Note how the `deps` section essentially assigns free-form names that you choose, to API refs. Here we for example map `configApiRef` to the name `configApi`, but that's just a convention. The framework will ensure that all of those deps get instantiated and passed into your `factory` function with the same set of names as your `deps`. At that point, `configApi` refers to an actual functioning instance of that API ref.
Project: KubeEdge (Provisioning / Automation & Configuration)
File: SECURITY.md

Join the [kubernetes-security-announce] group for security and vulnerability announcements. You can also subscribe to an RSS feed of the above using . Instructions for reporting a vulnerability can be found on the [Kubernetes Security and Disclosure Information] page. Information about supported Kubernetes versions can be found on the [Kubernetes version and version skew support policy] page on the Kubernetes website.