cwielenb/CNCF-Dataset huggingface dataset:
Project: Meshery (Provisioning / Automation & Configuration)
File: kubernetes.md

layout: default title: Kubernetes permalink: installation/kubernetes type: installation category: kubernetes redirect_from: installation/platforms/kubernetes display-title: "false" language: en list: include image: /assets/img/platforms/kubernetes.svg abstract: Install Meshery on Kubernetes. Deploy Meshery in Kubernetes in-cluster or outside of Kubernetes out-of-cluster. <h1>Quick Start with {{ page.title }} <img src="{{ page.image }}" style="width:35px;height:35px;" /></h1> Manage your kubernetes clusters with Meshery. Deploy Meshery in kubernetes or outside of kubernetes . _Note: It is advisable to _ <div class="prereqs"><h4>Prerequisites</h4> <ol> <li>Install the Meshery command line client, <a href="{{ site.baseurl }}/installation/mesheryctl" class="meshery-light">mesheryctl</a>.</li> <li>Install <a href="https://kubernetes.io/docs/tasks/tools/">kubectl</a> on your local machine.</li> <li>Access to an active kubernetes cluster.</li> </ol> </div> - - - - Follow the steps below to install Meshery in your kubernetes cluster. Read through the following considerations prior to deploying Meshery on kubernetes. Verify your kubeconfig's current context is set the kubernetes cluster you want to deploy Meshery. {% capture code_content %}kubectl config current-context{% endcapture %} {% include code.html code=code_content %} Once configured, execute the following command to start Meshery. Before executing the below command, go to ~/.meshery/config.yaml and ensure that current platform is set to kubernetes. {% capture code_content %}$ mesheryctl system start{% endcapture %} {% include code.html code=code_content %} For detailed instructions on installing Meshery using Helm V3, please refer to the guide. Optionally, you can verify the health of your Meshery deployment, using <a href='/reference/mesheryctl/system/check'>mesheryctl system check</a>. You're ready to use Meshery! Open your browser and navigate to the Meshery UI. {% include_cached installation/accessing-meshery-ui.md display-title="true" %} Install Meshery on Docker (out-of-cluster) and connect it to your Kubernetes cluster. Run the below command to generate the "configminikube.yaml"_ file for your cluster: <pre class="codeblock-pre"><div class="codeblock"> <div class="clipboardjs">kubectl config view --minify --flatten > config_minikube.yaml</div></div> </pre> Upload the generated config file by navigating to Settings > Environment > Out of Cluster Deployment in the Web UI and using the "Upload kubeconfig" option. {% include related-discussions.html tag="meshery" %}
Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: Clickhouse.md

Clickhouse source connector Spark<br/> Flink<br/> SeaTunnel Zeta<br/> supports query SQL and can achieve projection effect. Used to read data from Clickhouse. In order to use the Clickhouse connector, the following dependencies are required. They can be downloaded via install-plugin.sh or from the Maven central repository. | Datasource | Supported Versions | Dependency | ||--|| | Clickhouse | universal | | | Clickhouse Data Type | SeaTunnel Data Type | |--|| | String / Int128 / UInt128 / Int256 / UInt256 / Point / Ring / Polygon MultiPolygon | STRING | | Int8 / UInt8 / Int16 / UInt16 / Int32 | INT | | UInt64 / Int64 / IntervalYear / IntervalQuarter / IntervalMonth / IntervalWeek / IntervalDay / IntervalHour / IntervalMinute / IntervalSecond | BIGINT | | Float64 | DOUBLE | | Decimal | DECIMAL | | Float32 | FLOAT | | Date | DATE | | DateTime | TIME | | Array | ARRAY | | Map | MAP | | Name | Type | Required | Default | Description | ||--|-||| | host | String | Yes | - | `ClickHouse` cluster address, the format is `host:port` , allowing multiple `hosts` to be specified. Such as `"host1:8123,host2:8123"` . | | database | String | Yes | - | The `ClickHouse` database. | | sql | String | Yes | - | The query sql used to search data though Clickhouse server. | | username | String | Yes | - | `ClickHouse` user username. | | password | String | Yes | - | `ClickHouse` user password. | | servertimezone | String | No | ZoneId.systemDefault() | The session time zone in database server. If not set, then ZoneId.systemDefault() is used to determine the server time zone. | | common-options | | No | - | Source plugin common parameters, please refer to for details. | The following example demonstrates how to create a data synchronization job that reads data from Clickhouse and prints it on the local client: ```bash env { parallelism = 10 job.mode = "BATCH" } source { Clickhouse { host = "localhost:8123" database = "default" sql = "select * from test where age = 20 limit 100" username = "xxxxx" password = "xxxxx" servertimezone = "UTC" resulttablename = "test" } } sink { Console { parallelism = 1 } } ``` 1..
Project: Meshery (Provisioning / Automation & Configuration)
File: tinkerbell.md

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

