cwielenb/CNCF-Dataset huggingface dataset:
Project: KICS (Provisioning / Security & Compliance)
File: a31b7b82-d994-48c4-bd21-3bab6c31827a.md

title: Deployment Has No PodAntiAffinity hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a31b7b82-d994-48c4-bd21-3bab6c31827a Query name: Deployment Has No PodAntiAffinity Platform: Kubernetes Severity: <span style="color:#edd57e">Low</span> Category: Resource Management URL: Check if Deployment resources don't have a podAntiAffinity policy, which prevents multiple pods from being scheduled on the same node.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="19 39" apiVersion: apps/v1 kind: Deployment metadata: name: label-mismatch spec: selector: matchLabels: app: web-store replicas: 3 template: metadata: labels: app: web-shore spec: affinity: podAntiAffinity: requiredDuringSchedulingIgnoredDuringExecution: labelSelector: matchLabels: app: web-store topologyKey: "kubernetes.io/hostname" containers: name: web-app image: nginx:1.16-alpine apiVersion: apps/v1 kind: Deployment metadata: name: no-affinity spec: selector: matchLabels: app: web-store replicas: 3 template: metadata: labels: app: web-store spec: containers: name: web-app image: nginx:1.16-alpine ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: apps/v1 kind: Deployment metadata: name: web-server spec: selector: matchLabels: app: web-store replicas: 3 template: metadata: labels: app: web-store spec: affinity: podAntiAffinity: requiredDuringSchedulingIgnoredDuringExecution: labelSelector: matchExpressions: key: app operator: In values: web-store topologyKey: "kubernetes.io/hostname" containers: name: web-app image: nginx:1.16-alpine ```
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.0.14.3.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | NPE in JvmMetrics.doThreadUpdates | Blocker | metrics | Koji Noguchi | Nigel Daley | | | OutOfMemoryError : Java heap space errors in hadoop 0.14 | Blocker | . | Lohit Vijayarenu | Arun C Murthy | | | 0.14.2 release compiled with Java 1.6 instead of Java 1.5 | Blocker | build | Doug Cutting | Doug Cutting | | | RawLocalFileStatus is causing Path problems | Major | fs | Dennis Kubes | |
Project: Beam (App Definition and Development / Streaming & Messaging)
File: graalsystems.md

title: "GraalSystems" icon: /images/logos/powered-by/graalsystems.png hasNav: true cardDescription: "GraalSystems is a cloud native data platform providing support for Beam, Spark, Tensorflow, Samza and many other data processing solutions. At the heart of our architecture are a set of distributed processing and analytics modules using Beam to route over 2 billion events per day from our Apache Pulsar clusters. For our clients, we run also more than 2,000 Beam jobs per day at a very large scale in our production platform." <!-- 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. --> is a cloud native data platform providing support for Beam, Spark, Tensorflow, Samza and many other data processing solutions. At the heart of our architecture are a set of distributed processing and analytics modules using Beam to route over 2 billion events per day from our Apache Pulsar clusters. For our clients, we run also more than 2,000 Beam jobs per day at a very large scale in our production platform
Project: StarRocks (App Definition and Development / Database)
File: rand.md

displayed_sidebar: "English" Returns a random floating-point number between 0 (inclusive) and 1 (exclusive). ```Haskell RAND(x); ``` `x`: optional. The data type is BIGINT. If `x` is specified, this function returns a repeatable random number. If `x` is not specified, this function returns a completely random number. Returns a value of the DOUBLE type. ```Plain Text select rand(); +--+ | rand() | +--+ | 0.9393535880089522 | +--+ 1 row in set (0.01 sec) select rand(3); +--+ | rand(3) | +--+ | 0.6659865964511347 | +--+ 1 row in set (0.00 sec) ``` RAND, RANDOM
Project: ShardingSphere (App Definition and Development / Database)
File: show-unused-sharding-auditors.en.md

