cwielenb/CNCF-Dataset huggingface dataset:
Project: Piraeus Datastore (Runtime / Cloud Native Storage)
File: 4-install-operator-v2.md

After removing the Piraeus Operator v1 deployment, you can install Piraeus Operator v2. You can either use the `kubectl` method to deploy Piraeus Operator, or alternatively deploy the Operator using Helm. This is the last step when migrating Piraeus Operator from version 1 (v1) to version 2 (v2). . You can use `kubectl` and the built-in `kustomize` feature to deploy Piraeus Operator v2. First, create a file named `kustomization.yaml`, referencing the latest Piraeus Operator release, and the namespace you which to deploy the Piraeus Operator in. The latest releases are available on the [release page]. In the example below, the version is `v2.3.0`, and the namespace is `piraeus-datastore`. ```yaml apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization resources: https://github.com/piraeusdatastore/piraeus-operator//config/default?ref=v2.3.0 # Change the version here namespace: piraeus-datastore # Change the namespace here ``` Then, deploy the Operator using `kubectl` and wait for the deployment to complete: ``` $ kubectl apply -k . --server-side $ kubectl rollout status -n piraeus-datastore -w deploy/piraeus-operator-controller-manager ``` To deploy Piraeus Operator v2 using Helm, clone the latest v2 release of Piraeus. The latest releases are available on the [release page]. To also install the necessary Custom Resource Definitions for Piraeus, set `installCRDs` to `true`. ``` $ git clone -b v2.3.0 https://github.com/piraeusdatastore/piraeus-operator.git $ cd piraeus-operator $ helm install piraeus-operator charts/piraeus --set installCRDs=true ``` Once the Operator is deployed, deploy the Cluster using the generated resources from . First, create the secret used for the LINSTOR passphrase collected at the . ``` $ cat <<-EOF | kubectl apply -f - --server-side apiVersion: v1 kind: Secret metadata: name: piraeus-op-passphrase namespace: piraeus-datastore # Change the namespace here data: MASTER_PASSPHRASE: ZVRxanl1cVBscXV1ZTk1cmEwVTk5b0ptd0F4OGFmWlVPUVA0NWNnUw== EOF ``` Then, apply the resource generated by the script from step 2: ``` $ kubectl apply -f v2-resources.yaml --server-side linstorcluster.piraeus.io/linstorcluster created linstorsatelliteconfiguration.piraeus.io/host-networking created linstorsatelliteconfiguration.piraeus.io/piraeus-op-ns created ``` Now the cluster will come up, using the existing data to restore the cluster state. You can check the Cluster state by using the `linstor` command line client: ``` $ kubectl exec deploy/linstor-controller -- linstor node list $ kubectl exec deploy/linstor-controller -- linstor storage-pool list $ kubectl exec deploy/linstor-controller -- linstor resource list-volumes $ kubectl exec deploy/linstor-controller -- linstor error-reports list ``` You can also provision new volumes, to verify that the cluster is operational.
Project: FabEdge (Runtime / Cloud Native Network)
File: troubleshooting-guide.md

