cwielenb/CNCF-Dataset huggingface dataset:
Project: CockroachDB (App Definition and Development / Database)
File: 20150729_bounds_generation.md

Feature Name: bounds_generation Status: rejected Start Date: 2015-07-29 RFC PR: Cockroach Issue: This RFC supplements #1866, which was rejected. Add a bounds generation number to all range descriptors, and use it to maintain consistency of the store's `replicasByKey` map. One of the issues in is that a replica may be created in response to a raft message before the split that created the range has been processed, leading to conflicts in the `Store.replicasByKey` map. Add a field `bounds_generation` to `RangeDescriptor`. This value is incremented whenever the bounds of the range change. On a split, the `bounds_generation` of each post-split range is one plus the pre-split `boundsgeneration`. On a merge, the `boundsgeneration` of the post-merge range is one plus the maximum of the two pre-merge ranges' values. In `Store.addRangeInternal`, when we add the range to `replicasByKey`, we first test for an overlapping range. If we find one, we compare bounds generations: the range with the lower bounds generation has its effective bounds reduced to eliminate the conflict. When this happens, the range whose bounds have been reduced will stop receiving KV requests for the affected portion of the keyspace. It will, however, continue to receive raft messages, which are routed by ID instead of by key. This will allow the replica to catch up and process the split transaction that allowed the new range with a higher bounds generation to come into existence (or the replica has been removed and will eventually be garbage-collected).
Project: Open Policy Agent (OPA) (Provisioning / Security & Compliance)
File: strimzi.md

title: Strimzi (Apache Kafka on Kubernetes) software: kafka strimzi labels: category: streaming layer: data blogs: https://strimzi.io/blog/2020/08/05/using-open-policy-agent-with-strimzi-and-apache-kafka/ https://strimzi.io/blog/2020/09/01/enforce-custom-resource-policies-with-opa-gatekeeper/ code: https://github.com/strimzi/strimzi-kafka-operator https://github.com/scholzj/demo-opa-kafka-authorization https://github.com/StyraInc/opa-kafka-plugin inventors: redhat docs_features: rest-api-integration: note: | Strimzi can be configured to use OPA via the REST API as the Kafka authorizer using . Strimzi provides a way to run an Apache Kafka cluster on Kubernetes in various deployment configurations. Strimzi ships with the OPA authorizer plugin right out of the box, and supports OPA as an option for Kafka authorization.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.4.14.md