+++ title = "SHOW UNUSED SHARDING AUDITORS" weight = 8 +++ `SHOW SHARDING AUDITORS` syntax is used to query sharding auditors that are not used in specified database. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ShowUnusedShardingAuditors::= 'SHOW' 'UNUSED' 'SHARDING' 'AUDITOR' ('FROM' databaseName)? 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. | column | Description | |--|| | name | Sharding auditor name | | type | Sharding auditor algorithm type | | props | Sharding auditor algorithm properties | Query sharding auditors that are not used in the specified logical database ```sql SHOW UNUSED SHARDING AUDITORS FROM sharding_db; ``` ```sql mysql> SHOW UNUSED SHARDING AUDITORS FROM sharding_db; +-+-+-+ | name | type | props | +-+-+-+ | shardingkeyrequiredauditor | dmlsharding_conditions | | +-+-+-+ 1 row in set (0.01 sec) ``` Query sharding auditors are not used in the current logical database ```sql SHOW UNUSED SHARDING AUDITORS; ``` ```sql mysql> SHOW UNUSED SHARDING AUDITORS; +-+-+-+ | name | type | props | +-+-+-+ | shardingkeyrequiredauditor | dmlsharding_conditions | | +-+-+-+ 1 row in set (0.00 sec) ``` `SHOW`, `UNUSED`, `SHARDING`, `AUDITORS`, `FROM`
Project: Devfile (App Definition and Development / Application Definition & Image Build)
File: CONTRIBUTING.md

Welcome to Kubernetes. We are excited about the prospect of you joining our ! The Kubernetes community abides by the CNCF . Here is an excerpt: As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities. We have full documentation on how to get started contributing here: <! If your repo has certain guidelines for contribution, put them here ahead of the general k8s resources --> Kubernetes projects require that you sign a Contributor License Agreement (CLA) before we can accept your pull requests - Main contributor documentation, or you can just jump directly to the - Common resources for existing developers - We have a diverse set of mentorship programs available that are always looking for volunteers! <! Custom Information - if you're copying this template for the first time you can add custom content here, for example: - Replace `kubernetes-users` with your slack channel string, this will send users directly to your channel. --> ontributor-cheatsheet) - Common resources for existing developers You can reach the maintainers of this project via the . - We have a diverse set of mentorship programs available that are always looking for volunteers!
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: v1.5.0-next.3-changelog.md

bfc7c50a09: Display associated entity as a chip in `AdrSearchResultListItem` BREAKING: `AdrDocument` now includes a `entityRef` property, if you have a custom `AdrParser` you will have to supply this property in your returned documents Updated dependencies @backstage/plugin-adr-common@0.2.0-next.1 bfc7c50a09: Display associated entity as a chip in `AdrSearchResultListItem` BREAKING: `AdrDocument` now includes a `entityRef` property, if you have a custom `AdrParser` you will have to supply this property in your returned documents Updated dependencies @backstage/plugin-adr-common@0.2.0-next.1 @backstage/backend-common@0.15.0-next.2 bfc7c50a09: Display associated entity as a chip in `AdrSearchResultListItem` BREAKING: `AdrDocument` now includes a `entityRef` property, if you have a custom `AdrParser` you will have to supply this property in your returned documents 5e4dc173f7: Added a second validation to the `dir()` method of ZIP archive responses returned from `readTree()` that ensures that extracted files do not fall outside the target directory. Bumped create-app version.
Project: Pomerium (Provisioning / Key Management)
File: support.md

Unlike many projects on GitHub, Pomerium does not use its bug tracker for general discussion or asking questions. We only use our bug tracker for tracking bugs, feature requests, and proposals. We use Discuss at <https://discuss.pomerium.com/> to answer and archive support questions for users that may not be as comfortable with GitHub as developers. For asking questions, see: . Specifically, search the to see if your question has already been addressed. If not, open a new topic and follow the support template provided. .
Project: YDB (App Definition and Development / Database)
File: load-actors-pdisk-log.md