English | [toc] ```shell kubectl get po -n kube-system kubectl get no ``` If the FabEdge service is abnormal, check the pod logs. ```shell kubectl get po -n fabedge kubectl describe po -n fabedge fabedge-operator-xxx kubectl describe po -n fabedge fabedge-connector-xxx kubectl describe po -n fabedge fabedge-agent-xxx kubectl logs --tail=50 -n fabedge fabedge-operator-5fc5c4b56-glgjh kubectl logs --tail=50 -n fabedge fabedge-connector-68b6867bbf-m66vt -c strongswan kubectl logs --tail=50 -n fabedge fabedge-connector-68b6867bbf-m66vt -c connector kubectl logs --tail=50 -n fabedge fabedge-agent-edge1 -c strongswan kubectl logs --tail=50 -n fabedge fabedge-agent-edge1 -c agent ``` ```shell kubectl exec -n fabedge fabedge-connector-xxx -c strongswan -- swanctl --list-conns kubectl exec -n fabedge fabedge-connector-xxx -c strongswan -- swanctl --list-sas kubectl exec -n fabedge fabedge-agent-xxx -c strongswan -- swanctl --list-conns kubectl exec -n fabedge fabedge-agent-xxx -c strongswan -- swanctl --list-sas ``` If the tunnel cannot be established, check whether the firewall opens related ports. For details, see the . ```shell ip l ip r ip r s t 220 ip x p ip x s ip l ip r ip r s t 220 ip x p ip x s ip l ip r ``` Note: If edge node has interfaces such as CNI, means flannel residues exist and you need to restart the node. ```shell iptables -S iptables -L -nv --line-numbers iptables -t nat -S iptables -t nat -L -nv --line-numbers iptables -S iptables -L -nv --line-numbers iptables -t nat -S iptables -t nat -L -nv --line-numbers ``` Check whether the environment has host firewall DROP rules, especially INPUT and FORWARD chains. FabEdge related certificates including CA, Connector, and Agent, are stored in Secret and managed by Operator automatically. If some certificate-related error occur, you can use the following method to verify it. ```shell docker run fabedge/cert docker ps -a | grep cert 65ceb57d6656 fabedge/cert "/usr/local/bin/fabe" 15 seconds ago docker cp 65ceb57d6656:/usr/local/bin/fabedge-cert . kubectl get secret -n fabedge NAME TYPE DATA AGE api-server-tls kubernetes.io/tls 4 3d22h cert-token-csffn kubernetes.io/service-account-token 3 3d22h connector-tls kubernetes.io/tls 4 3d22h default-token-rq9mv kubernetes.io/service-account-token 3 3d22h fabedge-agent-tls-edge1 kubernetes.io/tls 4 3d22h fabedge-agent-tls-edge2 kubernetes.io/tls 4 3d22h fabedge-ca Opaque 2 3d22h fabedge-operator-token-tb8qb kubernetes.io/service-account-token 3 3d22h ./fabedge-cert verify -s connector-tls Your cert is ok ./fabedge-cert verify -s fabedge-agent-tls-edge1 Your cert is ok ``` You can use the script below to quickly collect the diagnostic information. If support is needed, please submit the generated files. ``` curl http://116.62.127.76/checker.sh | bash -s master | tee /tmp/master-checker.log curl http://116.62.127.76/checker.sh | bash -s connector | tee /tmp/connector-checker.log curl http://116.62.127.76/checker.sh | bash -s edge | tee /tmp/edge-checker.log curl http://116.62.127.76/checker.sh | bash | tee /tmp/node-checker.log ```
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-dbg_preflight_fqdn-poller.md

<!-- This file was autogenerated via cilium cmdref, do not edit manually--> Prepare for DNS Polling upgrades to cilium 1.4 Prepare for DNS Polling upgrades to cilium 1.4 by creating a placeholder --tofqdns-pre-cache file that can be used to pre-seed the DNS cached used in toFQDNs rules. This is useful when upgrading cilium with DNS Polling policies where an interruption in allowed IPs is undesirable. It may also be used when switching from DNS Polling based DNS discovery to DNS Proxy based discovery where an endpoint may not make a DNS request soon enough to be used by toFQDNs policy rules ``` cilium-dbg preflight fqdn-poller [flags] ``` ``` -h, --help help for fqdn-poller --tofqdns-pre-cache string The path to write serialized ToFQDNs pre-cache information. stdout is the default --tofqdns-pre-cache-ttl int TTL, in seconds, to set on generated ToFQDNs pre-cache information (default 604800) ``` ``` --config string Config file (default is $HOME/.cilium.yaml) -D, --debug Enable debug messages -H, --host string URI to server-side API ``` - Cilium upgrade helper
Project: Cilium (Runtime / Cloud Native Network)
File: cilium-dbg_policy_delete.md

<!-- This file was autogenerated via cilium cmdref, do not edit manually--> Delete policy rules ``` cilium-dbg policy delete [<labels>] [flags] ``` ``` --all Delete all policies -h, --help help for delete -o, --output string json| yaml| jsonpath='{}' ``` ``` --config string Config file (default is $HOME/.cilium.yaml) -D, --debug Enable debug messages -H, --host string URI to server-side API ``` - Manage security policies
Project: HwameiStor (Runtime / Cloud Native Storage)
File: volume_clone.md