layout: release date: 2020-10-20 tag: v0.4.14 General Translate contribute guide to docs to spanish @jesuslerma (#1696) security: update ui deps to avoid DOS @kushthedude (#1689) fix(UI): table filters not rendering due to custom header @dhruv0000 (#1694) Updating Istio Documentation, @Maxgit3 (#1683) Fetch Grafana Boards after config. @dhruv0000 (#1688) [Docs] Installation Guides @chandrashritii (#1673) [ImgBot] Optimize images @IMGBOT (#1687) [Docs] Update Meshery architecture page @chandrashritii (#1675) UI: Remove smi conformance results chip @daksh-sagar (#1686) [Docs] Update windows installation guide for Meshery @chandrashritii (#1657) Updated 'Kong' -> 'Kuma' @Neilblaze (#1681) Documentation [mesheryctl] Generate cluster access for Minikube clusters @leecalcote (#1672)
Project: Harbor (Provisioning / Container Registry)
File: 10-01-Cliar-can-not-scan-some-images.md

Test 10-01 Trivy can not scan some images ======= To verify that trivy can not scan some image. User guide This test requires that a Harbor instance is running and available. A linux host with Docker CLI installed. Trivy has been updated to the latest. Login Harbor as admin. Create a project and push an image trivy does not recognize(for example: photon). Scan the pushed image. View the scan result. Rescan it. Step3 should show view log link. Step4 the scan log should be can not scan. Step5 should be the same as step3. None
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 14_advanced_pipeline_patterns.md

Prompt: What pipeline patterns exist in Apache Beam? Response: Beam pipeline patterns are a set of best practices for building Apache Beam pipelines. They are based on real-world Beam deployments and are designed to help you build resilient, flexible, and portable pipelines. The following list includes some of the most common pipeline patterns: For more information, see the section of the Beam Programming Guide.
Project: ko (App Definition and Development / Application Definition & Image Build)
File: migrating-from-dockerfile.md

If your `Dockerfile` looks like either of the examples in the , you can easily migrate to use `ko` instead. Let's review the best practice multi-stage Dockerfile in that tutorial first: ```plaintext FROM golang:1.16-buster AS build WORKDIR /app COPY go.mod ./ COPY go.sum ./ RUN go mod download COPY *.go ./ RUN go build -o /docker-gs-ping FROM gcr.io/distroless/base-debian10 WORKDIR / COPY --from=build /docker-gs-ping /docker-gs-ping EXPOSE 8080 USER nonroot:nonroot ENTRYPOINT ["/docker-gs-ping"] ``` This `Dockerfile`: pulls the `golang:1.16` image `COPY`s your local source into the container environment (`COPY`ing `go.mod` and `go.sum` first and running `go mod download`, to cache dependencies in the container environment) `RUN`s `go build` on your source, inside the container, to produce an executable `COPY`s the executable built in the previous step into a new image, on top of a minimal base image. The result is a Go application built on a minimal base image, with an optimally cached build sequence. After running `docker build` on this `Dockerfile`, don't forget to push that image to the registry so you can deploy it. If yourGo source is laid out as described in the tutorial, and you've and , you can simply run `ko build ./` to build and push the container image to your registry. You're done. You can delete your `Dockerfile` and uninstall `docker`. `ko` takes advantage of your local without needing to be told to, and it sets the `ENTRYPOINT` and uses a nonroot distroless base image by default. To build a multi-arch image, simply add `--platform=all`. Compare this to the .
Project: KICS (Provisioning / Security & Compliance)
File: 5864fb39-d719-4182-80e2-89dbe627be63.md

title: Amazon DMS Replication Instance Is Publicly Accessible hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 5864fb39-d719-4182-80e2-89dbe627be63 Query name: Amazon DMS Replication Instance Is Publicly Accessible Platform: CloudFormation Severity: <span style="color:#ff0000">Critical</span> Category: Access Control URL: Amazon DMS is publicly accessible, therefore exposing possible sensitive information. To prevent such a scenario, update the attribute 'PubliclyAccessible' to false.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="9" Resources: ReplicationInstance: Type: "AWS::DMS::ReplicationInstance" Properties: ReplicationInstanceIdentifier: my-replication-instance ReplicationInstanceClass: dms.r5.large AllocatedStorage: 100 EngineVersion: "3.4.3" PubliclyAccessible: true ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="4" Resources: ReplicationInstance: Type: "AWS::DMS::ReplicationInstance" Properties: ReplicationInstanceIdentifier: my-replication-instance ReplicationInstanceClass: dms.r5.large AllocatedStorage: 100 EngineVersion: "3.4.3" ``` ```yaml title="Negative test num. 1 - yaml file" Resources: ReplicationInstance: Type: "AWS::DMS::ReplicationInstance" Properties: ReplicationInstanceIdentifier: my-replication-instance ReplicationInstanceClass: dms.r5.large AllocatedStorage: 100 EngineVersion: "3.4.3" PubliclyAccessible: false ```
Project: KubeArmor (Provisioning / Security & Compliance)
File: CONTRIBUTING.md

Pick an to work on. For first-time contributors, the best would be to pick an issue . If you feel adventurous and would like to take a challenging issue, we would love to have you contribute on issues . There is a that explains how to create a fork and raise PR on GitHub. If the issue involves code changes you need to install development env using this . Contributions are not necessarily in the form of code changes. KubeArmor community can benefit from contributions such as: Users are welcome to contribute policy-templates for their workloads. The workloads have to be generic enough such that it benefits the wider community. E.g., if someone brings up a system policy restricting access to nginx process that would be useful in multiple scenarios and for the wider community then come up with a policy-template that is specific to your proprietary application. Blogs a. Explain The use of KubeArmor's features (KVMService, Event Auditor, Visibility, etc) b. Describe How to use KubeArmor to protect your workload with specific use-cases you may have. Please do not shy away from getting as technical as you can. c. Put your topic of interest Feedback to the community Just helping advance any discussion on KubeArmor Slack, Community meetings, office hours will make a big difference. Talking about KubeArmor in meetups We would certainly encourage users or devs of KubeArmor to talk about it in open/closed forums. The community can help with logistics such as compiling/feedback on slide-decks, technical diagrams, etc.
Project: YDB (App Definition and Development / Database)
File: docker-connect.md

Currently, the PostgreSQL compatibility feature is available for testing in the Docker image: `ghcr.io/ydb-platform/local-ydb:nightly`. Commands for starting a local Docker container with YDB and open ports for PostgreSQL and Web-UI: {% note tip %} In this example, the containers are intentionally created in a way that their state is deleted after they stop. This simplifies the instructions and allows you to repeatedly run tests in a known environment without worrying about past test failures. To preserve the container's state, you need to remove the environment variable `YDBUSEINMEMORYPDISKS`. {% endnote %} {% list tabs %} Docker-compose To launch using a Docker Compose configuration file, it must already be . docker-compose.yaml: ``` services: ydb: image: ghcr.io/ydb-platform/local-ydb:nightly ports: "5432:5432" "8765:8765" environment: "YDBUSEINMEMORYPDISKS=true" "POSTGRESUSER=${YDBPG_USER:-root}" "POSTGRESPASSWORD=${YDBPG_PASSWORD:-1234}" "YDBEXPERIMENTALPG=1" ``` Run: ```bash docker-compose up -d --pull=always ``` Docker command: ```bash docker run --name ydb-postgres -d --pull always -p 5432:5432 -p 8765:8765 -e POSTGRESUSER=root -e POSTGRESPASSWORD=1234 -e YDBEXPERIMENTALPG=1 -e YDBUSEINMEMORYPDISKS=true ghcr.io/ydb-platform/local-ydb:nightly ``` {% endlist %} After launching the container, you can connect to it via PostgreSQL clients on port 5432, the database `local`, or open the on port 8765. Upon executing this command, the interactive command-line interface of `psql`, the PostgreSQL client, will be launched. All subsequent queries should be entered within this client interface. ```bash docker run --rm -it --network=host postgres:14 psql postgresql://root:1234@localhost:5432/local ``` ```sql SELECT 'Hello, world!'; ``` Output: ``` column0 Hello, world! (1 row) ``` The primary purpose of database management systems is to store data for later retrieval. As an SQL-based system, the principal abstraction for storing data is the table. To create our first table, execute the following query: ```sql CREATE TABLE example ( key int4, value text, PRIMARY KEY (key) ); ``` Now let's populate our table with some initial data. The simplest way to do this is by using literals. ```sql INSERT INTO example (key, value) VALUES (123, 'hello'), (321, 'world'); ``` ```sql SELECT COUNT(*) FROM example; ``` Output: ``` column0 2 (1 row) ``` This command will stop the running container and delete all data stored within it. {% list tabs %} Docker-compose In the directory containing the `docker-compose.yaml` file, execute the command that will stop the container and remove its data: ```bash docker-compose down -vt 1 ``` {% note info %} To stop a Docker container and preserve its data, you should run it without the `YDBUSEINMEMORYPDISKS` environment variable and use the stop command: ```bash docker-compose stop ``` {% endnote %} Docker command This command will stop the container and remove the data: ```bash docker rm -f ydb-postgres ``` {% endlist %}
Project: BigchainDB (App Definition and Development / Database)
File: set-up-node-software.md

<! Copyright 2020 Interplanetary Database Association e.V., BigchainDB and IPDB software contributors. SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0) Code is Apache-2.0 and docs are CC-BY-4.0 > We now install and configure software that must run in every BigchainDB node: BigchainDB Server, MongoDB and Tendermint. BigchainDB Server requires Python 3.6+, so make sure your system has it. Install the required OS-level packages: ``` sudo apt install -y python3-pip libssl-dev ``` BigchainDB Server requires , and to install gevent, you must use pip 19 or later (as of 2019, because gevent now uses manylinux2010 wheels). Upgrade pip to the latest version: ``` sudo pip3 install -U pip ``` Now install the latest version of BigchainDB Server. You can find the latest version by going to the . For example, to install version 2.2.2, you would do: ``` sudo pip3 install bigchaindb==2.2.2 ``` Check that you installed the correct version of BigchainDB Server using `bigchaindb --version`. To configure BigchainDB Server, run: ``` bigchaindb configure ``` The first question is ``API Server bind? (default `localhost:9984`)``. If you're using NGINX (e.g. if you want HTTPS), then accept the default value (`localhost:9984`). If you're not using NGINX, then enter the value `0.0.0.0:9984` You can accept the default value for all other BigchainDB config settings. If you're using NGINX, then you should edit your BigchainDB config file (in `$HOME/.bigchaindb` by default) and set the following values under `"wsserver"`: ``` "advertised_scheme": "wss", "advertised_host": "bnode.example.com", "advertised_port": 443 ``` where `bnode.example.com` should be replaced by your node's actual subdomain. Install a recent version of MongoDB. BigchainDB Server requires version 3.4 or newer. ``` sudo apt install mongodb ``` If you install MongoDB using the above command (which installs the `mongodb` package), it also configures MongoDB, starts MongoDB (in the background), and installs a MongoDB startup script (so that MongoDB will be started automatically when the machine is restarted). Note: The `mongodb` package is not the official MongoDB package from MongoDB the company. If you want to install the official MongoDB package, please see . Note that installing the official package doesn't also start MongoDB. The version of BigchainDB Server described in these docs only works well with Tendermint 0.31.5 (not a higher version number). Install that: ``` sudo apt install -y unzip wget https://github.com/tendermint/tendermint/releases/download/v0.31.5/tendermintv0.31.5linux_amd64.zip unzip tendermintv0.31.5linux_amd64.zip rm tendermintv0.31.5linux_amd64.zip sudo mv tendermint /usr/local/bin ``` You won't be able to finish configuring Tendermint until you have some information from the other nodes in the network, but you can start by doing: ``` tendermint init ```
Project: KICS (Provisioning / Security & Compliance)
File: integrations_gitlabci.md