All VDisks hosted on a certain PDisk log data about their own performance to the common PDisk log. VDisks gradually delete their obsolete data at the beginning of the log to free up disk space. Sometimes, after one VDisk completes logging data and before another one starts logging it, a section with useless obsolete data may appear. In this case, such data is deleted automatically, and the PDiskLogLoad actor will perform a test to check whether such an operation is running correctly. <center> </center> {% note info %} This ad-hoc actor is used for testing specific functionality. This is not a load actor. It is designed to check whether something works properly. {% endnote %} {% include %} | Parameter | Description | | | `PDiskId` | ID of the Pdisk being loaded on the node. | | `PDiskGuid` | Globally unique ID of the PDisk being loaded. | | `VDiskId` | Parameters of the VDisk used to generate load.<ul><li>`GroupID`: Group ID.</li><li>`GroupGeneration`: Group generation.</li><li>`Ring`: Group ring ID.</li><li>`Domain`: Ring fail domain ID.</li><li>`VDisk`: Index of the VDisk in the fail domain.</li></ul> | | `MaxInFlight` | Number of simultaneously processed requests. | | `SizeIntervalMin` | Minimum size of log record in bytes. | | `SizeIntervalMax` | Maximum size of log record in bytes. | | `BurstInterval` | Interval between logging sessions in bytes. | | `BurstSize` | Total amount of data to log per session, in bytes. | | `StorageDuration` | Virtual time in bytes. Indicates how long the VDisk should store its data in the log. | | `IsWardenlessTest` | Set it to `False` in case the PDiskReadLoad actor is run on the cluster; otherwise, e.g. when it is run during unit tests, set it to `True`. | The following actor simulates the performance of two VDisks. The first VDisk logs a message of `65536` bytes every `65536` bytes and deletes data that exceeds `1048576` bytes. The second one writes `1024` bytes as messages of `128` bytes every `2147483647` bytes and deletes data that exceeds `2147483647` bytes. ```proto PDiskLogLoad: { Tag: 1 PDiskId: 1 PDiskGuid: 12345 DurationSeconds: 60 Workers: { VDiskId: {GroupID: 1 GroupGeneration: 5 Ring: 1 Domain: 1 VDisk: 1} MaxInFlight: 1 SizeIntervalMin: 65536 SizeIntervalMax: 65536 BurstInterval: 65536 BurstSize: 65536 StorageDuration: 1048576 } Workers: { VDiskId: {GroupID: 2 GroupGeneration: 5 Ring: 1 Domain: 1 VDisk: 1} MaxInFlight: 1 SizeIntervalMin: 128 SizeIntervalMax: 128 BurstInterval: 2147483647 BurstSize: 1024 StorageDuration: 2147483647 } IsWardenlessTest: false } ``` The test passes if none of the cluster nodes got overloaded and the status of the PDisk in question is `Normal`. You can check this using the cluster Embedded UI.
Project: ArangoDB (App Definition and Development / Database)
File: implicit_success_copy_constructor.md

+++ title = "`basicresult(const successtype<T> &)`" description = "Implicit value-from-success-type-sugar copy constructor. Available if `predicate::enablecompatibleconversion<T, void, void>` is true, or `T` is `void`. Constexpr, triviality and noexcept propagating." categories = ["constructors", "implicit-constructors", "tagged-constructors"] weight = 500 +++ Implicit value-from-success-type-sugar copy constructor used to disambiguate the construction of the value type. Note that if `T = void`, `valuetype` will be default constructed. Calls {{% api "void onresultcopyconstruction(T *, U &&) noexcept" %}} with `this` and `const success_type<T> &`. Requires: `predicate::enablecompatibleconversion<T, void, void>` is true, or `T` is `void`. Complexity: Same as for the `valuetype` constructor which accepts `T`, or the `valuetype` default constructor if `T` is `void`. Constexpr, triviality and noexcept of underlying operations is propagated.
Project: Quay (Provisioning / Container Registry)
File: TESTING.md

Basic unit tests for testing all the functionality of Quay: ```sh make unit-test ``` Quay has two sets of registry tests (current and legacy), which simulate Docker clients by executing REST operations against a spanwed Quay. ```sh make registry-test make registry-test-old ``` Ensures that custom TLS certificates are correctly loaded into the Quay container on startup. ```sh make certs-test ``` The full database tests runs the entire suite of Quay unit tests against a real running database instance. NOTE: The database must be running on the local machine before this test can be run. ```sh TESTDATABASEURI=database-connection-string make full-db-test ``` The clients test spawns CoreOS virtual machines via Vagrant and VirtualBox and runs real Docker/podman commands against a running Quay. NOTE: A Quay must be running on the local machine before this test can be run. ```sh make clients-test 10.0.2.2:5000 # IP+Port of the Quay on the host machine. ```
Project: Kapitan (Provisioning / Automation & Configuration)
File: kap_1_external_dependencies.md