sidebar_position: 5 sidebar_label: "Volume Clone" In HwameiStor, users can create clone volume for data volumes that have the same data as the source volume at the moment the clone occurs. :::note Creating clones of non-HA volume is currently only supported, and only in-place cloning is supported. Volume clone is implemented using snapshot technology. To avoid data inconsistency, please pause or stop I/O before cloning. ::: Follow the steps below to create and use clone volume. You can create a pvc to perform a cloning operation on a data volume. The details are as follows: ```yaml apiVersion: v1 kind: PersistentVolumeClaim metadata: name: hwameistor-lvm-volume-clone spec: storageClassName: hwameistor-storage-lvm-ssd dataSource: name: data-sts-mysql-local-0 kind: PersistentVolumeClaim apiGroup: "" accessModes: ReadWriteOnce resources: requests: storage: 1Gi ``` Use the following command to create an `nginx` application and use the data volume `hwameistor-lvm-volume-clone`: ```console cat << EOF | kubectl apply -f - apiVersion: v1 kind: Pod metadata: name: nginx namespace: default spec: containers: name: nginx image: docker.io/library/nginx:latest imagePullPolicy: IfNotPresent volumeMounts: name: data mountPath: /data ports: containerPort: 80 volumes: name: data persistentVolumeClaim: claimName: hwameistor-lvm-volume-clone EOF ```
Project: Piraeus Datastore (Runtime / Cloud Native Storage)
File: openshift.md

This guide shows you how to set the DRBD Module Loader when using OpenShift. To complete this guide, you should be familiar with: editing `LinstorSatelliteConfiguration` resources. using the `oc` command line tool to access the OpenShift cluster. The image contains the necessary files for building DRBD. Every OpenShift release includes a version of the Driver Toolkit image matching the operating system version of the release. You can use `oc` to print the correct image version: ``` $ oc adm release info --image-for=driver-toolkit quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:1328c4e7944b6d8eda40a8f789471a1aec63abda75ac1199ce098b965ec16709 ``` By default, the DRBD Module Loader will try to find the necessary header files to build DRBD from source on the host system. In OpenShift, these header files are not included in the host system. Instead, they are included in the Driver Toolkit image. To change the DRBD Module Loader, so that it uses the header files included in the Driver Toolkit image, apply the following `LinstorSatelliteConfiguration`: ```yaml apiVersion: piraeus.io/v1 kind: LinstorSatelliteConfiguration metadata: name: openshift-loader-override spec: podTemplate: spec: volumes: name: usr-src emptyDir: { } hostPath: $patch: delete initContainers: name: kernel-header-copy image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:1328c4e7944b6d8eda40a8f789471a1aec63abda75ac1199ce098b965ec16709 args: cp -avt /container/usr/src /usr/src/kernels volumeMounts: name: usr-src mountPath: /container/usr/src securityContext: privileged: true name: drbd-module-loader securityContext: privileged: true ``` NOTE: Replace the `image` of the `kernel-header-copy` container with the image returned by `oc adm release info`. After the automatic restart of the LINSTOR Satellite Pods, DRBD will be built from source, using the correct header files. OpenShift updates also update the host operating system. Since every node will be rebooted during the update, the DRBD Module loader needs to rebuild DRBD once after the restart for the new host operating system. To ensure that the DRBD rebuild is successful, you need to update the image in the `openshift-loader-override` configuration before starting the upgrade process. You can extract the Driver Toolkit image for the new OpenShift version before starting the upgrade like this: ``` $ oc adm release info 4.12.2 --image-for=driver-toolkit quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:1328c4e7944b6d8eda40a8f789471a1aec63abda75ac1199ce098b965ec16709 ```
Project: Longhorn (Runtime / Cloud Native Storage)
File: ci.md

name: CI task about: Create a CI task title: "[CI] " labels: ["kind/task", "area/ci"] assignees: '' <!--A clear and concise description of what CI task you want to develop.--> <!-- Please use a task list for items on a separate line with a clickable checkbox https://docs.github.com/en/issues/tracking-your-work-with-issues/about-task-lists [ ] `item 1` --> <!--Add any other context or screenshots about the request here.-->
Project: JuiceFS (Runtime / Cloud Native Storage)
File: support.md

name: Support Request about: Support request or question relating to JuiceFS labels: kind/question <!-- STOP -- PLEASE READ! GitHub issue is not the right place for support requests. If you're looking for help, check the Discussions (https://github.com/juicedata/juicefs/discussions). You can also post your question on the Discussions or the JuiceFS Slack channel (https://juicefs.slack.com). -->
Project: rkt (Runtime / Container Runtime)
File: integrations.md

