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

<!-- Copyright Pravega Authors. 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. --> Instructions to generate Server REST API stubs ``` rm -Rf controller/src/main/java/io/pravega/controller/server/rest/generated ``` All REST API modifications should be done by updating the swagger/Controller.yaml specification file. This can be done manually or by using the online editor at http://editor.swagger.io. Download swagger-codegen-cli from maven - https://repo1.maven.org/maven2/io/swagger/swagger-codegen-cli/2.2.3/swagger-codegen-cli-2.2.3.jar ``` java -jar swagger-codegen-cli.jar generate -i <pravega root>/shared/controller-api/src/main/swagger/Controller.yaml -l jaxrs -c <pravega root>/shared/controller-api/src/main/swagger/server.config.json -o <pravega root>/controller/ ``` All files that get generated outside of the controller/src/main/java/io/pravega/controller/server/rest/generated folder should be deleted and not committed to git. The JAXRS API stubs decorated with swagger annotations are generated in .../server/rest/generated/api/ScopesApi.java class. Copy these API descriptions into interfaces in .../server/rest/v1/ApiV1.java. Also ensure that the APIs in ApiV1.java are modified to use only jersey async interfaces. Swagger codegen truncates common enum prefixes. So until https://github.com/swagger-api/swagger-codegen/issues/4261 is fixed we need to perform the following manual step. In file RetentionConfig.java replace DAYS to LIMITEDDAYS and SIZEMB to LIMITEDSIZEMB. https://jcenter.bintray.com/io/github/swagger2markup/swagger2markup-cli/1.3.3/swagger2markup-cli-1.3.3.jar ``` java -Dswagger2markup.markupLanguage=MARKDOWN -Dswagger2markup.generatedExamplesEnabled=true -jar swagger2markup-cli-1.3.3.jar convert -i <pravega root>/shared/controller-api/src/main/swagger/Controller.yaml -f <pravega root>/documentation/src/docs/rest/restapis ```
Project: Polaris (Provisioning / Security & Compliance)
File: README.md

<div align="center" class="no-border"> <img src="https://polaris.docs.fairwinds.com/img/polaris-logo.png" alt="Polaris Logo"> <br> <h3>Polaris is an open source policy engine for Kubernetes</h3> <a href="https://github.com/FairwindsOps/polaris/releases"> <img src="https://img.shields.io/github/v/release/FairwindsOps/polaris"> </a> <a href="https://goreportcard.com/report/github.com/FairwindsOps/polaris"> <img src="https://goreportcard.com/badge/github.com/FairwindsOps/polaris"> </a> <a href="https://circleci.com/gh/FairwindsOps/polaris"> <img src="https://circleci.com/gh/FairwindsOps/polaris.svg?style=svg"> </a> <a href="https://insights.fairwinds.com/gh/FairwindsOps/polaris"> <img src="https://insights.fairwinds.com/v0/gh/FairwindsOps/polaris/badge.svg"> </a> </div> Polaris is an open source policy engine for Kubernetes that validates and remediates resource configuration. It includes 30+ built in configuration policies, as well as the ability to build custom policies with JSON Schema. When run on the command line or as a mutating webhook, Polaris can automatically remediate issues based on policy criteria. Polaris can be run in three different modes: As a - Validate Kubernetes resources against policy-as-code. As an - Automatically reject or modify workloads that don't adhere to your organization's policies. As a - Incorporate policy-as-code into the CI/CD process to test local YAML files. <p align="center"> <img src="https://polaris.docs.fairwinds.com/img/architecture.svg" alt="Polaris Architecture" width="550"/> </p> Check out the <!-- Begin boilerplate --> The goal of the Fairwinds Community is to exchange ideas, influence the open source roadmap, and network with fellow Kubernetes users. or to get involved! <a href="https://insights.fairwinds.com/auth/register/"> <img src="https://www.fairwinds.com/hubfs/DocBanners/FairwindsOSSUserGroup740x125v6.png" alt="Love Fairwinds Open Source? Automate Fairwinds Open Source for free with Fairwinds Insights. Click to learn more" /> </a> Enjoying Polaris? Check out some of our other projects: - Right-size your Kubernetes Deployments by compare your memory and CPU settings against actual usage - Detect Kubernetes resources that have been deprecated or removed in future versions - Check to see if any of your Helm charts have updates available - Simplify the management of RBAC in your Kubernetes clusters Or If you're interested in running Polaris in multiple clusters, tracking the results over time, integrating with Slack, Datadog, and Jira, or unlocking other functionality, check out , a platform for auditing and enforcing policy in Kubernetes clusters. <a href="https://fairwinds.com/pricing"> <img src="https://www.fairwinds.com/hubfs/DocBanners/FairwindsPolaris_Ad.png" alt="Fairwinds Insights" /> </a>
Project: ArangoDB (App Definition and Development / Database)
File: try_operation_has_value.md

