cwielenb/CNCF-Dataset huggingface dataset:
Project: KubeArmor (Provisioning / Security & Compliance)
File: net-acc.md

Set the default security posture to default-deny ```sh kubectl annotate ns default kubearmor-network-posture=block --overwrite ``` ```sh kubectl exec -it nginx-77b4fdf86c-x7sdm -- bash root@nginx-77b4fdf86c-x7sdm:/# curl www.google.com curl: (6) Could not resolve host: www.google.com root@nginx-77b4fdf86c-x7sdm:/# wget https://github.com/kubearmor/KubeArmor/blob/main/examples/wordpress-mysql/original/wordpress-mysql-deployment.yaml --2023-10-06 11:08:58-- https://github.com/kubearmor/KubeArmor/blob/main/examples/wordpress-mysql/original/wordpress-mysql-deployment.yaml Resolving github.com (github.com)... 20.207.73.82 Connecting to github.com (github.com)|20.207.73.82|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 15051 (15K) [text/plain] Saving to: 'wordpress-mysql-deployment.yaml.2' wordpress-mysql-deployment.ya 100%[=================================================>] 14.70K --.-KB/s in 0.08s 2023-10-06 11:08:59 (178 KB/s) - 'wordpress-mysql-deployment.yaml.2' saved [15051/15051] ``` ``` { "Action": "Block", "ClusterName": "0-trust", "ContainerID": "20a6333c6a46e0da32b3062f0ba76e9aed4fc5ef51f5ee8aec5b980963cedea3", "ContainerImage": "docker.io/library/nginx:latest@sha256:32da30332506740a2f7c34d5dc70467b7f14ec67d912703568daff790ab3f755", "ContainerName": "nginx", "Data": "syscall=SYS_SOCKET", "Enforcer": "AppArmor", "HostName": "aditya", "HostPID": 73952, "HostPPID": 73945, "Labels": "app=nginx", "NamespaceName": "default", "Operation": "Network", "Owner": { "Name": "nginx", "Namespace": "default", "Ref": "Deployment" }, "PID": 532, "PPID": 525, "ParentProcessName": "/usr/bin/bash", "PodName": "nginx-77b4fdf86c-x7sdm", "PolicyName": "DefaultPosture", "ProcessName": "/usr/bin/curl", "Resource": "domain=AFINET type=SOCKDGRAM|SOCKNONBLOCK|SOCKCLOEXEC protocol=0", "Result": "Permission denied", "Source": "/usr/bin/curl www.google.com", "Timestamp": 1696588301, "Type": "MatchedPolicy", "UpdatedTime": "2023-10-06T10:31:41.935146Z", "cluster_id": "4291", "component_name": "kubearmor", "instanceGroup": "0", "instanceID": "0", "tenant_id": "167", "workload": "1" } ```
Project: Cyclops (App Definition and Development / Application Definition & Image Build)
File: validations.md

title: Validation Cyclops renders its UI based on the Helm chart JSON schema. JSON schema provides some fields to help with validations. Those fields are listed below, as well as whether or not Cyclops currently supports those. | Name | Description | Supported | | :- | - | | | `minLength` | minimum length of the field value | :whitecheckmark: | | `maxLength` | minimum length of the field value | :whitecheckmark: | | `pattern` | restrict a string to a particular regular expression | :whitecheckmark: | | `format` | allows for basic semantic identification of certain kinds of string values that are commonly used | :x: | <hr/> | Name | Description | Supported | | :-- | -- | | | `minimum` | minimum field value | :whitecheckmark: | | `maximum` | maximum field value | :whitecheckmark: | | `exclusiveMinimum` | exclusive minimum field value | :whitecheckmark: | | `exclusiveMaximum` | exclusive minimum field value | :whitecheckmark: | | `multipleOf` | field value has to be a multiple of | :whitecheckmark: |
Project: FOSSA (Provisioning / Security & Compliance)
File: releases.md