This document tracks projects that integrate with rkt. , and help us keep the list up-to-date. : an enterprise grade container orchestration solution. Kubernetes offers rkt support as an alternative to the standard install. : Apache Mesos abstracts CPU, memory, storage, and other compute resources away from machines (physical or virtual), enabling fault-tolerant and elastic distributed systems to easily be built and run effectively. : a container orchestration platform focused on ease of use. Nomad supports rkt through the rkt driver. : a container build and runtime tool, preferring convention over configuration. : a tool for generating minimal container images. : an enterprise ready container registry. Quay hosts rkt images. : an access control and security toolkit for containers. : an open and extensible OS. rkt is included in the package managers on Red Hat, Ubuntu, and many other popular Linux distributions. : a daemon that monitors resource usage and performance for running containers.
Project: KICS (Provisioning / Security & Compliance)
File: 11bd3554-cd56-4257-8e25-7aaf30cf8f5f.md

title: IP Forwarding Enabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 11bd3554-cd56-4257-8e25-7aaf30cf8f5f Query name: IP Forwarding Enabled Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: Instances must not have IP forwarding enabled, which means the attribute 'canipforward' must not be true<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="22" name: create a instance google.cloud.gcpcomputeinstance: name: test_object machine_type: n1-standard-1 metadata: startup-script-url: gs:://graphite-playground/bootstrap.sh cost-center: '12345' labels: environment: production network_interfaces: network: "{{ network }}" access_configs: name: External NAT nat_ip: "{{ address }}" type: ONETOONE_NAT zone: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present canipforward: yes ``` ```yaml title="Negative test num. 1 - yaml file" name: create a instance google.cloud.gcpcomputeinstance: name: test_object machine_type: n1-standard-1 metadata: startup-script-url: gs:://graphite-playground/bootstrap.sh cost-center: '12345' labels: environment: production network_interfaces: network: '{{ network }}' access_configs: name: External NAT nat_ip: '{{ address }}' type: ONETOONE_NAT zone: us-central1-a project: test_project auth_kind: serviceaccount serviceaccountfile: /tmp/auth.pem state: present canipforward: no ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.66.md