+++ title = "`bool tryoperationhas_value(X)`" description = "Default implementation of `tryoperationhasvalue(X)` ADL customisation point for `BOOSTOUTCOME_TRY`." +++ This default implementation returns whatever the `.has_value()` member function returns. Requires: That the expression `std::declval<T>().has_value()` is a valid expression. Namespace: `BOOSTOUTCOMEV2_NAMESPACE` Header: `<boost/outcome/try.hpp>`
Project: ClickHouse (App Definition and Development / Database)
File: v21.2.3.15-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Fix a bug that moving pieces to destination table may failed in case of launching multiple clickhouse-copiers. (). Backported in : Bugfix in StorageJoin. (). Backported in : The `MongoDB` table engine now establishes connection only when it's going to read data. `ATTACH TABLE` won't try to connect anymore. (). Backported in : Fix CTE when using in INSERT SELECT. This fixes , fixes . (). Backported in : Fix rare server crash on config reload during the shutdown. Fixes . (). Backported in : Fix exception during vertical merge for `MergeTree` table engines family which don't allow to perform vertical merges. Fixes . (). Backported in : Restrict to `DROP` or `RENAME` version column of `CollapsingMergeTree` and `ReplacingMergeTree` table engines. (). Backported in : Fix too often retries of failed background tasks for `ReplicatedMergeTree` table engines family. This could lead to too verbose logging and increased CPU load. Fixes . (). Backported in : Fix incorrect result of binary operations between two constant decimals of different scale. Fixes . (). Backported in : Fix null dereference with `joinusenulls=1`. (). Backported in : Avoid invalid dereference in RANGE_HASHED() dictionary. (). NO CL ENTRY: 'Revert "Backport to 21.2: Fix access control manager destruction order"'. (). Handle syntax error for ARRAY JOIN with no args ().
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_plugin_s3.md

/ @kui-shell/plugin-s3 ProviderInitializer: `Object` | Name | Type | | :- | : | | `mountName` | `string` | | `init` | (`repl`: `default`, `reinit?`: () => `void`) => \| `Promise`<\> \| `Promise`<[]\> | S3Provider: `ClientOptions` & { `bucketFilter?`: `BucketFilter` ; `directEndPoint?`: `string` ; `error?`: `Error` ; `isDefault?`: `boolean` ; `listBuckets?`: `ClientOptions` ; `mountName`: `string` ; `publicOnly?`: `boolean` ; `region?`: `string` ; `subdir?`: `string` ; `understandsFolders?`: `boolean` } eventBus: `EventBus` addProviderInitializer(`providerInitializers`): `void` | Name | Type | | : | :-- | | `providerInitializers` | [] | `void` getCurrentMounts(): [] [] a list of the providers, with info about mount status for each minioConfig(`direct?`): `Promise`<\> This takes the S3 providers that we know about, and produces a model that can be fed into `mc alias set`. Special case: if this user does not have a configured AWS provider (i.e. we have no AWS S3 credentials for them), we will create an auth-less entry; this will allow access to public AWS s3 buckets. | Name | Type | Default value | | :- | :-- | : | | `direct` | `boolean` | `false` | `Promise`<\>
Project: Meshery (Provisioning / Automation & Configuration)
File: nighthawk.md