So you've made a change that you want to get out to users. Great! Let's get that released! We'll assume that you want to release all changes currently on `master`. You should not release anything from another branch. First, make sure that you update the release notes. Create a PR that updates the . Rename the "Unreleased" section and to the next version, incrementing the version number as appropriate. Make sure that change makes it to the `master` branch before continuing. Ensure that your local master branch is up to date and then create a tag for the new release. The commands would look something like the following. ```shell git checkout master git pull origin git tag -a vX.Y.Z -m "Releases vX.Y.Z" git push origin vX.Y.Z ``` Replace `vX.Y.Z` with your version number, such as `v3.1.4`. The tag must start with `v`. GitHub Actions will take the tag and run some tests before generating a draft release which can be found on the . If nothing has changed to dissuade you it's time to publish. Add the notes for this release from to the release description. Hit "publish" at the bottom. Inform our users!
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.9.24.md

RabbitMQ `3.9.24` is a maintenance release in the `3.9.x` release series. Please refer to the Upgrading to 3.9 section from if upgrading from a version prior to 3.9.0. This release requires at least Erlang 24.2, and supports Erlang 25. has more details on Erlang version requirements for RabbitMQ. Erlang 23 support has reached its . Starting with this release, RabbitMQ requires Erlang 24.2 or later versions. Nodes will fail to start on older Erlang releases. Release notes can be found on GitHub at . Intra-cluster communication link metric collector could run into an exception when peer connection has just been re-established, e.g. after a peer node restart. GitHub issue: When a node was , it closed all MQTT client connections cluster-wide instead of just local client connections. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.24.tar.xz` instead of the source tarball produced by GitHub.
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: API-007-tracing-endpoint.md

Proposed We now support distributed tracing across Dapr sidecars, and we inject correlation id to HTTP headers and gRPC metadata before we hand the requests to user code. However, it's up to the user code to configure and implement proper tracing themselves. We should consider adding a tracing endpoint that user code can call in to log traces and telemetries.
Project: YDB (App Definition and Development / Database)
File: run_custom.md

To run the example against any available YDB database, you need to know the and the . If authentication is enabled in the database, you also need to select the and get secrets (a token or username/password pair). Run the command as follows: ```bash ( export <authmodevar>="<authmodevalue>" && cd ydb-go-examples && \ go run ./basic -ydb="<endpoint>?database=<database>" ) ``` where `<endpoint>`: The . `<database>`: The . `<authmodevar>`: The that determines the authentication mode. `<authmodevalue>` is the authentication parameter value for the selected mode. For example: ```bash ( export YDBACCESSTOKEN_CREDENTIALS="t1.9euelZqOnJuJlc..." && cd ydb-go-examples && \ go run ./basic -ydb="grpcs://ydb.example.com:2135?database=/somepath/somelocation" ) ```
Project: ClickHouse (App Definition and Development / Database)
File: v23.8.12.13-lts.md

sidebar_position: 1 sidebar_label: 2024 Improve isolation of query cache entries under re-created users or role switches (). Fix string search with const position (). Fix crash in `multiSearchAllPositionsCaseInsensitiveUTF8` for incorrect UTF-8 (). Backported in :. (). Backported in : ... ().
Project: Pinniped (Provisioning / Key Management)
File: fips.md

title: FIPS-compatible builds of Pinniped binaries description: Reference for FIPS builds of Pinniped binaries cascade: layout: docs menu: docs: name: FIPS-compatible builds weight: 30 parent: reference By default, the Pinniped supervisor and concierge use ciphers that are not supported by FIPS 140-2. If you are deploying Pinniped in an environment with FIPS compliance requirements, you will have to build the binaries yourself using the `fips_strict` build tag and Golang's `go-boringcrypto` fork. The Pinniped team provides an demonstrating how you can build Pinniped images in a FIPS compatible way. However, we do not provide official support for FIPS configuration, and we may not respond to GitHub issues opened related to FIPS support. We provide this for informational purposes only. To build Pinniped use our example fips Dockerfile, you can run: ```bash $ git clone git@github.com:vmware-tanzu/pinniped.git $ cd pinniped $ git checkout {{< latestversion >}} $ docker build -f hack/Dockerfile_fips . ``` Now you can deploy and by specifying this image instead of the standard Pinniped image in your `values.yaml` or `deployment.yaml` file.
Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: add-to-directory.md

id: add-to-directory title: Add to Directory description: Documentation on Adding Plugin to Plugin Directory To add a new plugin to the create a file in with your plugin's information. Example: ```yaml title: Your Plugin author: Your Name authorUrl: # A link to information about the author E.g. Company url, github user profile, etc category: Monitoring # A single category e.g. CI, Machine Learning, Services, Monitoring description: A brief description of the plugin. # Max 170 characters documentation: # A link to your documentation E.g. Your github README iconUrl: # Used as the src attribute for your logo. npmPackageName: # Your npm package name E.g. '@backstage/plugin-<etc>' quotes are required addedDate: # The date plugin added to directory E.g. '2022-10-01' quotes are required ``` Here are a few tips to help speed up the review process when you submit your plugin: For any icon that you use make sure you have the proper rights to use it. Make sure that your package had been published on the NPM registry and that it's public. Make sure your package on NPM has a link back to your code repo, this helps provide confidence that it's the right package. Where possible, please use an that matches either your Organization name or user name, this provides trust in the plugin If your plugin has both a frontend and backend link the documentation to the frontend package but make sure it mentioned needing to install the backend package. Where possible include a screenshot of the features in you plugin documentation, it really does help when deciding to use a plugin.
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: operator-sdk_create_webhook.md