layout: release date: 2023-03-22 tag: v0.6.66 Fix invalid SVG on dynamic meshmodel kubernetes component @Revolyssup (#7351) MeshModel API restructure @Revolyssup (#7364 ) aligned icon in footer @soham4abc (#7275) [UI] Added theme neutral background for meshery logo @soham4abc (#7341) icons under actions are now visible in light mode @sudhanshutech (#7202) MeshSync icon aligned with heading @Ambareen09 (#7372) sort endpoints alphabetically and group 'em by path hierarchy @vishalvivekm (#7367) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Ambareen09, @Chadha93, @Revolyssup, @l5io, @leecalcote, @soham4abc, @sudhanshutech and @vishalvivekm
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.CellShould.md

/ / CellShould .CellShould Hints to improve visualization of table cells BeGrayish = `"sub-text"` BeHidden = `"hide"` ElideWhenNarrow = `"elide-with-narrow-window"` HaveGrayBadge = `"gray-background"` HaveGreenBadge = `"green-background"` HaveRedBadge = `"red-background"` HaveYellowBadge = `"yellow-background"` HideWhenNarrow = `"hide-with-narrow-window"` HideWithSidecar = `"hide-with-sidecar"`
Project: StarRocks (App Definition and Development / Database)
File: SHOW_TRANSACTION.md

displayed_sidebar: "English" This syntax is used to view the transaction details of the specified transaction id. Syntax: ```sql SHOW TRANSACTION [FROM <db_name>] WHERE id = transaction_id ``` Examples of returned results: ```plain text TransactionId: 4005 Label: insert_8d807d5d-bcdd-46eb-be6d-3fa87aa4952d Coordinator: FE: 10.74.167.16 TransactionStatus: VISIBLE LoadJobSourceType: INSERT_STREAMING PrepareTime: 2020-01-09 14:59:07 CommitTime: 2020-01-09 14:59:09 FinishTime: 2020-01-09 14:59:09 Reason: ErrorReplicasCount: 0 ListenerId: -1 TimeoutMs: 300000 ``` TransactionId: transaction id Label: import the label corresponding to the task Coordinator: the node responsible for transaction coordination TransactionStatus: transaction status PREPARE: preparation stage COMMITTED: the transaction succeeded, but the data is not visible VISIBLE: the transaction is successful and the data is visible ABORTED: transaction failed LoadJobSourceType: type of import task. PrepareTime: transaction start time CommitTime: the time when the transaction is successfully committed FinishTime: the time when the data is visible Reason: error message ErrorReplicasCount: number of replicas with errors ListenerId: id of the related import job TimeoutMs: transaction timeout, in milliseconds To view a transaction with id 4005: ```sql SHOW TRANSACTION WHERE ID=4005; ``` In the specified dB, view the transaction with id 4005: ```sql SHOW TRANSACTION FROM db WHERE ID=4005; ```
Project: ko (App Definition and Development / Application Definition & Image Build)
File: ROADMAP.md

Last updated October 2022 Foster a community of contributors and users give talks, do outreach, expand the pool of contributors identify projects that could benefit from using `ko`, and help onboard them publish case studies from successful migrations Integrate for built artifacts attach signed SBOMs attach signed provenance attestations support the OCI referrers API and integrate with CI workload identity (e.g., GitHub OIDC) to keylessly sign artifacts Faster builds identify unnecessary work and avoid it when possible Ecosystem integrations support Terraform provider, and potentially Pulumi and CDK, others provide working examples of these integrations
Project: KICS (Provisioning / Security & Compliance)
File: c47f90e8-4a19-43f0-8413-cc434d286c4e.md

title: Network Policy Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: c47f90e8-4a19-43f0-8413-cc434d286c4e Query name: Network Policy Disabled Platform: GoogleDeploymentManager Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Kubernetes Engine Clusters must have Network Policy enabled, meaning that the attribute 'networkPolicy.enabled' must be true and the attribute 'addonsConfig.networkPolicyConfig.disabled' must be false<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="4" resources: name: cluster type: container.v1.cluster properties: description: my-cluster ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="4 7" resources: name: cluster type: container.v1.cluster properties: description: my-cluster networkPolicy: enabled: false ``` ```yaml title="Positive test num. 3 - yaml file" hl_lines="8 4" resources: name: cluster type: container.v1.cluster properties: description: my-cluster addonsConfig: networkPolicyConfig: disabled: true ``` <details><summary>Positive test num. 4 - yaml file</summary> ```yaml hl_lines="10 7" resources: name: cluster type: container.v1.cluster properties: description: my-cluster networkPolicy: enabled: false addonsConfig: networkPolicyConfig: disabled: true ``` </details> ```yaml title="Negative test num. 1 - yaml file" resources: name: cluster type: container.v1.cluster properties: description: my-cluster networkPolicy: enabled: true addonsConfig: networkPolicyConfig: disabled: false ```
Project: StarRocks (App Definition and Development / Database)
File: regexp_replace.md

displayed_sidebar: "English" This function uses repl to replace a sequence of characters in str that matches a regular expression pattern. ```Haskell VARCHAR regexp_replace(VARCHAR str, VARCHAR pattern, VARCHAR repl) ``` ```Plain Text MySQL > SELECT regexp_replace('a b c', " ", "-"); +--+ | regexp_replace('a b c', ' ', '-') | +--+ | a-b-c | +--+ MySQL > SELECT regexp_replace('a b c','(b)','<\\1>'); +-+ | regexp_replace('a b c', '(b)', '<\1>') | +-+ | a <b> c | +-+ ``` REGEXP_REPLACE,REGEXP,REPLACE
Project: Vald (App Definition and Development / Database)
File: mirroring-configuration.md

This page describes how to enable mirroring features on the Vald cluster. Before you use the mirroring functions, please look at for what you can do. Vald version: v1.8 The number of Vald clusters: 2~ This chapter shows how to configure values.yaml to enable Vald Mirror Gateway and how to interconnect Vald Mirror Gateways. The setting points are the followings: Enable the Vald Mirror Gateway using Helm values configuration Interconnect Vald Mirror Gateways using the Custom Resource configuration The Helm values configuration is required for each Vald cluster to be deployed. It is easy to enable the mirroring feature. ```yaml gateway: mirror: enabled: true ``` If you want to make more detailed settings, please set the following parameters. ```yaml gateway: mirror: ... gateway_config: ... client: {} register_duration: "1s" namespace: "vald" group: "group1" discovery_duration: 1s colocation: "dc1" ``` The cluster role configuration is required when you deploy Vald clusters with Vald Mirror Gateway on multiple Namespaces in the Kubernetes cluster. Please refer to about cluster role settings for Mirror Gateway. The Mirror Gateway is not connected to other mirror gateways when deployed. The Vald Mirror Gateway connects to another Mirror Gateway component specified in the `ValdMirrorTarget` resource (Custom Resource). Based on this resource, if the connection succeeds, the Mirror Gateway will interconnect with another. ```yaml apiVersion: vald.vdaas.org/v1 kind: ValdMirrorTarget metadata: name: mirror-target-01 namespace: vald-03 labels: group: mirror-group-01 spec: colocation: dc1 target: host: vald-mirror-gateway.vald-01.svc.cluster.local port: 8081 ```