cwielenb/CNCF-Dataset huggingface dataset:
Project: LinuxKit (Provisioning / Automation & Configuration)
File: 2017-04-30.md

The seventh weekly development report. Last week we had a instead. Feel free to send PRs if you want to add to these reports (or correct them). We are settling in to the project (finally) being open source, and have got lots of new contributions and interest. It has been a hectic few days during and after DockerCon, and it is good to shift from focus on launch, demos and preparation to getting the project on a good path, and welcoming new directions and contributions. Welcome everyone, looking forward to your contributions and working with you. Please open issues on GitHub if you need help, or ask on #linuxkit in the . Quite a few changes post DockerCon as we started making more breaking changes. The `moby` command was split up, into for just the assembly phase, ie `moby build` and the `linuxkit` tool in the LinuxKit repo for the parts that are specific to VM images. This is not the final arrangement, in particular the build process will probably be reworked into more phases, and be made more modular. The `linuxkit` command had a `push` stage added, which can push VM images to remote store; currently this supports pushing images to Google Cloud but more will be added. A lot of rework is planned with the `moby` tool, and it will move to soon. The and were added to the Github org. There is a lot of ongoing work to improve the test and CI, with testing on all the platforms that LinuxKit runs on. This is being led by @dave-tucker, and is outlined in the Support for using kernels from other Linux distros has been added, see the for more details. The main planned use case is for testing software easily with a wide variety of kernels, for example and `runc`. @deitch added support for swap, including encrypted swap (which you should always use if using swap). Note that we added support for devicemapper to enable this; we also added `btrfs` (for testing `containerd`) and `xfs` (for better quota support and other advantages over ext4) in to the kernel config. Apart from ongoing tooling and test improvements mentioned above, work is starting on rebasing the Docker Editions on the open source version of LinuxKit, rather than the internal version. This will involve adding detailed blueprints for the platforms, porting over missing pieces, and adding testing for each platform. Making multiple architecture support work well, starting with Arm64 is also a priority. Several more talk recordings will be available shortly.
Project: Cyclops (App Definition and Development / Application Definition & Image Build)
File: roadmap.md

We're thrilled to share that we are currently hard at work crafting the MVP (Minimum Viable Product) of our groundbreaking new offering. Our dedicated team is pouring their expertise, creativity, and countless hours into building a solution that will revolutionize the way you manage your Kubernetes clusters. The MVP represents a significant milestone in our journey, as it will serve as the initial version of our product that encompasses the core features and functionalities. This strategic approach allows us to gather valuable feedback from early users like yourself and shape the future development of the product based on real-world insights. We intend to finish developing a stable version by the start of the next year. If you have the knowledge or resources to help in contributing to Cyclops, contact us at info@cyclops-ui.com
Project: Qdrant (App Definition and Development / Database)
File: PULL_REQUEST_TEMPLATE.md

[ ] Contributions should target the `dev` branch. Did you create your branch from `dev`? [ ] Have you followed the guidelines in our Contributing document? for the same update/change? <!-- You can erase any parts of this template not applicable to your Pull Request. --> [ ] Does your submission pass tests? [ ] Have you formatted your code locally using `cargo +nightly fmt --all` command prior to submission? [ ] Have you checked your code using `cargo clippy --all --all-features` command? [ ] Have you added an explanation of what your changes do and why you'd like us to include them? [ ] Have you written new tests for your core changes, as applicable? [ ] Have you successfully ran tests with your changes locally?
Project: Harbor (Provisioning / Container Registry)
File: 3-02-DB-user-manage-project-publicity.md