This features allows kapitan to fetch files from online repositories/sources during compile and store in a particular target directory. Author: @yoshi-1224 Specify the files to be fetched as follows: ```yaml parameters: kapitan: dependencies: type: git | http[s] outputpath: <outputpath> source: <git/http[s]_url> ``` The output path is the path to save the dependency into. For example, it could be `/components/external/manifest.jsonnet`. Then, the user can specify the fetched file as a `kapitan.compile` item along with the locally-created files. Git type may also include `ref` and `subdir` parameters as illustrated below: ```yaml type: git outputpath: <outputpath> source: <git_url> subdir: relative/path/in/repository ref: <commit_hash/branch/tag> force_fetch: <bool> ``` If the file already exists at `output_path`, the fetch will be skipped. For fresh fetch of the dependencies, users may add `--fetch` option as follows: ```bash kapitan compile --fetch ``` Users can also add the `force_fetch: true` option to the `kapitan.dependencies` in the inventory in order to force fetch of the dependencies of the target every time. module (and git executable) for git type requests module for http[s] (optional) for reporting download progress
Project: ClickHouse (App Definition and Development / Database)
File: client-libraries.md

slug: /en/interfaces/third-party/client-libraries sidebar_position: 26 sidebar_label: Client Libraries description: Third-party client libraries :::note ClickHouse Inc does not maintain the libraries listed below and hasnt done any extensive testing to ensure their quality. ::: - - - - - - - - - - - - - - - - - - - - - - - - - -
Project: Chef Habitat (App Definition and Development / Application Definition & Image Build)
File: sup_config.md

+++ title = "Supervisor Configuration File" description = "Service Change Rollback" date = 2020-10-26T17:32:36-07:00 draft = false gh_repo = "habitat" [menu] [menu.habitat] title = "Supervisor Configuration File" identifier = "habitat/supervisors/sup_config How to Rollback" parent = "habitat/supervisors" weight = 85 +++ Generate a Supervisor configuration file and use it to set any of the 40+ Supervisor configuration settings instead of configuring them on the command line. <div style="justify-content: center; display: flex; padding-top:2rem; padding-bottom:2rem"> <iframe width="560" height="315" src="https://www.youtube.com/embed/B_ppJ1xaC5o" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen ></iframe> </div> Chef Habitat looks for Supervisor configuration settings in four locations and applies them in order, which means that settings defined in later locations overwrite earlier ones. ```bash hab sup run --generate-config ``` ```bash hab sup run --generate-config > config.toml ``` The Supervisor settings look-up order: The fixed config file location `/hab/sup/default/config/sup.toml` on the Supervisor Files passed with the command, `hab sup run --config-files /config/file1.toml /config/file2.toml`, where You can pass more than one file command The settings in the later files overwrite those from the earlier, which means that for the same settings specified in both files in the command `hab sup run --config-files /config/file1.toml /config/file2.toml`, you will end up with the settings from `file2.toml` applied to the Supervisor From , if they exist From settings passed from the ```toml config.toml listen_gossip = "0.0.0.0:9638" localgossipmode = false listen_http = "0.0.0.0:9631" http_disable = false listen_ctl = "127.0.0.1:9632" organization = "my-org" peer = ["1.1.1.1:9632", "2.2.2.2:9632", "3.3.3.3:9632"] permanent_peer = false peerwatchfile = "/path/to/file" cachekeypath = "/path/to/file" ring = "my-ring" config_from = "/path/to/file" auto_update = false key_file = "/path/to/file" cert_file = "/path/to/file" cacertfile = "/path/to/file" pkgidentor_artifact = "core/redis" verbose = false no_color = false json_logging = false sysipaddress = "1.2.3.4" eventstreamapplication = "my-app" eventstreamenvironment = "my-env" eventstreamconnect_timeout = 60 eventstreamurl = "nats://127.0.0.1:4222" eventstreamsite = "my-site" eventstreamtoken = "my-token" event_meta = ["my-key1=my-val1", "my-key2=my-val2", "abc=123"] eventstreamserver_certificate = "/path/to/file" keeplatestpackages = 1 channel = "my-channel" bldr_url = "https://my-bldr.url" group = "my-group" topology = "leader" strategy = "at-once" update_condition = "track-channel" serviceminbackoff_period = 10 servicemaxbackoff_period = 180 servicerestartcooldown_period = 300 bind = ["port:redis.default"] binding_mode = "strict" healthcheckinterval = 60 shutdown_timeout = 10 ```
Project: Meshery (Provisioning / Automation & Configuration)
File: porter.md