title: "operator-sdk create webhook" Scaffold a webhook for an API resource Scaffold a webhook for an API resource. You can choose to scaffold defaulting, validating and/or conversion webhooks. ``` operator-sdk create webhook [flags] ``` ``` operator-sdk create webhook --group ship --version v1beta1 --kind Frigate --defaulting --programmatic-validation operator-sdk create webhook --group ship --version v1beta1 --kind Frigate --conversion ``` ``` --conversion if set, scaffold the conversion webhook --defaulting if set, scaffold the defaulting webhook --force attempt to create resource even if it already exists --group string resource Group -h, --help help for webhook --kind string resource Kind --plural string resource irregular plural form --programmatic-validation if set, scaffold the validating webhook --version string resource Version ``` ``` --plugins strings plugin keys to be used for this subcommand execution --verbose Enable verbose logging ``` - Scaffold a Kubernetes API or webhook
Project: Fluvio (App Definition and Development / Streaming & Messaging)
File: pull_request_template.md

A brief description of the change being made in this pull request. What inspired you to submit this pull request? A list of issues closed by or relevant to this PR. Closes #. Is there anything else you'd like us to know while reviewing this? [ ] Created or updated all relevant documentation [ ] Added unit tests to relevant added or changed code [ ] Bumped required crate version numbers [ ] Updated CHANGELOG.md
Project: ScalarDB (App Definition and Development / Database)
File: add-scalardb-to-your-build.md

The ScalarDB library is available on the . You can add the library as a build dependency to your application by using Gradle or Maven. Select your build tool, and follow the instructions to add the build dependency for ScalarDB to your application. <div id="tabset-1"> <div class="tab"> <button class="tablinks" onclick="openTab(event, 'Gradle', 'tabset-1')" id="defaultOpen-1">Gradle</button> <button class="tablinks" onclick="openTab(event, 'Maven', 'tabset-1')">Maven</button> </div> <div id="Gradle" class="tabcontent" markdown="1"> To add the build dependency for ScalarDB by using Gradle, add the following to `build.gradle` in your application, replacing `<VERSION>` with the version of ScalarDB that you want to use: ```gradle dependencies { implementation 'com.scalar-labs:scalardb:<VERSION>' } ``` </div> <div id="Maven" class="tabcontent" markdown="1"> To add the build dependency for ScalarDB by using Maven, add the following to `pom.xml` in your application, replacing `<VERSION>` with the version of ScalarDB that you want to use: ```xml <dependency> <groupId>com.scalar-labs</groupId> <artifactId>scalardb</artifactId> <version><VERSION></version> </dependency> ``` </div> </div>
Project: Ansible (Provisioning / Automation & Configuration)
File: README.md