Test 3-02 - Manage Project Publicity (DB Mode) ======= To verify that a non system admin user can change project publicity of a project when users are managed locally by Harbor (DB mode). User guide This test requires that a Harbor instance is running and available. Harbor is set to authenticate against a local database. ( auth_mode is set to db_auth* .) The user data is stored in a local database. A linux host with Docker CLI installed (Docker client). At least three non-admin users are in Harbor. NOTE: In below test, user A, B are non system admin users. User A, B and project X should be replaced by longer and meaningful names. MUST use two kinds of browsers at the same time to ensure independent sessions. For example, use Chrome and Firefox, or Chrome and Safari. DO NOT use the same browser to log in two users at the same time in different windows(tabs). Log in to UI as user A (non-admin). Create a new project X with publicity is on. On a Docker client host, use `docker login <harbor_host>` to log in as user A. Push an image to project X. On the Docker client host, log out user A and log in as user B. User B pulls an image from project X. Keeps user A's UI session logging on, in a different browser log in as user B. User B views "My Projects", should not see project X. User B views "Public Projects", should see project X. In user A's UI, change publicity of project X to off. In user B's UI, user B checks "My Projects" and "Public Projects", should not see project X in both places. On the Docker client host, user B pulls an image from project X. (should fail) In user A's UI, change publicity of project X to on again. User B views "My Projects", should not see project X. User B views "Public Projects", should see project X. Step 6, user B's pulling image from project X should succeed. Step 7, make sure to keep A's session while using another browser to log in user B. Step 8-11, as described. Step 12, user B's pulling should fail. Step 13-15, as described. None
Project: KubeArmor (Provisioning / Security & Compliance)
File: contribution_guide.md