layout: default title: Meshery Adapter for Nighthawk name: Meshery Adapter for Nighthawk component: Nighthawk earliest_version: v0.7 port: 10013/gRPC project_status: alpha github_link: https://github.com/meshery/meshery-nighthawk image: /assets/img/adapters/nighthawk/nighthawk.svg white_image: /assets/img/adapters/nighthawk/nighthawk-white.svg permalink: extensibility/adapters/nighthawk language: en {% assign sortedtestsgroup = site.compatibility | group_by: "meshery-component" %} {% for group in sortedtestsgroup %} {% if group.name == "meshery-linkerd" %} {% assign items = group.items | sort: "meshery-component-version" | reverse %} {% for item in items %} {% if item.meshery-component-version != "edge" %} {% if item.overall-status == "passing" %} {% assign adapterversiondynamic = item.meshery-component-version %} {% break %} {% elsif item.overall-status == "failing" %} {% continue %} {% endif %} {% endif %} {% endfor %} {% endif %} {% endfor %} {% include compatibility/adapter-status.html %} <!-- {% include adapter-labs.html %} --> Lifecycle management of {{page.component}} Performance characterization The {{page.name}} can install {{page.earliest_version}} of {{page.component}}. Performance tests of various configurations can run using the {{page.name}}. <!-- <a href="{{ site.baseurl }}/assets/img/adapters/linkerd/linkerd-adapter.png"> <img style="width:500px;" src="{{ site.baseurl }}/assets/img/adapters/linkerd/linkerd-adapter.png" /> </a> --> <!-- <a href="{{ site.baseurl }}/assets/img/adapters/linkerd/linkerd-install.png"> <img style="width:500px;" src="{{ site.baseurl }}/assets/img/adapters/linkerd/linkerd-install.png" /> </a> --> Identify overhead involved in running {{page.component}}, various {{page.component}} configurations while running different workloads and on different infrastructure. The adapter facilitates data plane and control plane performance testing. Prometheus integration Grafana integration
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.36.md