Role Name ========= A brief description of the role goes here. Requirements Any pre-requisites that may not be covered by Ansible itself or the role should be mentioned here. For instance, if the role uses the EC2 module, it may be a good idea to mention in this section that the boto package is required. Role Variables -- A description of the settable variables for this role should go here, including any variables that are in defaults/main.yml, vars/main.yml, and any variables that can/should be set via parameters to the role. Any variables that are read from other roles and/or the global scope (ie. hostvars, group vars, etc.) should be mentioned here as well. Dependencies A list of other roles hosted on Galaxy should go here, plus any details in regards to parameters that may need to be set for other roles, or variables that are used from other roles. Example Playbook Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too: hosts: servers roles: { role: username.rolename, x: 42 } License BSD Author Information An optional section for the role authors to include contact information, or a website (HTML is not allowed). tion, or a website (HTML is not allowed).
Project: SPIFFE (Provisioning / Key Management)
File: VOLKAN_OZCELIK.md

Volkan is the author of , the founder of , and last but not least, is truly a force of his own. With an uncanny ability to explain complicated topics in a very succinct way, he is not just an accomplished technologist, but also a prolific creator. Through his tutorials, videos, livestreams and the like, Volkan has very significantly broadened the SPIFFE community. Along the way, he's gained a strong understanding of the SPIFFE and cloud native ecosystem at large, and captured hearts and minds globally. If elected, I believe that Volkan will bring a broad and far reaching perspective to the SSC, a wholistic representation of the industry at large. Further, he is well equipped to connect on a personal basis with our community and others - a skill which is truly invaluable in this setting. GitHub Handle: @v0lkan Email Address: me@volkan.io LinkedIn Profile: https://www.linkedin.com/in/volkanozcelik Current Affiliation: VMware
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: create-jobs.md

title: Kubernetes &mdash; Working with Jobs layout: 1: left A Job creates one or more Pods and will continue to retry execution of the Pods until a specified number of them successfully terminate. As pods successfully complete, the Job tracks the successful completions. When a specified number of successful completions is reached, the task (ie, Job) is complete. Deleting a Job will clean up the Pods it created. Suspending a Job will delete its active Pods until the Job is resumed again. ???+ tip "Controlling Parallelism" Kubernetes Jobs use two parameters, `completions` and `parallelism`, to control how a Job is subdivided into units of work. Each unit of work is executed by a Pod. First, let's create a namespace to keep our work isolated: ```bash validate: kubectl get ns kui-notebook-2 cleanup: kubectl delete ns kui-notebook-2 kubectl create ns kui-notebook-2 ``` To schedule a job, use `kubectl apply` with a definition of your job. The following command applies a `job.yaml` to our scratch namespace. The response from this command is a live visualization of the progress of the Job. ```bash validate: kubectl get job pi -n kui-notebook-2 cleanup: kubectl delete job pi -n kui-notebook-2 k apply -f https://raw.githubusercontent.com/kubernetes-sigs/kui/master/plugins/plugin-kubectl/tests/data/k8s/job2.yaml -n kui-notebook-2 ``` This visualization shows how the tasks of our Job are scheduled, over time. You can see concurrency and cold start penalties. The live table will update as tasks are scheduled. ```bash execute: now kubectl dashboard job -n kui-notebook-2 --watch ``` ```bash execute: now kubectl get events -n kui-notebook-2 --field-selector=involvedObject.kind=Pod --field-selector=involvedObject.kind=Job --watch ```
Project: CloudMatos (Provisioning / Security & Compliance)
File: ROADMAP.md