You can integrate KICS into your GitLab CI/CD pipelines. This provides you the ability to run KICS scans in your GitLab repositories and streamline vulnerabilities and misconfiguration checks to your infrastructure as code (IaC). <!-- ### Including Template You can integrate KICS into your pipeline by our in your `gitlabci.yaml`: --> <!-- ```yaml include: remote: https://raw.githubusercontent.com/checkmarx/kics/master/examples/gitlab/KICS.v1.gitlabci.yaml ``` --> ```yaml image: name: checkmarx/kics:latest entrypoint: [""] stages: kics kics-scan: stage: kics script: kics scan --no-progress -p ${PWD} -o ${PWD} --report-formats json --output-name kics-results artifacts: name: kics-results.json paths: kics-results.json when: always ``` When your pipeline executes, it will run this job. If KICS finds any issues, it will fail the build. <img src="https://raw.githubusercontent.com/Checkmarx/kics/fb3d0d28a14d79040e9368418016788bdd155017/docs/img/kicsgitlabpipeline_failure.png" width="850"> <img src="https://raw.githubusercontent.com/Checkmarx/kics/fb3d0d28a14d79040e9368418016788bdd155017/docs/img/kicsgitlabpipeline_success.png" width="850"> <img src="https://raw.githubusercontent.com/Checkmarx/kics/f2cd57f929424ee60765622d8b1a3f784707a58f/docs/img/kicsgitlabpipeline_artifact.png" width="850"> ```yaml image: name: checkmarx/kics:latest entrypoint: [""] stages: kics kics-scan: stage: kics script: kics scan -p ${PWD} --ignore-on-exit all --report-formats glsast -o ${PWD} --output-name kics-results artifacts: reports: sast: gl-sast-kics-results.json when: always ``` <br> &nbsp; This feature requires . <br> <img src="https://raw.githubusercontent.com/Checkmarx/kics/master/docs/img/kicsgitlabpipelinesastreport.png" width="850"> <br> <img src="https://raw.githubusercontent.com/Checkmarx/kics/master/docs/img/kicsgitlabpipelinesastreport_result.png" width="850"> It is possible to get code quality report with Kics scan, see the example: ```yaml image: name: checkmarx/kics:latest entrypoint: [""] stages: test code_quality: stage: test script: kics scan --no-progress -p ${PWD} -o ${PWD} --report-formats codeclimate --output-name codeclimate-result artifacts: paths: codeclimate-result.json reports: codequality: codeclimate-result.json ``` <img src="https://raw.githubusercontent.com/Checkmarx/kics/master/docs/img/kicsgitlabcodequalityreport.png" width="850">
Project: ClickHouse (App Definition and Development / Database)
File: v22.8.4.7-lts.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix possible error 'Decimal math overflow' while parsing DateTime64. (). Backported in : In it was reported that the `host_regexp` functionality was not working properly with a name to address resolution in `/etc/hosts`. It's fixed. (). Migrate artifactory ().
Project: YugabyteDB (App Definition and Development / Database)
File: scaling-reads.md