layout: release date: 2021-07-11 tag: v0.5.36 General [mesheryctl] Fix for @piyushsingariya (#3451) [Fix] Add case for empty token @utkarsh-pro (#3445) [CI] - Added Meshery UI Figma File Link @adithyaakrishna (#3437) [Docs] Release Notes for Meshery v0.5.35 @l5io (#3428) Update missing release pages in doc @alphaX86 (#3453) Thank you to our contributors for making this release possible: @adithyaakrishna, @alphaX86, @l5io, @leecalcote, @piyushsingariya and @utkarsh-pro
Project: Meshery (Provisioning / Automation & Configuration)
File: 1.10.4.md

component: 1.10.4 integrations: consulmesh.meshery consulmesh_definition.json exportedservices.meshery exportedservices.meshery ingressgateway.meshery ingressgateway.meshery mesh.meshery mesh.meshery proxydefaults.meshery proxydefaults.meshery servicedefaults.meshery servicedefaults.meshery serviceintentions.meshery serviceintentions.meshery serviceresolver.meshery serviceresolver.meshery servicerouter.meshery servicerouter.meshery servicesplitter.meshery servicesplitter.meshery terminatinggateway.meshery terminatinggateway.meshery
Project: Paralus (Provisioning / Security & Compliance)
File: ROADMAP.md

Our aim is to make Paralus a robust, easy to use and a feature loaded application. There is a long list of features we wish to add and improvements that we wish to make. Most of this will be tracked via , however this road map provides a gist of what you can expect from Paralus in the future. Below is a list of features that are planned for Paralus: SAML Support: Adding SAML based login support in addition to OIDC that will provide users/organisations with an additional way to login to Paralus using multiple applications. Resource Specific Access: Ability to provide fine grained access to individual resources like a workloads, pods, services etc. Support For System Users: Currently Paralus allows you to add & manage normal users. We want to allow Paralus to be able to add & manage System users/Service accounts that will be used by automation scripts, applications to interact with Paralus. Paralus Access Plane: Enable Paralus to provide zero trust access to resources outside of Kubernetes like Virtual Machines, Servers, Databases etc. Multi Factor Authentication: Make Paralus more robust and secured by implementing multi factor authentication for users. Unified Error Handling: We want to improve the way we handle errors. Make them more streamlined and standardized across all the APIs in Paralus. Easier CLI Download: Currently the end user has to choose the CLI binary based on their system which means they can download an incompatible binary. The goal is to automatically identify user's system and provide the correct binary for download. Update Group Flows From OIDC Provider: We want to add the ability to automatically configure groups in Paralus based on changes made to a user's associated group in the OIDC provider. Currently, the org admin has to manually update the groups in Paralus if there's any changes made in the OIDC provider. Fix Buf Lint Issues: Paralus makes extensive use of across the application. The code currently isn't as per the standards and hence there are linting issues that we want to fix in the near future. Add Cluster / Namespace selection in role association: Currently the user needs to input namespace(s) to be given access to when choosing a namespace related role. This enhancement will add the ability to choose a cluster and pre-populate namespaces from the target cluster for user to choose from. Cluster status - heartbeat: Ability to regularly check in on the target cluster status While these are the planned features and enhancements, we definitely welcome suggestions and ideas from everyone. Feel free to .
Project: Shifu (Provisioning / Automation & Configuration)
File: CHANGELOG-v0.40.0.md

Change the field from "telemetrySeriveEndpoint" to "telemetryServiceEndpoint" by @p-mega in Added the cncf recorded broadcast for readme by @p-mega in updated the go version to 1.22 by @p-mega in add the killercoda link to readme by @p-mega in update README with correct img link by @tomqin93 in Full Changelog: https://github.com/Edgenesis/shifu/compare/v0.39.0...v0.40.0
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: API-004-binding-manifests.md

Accepted As we rename Event Sources to Bindings, and formally separate State Stores, Message Buses, and Bindings, we need to decide if we need to introduce different manifest types. All components use the same Component manifests, identified by a component type*. We'll come up with a mechanism to support pluggable secret stores. We'll support Kubernetes native secret store and Azure Key Vault in the initial release.
Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.18.md

RabbitMQ `3.11.18` is a maintenance release in the `3.11.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25 and supports Erlang versions up to `25.3.x`. has more details on Erlang version requirements for RabbitMQ. As of 3.11.0, RabbitMQ requires Erlang 25. Nodes will fail to start on older Erlang releases. Erlang 25 as our new baseline means much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. Release notes can be found on GitHub at . Classic queues v1 (CQv1) that had a backlog of messages stored by 3.9 and earlier versions could run into an exception during queue index recovery after an upgrade to 3.10.x or any later series. CQv2 and queues without a backlog were not affected. Contributed by @gomoripeti (CloudAMQP). GitHub issue: `rabbitmq-upgrade drain` failed with an exception in environments where management plugin (HTTP API) plugin listener was bound to a specific interface. GitHub issue: The plugin will now accept JWT tokens without a `scope`. Such tokens would only be useful when the plugin is used exclusively for authentication and not authorization. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.18.tar.xz` instead of the source tarball produced by GitHub.
Project: KICS (Provisioning / Security & Compliance)
File: a97a340a-0063-418e-b3a1-3028941d0995.md

title: Pod or Container Without Security Context hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: a97a340a-0063-418e-b3a1-3028941d0995 Query name: Pod or Container Without Security Context Platform: Kubernetes Severity: <span style="color:#edd57e">Low</span> Category: Insecure Configurations URL: A security context defines privilege and access control settings for a Pod or Container<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="19 5" apiVersion: v1 kind: Pod metadata: name: frontend spec: containers: name: app image: images.my-company.example/app:v4 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" name: log-aggregator image: images.my-company.example/log-aggregator:v6 resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: frontend spec: securityContext: runAsUser: 1000 containers: name: app image: images.my-company.example/app:v4 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" name: log-aggregator image: images.my-company.example/log-aggregator:v6 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_runtime_config_config.md

+++ title = "googleruntimeconfig_config resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleruntimeconfig_config" identifier = "inspec/resources/gcp/googleruntimeconfigconfig.md googleruntimeconfigconfig resource" parent = "inspec/resources/gcp" +++ A `googleruntimeconfig_config` is used to test a Google Config resource ```ruby describe googleruntimeconfig_config(project: 'chef-gcp-inspec', name: 'inspec-gcp-runtime-config') do it { should exist } its('description') { should cmp 'My runtime configurations' } end describe googleruntimeconfig_config(project: 'chef-gcp-inspec', name: 'nonexistent') do it { should_not exist } end ``` Properties that can be accessed from the `googleruntimeconfig_config` resource: `description` : The description to associate with the runtime config. `name` : The name of the runtime config. Ensure the is enabled for the current project.
Project: KubeDL (Provisioning / Automation & Configuration)
File: sync_code.md

KubeDL supports downloading custom artifacts from remote repositories into the container. With that, user can commit their code to remote repository and re-submit the jobs without re-building the image to include the artifacts. Currently, only github is supported. The framework is pluggable and can easily support other storage systems like `HDFS`. Users can set the git config in the job's annotation with key `kubedl.io/git-sync-config` as below. The git repo will be downloaded and saved in the container's `working dir` by default. Please use the git repo's clone url ending with the `.git`, rather than the git repo's web url. ```yaml apiVersion: training.kubedl.io/v1alpha1 kind: "TFJob" metadata: name: "mnist" namespace: kubedl annotations: kubedl.io/git-sync-config: '{"source": "https://github.com/alibaba/kubedl.git" }' spec: cleanPodPolicy: None tfReplicaSpecs: ... ``` In addition, there are various of options for users to customize downloading policies, a full list of supported options are as follows: ```json { "source": "https://github.com/sample/sample.git", // code source (required). "image": "xxx", // the image to execute the git-sync logic (optional). "rootPath": "xxx", // the path to save downloaded files (optional). "destPath": "xxx", // the name of (a symlink to) a directory in which to check-out files (optional). "envs": [], // user-customized environment variables (optional). "branch": "xxx", // git repo branch (optional). "revison": "xxx", // git repo commit revision (optional). "depth": "xxx", // git sync depth (optional). "maxFailures" : 3, // max consecutive failures allowed (optional). "ssh": false, // use ssh mode or not (optional). "sshFile": "xxx", // ssh file path (optional). "user": "xxx", // git config username (optional). "password": "xxx" // git config password (optional). } ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: python-unrecoverable-errors.md

type: languages title: "Unrecoverable Errors in Beam Python" <!-- 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. --> Unrecoverable errors are issues that occur at job start-up time and prevent jobs from ever running successfully. The problem usually stems from a misconfiguration. This page provides context about common errors and troubleshooting information. If the Python version that you use to submit your job doesn't match the Python version used to build the worker container, the job doesn't run. The job fails immediately after job submission. To resolve this issue, ensure that the Python version used to submit the job matches the Python container version. During worker start-up, the worker might fail and, depending on the runner, try to restart. Before workers accept work, dependencies are checked and installed in the worker container. If a pipeline requires dependencies not already present in the runtime environment, they are installed at this time. When a problem occurs during this process, you might encounter dependency resolution failures. Examples of problems include the following: A dependency version can't be found. A worker can't connect to PyPI. To resolve this issue, before submitting your job, ensure that the dependency versions provided in your `requirements.txt` file exist and that you can install them locally. When your pipeline has dependency version mismatches, you might see `ModuleNotFound` errors or `AttributeError` messages. The `ModuleNotFound` errors occur when additional dependencies, such as `torch` and `transformers`, are neither specified in a `requirements_file` nor preinstalled in a custom container. In this case, the worker might fail to deserialize (unpickle) the user code. Your pipeline might have `AttributeError` messages when dependencies are installed but their versions don't match the versions in submission environment. To resolve these problems, ensure that the required dependencies and their versions are the same at runtime and in the submission environment. To help you identify these issues, in Apache Beam 2.52.0 and later versions, debug logs specify the dependencies at both stages. For more information, see .