Roadmap is where you can learn about what features community is currently working on and expected release time. Existing reported issues can be found at . Contributions to defined roadmap items can be done by following . Have any questions or comments about items on the roadmap? Share your feedback via . The following is a list of our focus areas: Deep Observability Native cloud API's Integrations with third party observability tools Anomaly and Drift Detection Recommend Remediation Support AWS and GCP Get current real time resource information and metadata Identify anomalies and policy/configuration drifts Extend Support to more resources and Services Detection scope for more use cases Support for more cloud platforms Get health information and compare against set/defined thresholds Recommend remediation for detected anomalies and drifts Any statement in this repository that is not purely historical is considered a forward-looking statement. Forward-looking statements included in this repository are based on information available to Matos as of the date they are made, and Matos assumes no obligation to update any forward-looking statements. The forward-looking roadmap does not represent a commitment, guarantee, obligation or promise to deliver any product or feature, or to deliver any product and feature by any particular date, and is intended to outline the general development plans.
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.3.0.3.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Major | Ensure only NM classpath in 2.x gets TSv2 related hbase jars, not the user classpath* Ensure only NM classpath in 2.x gets TSv2 related hbase jars, not the user classpath. | Minor | RBF: Use the ZooKeeper as the default State Store* Change default State Store from local file to ZooKeeper. This will require additional zk address to be configured.
Project: StarRocks (App Definition and Development / Database)
File: SUSPEND_or_RESUME_PIPE.md

displayed_sidebar: "English" Suspends or resumes a pipe: When a load job is in progress (namely, in the `RUNNING` state), suspending (`SUSPEND`) the pipe for the job interrupts the job. When a load job encounters errors, resuming (`RESUME`) the pipe for the job will continue to run the erroneous job. This command is supported from v3.2 onwards. ```SQL ALTER PIPE [ IF EXISTS ] <pipe_name> { SUSPEND | RESUME [ IF SUSPENDED ] } ``` The name of the pipe. Suspend the pipe named `userbehaviorreplica` (which is in the `RUNNING` state) in the database named `mydatabase`: ```SQL USE mydatabase; ALTER PIPE userbehaviorreplica SUSPEND; ``` If you use to query the pipe, you can see that its state has changed to `SUSPEND`. Resume the pipe named `userbehaviorreplica` in the database named `mydatabase`: ```SQL USE mydatabase; ALTER PIPE userbehaviorreplica RESUME; ``` If you use to query the pipe, you can see that its state has changed to `RUNNING`.
Project: StarRocks (App Definition and Development / Database)
File: str_to_map.md

displayed_sidebar: "English" Splits a given string into key-value pairs using two delimiters and returns a map of the split pairs. This function is supported from v3.1 onwards. ```Haskell MAP<VARCHAR, VARCHAR> strtomap(VARCHAR content[, VARCHAR delimiter[, VARCHAR map_delimiter]]) ``` `content`: required, the string expression to split. `delimiter`: optional, the delimiter used to split `content` into key-value pairs, defaults to `,`. `map_delimiter`: optional, the delimiter used to separate each key-value pair, defaults to `:`. Returns a MAP of STRING elements. Any null input results in NULL. ```SQL mysql> SELECT strtomap('a:1|b:2|c:3', '|', ':') as map; ++ | map | ++ | {"a":"1","b":"2","c":"3"} | ++ mysql> SELECT strtomap('a:1;b:2;c:3', ';', ':') as map; ++ | map | ++ | {"a":"1","b":"2","c":"3"} | ++ mysql> SELECT strtomap('a:1,b:2,c:3', ',', ':') as map; ++ | map | ++ | {"a":"1","b":"2","c":"3"} | ++ mysql> SELECT strtomap('a') as map; ++ | map | ++ | {"a":null} | ++ mysql> SELECT strtomap('a:1,b:2,c:3',null, ':') as map; ++ | map | ++ | NULL | ++ mysql> SELECT strtomap('a:1,b:2,c:null') as map; ++ | map | ++ | {"a":"1","b":"2","c":"null"} | ++ ``` STRTOMAP
Project: Nocalhost (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. -->