If a yaml/json output is to be used as k8s manifest, users may specify its kind and have kapitan validate its structure during `kapitan compile`. The plan is to have this validation feature extendable to other outputs as well, such as terraform. Author: @yoshi-1224 The following inventory will validate the structure of Kubernetes Service manifest file in <output_path>. ```yaml parameters: kapitan: validate: output_type: kubernetes.service version: 1.6.6 output_path: relative/path/in/target ``` `version` parameter is optional: if omitted, the version will be set to the stable release of kubernetes (tbc). The schemas will be downloaded by requests from . Caching of schema will also be implemented. to validate the output yaml/json against the correct schema
Project: Fabric8 Kubernetes Client (App Definition and Development / Application Definition & Image Build)
File: PULL_REQUEST_TEMPLATE.md

<!-- Thank a lot for taking time to contribute to Fabric8 <3! Please provide a description of what your PR does providing a link (if applicable) to the issue it fixes. It is really helpful for people who would review your code. --> <! What types of changes does your code introduce? Put an `x` in all the boxes that apply --> [ ] Bug fix (non-breaking change which fixes an issue) [ ] Feature (non-breaking change which adds functionality) [ ] Breaking change (fix or feature that would cause existing functionality to change [ ] Chore (non-breaking change which doesn't affect codebase; test, version modification, documentation, etc.) - entry regarding this change [ ] I have implemented unit tests to cover my changes and other accordingly report [ ] I tested my code in Kubernetes [ ] I tested my code in OpenShift <!-- Integration tests (https://github.com/fabric8io/kubernetes-client/tree/master/kubernetes-itests) Please check integration tests and provide/improve tests if applicable. Open your PR in Draft mode and verify all of the applicable Checklist items before marking your pull request as ready for review -->
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: pull_request_template.md

Explain what this PR does. <!-- Before you push your changes: Run `make pre-push -B` to fix codegen and lint problems. Then, you MUST: Sign-off your commit (otherwise the DCO check will fail). Use (otherwise the commit message check will fail). If you did not do this, reset all your commit and replace them with a single commit: ``` git reset HEAD~1 ;# change 1 to how many commits you made git commit --signoff -m 'feat: my feat. Fixes #1234' ``` When creating your PR: Make sure that "Fixes #" or "Closes #" is in both the PR title (for release notes) and description (to automatically link and close the issue). Say how you tested your changes. If you changed the UI, attach screenshots. Set your PR as a draft initially. Your PR needs to pass the required checks before it can be approved. Once required tests have passed, mark your PR "Ready for review". If changes were requested, once you've made them, you MUST dismiss the review to get it reviewed again. -->
Project: ClickHouse (App Definition and Development / Database)
File: v22.6.2.12-stable.md

sidebar_position: 1 sidebar_label: 2022 Backported in : Improve the stability for hive storage integration test. Move the data prepare step into test.py. (). Backported in : Fix bug with nested short-circuit functions that led to execution of arguments even if condition is false. Closes . (). Remove processor description from span attributes - it is not working (). Checkout full repositories for performance tests (). Try to fix 02305schemainferencewithglobs ().
Project: Trivy (Provisioning / Security & Compliance)
File: prod.md

is an open-source system for automating deployment, scaling, and management of containerized applications. Using the Trivy Operator you can install Trivy into a Kubernetes cluster so that it automatically and continuously scan your workloads and cluster for security issues. Get it at: <https://github.com/aquasecurity/trivy-operator> is an open source cloud native container and artifact registry. Trivy is natively integrated into Harbor, no installation is needed. More info in Harbor documentation: <https://goharbor.io/docs/2.6.0/administration/vulnerability-scanning> is a policy management tool for Kubernetes. You can use Kyverno to ensure and enforce that deployed workloads' images are scanned for vulnerabilities. Get it at: <https://neonmirrors.net/post/2022-07/attesting-image-scans-kyverno> is an open-source solution that scans Kubernetes clusters with multiple plugins at scheduled times. Trivy is integrated into Zora as a vulnerability scanner plugin. Get it at: <https://zora-docs.undistro.io/latest/plugins/trivy/>
Project: Meshery (Provisioning / Automation & Configuration)
File: istio-ratelimit-operator.md

layout: integration title: Istio Rate Limit Operator subtitle: The easiest way to get production-grade Istio service mesh up and running image: /assets/img/integrations/istio-ratelimit-operator/icons/color/istio-ratelimit-operator-color.svg permalink: extensibility/integrations/istio-ratelimit-operator docURL: https://docs.meshery.io/extensibility/adapters/istio description: integrations-category: Cloud Native Network integrations-subcategory: Service Mesh registrant: Artifact Hub components: name: global-rate-limit-config colorIcon: assets/img/integrations/istio-ratelimit-operator/components/global-rate-limit-config/icons/color/global-rate-limit-config-color.svg whiteIcon: assets/img/integrations/istio-ratelimit-operator/components/global-rate-limit-config/icons/white/global-rate-limit-config-white.svg description: name: global-rate-limit colorIcon: assets/img/integrations/istio-ratelimit-operator/components/global-rate-limit/icons/color/global-rate-limit-color.svg whiteIcon: assets/img/integrations/istio-ratelimit-operator/components/global-rate-limit/icons/white/global-rate-limit-white.svg description: name: rate-limit-service colorIcon: assets/img/integrations/istio-ratelimit-operator/components/rate-limit-service/icons/color/rate-limit-service-color.svg whiteIcon: assets/img/integrations/istio-ratelimit-operator/components/rate-limit-service/icons/white/rate-limit-service-white.svg description: name: local-rate-limit-config colorIcon: assets/img/integrations/istio-ratelimit-operator/components/local-rate-limit-config/icons/color/local-rate-limit-config-color.svg whiteIcon: assets/img/integrations/istio-ratelimit-operator/components/local-rate-limit-config/icons/white/local-rate-limit-config-white.svg description: name: local-rate-limit colorIcon: assets/img/integrations/istio-ratelimit-operator/components/local-rate-limit/icons/color/local-rate-limit-color.svg whiteIcon: assets/img/integrations/istio-ratelimit-operator/components/local-rate-limit/icons/white/local-rate-limit-white.svg description: featureList: [ "Enable and enforce mutual TLS between your clusters", "Analyze Istio Destination Rules", "Design Istio Virtual Services" ] 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: Veinmind Tools (Provisioning / Security & Compliance)
File: veinmind-runner_completion.md

Generate the autocompletion script for the specified shell Generate the autocompletion script for veinmind-runner for the specified shell. See each sub-command's help for details on how to use the generated script. ``` -h, --help help for completion ``` ``` -e, --exit-code int exit-code when veinmind-runner find security issues -g, --glob string specifies the pattern of plugin file to find -o, --output string output filepath of report --threads int threads for scan action (default 5) ``` - - Generate the autocompletion script for bash - Generate the autocompletion script for fish - Generate the autocompletion script for powershell - Generate the autocompletion script for zsh
Project: SPIRE (Provisioning / Key Management)
File: ROADMAP.md

Provide a turn-key Kubernetes experience that adheres to security best practices (In Progress) Support for supply chain provenance attestation by verification of binary signing (e.g. TUF/notary/in-toto metadata validation) Secretless authentication to Google Compute Platform by expanding OIDC Federation integration support Ensure error messages are indicative of a direction towards resolution Secretless authentication to Microsoft Azure by expanding OIDC Federation integration support Thank you to for helping the SPIRE team keep this roadmap accurate and up-to-date
Project: YugabyteDB (App Definition and Development / Database)
File: upgrade-yp-installer.md

title: Upgrade YugabyteDB Anywhere using YBA Installer headerTitle: Upgrade YugabyteDB Anywhere linkTitle: Upgrade installation description: Use YBA Installer to upgrade YugabyteDB Anywhere menu: v2.18_yugabyte-platform: identifier: upgrade-yp-1-installer parent: upgrade weight: 80 type: docs <ul class="nav nav-tabs-alt nav-tabs-yb"> <li> <a href="../upgrade-yp-installer/" class="nav-link active"> <i class="fa-solid fa-building"></i>YBA Installer</a> </li> <li> <a href="../upgrade-yp-replicated/" class="nav-link"> <i class="fa-solid fa-cloud"></i>Replicated</a> </li> <li> <a href="../upgrade-yp-kubernetes/" class="nav-link"> <i class="fa-regular fa-dharmachakra" aria-hidden="true"></i>Kubernetes</a> </li> </ul> If your YugabyteDB Anywhere installation was installed using , use YBA Installer to upgrade to a newer version. Note that you can only upgrade to a newer version; downgrades are not supported. If you are upgrading a YugabyteDB Anywhere installation with high availability enabled, follow the instructions provided in . To upgrade using YBA Installer, first download the version of YBA Installer corresponding to the version of YBA you want to upgrade to. Download and extract the YBA Installer by entering the following commands: ```sh $ wget https://downloads.yugabyte.com/releases/{{<yb-version version="v2.18" format="long">}}/ybainstallerfull-{{<yb-version version="v2.18" format="build">}}-linux-x86_64.tar.gz $ tar -xf ybainstallerfull-{{<yb-version version="v2.18" format="build">}}-linux-x86_64.tar.gz $ cd ybainstallerfull-{{<yb-version version="v2.18" format="build">}}/ ``` If you are upgrading to a version earlier than v2.18.4.2, set umask for the root user to 022. When ready to upgrade, run the `upgrade` command from the untarred directory of the target version of the YBA upgrade: ```sh $ sudo ./yba-ctl upgrade ``` The upgrade takes a few minutes to complete. When finished, use the status command to verify that YBA has been upgraded to the target version: ```sh $ sudo yba-ctl status ``` If you encounter errors or have any problems with an upgrade, contact {{% support-platform %}}. For more information about using YBA Installer, refer to .
Project: YugabyteDB (App Definition and Development / Database)
File: dcl_create_user.md

title: CREATE USER statement [YSQL] headerTitle: CREATE USER linkTitle: CREATE USER description: Use the CREATE USER statement to create a user. The CREATE USER statement is an alias for CREATE ROLE, but creates a role that has LOGIN privileges by default. menu: v2.18: identifier: dclcreateuser parent: statements type: docs Use the `CREATE USER` statement to create a user. The `CREATE USER` statement is an alias for , but creates a role that has LOGIN privileges by default. {{%ebnf%}} create_user, role_option {{%/ebnf%}} See for more details. Create a sample user with password. ```plpgsql yugabyte=# CREATE USER John WITH PASSWORD 'password'; ``` Grant John all permissions on the `yugabyte` database. ```plpgsql yugabyte=# GRANT ALL ON DATABASE yugabyte TO John; ``` Remove John's permissions from the `yugabyte` database. ```plpgsql yugabyte=# REVOKE ALL ON DATABASE yugabyte FROM John; ```
Project: Meshery (Provisioning / Automation & Configuration)
File: kube-rs.md

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

name: Task about: Issue for project support and quality assurance title: '' labels: '' assignees: '' <!-- The Task issue template is for project support and quality assurance items. For example, tests or ci related issues, readme update, technical debt, etc. can be created with this template. For a new feature or an enhancement, please submit a feature request or user story issue. Thanks for understanding and for contributing to the project! --> <!-- Uncomment appropriate `/area` lines, and delete the rest. For example, `> /area api` would simply become: `/area api` --> /area ci /area api /area library /area registry /area alizer /area devworkspace /area integration-tests /area test-automation /area releng /area landing-page <!-- A clear and concise description of what the task is. --> <!-- Please uncomment and provide the target Odo version if this task is for QE integration test. Leave if blank if it's a future QE issue. Delete this comment if it's not related QE integration test. --> Target Odo version:
Project: Apache Hadoop (App Definition and Development / Database)
File: CHANGELOG.2.2.1.md

<! --> | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | add debug information when NFS fails to start with duplicate user or group names | Minor | nfs | Brandon Li | Brandon Li | | JIRA | Summary | Priority | Component | Reporter | Contributor | |:- |:- | : |:- |:- |:- | | | hadoop-auth has a build break due to missing dependency | Blocker | build | Chuan Liu | Chuan Liu |
Project: Chef InSpec (Provisioning / Security & Compliance)
File: podman_container.md

+++ title = "podman_container resource" draft = false gh_repo = "inspec" platform = "unix" [menu] [menu.inspec] title = "podman_container" identifier = "inspec/resources/os/podmancontainer.md podmancontainer resource" parent = "inspec/resources/os" +++ Use the `podman_container` Chef InSpec audit resource to test the configuration of Podman containers. This resource is distributed with Chef InSpec and is automatically available for use. Use the `podman_container` Chef InSpec audit resource to test the properties of a Podman container. ```ruby describe podmancontainer("sweetmendeleev") do it { should exist } it { should be_running } its("id") { should eq "591270d8d80d26671fd6ed622f367fbe19004d16e3b519c292313feb5f22e7f7" } its("image") { should eq "docker.io/library/nginx:latest" } its("labels") { should include "maintainer"=>"NGINX Docker Maintainers <docker-maint@nginx.com>" } its("ports") { should eq nil } end ``` The container name can be provided with the `name` resource parameter. ```ruby describe podman_container(name: 'an-echo-server') do it { should exist } it { should be_running } end ``` Alternatively, you can pass the container ID. ```ruby describe podman_container(id: '71b5df59442b') do it { should exist } it { should be_running } end ``` The following examples show how to use this Chef InSpec resource. The `id` property tests the container ID. ```ruby its('id') { should eq '71b5df59...442b' } ``` The `image` property tests the value of the container image. ```ruby its('image') { should eq 'docker.io/library/nginx:latest' } ``` The `labels` property tests the value of container image labels. ```ruby its('labels') { should eq "maintainer" => "NGINX Docker Maintainers <docker-maint@nginx.com>" } ``` The `ports` property tests the value of the Podmans ports. ```ruby its('ports') { should eq '0.0.0.0:1234->1234/tcp' } ``` The `command` property tests the value of the container run command. ```ruby its('command') { should eq 'nc -ll -p 1234 -e /bin/cat' } ``` {{< readfile file="content/inspec/reusable/md/inspecmatcherslink.md" >}} The specific matchers of this resource are: `exist` and `be_running`. The `exist` matcher specifies if the container exists. ```ruby it { should exist } ``` The `be_running` matcher checks if the container is running. ```ruby it { should be_running } ``` The following examples show how to use this Chef InSpec audit resource. The below test passes if the container `sweet_mendeleev` exists as part of the Podman instances. ```ruby describe podmancontainer('sweetmendeleev') do it { should exist } end ``` The below test passes if the container `sweet_mendeleev` exists as part of the Podman instances and the status is running. ```ruby describe podmancontainer('sweetmendeleev') do it { should be_running } end ```