cwielenb/CNCF-Dataset huggingface dataset:
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.Table.md

/ / Table .Table | Name | Type | | :-- | :- | | `RowType` | extends = | new Table<`RowType`\>(`table`) | Name | Type | | :-- | :- | | `RowType` | extends <`RowType`\> = | | Name | Type | | : | : | | `table` | <\> | `Optional` allowedPresentations: `PresentationStyle`[] Allowed presentations? body: `RowType`[] `Optional` breadcrumbs: [] `Optional` coldStartColumnIdx: `number` Column index to be interpreted as a time to initialize the computation `Optional` colorBy: `"default"` \| `"status"` \| `"duration"` Coloring strategy for e.g. 'grid' and 'sequence-diagram' and 'histogram' `Optional` completeColumnIdx: `number` Column index to be interpreted as a complete timestamp column `Optional` defaultPresentation: `PresentationStyle` Default presentation? `Optional` drilldownTo: `"side-split"` \| `"this-split"` \| `"new-window"` Should drilldowns go to a side split, or to this split? Default: `side-split`, unless the user chords the click with the Meta key (which is Command on macOS, and Option on Linux/Windows `Optional` durationColumnIdx: `number` Column index to be interpreted as a duration column `Optional` flexWrap: `number` \| `boolean` `Optional` fontawesome: `string` `Optional` fontawesomeBalloon: `string` `Optional` fontawesomeCSS: `string` `Optional` footer: `string`[] `Optional` header: `RowType` & { `isSortable?`: `boolean` } `Optional` markdown: `boolean` Markdown cells? `Optional` nFooterMessages: `number` E.g. when displaying events for a Kubernetes table, how many events to show in the viewport. Use -1 to show them all. [Default: 6] `Optional` noSort: `boolean` `Optional` queueingDelayColumnIdx: `number` Column index to be interpreted as a time spent in a run queue `Optional` resourceVersion: `string` \| `number` This field helps with watching/paginating `Optional` startColumnIdx: `number` Column index to be interpreted as a start timestamp column `Optional` statusColumnIdx: `number` Column index to be interpreted as a status column `Optional` style: `Optional` tableCSS: `string` `Optional` title: `string`
Project: Apache Hadoop (App Definition and Development / Database)
File: RELEASENOTES.2.7.1.md

<! --> These release notes cover new developer and user-facing incompatibilities, important issues, features, and major improvements. | Blocker | Non-HA rollback compatibility broken* Non-HA rollback steps have been changed. Run the rollback command on the namenode (\`bin/hdfs namenode -rollback\`) before starting cluster with '-rollback' option using (sbin/start-dfs.sh -rollback). | Blocker | DN startup may cause severe data loss* <!-- markdown --> Public service notice: Every restart of a 2.6.x or 2.7.0 DN incurs a risk of unwanted block deletion. Apply this patch if you are running a pre-2.7.1 release. | Major | create() always retried with hardcoded timeout when file already exists with open lease* Proxy level retries will not be done on AlreadyBeingCreatedExeption for create() op.
Project: CloudEvents (App Definition and Development / Streaming & Messaging)
File: authcontext.md

This extension embeds information about the principal which triggered an occurrence. This allows consumers of the CloudEvent to perform user-dependent actions without requiring the user ID to be embedded in the `data` or `source` field. This extension is purely informational and is not intended to secure CloudEvents. As with the main , the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in . However, the scope of these key words is limited to when this extension is used. For example, an attribute being marked as "REQUIRED" does not mean it needs to be in all CloudEvents, rather it needs to be included only when this extension is being used. Type: `String` Description: An enum representing the type of principal that triggered the occurrence. Valid values are: `app_user`: An end user of an application. Examples include an AWS cognito, Google Cloud Identity Platform, or Azure Active Directory user. `user`: A user account registered in the infrastructure. Examples include developer accounts secured by IAM in AWS, Google Cloud Platform, or Azure. `service_account`: A non-user principal used to identify a service. `api_key`: A non-user API key `system`: An obscured identity used when a cloud platform or other system service triggers an event. Examples include a database record which was deleted based on a TTL. `unauthenticated`: No credentials were used to authenticate the change that triggered the occurrence. `unknown`: The type of principal cannot be determined and is unknown. Constraints REQUIRED This specification defines the following values, and it is RECOMMENDED that they be used. However, implementations MAY define additional values. Type: `String` Description: A unique identifier of the principal that triggered the occurrence. This might, for example, be a unique ID in an identity database (userID), an email of a platform user or service account, or the label for an API key. Constraints OPTIONAL Type: `String` Description: A JSON string representing claims of the principal that triggered the event. Constraints OPTIONAL MUST NOT contain actual credentials sufficient for the Consumer to impersonate the principal directly. MAY contain enough information that a Consumer can authenticate against an identity service to mint a credential impersonating the original principal.
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_dns_resource_record_set.md

+++ title = "googlednsresourcerecordset resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googlednsresourcerecordset" identifier = "inspec/resources/gcp/googlednsresourcerecordset.md googlednsresourcerecordset resource" parent = "inspec/resources/gcp" +++ A `googlednsresourcerecordset` is used to test a Google ResourceRecordSet resource This resource has beta fields available. To retrieve these fields, include `beta: true` in the constructor for the resource ```ruby describe googlednsresourcerecordset(project: 'chef-gcp-inspec', name: 'backend.my.domain.com.', type: 'A', managed_zone: 'inspec-gcp-managed-zone') do it { should exist } its('type') { should eq 'A' } its('ttl') { should eq '300' } its('target') { should include '8.8.8.8' } its('target') { should include '8.8.4.4' } end ``` Properties that can be accessed from the `googlednsresourcerecordset` resource: `name` : For example, `www.example.com`. `type` : One of valid DNS resource types. Possible values: A AAAA CAA CNAME MX NAPTR NS PTR SOA SPF SRV TLSA TXT `ttl` : Number of seconds that this ResourceRecordSet can be cached by resolvers. `target` : As defined in RFC 1035 (section 5) and RFC 1034 (section 3.6.1) `managed_zone` : Identifies the managed zone addressed by this request. Ensure the is enabled for the current project.
Project: KubeOrbit (App Definition and Development / Application Definition & Image Build)
File: README.md

<p> <a href="https://kubeorbit.io/#gh-light-mode-only"> <img src="https://raw.githubusercontent.com/teamcode-inc/public-resources/main/kubeOrbit_log.svg" width="400px"> </a> <a href="https://kubeorbit.io/#gh-dark-mode-only"> <img src="https://raw.githubusercontent.com/teamcode-inc/public-resources/main/KubeOrbitforDark_Mode.svg" width="400px"> </a> </p> Like KubeOrbit idea? Give us a GitHub Star! ](https://github.com/teamcode-inc/kubeorbit/blob/master/LICENSE) ](https://discord.gg/5XaTS9VArf) KubeOrbit is an open-source tool that turns easy apps testing&debuging on Kubernetes in a new way. Our KubeOrbit is meant to create a channel automatically. You can test your cloud-native applications through this channel in a hands-free style. It solves the following problems during integration tests: Under limited resource and restricted environment, developers in a team may be blocked by others who are testing their own functionalities, and it slows down the development progress. On the other hand, an unstable feature being deployed to a microservice may cause entire system crash. <p align="center"> <img src="https://raw.githubusercontent.com/teamcode-inc/public-resources/main/kubeorbit_architecture.png" width="90%"> </p> From now on, stop testing your application in local infra naively. Also, no more endless efforts in managing various cloud-based test environments. KubeOrbit CLI: just using one command, forward the traffic from in-cluster service to local service in a flash, no matter your service discovery is based on Eureka, Consul, Nacos or Kubernetes SVC. Protocol support: various protocols based on Layer-7 are supported. HTTP, gRPC, Thrift, Dubbo ... Workload label: Label your workload by creating a new channel so that your request can be directed to the appropriate workload replica. This enables you to collaborate with your colleagues to test and debug the same feature.. With the following tutorials: KubeOrbit CLI: We're a warm and welcoming community of open source contributors. Please join. All types of contributions are welcome. Be sure to read our before submitting a Pull Request to the project. Join the to chat with KubeOrbit developers and other users. This is a good place to learn about KubeOrbit, ask questions, and share your experiences. The KubeOrbit user space components are licensed under the .
Project: KusionStack (Provisioning / Automation & Configuration)
File: kusion_workspace_list.md

List all workspace names This command list the names of all workspaces. ``` kusion workspace list ``` ``` kusion workspace list ``` ``` -h, --help help for list ``` ``` --profile string Name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex) (default "none") --profile-output string Name of the file to write the profile to (default "profile.pprof") ``` - Workspace is a logical concept representing a target that stacks will be deployed to
Project: SPIRE (Provisioning / Key Management)
File: plugin_server_credentialcomposer_uniqueid.md

The `uniqueid` plugin adds the `x509UniqueIdentifier` attribute to the X509-SVID subject for workloads. Server and agent X509-SVIDs are not modified. The x509UniqueIdentifier is formed from a hash of the SPIFFE ID of the workload. This plugin is intended for backwards compatibility for deployments that have come to rely on this attribute (introduced in SPIRE 1.4.2 and reverted in SPIRE 1.9.0). This plugin has no configuration. To use the plugin, add it to the plugins section of the SPIRE Server configuration: ```hcl plugins { CredentialComposer "uniqueid" {} // ... other plugins ... } ```
Project: ShardingSphere (App Definition and Development / Database)
File: import-database-configuration.en.md

+++ title = "IMPORT DATABASE CONFIGURATION" weight = 14 +++ The `IMPORT DATABASE CONFIGURATION` syntax is used to import a database from the configuration in `YAML`. {{< tabs >}} {{% tab name="Grammar" %}} ```sql ExportDatabaseConfiguration ::= 'IMPORT' 'DATABASE' 'CONFIGURATION' 'FROM' 'FILE' filePath filePath ::= string ``` {{% /tab %}} {{% tab name="Railroad diagram" %}} <iframe frameborder="0" name="diagram" id="diagram" width="100%" height="100%"></iframe> {{% /tab %}} {{< /tabs >}} When a database with the same name already exists in the metadata, it cannot be imported; When `databaseName` in YAML is empty, it cannot be imported; When `dataSources` in YAML is empty, only empty database will be imported. ```sql IMPORT DATABASE CONFIGURATION FROM FILE "/xxx/configshardingdb.yaml"; ``` `IMPORT`, `DATABASE`, `CONFIGURATION`, `FROM`, `FILE`
Project: KubeVirt (App Definition and Development / Application Definition & Image Build)
File: K8S_AUTOMATION.md

There exist automated steps for creating, updating and integrating k8s providers. These are all described as prow jobs in . | Trigger | Job | Result | | -- | -- | -- | | release of a new kubernetes minor version | | Creates a new provider for that release | | release of a new kubernetes minor version | | Creates a PR with a new check-provision job to enable testing of the new provider | | release of a new kubernetes minor version | | Creates a PR with a new set of kubevirt sig jobs to enable testing of kubevirt with the new provider | | release of new kubernetes patch version | | Creates a PR that updates the patch version for each KubeVirtCI k8s provider | | merge to kubevirt/kubevirtci main branch | | Creates a PR to update KubeVirtCI in kubevirt/kubevirt | | at the start of each month | | Checks always_run and optional states of latest kubevirt sig test jobs |
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: podman-machine-start.1.md

% podman-machine-start 1 podman\-machine\-start - Start a virtual machine podman machine start [name] Starts a virtual machine for Podman. Rootless only. Podman on MacOS and Windows requires a virtual machine. This is because containers are Linux - containers do not run on any other OS because containers' core functionality are tied to the Linux kernel. Podman machine must be used to manage MacOS and Windows machines, but can be optionally used on Linux. The default machine name is `podman-machine-default`. If a machine name is not specified as an argument, then `podman-machine-default` will be started. Only one Podman managed VM can be active at a time. If a VM is already running, `podman machine start` returns an error. podman machine start starts a Linux virtual machine where containers are run. Print usage statement. Suppress informational tips. Suppress machine starting status output. Start the specified podman machine. ``` $ podman machine start myvm ``` , March 2021, Originally compiled by Ashley Cui <acui@redhat.com>
Project: Apache Heron (App Definition and Development / Streaming & Messaging)
File: cluster-config-tmanager.md

id: version-0.20.0-incubating-cluster-config-tmanager title: Topology Manager sidebar_label: Topology Manager original_id: cluster-config-tmanager <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you 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. --> You can configure the [Topology Manager](heron-architecture#topology-manager) (TM) for a topology using the parameters below. Parameter | Meaning | Default :-- |:- |:- `heron.tmanager.metrics.collector.maximum.interval.min` | The maximum interval, in minutes, for metrics to be kept in the Topology Manager | 180 `heron.tmanager.establish.retry.times` | The maximum time to retry to establish the Topology Manager | 30 `heron.tmanager.establish.retry.interval.sec` | The interval to retry to establish the Topology Manager | 1 `heron.tmanager.network.server.options.maximum.packet.mb` | The maximum packet size, in megabytes, of the Topology Manager's network options for Stream Managers to connect to | 16 `heron.tmanager.network.controller.options.maximum.packet.mb` | The maximum packet size, in megabytes, of the Topology Manager's network options for scheduler to connect to | 1 `heron.tmanager.network.stats.options.maximum.packet.mb` | The maximum packet size, in megabytes, of the Topology Manager's network options for stat queries | 1 `heron.tmanager.metrics.collector.purge.interval.sec` | The interval, in seconds, at which the Topology Manager purges metrics from the socket | 60 `heron.tmanager.metrics.collector.maximum.exception` | The maximum number of exceptions to be stored in the topology's metrics collector, to prevent potential out-of-memory issues | 256 `heron.tmanager.metrics.network.bindallinterfaces` | Whether the metrics reporter binds on all interfaces | `False` `heron.tmanager.stmgr.state.timeout.sec` | The timeout, in seconds, for the Stream Manager, compared with (current time - last heartbeat time) | 60
Project: LinuxKit (Provisioning / Automation & Configuration)
File: kernel-perf.md

The `perf` utility is a standard Linux tool to access performance counters, trace events and access various other kernel internals for performance analysis. The `perf` utility needs to matched be with the kernel. For recent kernel build, LinuxKit provides a `linuxkit/kernel-perf` package with a matching tag for each kernel under `linuxkit/kernel`. There are a number of ways to use `linuxkit/kernel-perf` package: Add it to the `init` section. This adds `/usr/bin/perf` to the systems' root filesystem. From there it can be bind mounted into your container accessed via `/proc/1/root/usr/bin/perf` from with in the `getty` or `ssh` container. Add it to you package. If you have a custom package already, you can add `linuxkit/kernel-perf` as another stage in your package and then copy `/usr/bin/perf` into the final stage. The first method is preferable since you need to match with the kernel package tag and that is typically defined in the YAML file. I typically don't add the bind mount since this requires further modification and simply create a symlink in the `ssh` or `getty` container: ``` ln -s /proc/1/root/usr/bin/perf /usr/bin/perf ``` If you want to use `perf` you may also want to remove the `sysctl` container, or alternatively, disable the kernel pointer restriction it enables by default: ``` echo 0 > /proc/sys/kernel/kptr_restrict ``` Now, `perf` is ready to use. The LinuxKit `perf` package only contains the `perf` binary, but excludes the detailed help messages or additional scripts. If there is demand, we can add them to the LinuxKit package.
Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: organizations.md

Here are some step-by-step guides to help walk you through useful organization-related tasks in the Lagoon UI, working with groups, projects, users, and roles. <iframe src="https://scribehow.com/embed/LoginandfindorganizationsKkZhAk3gRkq2kfeaYHaI9g?removeLogo=true" width="100%" height="640" allowfullscreen frameborder="0"></iframe> <iframe src="https://scribehow.com/embed/ViewwhohasaccesstoaprojecthiB4C4bYRcuAdGsZ5b4LNw?removeLogo=true" width="100%" height="640" allowfullscreen frameborder="0"></iframe> <iframe src="https://scribehow.com/embed/AddUsertoGroupwithRole_xGA4Xl6sSYa7bz0SZb2hbQ?removeLogo=true" width="100%" height="640" allowfullscreen frameborder="0"></iframe> <iframe src="https://scribehow.com/embed/RemoveaUserfromaGroup_mSXpvF91R-irT19f3gCI2A?removeLogo=true" width="100%" height="640" allowfullscreen frameborder="0"></iframe> <iframe src="https://scribehow.com/embed/ChangeaUserRole_zj1UqJ3iTDCTvRKg3zLIFg?removeLogo=true" width="100%" height="640" allowfullscreen frameborder="0"></iframe> <iframe src="https://scribehow.com/embed/HowtoAddanEmailNotificationtoaProjectH9SHY7QvTzG4ZOK9-Bsw1g?removeLogo=true" width="100%" height="640" allowfullscreen frameborder="0"></iframe> <iframe src="https://scribehow.com/embed/AddaGrouptoaProject_Mvk-LUmaSsyaW2t3ioLuWw?removeLogo=true" width="100%" height="640" allowfullscreen frameborder="0"></iframe> <iframe src="https://scribehow.com/embed/AddaUserwithOrganizationOwnerPrivilegesi3EgoX4hSy-Da9OTL83XXQ?removeLogo=true" width="100%" height="640" allowfullscreen frameborder="0"></iframe> <iframe src="https://scribehow.com/embed/CreateanewProjectaddaGroupandcreateaProductionEnvironment_pn1gouJXTm-lPy-SaLuTcg?removeLogo=true" width="100%" height="640" allowfullscreen frameborder="0"></iframe>
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.152.md

layout: release date: 2023-10-01 tag: v0.6.152 [Extension] Docker: Update docker-compose.yaml @leecalcote (#8969) fix: Updated format script to escape quotes @nebula-aac (#8967) [UI] Integrating CASL into Meshery UI @Mohith234 (#8945) Fix Failing End to End Meshctl test @KiptoonKipkurui (#8973) [chore] Fix MeshModel models reterival @theBeginner86 (#8941) [CI] Upgrade docker/setup-buildx-action and docker/setup-qemu-action @leecalcote (#8960) [Docs] Control the display of the intra-page navigator toolbar @leecalcote (#8947) [Docs] Enhance docs for /api/user/token @coder12git (#8968) Update URL with #anchor @goldfishdolphin (#8952) [Docs] Preparation for moving from Apps to Designs @leecalcote (#8953) [Docs] Added link for discussion forum @GLADI8R (#8955) Thank you to our contributors for making this release possible: @Aisuko, @GLADI8R, @KiptoonKipkurui, @Mohith234, @aabidsofi19, @coder12git, @goldfishdolphin, @l5io, @leecalcote, @nebula-aac, @theBeginner86 and l5io
Project: Podman (App Definition and Development / Application Definition & Image Build)
File: ISSUE-EOL-POLICY.md

jetsam (n): the part of a ship, its equipment, or its cargo that is cast overboard to lighten the load in time of distress Finite resources demand some level of pruning. This document describes the basic principles used by the Containers team to identify and close stale issues. : open, but no activity in the last thirty days. crickets: closed due to lack of response from reporting party. : closed without being implemented. A deliberate decision made in recognition of human limitations. In order of judgment, from least to most. Issues are marked with the label stale-issue by a that runs daily at 00:00 UT. This also triggers an email alert to subscribers on that issue. Judgment: typically a team member will skim the issue, then decide whether to: remove the label; or close the issue (see below); or do nothing. This is informal: there is no guarantee that anyone will actually do this. Typically done by a team member after receiving a stale-issue email. Judgment: there is not enough information to act on the issue; and someone on the team has asked the reporter for more details (like NEEDINFO); and the reporter has not responded. There is no actual crickets label. There is no automated way to find issues that have been closed for this reason. Last-resort closing of an issue that will not be worked on. Factors: issue has remained open for over sixty days; and reporter is responsive, and still wishes to have the issue addressed (as does the team). Judgment: the issue is too difficult or complicated or hard to track down. decision should be made by two or more team members, with discussion in the issue/PR itself. When such an issue is closed, team member should apply the jetsam label. `stalebot` isn't perfect. It often misses issues, and we end up with some that have been open a long time and do not have the `stale-issue` label. These are hard to find manually. There is no defined process for identifying or acting on them. If and when someone finds these, they should be handled through the process defined above.
Project: Monokle (App Definition and Development / Application Definition & Image Build)
File: 2.3.md

Introducing Monokle Desktop 2.3 Release: Helm Releases in Cluster Mode Interact with Helm Releases within your cluster Dry-run upgrade to assess the impact before deployment View and manage all resources created by the selected Helm Chart Track and manage revision history of the Helm Chart Review the Values File used for deployment Explore the YAML manifests of deployed resources Validation Plugins for extended configuration validation Install community-contributed plugins