KubeArmor maintainers welcome individuals and organizations from across the cloud security landscape (creators and implementers alike) to make contributions to the project. We equally value the addition of technical contributions and enhancements of documentation that helps us grow the community and strengthen the value of KubeArmor. We invite members of the community to contribute to the project! To make a contribution, please follow the steps below. Fork this repository \(KubeArmor\) First, fork this repository by clicking on the Fork button \(top right\). Then, click your ID on the pop-up screen. This will create a copy of KubeArmor in your account. Clone the repository Now clone Kubearmor locally into your dev environment. ```text $ git clone https://github.com/[your GitHub ID]/KubeArmor ``` This will clone a copy of Kubearmor installed in your dev environment. Make changes First, go into the repository directory and make some changes. Please refer to to set up your environment for KubeArmor contribution. Check the changes Please run "test_kubearmor.sh" before committing the changes ```text cd KubeArmor/KubeArmor/build ~/KubeArmor/KubeArmor/build$ ./test_kubearmor.sh ``` If you see any warnings or errors, please fix them first. Commit changes Please see your changes using "git status" and add them to the branch using "git add". ```text $ cd KubeArmor ~/KubeArmor$ git status ~/KubeArmor$ git add [changed file] ``` Then, commit the changes using the "git commit" command. ```text ~/KubeArmor$ git commit -s -m "Add a new feature by [your name]" ``` Please make sure that your changes are properly tested on your machine. Push changes to your forked repository Push your changes using the "git push" command. ```text ~/KubeArmor$ git push ``` Create a pull request with your changes with the following steps First, go to your repository on GitHub. Then, click "Pull request" button. After checking your changes, click 'Create pull request'. A pull request should contain the details of all commits as specific as possible, including "Fixes: \#\(issue number\)". Finally, click the "Create pull request" button. The changes would be merged post a review by the respective module owners. Once the changes are merged, you will get a notification, and the corresponding issue will be closed. DCO Signoffs To ensure that contributors are only submitting work that they have rights to, we are requiring everyone to acknowledge this by signing their work. Any copyright notices in this repo should specify the authors as "KubeArmor authors". To sign your work, just add a line like this at the end of your commit message: ``` Signed-off-by: FirstName LastName <email@address.com> ``` This can easily be done with the `-s` or `--signoff` option to `git commit`. By doing this, you state that the source code being submitted originated from you (see https://developercertificate.org).
Project: YugabyteDB (App Definition and Development / Database)
File: alter_server.diagram.md

<svg class="rrdiagram" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" width="1111" height="50" viewbox="0 0 1111 50"><path class="connector" d="M0 22h15m58 0h10m68 0h10m99 0h30m75 0h10m108 0h20m-228 0q5 0 5 5v8q0 5 5 5h203q5 0 5-5v-8q0-5 5-5m5 0h30m74 0h10m25 0h10m127 0h10m25 0h20m-316 0q5 0 5 5v8q0 5 5 5h291q5 0 5-5v-8q0-5 5-5m5 0h30m66 0h10m36 0h10m90 0h20m-247 0q5 0 5 5v8q0 5 5 5h222q5 0 5-5v-8q0-5 5-5m5 0h15"/><polygon points="0,29 5,22 0,15" style="fill:black;stroke-width:0"/><rect class="literal" x="15" y="5" width="58" height="25" rx="7"/><text class="text" x="25" y="22">ALTER</text><rect class="literal" x="83" y="5" width="68" height="25" rx="7"/><text class="text" x="93" y="22">SERVER</text><a xlink:href="../../../syntaxresources/grammardiagrams#server-name"><rect class="rule" x="161" y="5" width="99" height="25"/><text class="text" x="171" y="22">servername</text></a><rect class="literal" x="290" y="5" width="75" height="25" rx="7"/><text class="text" x="300" y="22">VERSION</text><a xlink:href="../../../syntaxresources/grammardiagrams#server-version"><rect class="rule" x="375" y="5" width="108" height="25"/><text class="text" x="385" y="22">serverversion</text></a><rect class="literal" x="533" y="5" width="74" height="25" rx="7"/><text class="text" x="543" y="22">OPTIONS</text><rect class="literal" x="617" y="5" width="25" height="25" rx="7"/><text class="text" x="627" y="22">(</text><a xlink:href="../../../syntaxresources/grammardiagrams#alter-fdw-options"><rect class="rule" x="652" y="5" width="127" height="25"/><text class="text" x="662" y="22">alterfdwoptions</text></a><rect class="literal" x="789" y="5" width="25" height="25" rx="7"/><text class="text" x="799" y="22">)</text><rect class="literal" x="864" y="5" width="66" height="25" rx="7"/><text class="text" x="874" y="22">OWNER</text><rect class="literal" x="940" y="5" width="36" height="25" rx="7"/><text class="text" x="950" y="22">TO</text><a xlink:href="../../../syntaxresources/grammardiagrams#new-owner"><rect class="rule" x="986" y="5" width="90" height="25"/><text class="text" x="996" y="22">new_owner</text></a><polygon points="1107,29 1111,29 1111,15 1107,15" style="fill:black;stroke-width:0"/></svg>
Project: YugabyteDB (App Definition and Development / Database)
File: yba_storage-config_gcs_update.md

Update an GCS YugabyteDB Anywhere storage configuration Update an GCS storage configuration in YugabyteDB Anywhere ``` yba storage-config gcs update [flags] ``` ``` --update-credentials [Optional] Update credentials of the storage configuration. (default false) If set to true, provide either credentials-file-path or set use-gcp-iam. --credentials-file-path string GCS Credentials File Path. Required for non IAM role based storage configurations. Can also be set using environment variable GOOGLEAPPLICATIONCREDENTIALS. --use-gcp-iam [Optional] Use IAM Role from the YugabyteDB Anywhere Host. Supported for Kubernetes GKE clusters with workload identity. Configuration creation will fail on insufficient permissions on the host. (default false) --new-name string [Optional] Update name of the storage configuration. -h, --help help for update ``` ``` -a, --apiToken string YugabyteDB Anywhere api token. --config string Config file, defaults to $HOME/.yba-cli.yaml --debug Use debug mode, same as --logLevel debug. --disable-color Disable colors in output. (default false) -H, --host string YugabyteDB Anywhere Host (default "http://localhost:9000") -l, --logLevel string Select the desired log level format. Allowed values: debug, info, warn, error, fatal. (default "info") -n, --name string [Optional] The name of the storage configuration for the operation. Required for create, delete, describe, update. -o, --output string Select the desired output format. Allowed values: table, json, pretty. (default "table") --timeout duration Wait command timeout, example: 5m, 1h. (default 168h0m0s) --wait Wait until the task is completed, otherwise it will exit immediately. (default true) ``` - Manage a YugabyteDB Anywhere GCS storage configuration
Project: Beam (App Definition and Development / Streaming & Messaging)
File: twitter-handle.md

title: 'Beam Twitter handle' <!-- 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. --> Apache Beam community thrives to be inclusive to everyone. As part of this effort, we want to enable any community member to share anything interesting and fun related to Beam via its . The Twitter feed found here is owned by the Apache Beam PMC, and the process of proposing new tweets is documented below. <a class="twitter-timeline" data-lang="en" data-height="500" data-theme="light" data-link-color="#E95F28" href="https://twitter.com/ApacheBeam?ref_src=twsrc%5Etfw">Tweets by ApacheBeam</a> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> Compose a tweet with the news you want to share. It can be anything that is relevant to Apache Beam. For example, it can be a tweet to welcome new committers, announce new Beam features, share and recognize contributors publicly, promote events and meetups, share trending articles around batch and stream processing big data, etc. Go to and request Edit access. After you are able to edit the document, fill out the necessary fields: Date - the date when you are filling out the document Author - your name Topic - what is the tweet about Content - the actual text of the tweet or link to the tweet that need to be retweeted Links/media - anything you want to add to the tweet, eg. photos, videos, references Deadline - by when the tweet needs to be out, or preferred date when it needs to be out After you type in your tweets, PMC members that are subscribed to the document will get notified and review the content. After approval, a PMC member with access to the Twitter handle will publish the tweet. Follow to see if your content is published!
Project: Meshery (Provisioning / Automation & Configuration)
File: managing-notifications.md

layout: default title: Managing Events with Notification Center permalink: guides/infrastructure-management/notification-management type: guides category: infrastructure language: en list: include abstract: "Meshery tracks operations performed on your infrastructure and workloads, and provides notification of environment issues, application conflicts with infrastructure configuration, policy violations, and so on." Meshery tracks operations that you perform on infrastructurees and their workloads. Meshery provides notification of environment issues, application conflicts with infrastructure configuration, and so on. Depending upon the severity of the notification, many notifications are informational and can readily be dismissed after reading. Some notifications include actionable alerts. Learn more in "". Particular notifications that Meshery presents are immediately actionable. These are denoted by a red colored highlight. Be on the lookout for these alerts and take action promptly to ensure a smooth running infrastructure.
Project: Puppet (Provisioning / Automation & Configuration)
File: http_file_content.md

File Content ============= The `file_content` endpoint returns the contents of the specified file. Find Get a file. GET /puppet/v3/filecontent/:mountpoint/:name The endpoint path includes a `:mount_point` which can be one of the following types: Custom file serving mounts as specified in fileserver.conf see . `modules/<MODULE>` a semi-magical mount point which allows access to the `files` subdirectory of `<MODULE>` see . `plugins` a highly magical mount point which merges the `lib` directory of every module together. Used for syncing plugins; not intended for general consumption. Per-module sub-paths can not be specified. `pluginfacts` a highly magical mount point which merges the `facts.d` directory of every module together. Used for syncing external facts; not intended for general consumption. Per-module sub-paths can not be specified. `tasks/<MODULE>` a semi-magical mount point which allows access to files in the `tasks` subdirectory of `<MODULE>` see the . `:name` is the path to the file within the `:mount_point` that is requested. GET `application/octet-stream` None GET /puppet/v3/filecontent/modules/example/myfile?environment=env Accept: application/octet-stream HTTP/1.1 200 OK Content-Type: application/octet-stream Content-Length: 16 this is my file GET /puppet/v3/filecontent/modules/example/notfound?environment=env Accept: application/octet-stream HTTP/1.1 404 Not Found Content-Type: text/plain Not Found: Could not find filecontent modules/example/notfound GET /puppet/v3/file_content?environment=env HTTP/1.1 400 Bad Request Content-Type: text/plain No request key specified in /puppet/v3/file_content/ Schema A `file_content` response body is not structured data according to any standard scheme such as json/pson/yaml, so no schema is applicable.
Project: Meshery (Provisioning / Automation & Configuration)
File: installation-bash.md

To install or upgrade `mesheryctl` using `bash`, execute anyone of the following commands. <pre class="codeblock-pre"> <div class="codeblock"> <div class="clipboardjs"> $ curl -L https://meshery.io/install | DEPLOY_MESHERY=false bash - </div></div> </pre> <pre class="codeblock-pre"> <div class="codeblock"> <div class="clipboardjs"> $ curl -L https://meshery.io/install | PLATFORM=docker bash - </div></div> </pre> <pre class="codeblock-pre"> <div class="codeblock"> <div class="clipboardjs"> $ curl -L https://meshery.io/install | PLATFORM=kubernetes bash - </div></div> </pre> Install `mesheryctl` binary and include one or more to be deployed <pre class="codeblock-pre"> <div class="codeblock"> <div class="clipboardjs"> $ curl -L https://meshery.io/install | ADAPTERS=consul PLATFORM=kubernetes bash - </div></div> </pre> You are ready to deploy Meshery `mesheryctl``. To do so, execute the following command. <pre class="codeblock-pre"><div class="codeblock"> <div class="clipboardjs">mesheryctl system start</div></div> </pre>
Project: KICS (Provisioning / Security & Compliance)
File: f74b9c43-161a-4799-bc95-0b0ec81801b9.md

title: Shared Service Account hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: f74b9c43-161a-4799-bc95-0b0ec81801b9 Query name: Shared Service Account Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Secret Management URL: A Service Account token is shared between workloads<br> ```tf title="Positive test num. 1 - tf file" hl_lines="46" resource "kubernetespod" "withpod_affinity" { metadata { name = "with-pod-affinity" } spec { affinity { pod_affinity { requiredduringschedulingignoredduring_execution { label_selector { match_expressions { key = "security" operator = "In" values = ["S1"] } } topology_key = "failure-domain.beta.kubernetes.io/zone" } } podantiaffinity { preferredduringschedulingignoredduring_execution { weight = 100 podaffinityterm { label_selector { match_expressions { key = "security" operator = "In" values = ["S2"] } } topology_key = "failure-domain.beta.kubernetes.io/zone" } } } } container { name = "with-pod-affinity" image = "k8s.gcr.io/pause:2.0" } serviceaccountname = "terraform-example" } } resource "kubernetesserviceaccount" "terraform-example" { metadata { name = "terraform-example" } secret { name = kubernetes_secret.example.metadata.0.name } } resource "kubernetes_secret" "example" { metadata { name = "terraform-example" } } ``` ```tf title="Negative test num. 1 - tf file" resource "kubernetespod" "withpodaffinity1" { metadata { name = "with-pod-affinity-1" } spec { affinity { pod_affinity { requiredduringschedulingignoredduring_execution { label_selector { match_expressions { key = "security" operator = "In" values = ["S1"] } } topology_key = "failure-domain.beta.kubernetes.io/zone" } } podantiaffinity { preferredduringschedulingignoredduring_execution { weight = 100 podaffinityterm { label_selector { match_expressions { key = "security" operator = "In" values = ["S2"] } } topology_key = "failure-domain.beta.kubernetes.io/zone" } } } } container { name = "with-pod-affinity" image = "k8s.gcr.io/pause:2.0" } } } resource "kubernetespod" "withpodaffinity2" { metadata { name = "with-pod-affinity-2" } spec { affinity { pod_affinity { requiredduringschedulingignoredduring_execution { label_selector { match_expressions { key = "security" operator = "In" values = ["S1"] } } topology_key = "failure-domain.beta.kubernetes.io/zone" } } podantiaffinity { preferredduringschedulingignoredduring_execution { weight = 100 podaffinityterm { label_selector { match_expressions { key = "security" operator = "In" values = ["S2"] } } topology_key = "failure-domain.beta.kubernetes.io/zone" } } } } container { name = "with-pod-affinity" image = "k8s.gcr.io/pause:2.0" } serviceaccountname = "service-name" } } resource "kubernetesserviceaccount" "example" { metadata { name = "example" } secret { name = kubernetes_secret.example.metadata.0.name } } resource "kubernetes_secret" "example" { metadata { name = "terraform-example" } } ```