cwielenb/CNCF-Dataset huggingface dataset:
Project: Beam (App Definition and Development / Streaming & Messaging)
File: mascot.md

title: "Beam Mascot" <!-- 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. --> This page contains Apache Beam's mascot designs. Beam Firefly is cute, friendly, agile, easy to use, and its main objective is to fetch streams and batches of data and process it. The mascots model sheet is useful to understand its features, capabilities, as well as its morphology. The original design of the mascot was created by and was donated to the Apache Beam community under the . You can browse the original mascot and its adaptations in different sizes and image formats in . ](/images/mascot/model_sheet.png) The original Beam mascot - simple and eye-catching, was developed with its body shaped like a B from Beams logo. The ideal choice for printing in any size or using for swags. The lit-up tail is another element to play with if you want to animate the firefly. <img src="/images/mascot/beammascot500x500.png" width="200"/> The adaptation below represents independent learning. The bubble can be replaced by any other description. An ideal choice for promoting Beam talks, workshops, and webinars where the Beam community learns new things. <img src="/images/mascot/learningindependently500x500.png" width="280"/> The second adaptation below represents data processing. The data goes through the fireflys tail, filling the entire body with streams of information (for example, codes) and when it is done processing the mascots entire body outline lits up in yellow color to tell that it is loaded with data and is ready to process it, while it becomes stronger and faster. Mascot returns to its original status after finishing this process. <img src="/images/mascot/bigdata500x500.png" width="300"/> <!-- --> For the Beam mascot, we used Apache Beam projects predefined colors and fonts. has more information. Color Palette (RGB), Orange : #FF570B, Yellow : #FFF200, White: #FFFFFF, Black: #1D1D1B
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.64.md