title: Scaling reads headerTitle: Scaling reads linkTitle: Scaling reads description: Scaling reads in YugabyteDB. headcontent: Read performance when scaling horizontally menu: stable: identifier: scaling-reads parent: explore-scalability weight: 30 type: docs Reads scale linearly in YugabyteDB as more nodes are added to the cluster. The is very straightforward. As the mapping of a row to a tablet is deterministic, the system knows exactly where to look for a row. Let's go over how reads work and see how well they scale. When an application connected to a node sends a read request for a key, say `SELECT * FROM T WHERE K=5`, YugabyteDB first identifies the location of the tablet leader containing the row with the key specified (`K=5`). After the location of the tablet leader is identified, the request is internally re-directed to the node containing the tablet leader for the requested key. The leader has the latest data and responds immediately. A basic `select` statement involves a maximum of just 2 nodes. This redirection is completely transparent to the application. In the following illustration, you can see that the application sent the request for `K=5` to `NODE-2`. The system identified that the key `K=5` is located in `NODE-1` and internally redirected the request to that node. Multiple applications can connect to any node and the reads will be redirected correctly. The following chart shows how reads scale horizontally in YugabyteDB using a workload of basic selects. The cluster consisted of m6i.4xlarge instances and had 1024 connections. All requests had a latency of less than 3ms. You can clearly see that with an increase in the number of nodes, the number of reads scales linearly.
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.51.md