layout: integration title: Porter subtitle: Collaborative and visual infrastructure as code for Porter image: /assets/img/integrations/porter/icons/color/porter-color.svg permalink: extensibility/integrations/porter docURL: https://docs.meshery.io/extensibility/integrations/porter description: integrations-category: App Definition and Development integrations-subcategory: Application Definition & Image Build registrant: Artifact Hub components: name: bgp-conf colorIcon: assets/img/integrations/porter/components/bgp-conf/icons/color/bgp-conf-color.svg whiteIcon: assets/img/integrations/porter/components/bgp-conf/icons/white/bgp-conf-white.svg description: name: bgp-peer colorIcon: assets/img/integrations/porter/components/bgp-peer/icons/color/bgp-peer-color.svg whiteIcon: assets/img/integrations/porter/components/bgp-peer/icons/white/bgp-peer-white.svg description: name: eip colorIcon: assets/img/integrations/porter/components/eip/icons/color/eip-color.svg whiteIcon: assets/img/integrations/porter/components/eip/icons/white/eip-white.svg description: 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: Trivy (Provisioning / Security & Compliance)
File: alma.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`. AlmaLinux offers its own security advisories, and these are utilized when scanning AlmaLinux for vulnerabilities. See . When looking at fixed versions, it's crucial to consider the patches supplied by AlmaLinux. For example, for CVE-2023-0464, the fixed version for AlmaLinux 9 is listed as `3.0.7-16.el9_2` in . Note that this is different from the upstream fixed version, which is `3.0.9`, `3.1.1`, and son on. Typically, only the upstream information gets listed on [NVD], so it's important not to get confused. Trivy calculates the severity of an issue based on the severity provided by AlmaLinux. If the severity is not provided or defined yet by AlmaLinux, the severity from the NVD is taken into account. Using CVE-2023-0464 as an example, while it is rated as "High" in NVD, AlmaLinux has marked as . As a result, Trivy will display it as "Medium". The table below is the mapping of AlmaLinux's severity to Trivy's severity levels. | AlmaLinux | Trivy | | :-: | :: | | Low | Low | | Moderate | Medium | | Important | High | | Critical | Critical | Trivy supports the following [vulnerability statuses] for AlmaLinux. | 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: YugabyteDB (App Definition and Development / Database)
File: ddl_create_server.md

title: CREATE SERVER statement [YSQL] headerTitle: CREATE SERVER linkTitle: CREATE SERVER description: Use the CREATE SERVER statement to create a foreign server. menu: v2.18: identifier: ddlcreateserver parent: statements type: docs Use the `CREATE SERVER` command to create a foreign table. {{%ebnf%}} create_server {{%/ebnf%}} Create a foreign server named server_name. If server_name already exists in the specified database, an error will be raised unless the `IF NOT EXISTS` clause is used. The `TYPE` clause can be optionally used to specify the server type. The `VERSION` clause can be optionally used to specify the server version. The `FOREIGN DATA WRAPPER` clause can be used to specify the name of the foreign-data wrapper. The `OPTIONS` clause specifies options for the foreign server. They typically define the connection details of the server, but the actual permitted option names and values are specific to the servers foreign data wrapper. Basic example. ```plpgsql yugabyte=# CREATE SERVER myserver FOREIGN DATA WRAPPER mywrapper OPTIONS (host '187.51.62.1'); ```