layout: release date: 2021-10-06 tag: v0.5.64 Migrate from plain manifests to helm charts in mesheryctl @panyuenlau (#4318) [Extension] add remote components for changes @bariqhibat (#4317) index in spanish page had some words still in englosh @alonsolopezr (#4329) [Testing] Integration Test fail resolved @piyushsingariya (#4335) Fix mesheryctl static analysis bugs @navendu-pottekkat (#4330) Bump relay-runtime from 11.0.2 to 12.0.0 in /ui @dependabot (#4298) Fix mesheryctl static analysis bugs @navendu-pottekkat (#4330) Bump relay-runtime from 11.0.2 to 12.0.0 in /ui @dependabot (#4298) Update README.md @helloausrine (#4321) [Tests] Integration Test fix @piyushsingariya (#4336) [Testing] Integration Test fail resolved @piyushsingariya (#4335) Bump google.golang.org/grpc from 1.40.0 to 1.41.0 @dependabot (#4306) use alpine compatible version of jsonschema util @DelusionalOptimist (#4323) Bump billboard.js from 3.1.2 to 3.1.5 in /ui @dependabot (#4295) [error-codes.md] Add anchors for error codes in documentation @awardnasc (#4331) Thank you to our contributors for making this release possible: @DelusionalOptimist, @alonsolopezr, @awardnasc, @bariqhibat, @dependabot, @dependabot[bot], @helloausrine, @leecalcote, @navendu-pottekkat, @panyuenlau, @piyushsingariya, @ramrodo and @utkarsh-pro
Project: KubeVirt (App Definition and Development / Application Definition & Image Build)
File: conformance.md

KubeVirt releases a `kubevirt/conformance:<release>` image and `conformance.yaml` manifest starting from `v0.33.0`. It can be executed as a plugin to verify if the underlying cluster meets the basic needs to run KubeVirt. By default tests with a `[Conformance]` tag will be executed and tests with a `[Disruptive]` tag will be skipped. These tests will not destroy or modify anything outside of the explicitly created test namespaces by the binary. To execute the conformance tests for a released conformance test suite, run: ```bash KUBEVIRT_VERSION=v0.41.0 sonobuoy run --plugin https://github.com/kubevirt/kubevirt/releases/download/${KUBEVIRT_VERSION}/conformance.yaml ``` The execution can be monitored using the `status` command: ```bash sonobuoy status ``` ``` PLUGIN STATUS RESULT COUNT kubevirt-conformance complete passed 1 Sonobuoy has completed. Use `sonobuoy retrieve` to get results. ``` Once the test run finishes, the result can be fetched: ```bash sonobuoy retrieve ``` ``` 202008201609sonobuoy8f8d0b0e-1d37-485a-b61d-bf7185198fbf.tar.gz ``` And interpreted: ```bash sonobuoy results 202008201609sonobuoy8f8d0b0e-1d37-485a-b61d-bf7185198fbf.tar.gz ``` ``` Plugin: kubevirt-conformance Status: passed Total: 580 Passed: 1 Failed: 0 Skipped: 579 ``` In case of a failure the artifacts will be collected as well. Find them at `plugins/kubevirt-conformance/results/global/k8s-reporter` of the tar file. ```bash make conformance ``` To run without outside connectivity tests add the argument: ```bash SKIPOUTSIDECONN_TESTS=true make conformance ``` The following argument is only used for running the conformance tests on the Arm64 test infrastructure in KubeVirtCI. This is necessary because some specific setups, such as IPv6, are not enabled on the Arm64 test infrastructure. By adding the argument, we can skip the unsupported tests. ```bash RUNONARM64_INFRA=true make conformance ``` To focus on specific tests pass KUBEVIRTE2EFOCUS argument: ```bash KUBEVIRTE2EFOCUS=sig-network make conformance ``` To use on specific images tag on test suite override DOCKER_TAG argument: ```bash DOCKER_TAG=mybuild make conformance ``` Conformance tests plugin manifest template under `manifests/release/conformance.yaml` was generated with following commands: ```bash sonobuoy gen plugin --name kubevirt-conformance --cmd /usr/bin/conformance --image IMAGE -f junit > manifests/release/conformance.yaml.in sed -i 's#IMAGE#{{.DockerPrefix}}/conformance:{{.DockerTag}}#' manifests/release/conformance.yaml.in ```
Project: KubeBlocks by ApeCloud (App Definition and Development / Database)
File: kbcli_class_template.md

title: kbcli class template Generate class definition template ``` kbcli class template [flags] ``` ``` -h, --help help for template -o, --output string Output class definition template to a file ``` ``` --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 ``` - Manage classes
Project: Apache Storm (App Definition and Development / Streaming & Messaging)
File: Storm-Scheduler.md

title: Scheduler layout: documentation documentation: true Storm now has 4 kinds of built-in schedulers: , , , . You can implement your own scheduler to replace the default scheduler to assign executors to workers. You configure the class to use the "storm.scheduler" config in your storm.yaml, and your scheduler must implement the interface. The isolation scheduler makes it easy and safe to share a cluster among many topologies. The isolation scheduler lets you specify which topologies should be "isolated", meaning that they run on a dedicated set of machines within the cluster where no other topologies will be running. These isolated topologies are given priority on the cluster, so resources will be allocated to isolated topologies if there's competition with non-isolated topologies, and resources will be taken away from non-isolated topologies if necessary to get resources for an isolated topology. Once all isolated topologies are allocated, the remaining machines on the cluster are shared among all non-isolated topologies. You can configure the isolation scheduler in the Nimbus configuration by setting "storm.scheduler" to "org.apache.storm.scheduler.IsolationScheduler". Then, use the "isolation.scheduler.machines" config to specify how many machines each topology should get. This configuration is a map from topology name to the number of isolated machines allocated to this topology. For example: ``` isolation.scheduler.machines: "my-topology": 8 "tiny-topology": 1 "some-other-topology": 3 ``` Any topologies submitted to the cluster not listed there will not be isolated. Note that there is no way for a user of Storm to affect their isolation settings this is only allowed by the administrator of the cluster (this is very much intentional). The isolation scheduler solves the multi-tenancy problem avoiding resource contention between topologies by providing full isolation between topologies. The intention is that "productionized" topologies should be listed in the isolation config, and test or in-development topologies should not. The remaining machines on the cluster serve the dual role of failover for isolated topologies and for running the non-isolated topologies.
Project: Trivy (Provisioning / Security & Compliance)
File: oracle.md

Trivy supports the following scanners for OS packages. | Scanner | Supported | | :--: | :-: | | SBOM | | | Vulnerability | | | License | | Please see for supported versions. The table below outlines the features offered by Trivy. | Feature | Supported | | :--: | :-: | | Unfixed vulnerabilities | - | | | | Trivy detects packages that have been installed through package managers such as `dnf` and `yum`. Oracle Linux offers its own security advisories, and these are utilized when scanning Oracle Linux for vulnerabilities. See . Trivy takes fixed versions from . Trivy determines vulnerability severity based on the severity metric provided in . For example, the security patch for is provided as . Its severity is rated as "MODERATE". Thus, even though it's evaluated as "HIGH" in the NVD, Trivy displays it with a severity of "MEDIUM". The table below is the mapping of Oracle's threat to Trivy's severity levels. | Oracle | Trivy | | :-: | :: | | Low | Low | | Moderate | Medium | | Important | High | | Critical | Critical | Trivy supports the following [vulnerability statuses] for Oracle Linux. | Status | Supported | | :--: | :-: | | Fixed | | | Affected | | | Under Investigation | | | Will Not Fix | | | Fix Deferred | | | End of Life | | Trivy identifies licenses by examining the metadata of RPM packages.
Project: Grafeas (Provisioning / Security & Compliance)
File: versioning.md

Grafeas project uses a mix of and . This document clarifies the rationale behind this mix in versioning approaches. Grafeas API follows Google Cloud versioning scheme: v1alpha1, v1beta1, v1, etc. This allows us to keep it in sync with GCP implementation, [Container Analysis](https://cloud.google.com/container-registry/docs/get-image-vulnerabilities). Grafeas server uses semantic versioning. The current `0.1.0` release supports `v1beta1` of the API, with the plan of stable versions supporting stable API versions. This allows to communicate to the open source community the production readiness aspect of the Grafeas server, as well as differentiate between bug fixes, minor and major feature releases. Grafeas client libraries are currently maintained by the Grafeas team from the code generated by Swagger. This may change in the future, as the community contributions increase. Client libraries will use semantic versioning, to make it easier for the community to follow and contribute. The plan is to let the community to take over maintenance of these libraries in long-term. Google also produces a set of Grafeas client libraries that are supported by an internal team.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.155.md

layout: release date: 2023-10-09 tag: v0.6.155 tests for mesheryctl system package @Philip-21 (#8585) [FIXED] mesheryctl error code conflicts solved @zakisk (#9014) fix lint error issue @sudhanshutech (#9056) fixed the filter-dropdown component @captain-Akshay (#9021) [UI] rename MeshModel Summary to Registry in Settings @Adaminite (#9046) [UI] Add Menu colors to theme @aabidsofi19 (#9041) Fix Hover @ptdatta (#8989) Bump zod and next in /provider-ui @dependabot (#9037) Bump postcss and next in /provider-ui @dependabot (#9038) Fix ui issues @sudhanshutech (#9024) Bump postcss from 8.4.21 to 8.4.31 in /ui @dependabot (#9035) [UI] Fix darkmode issue in extentions @aabidsofi19 (#9025) fix: Swap Table and Grid icons on Activity Toolbar @akhilender-bongirwar (#9028) tests for mesheryctl system package @Philip-21 (#8585) Bump zod and next in /provider-ui @dependabot (#9037) Bump postcss and next in /provider-ui @dependabot (#9038) Bump postcss from 8.4.21 to 8.4.31 in /ui @dependabot (#9035) Update Artifacts sub-section in documentation @ValGrace (#8997) Deleted Duplicate line in Docs #9017 @aadityadike (#9047) Thank you to our contributors for making this release possible: @Adaminite, @Aisuko, @MUzairS15, @Philip-21, @ValGrace, @aabidsofi19, @aadityadike, @akhilender-bongirwar, @captain-Akshay, @dependabot, @dependabot[bot], @l5io, @leecalcote, @ptdatta, @sudhanshutech, @theBeginner86, @zakisk and l5io
Project: Meshery (Provisioning / Automation & Configuration)
File: k8gb.md

layout: integration title: K8GB subtitle: Collaborative and visual infrastructure as code for K8GB image: /assets/img/integrations/k8gb/icons/color/k8gb-color.svg permalink: extensibility/integrations/k8gb docURL: https://docs.meshery.io/extensibility/integrations/k8gb description: integrations-category: Orchestration & Management integrations-subcategory: Coordination & Service Discovery registrant: Artifact Hub components: featureList: [ "Drag-n-drop cloud native infrastructure designer to configure, model, and deploy your workloads.", "Invite anyone to review and make changes to your private designs.", "Ongoing synchronization of Kubernetes configuration and changes across any number of clusters." ] howItWorks: "Collaborative Infrastructure as Code" howItWorksDetails: "Collaboratively manage infrastructure with your coworkers synchronously sharing the same designs." language: en list: include type: extensibility category: integrations
Project: ShardingSphere (App Definition and Development / Database)
File: drop-sharding-key-generator.en.md

+++ title = "DROP SHARDING KEY GENERATOR" weight = 10 +++ The `DROP SHARDING KEY GENERATOR` syntax is used to drop sharding key generator for specified database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql DropShardingKeyGenerator ::= 'DROP' 'SHARDING' 'KEY' 'GENERATOR' ifExists? keyGeneratorName (keyGeneratorName)* ('FROM' databaseName)? ifExists ::= 'IF' 'EXISTS' keyGeneratorName ::= identifier databaseName ::= 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; `ifExists` clause is used for avoid `Sharding key generator not exists` error. Drop sharding key generator for specified database ```sql DROP SHARDING KEY GENERATOR tordersnowflake FROM sharding_db; ``` Drop sharding key generator for current database ```sql DROP SHARDING KEY GENERATOR tordersnowflake; ``` Drop sharding key generator with `ifExists` clause ```sql DROP SHARDING KEY GENERATOR IF EXISTS tordersnowflake; ``` `DROP`, `SHARDING`, `KEY`, `GENERATOR`, `FROM`
Project: external-secrets (Provisioning / Security & Compliance)
File: clustersecretstore.md

The `ClusterSecretStore` is a cluster scoped SecretStore that can be referenced by all `ExternalSecrets` from all namespaces. Use it to offer a central gateway to your secret backend. For a full list of supported fields see or dig into our . ``` yaml {% include 'full-cluster-secret-store.yaml' %} ```
Project: Stolon (App Definition and Development / Database)
File: upgrade.md

These stolon commands options were removed. You should update your scripts invoking the stolon components removing them. `--listen-address` `--port` `--pg-conf-dir` `--id` has been deprecated (but yet available). `--uid` should be used instead. `--listen-address` `--port` `--discovery-type` `--initial-cluster-config` (the equivalent for the new cluster spec format is `--initial-cluster-spec`) `--keeper-kube-label-selector` `--keeper-port` `--kubernetes-namespace` Stolon v0.5.0 received a big rework to improve its internal data model and implement new features. To upgrade an existing cluster from v0.4.0 to v0.5.0 you can follow the steps below (we suggest to try them in a test environment). Annotate the master keeperUID (previously called keeper id). You can retrieve this using `stolonctl status`. Stop all the cluster processes (keepers, sentinels and proxies) Upgrade the binaries to stolon v0.5.0 Relaunch all the cluster processes. They will loop reporting `unsupported clusterdata format version 0`. Initialize a new cluster data using the master keeperUID: ``` stolonctl init '{ "initMode": "existing", "existingConfig": { "keeperUID": "keeper01" } }' ``` The leader sentinel will choose the other keepers as standbys and they'll resync with the current master (they will do this also if before the upgrade they were already standbys since this is needed to adapt to the new cluster data format).
Project: YugabyteDB (App Definition and Development / Database)
File: cr-do-percent-rank.md

title: crdopercent_rank.sql linkTitle: crdopercent_rank.sql headerTitle: crdopercent_rank.sql description: crdopercent_rank.sql - Part of the code kit for the "Analyzing a normal distribution" section within the YSQL window functions documentation. menu: v2.18: identifier: cr-do-percent-rank parent: analyzing-a-normal-distribution weight: 120 type: docs Save this script as `crdopercent_rank.sql`. ```plpgsql create or replace procedure dopercentrank(noofbuckets in int) language sql as $body$ insert into results(method, bucket, n, mins, maxs) with measures as ( select score, (percent_rank() over w) as measure from t4_view window w as (order by score)) , bucket as ( select bucket(measure::numeric, 0::numeric, 1::numeric, $1) as bucket, score from measures) select 'percent_rank', bucket, count(*), min(score), max(score) from bucket group by bucket; $body$; ```
Project: Harbor (Provisioning / Container Registry)
File: 2-04-DB-user-view-projects.md

Test 2-04 - User View Projects (DB Mode) ======= To verify that a non-admin user can view projects 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. There is at least a non-admin user. The user has at least 3 private projects. The registry has at least 3 public repositories. NOTE: In below test, user A is non-admin user. User A should be replaced by a longer and meaningful name. Log in to UI as user A (non-admin). Create at least 3 projects if he/she has less than 3 projects. Switch a few times between "My Projects" and "Public projects" tab, view listed projects and click to check details of images. Check logs of projects in "My Projects". Step 3, verify the information listed of projects are correctly displayed, such as creation time and role. Step 4, should see logs of the project. None
Project: ClickHouse (App Definition and Development / Database)
File: v21.11.4.14-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix SHOW GRANTS when partial revokes are used. This PR fixes . (). Backported in : Fix some corner cases with intersect/except. Closes . (). Backported in : Fix bug which broke select queries if they happened after dropping materialized view. Found in . (). Backported in : Fix StorageMerge with aliases and where (it did not work before at all). Closes . (). Backported in : Fix bug in Keeper which can lead to inability to start when some coordination logs was lost and we have more fresh snapshot than our latest log. (). Backported in : Fix bug with group by and positional arguments. Closes #issuecomment-968696186. (). Backported in : Rename setting value `readthreadpool` to `threadpool` for setting `remotefilesystemreadmethod`. (). Fix threadpool read for remote disks (). Fix check in async buffer (). BloomFilter index check fix ().
Project: Beam (App Definition and Development / Streaming & Messaging)
File: contact-us.md

title: "Contact Us" aliases: /community/ /use/issue-tracking/ /use/mailing-lists/ /get-started/support/ <!-- 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. --> The Apache Beam community is friendly and welcoming. We are glad to help with any questions, suggestions, or ideas you have. Contact us in the following channels: {{< community/tablewithicons contact_us >}} The official communication channels for Apache projects are their , and Apache Beam has two main lists: and . The topics for each of them can be seen in the section above. Prior to sending emails to these lists, you need to subscribe. To subscribe, send a blank email to or depending on the list you want to write to. After you subscribe, youll receive all emails going to this mailing list. If you no longer wish to receive emails from these lists, you need to send another blank email to either or . Tip 1: Use tags in your subject line. A tag is a word within a pair of brackets [] that indicate the type of message youre sending. For example: [Bug] or [Proposal] or [Question] or [Idea]. Tags help folks navigate emails easier. Tip 2: If youre asking a troubleshooting question, provide as much information as possible to help others replicate your issue or find possible solutions.