layout: release date: 2023-02-11 tag: v0.6.51 language: en Skip dry run for meshery defined apiVersions in Meshmodel components @Revolyssup (#7054) Allow components inside Node @Revolyssup (#7041) upgrade meshkit @Revolyssup (#7040) Allow cross version deployment of meshmodel components @Revolyssup (#6988) Update component updater workflow to update only published models @Revolyssup (#7026) Refactor `mesheryctl mesh` commands @alphaX86 (#6921) [Extension] prevent dark mode in extension, until supported @Abhishek-kumar09 (#7055) [UI] Confirmation Modal and deployment badges @Abhishek-kumar09 (#7045) Fixed Dark mode button @AdityaPote (#7014) Fix: SVG scaling Problem in MesheryMeshInterface @thisiskaransgit (#7034) fix: style of input and white bg @harkiratsm (#7033) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @AdityaPote, @Chadha93, @Revolyssup, @alphaX86, @harkiratsm, @l5io, @leecalcote, @thisiskaransgit and l5io
Project: BigchainDB (App Definition and Development / Database)
File: quickstart.md

<! Copyright 2020 Interplanetary Database Association e.V., BigchainDB and IPDB software contributors. SPDX-License-Identifier: (Apache-2.0 AND CC-BY-4.0) Code is Apache-2.0 and docs are CC-BY-4.0 > This is the documentation for BigchainDB Server, or in other words, node - the BigchainDB software that is on servers (but not on clients). Quickstart link below To develop an app that talks to a BigchainDB network, you'll want a test network to test it against. You have a few options: The IPDB Test Network (or "Testnet") is a free-to-use, publicly-available test network that you can test against. It is available at . You could also run a BigchainDB node on you local machine. One way is to use this node setup guide with a one-node "network" by using the all-in-one docker solution, or manual installation and configuration of the components. Another way is to use one of the deployment methods listed in the or in the . <style media="screen" type="text/css"> .button { border-top: 1px solid #96d1f8; background: #65a9d7; background: -webkit-gradient(linear, left top, left bottom, from(#3e779d), to(#65a9d7)); background: -webkit-linear-gradient(top, #3e779d, #65a9d7); background: -moz-linear-gradient(top, #3e779d, #65a9d7); background: -ms-linear-gradient(top, #3e779d, #65a9d7); background: -o-linear-gradient(top, #3e779d, #65a9d7); padding: 8.5px 17px; -webkit-border-radius: 3px; -moz-border-radius: 3px; border-radius: 3px; -webkit-box-shadow: rgba(0,0,0,1) 0 1px 0; -moz-box-shadow: rgba(0,0,0,1) 0 1px 0; box-shadow: rgba(0,0,0,1) 0 1px 0; text-shadow: rgba(0,0,0,.4) 0 1px 0; color: white; font-size: 16px; font-family: Arial, Sans-Serif; text-decoration: none; vertical-align: middle; } .button:hover { border-top-color: #28597a; background: #28597a; color: #ccc; } .button:active { border-top-color: #1b435e; background: #1b435e; } a.button:visited { color: white } .buttondiv { margin-bottom: 1.5em; } </style> Create a transaction and post it to the test network: <div class="buttondiv"> <a class="button" href="https://www.bigchaindb.com/developers/getstarted/">Try BigchainDB Now</a> </div> <hr> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br>