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

RabbitMQ `3.9.25` is a maintenance release in the `3.9.x` release series. Please refer to the Upgrading to 3.9 section from if upgrading from a version prior to 3.9.0. This release requires at least Erlang 24.2, and supports Erlang 25. has more details on Erlang version requirements for RabbitMQ. Erlang 23 support has reached its . Starting with this release, RabbitMQ requires Erlang 24.2 or later versions. Nodes will fail to start on older Erlang releases. Release notes can be found on GitHub at . `rabbitmq-diagnostics status` now handles server responses where free disk space is not yet computed. This is the case with nodes early in the boot process. GitHub issue: Management UI links now include "noopener" and "noreferrer" attributes to protect them against . Note that since management UI only includes a small number of external links to trusted resources, reverse tabnabbing is unlikely to affect most users. However, it can show up in security scanner results and become an issue in environments where a modified version of RabbitMQ is offered as a service. Contributed by @illotum (AWS). GitHub issue: Plugin could stop in environments where no static Shovels were defined and a specific sequence of events happens at the same time. Contributed by @gomoripeti. GitHub issue: When installation directory was overridden, the plugins directory did not respect the updated base installation path. GitHub issue: None in this release. To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.9.25.tar.xz` instead of the source tarball produced by GitHub.
Project: StarRocks (App Definition and Development / Database)
File: unhex.md

displayed_sidebar: "English" This function performs the opposite operation of hex(). It interprets each pair of hexadecimal digits in the input string as a number and converts it to the byte represented by the number. The return value is a binary string. ```Haskell UNHEX(str); ``` `str`: the string to convert. The supported data type is VARCHAR. An empty string is returned if any of the following situations occur: The length of the string is 0 or the number of characters in the string is an odd number. The string contains characters other than `[0-9]`, `[a-z]`, and `[A-Z]`. Returns a value of the VARCHAR type. ```Plain Text mysql> select unhex('33'); +-+ | unhex('33') | +-+ | 3 | +-+ mysql> select unhex('6170706C65'); ++ | unhex('6170706C65') | ++ | apple | ++ mysql> select unhex('4142@'); +-+ | unhex('4142@') | +-+ | | +-+ 1 row in set (0.01 sec) ``` UNHEX
Project: CDK for Kubernetes (CDK8s) (Provisioning / Automation & Configuration)
File: constructs.md

Constructs are the basic building block of cdk8s. They are the instrument that enables composition and creation of higher-level abstractions through normal object-oriented classes. If you come from the Kubernetes world, you can think of constructs as programmatically defined Helm Charts. The nice thing about constructs being "programmatically defined" is that we can use them to leverage the full power of object-oriented programming. For example: You can express the abstraction's API using strong-typed data types You can express rich interactions with methods and properties You can create polymorphic programming models through interfaces and base classes Share them through regular package managers Test them using our familiar testing tools and techniques Version them ...and do all that stuff that we've been doing with software in the past 20 years.
Project: KubeLinter (Provisioning / Security & Compliance)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: "[FEATURE_REQUEST]" labels: '' assignees: '' Description of the problem/feature request A clear and concise description of the problem, or the proposed new feature. Description of the existing behavior vs. expected behavior If applicable, please paste in the existing KubeLinter output along with the input used, and point out which part should be modified (expected output). Additional context Add any other context or screenshots about the feature request here.
Project: Tremor (App Definition and Development / Streaming & Messaging)
File: windowkind.md

A `tumbling` window defines a wall-clock-bound or data-bound window of non-overlapping time for storing events. The windows can not overlap, and there are no gaps between windows permissible. A `sliding` window defines a wall-clock-bound or data-bound window of events that captures an intervalic window of events whose extent derives from the size of the window. A sliding window of size 2 captures up to to events. Every subsequent event will evict the oldest and retain the newest event with the previous ( now oldest ) event. Both kinds of window store events in arrival order
Project: KICS (Provisioning / Security & Compliance)
File: 2623d682-dccb-44cd-99d0-54d9fd62f8f2.md

title: EC2 Network ACL Ineffective Denied Traffic hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 2623d682-dccb-44cd-99d0-54d9fd62f8f2 Query name: EC2 Network ACL Ineffective Denied Traffic Platform: CloudFormation Severity: <span style="color:#ff7213">Medium</span> Category: Access Control URL: Ineffective deny rules. A deny rule should be applied to all IP addresses.<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="17" Resources: MyNACL: Type: AWS::EC2::NetworkAcl Properties: VpcId: vpc-1122334455aabbccd Tags: Key: Name Value: NACLforSSHTraffic InboundRule: Type: AWS::EC2::NetworkAclEntry Properties: NetworkAclId: Ref: MyNACL RuleNumber: 100 Protocol: 6 RuleAction: deny CidrBlock: 172.16.0.0/24 PortRange: From: 22 To: 22 OutboundRule: Type: AWS::EC2::NetworkAclEntry Properties: NetworkAclId: Ref: MyNACL RuleNumber: 100 Protocol: -1 Egress: true RuleAction: deny CidrBlock: 0.0.0.0/0 ``` ```json title="Positive test num. 2 - json file" hl_lines="20" { "Resources": { "MyNACL": { "Type": "AWS::EC2::NetworkAcl", "Properties": { "VpcId": "vpc-1122334455aabbccd", "Tags": [ { "Key": "Name", "Value": "NACLforSSHTraffic" } ] } }, "InboundRule": { "Properties": { "RuleNumber": 100, "Protocol": 6, "RuleAction": "deny", "CidrBlock": "172.16.0.0/24", "PortRange": { "From": 22, "To": 22 }, "NetworkAclId": { "Ref": "MyNACL" } }, "Type": "AWS::EC2::NetworkAclEntry" }, "OutboundRule": { "Properties": { "RuleAction": "deny", "CidrBlock": "0.0.0.0/0", "NetworkAclId": { "Ref": "MyNACL" }, "RuleNumber": 100, "Protocol": -1, "Egress": true }, "Type": "AWS::EC2::NetworkAclEntry" } } } ``` ```yaml title="Negative test num. 1 - yaml file" Resources: MyNACL: Type: AWS::EC2::NetworkAcl Properties: VpcId: vpc-1122334455aabbccd Tags: Key: Name Value: NACLforSSHTraffic InboundRule: Type: AWS::EC2::NetworkAclEntry Properties: NetworkAclId: Ref: MyNACL RuleNumber: 100 Protocol: 6 RuleAction: allow CidrBlock: 172.16.0.0/24 PortRange: From: 22 To: 22 OutboundRule: Type: AWS::EC2::NetworkAclEntry Properties: NetworkAclId: Ref: MyNACL RuleNumber: 100 Protocol: -1 Egress: true RuleAction: allow CidrBlock: 0.0.0.0/0 ``` ```json title="Negative test num. 2 - json file" { "Resources": { "MyNACL": { "Properties": { "VpcId": "vpc-1122334455aabbccd", "Tags": [ { "Key": "Name", "Value": "NACLforSSHTraffic" } ] }, "Type": "AWS::EC2::NetworkAcl" }, "InboundRule": { "Type": "AWS::EC2::NetworkAclEntry", "Properties": { "RuleAction": "allow", "CidrBlock": "172.16.0.0/24", "PortRange": { "From": 22, "To": 22 }, "NetworkAclId": { "Ref": "MyNACL" }, "RuleNumber": 100, "Protocol": 6 } }, "OutboundRule": { "Type": "AWS::EC2::NetworkAclEntry", "Properties": { "NetworkAclId": { "Ref": "MyNACL" }, "RuleNumber": 100, "Protocol": -1, "Egress": true, "RuleAction": "allow", "CidrBlock": "0.0.0.0/0" } } } } ```
Project: Operator Framework (App Definition and Development / Application Definition & Image Build)
File: operator-sdk_generate.md

title: "operator-sdk generate" Invokes a specific generator The 'operator-sdk generate' command invokes a specific generator to generate code or manifests. ``` -h, --help help for generate ``` ``` --plugins strings plugin keys to be used for this subcommand execution --verbose Enable verbose logging ``` - - Generates bundle data for the operator - Contains subcommands that generate operator-framework kustomize data for the operator
Project: CockroachDB (App Definition and Development / Database)
File: 20160524_time_travel.md

Feature Name: Time Travel Queries Status: completed Start Date: 2016-05-07 Authors: Matt Jibson RFC PR: Issue PR: Add support for `AS OF SYSTEM TIME` to `SELECT` statements to execute queries at some past time. Plumb doing things at a timestamp to various layers that previously did not need it. adds support for time travel queries. Our most immediate need for them is to support backups at a certain timestamp. (Consider a huge table being backed up. We need to page through the data in a way that will be consistent if a connection drops and needs to be resumed from where it left off.) The syntax is: `SELECT * FROM t AS OF SYSTEM TIME '2016-01-01 00:00'`. The term `TIME` will be used below as the time travel time. SQL queries already create a KV transaction with a timestamp. Hooking up the `AS OF SYSTEM TIME` syntax to set the transaction timestamp is straightforward. This causes older data in the MVCC table to be fetched. There are other issues that need to be taken into account. Before a SELECT, a table lease is obtained to determine the schema. If the schema has changed after `TIME`, we need to instead fetch the old schema as well. Since the schemas are stored in the KV store, we can use the same technique (setting the KV transaction timestamp) to fetch the old data. Since this query is known to be readonly, it should not trigger a lease even if `TIME` is now and the schema is current. We just need the descriptor at `TIME`. MVCC currently garbage collects old data after 1 day. If data is requested at a time before the oldest value, the MVCC layer currently returns empty data (not an error). This will be changed to return an error instead of an empty value. The GC will be changed to keep any data required so that it can respond to read requests within the GC threshold. For example instead of removing data older than 1d, it will keep any data that was valid within 1d-ago, and discard the rest. The HLC advance itself to the KV timestamp if that timestamp is higher than any other time value it has seen. Since `TIME` sets the KV timestamp, this would effectively allow queries to advance the HLC of the system to any point on the future, which would cause problems. It will thus be an error to specify `TIME` greater than the value of `clusterlogicaltimestamp()`. Do we care about the read timestamp cache? Do we care if these statements abort other transactions? If we do care does the TODO about the 250ms from now offset solve it?
Project: StarRocks (App Definition and Development / Database)
File: sign.md

displayed_sidebar: "English" Returns the sign of `x`. A negative number, 0, or a positive number as input corresponds to `-1`, `0`, or `1` as output, respectively. ```Haskell SIGN(x); ``` `x`: supports the DOUBLE data type. Returns a value of the FLOAT data type. ```Plain mysql> select sign(3.14159); ++ | sign(3.14159) | ++ | 1 | ++ 1 row in set (0.02 sec) ```
Project: Meshery (Provisioning / Automation & Configuration)
File: telepresence.md

layout: integration title: Telepresence subtitle: Collaborative and visual infrastructure as code for Telepresence image: /assets/img/integrations/telepresence/icons/color/telepresence-color.svg permalink: extensibility/integrations/telepresence docURL: https://docs.meshery.io/extensibility/integrations/telepresence description: integrations-category: App Definition and Development integrations-subcategory: Application Definition & Image Build 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: KICS (Provisioning / Security & Compliance)
File: 845acfbe-3e10-4b8e-b656-3b404d36dfb2.md

title: Service Type is NodePort hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 845acfbe-3e10-4b8e-b656-3b404d36dfb2 Query name: Service Type is NodePort Platform: Kubernetes Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: Service type should not be NodePort<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="6" apiVersion: v1 kind: Service metadata: name: my-service spec: type: NodePort selector: app: MyApp ports: port: 80 targetPort: 80 nodePort: 30007 ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Service metadata: name: my-service spec: selector: app: MyApp ports: protocol: TCP port: 80 targetPort: 9376 clusterIP: 10.0.171.239 type: LoadBalancer status: loadBalancer: ingress: ip: 192.0.2.127 ```
Project: CockroachDB (App Definition and Development / Database)
File: 20150720_schema_gossip.md

Feature Name: schema_gossip Status: completed Start Date: 2015-07-20 RFC PR: Cockroach Issue: This RFC suggests implementing eventually-consistent replication of the SQL schema to all Cockroach nodes in a cluster using gossip. In order to support performant SQL queries, each gateway node must be able to address the data requested by the query. Today this requires the node to read `TableDescriptor`s from the KV map, which we believe (though we haven't measured) will cause a substantial performance hit which we can mitigate by actively gossiping the necessary metadata. The entire `keys.SystemConfigSpan` span will have its writes bifurcated into gossip (with a TTL TBD) in the same way that `storage.(*Replica).maybeGossipConfigs()` works today. The gossip system will provide atomicity in propagating these modifications through the usual sequence number mechanism. Complete propagation of new metadata will take at most `numHops * gossipInterval` where `numHops` is the maximum number of hops between any node and the publishing node, and `gossipInterval` is the maximum interval between sequential writes to the gossip network on a given node. On the read side, metadata reads' behaviour will change such that they will read from gossip rather than the KV store. This will require plumbing a closure or a reference to the `Gossip` instance down to the `sql.Planner` instance. This is slightly more complicated than the current implementation. Because the schema is eventually-consistent, how do we know when migrations are done? We'll have to count on the TTL, which feels a little dirty. We could augment the current implementation with some of: inconsistent reads time-bounded local caching This will be strictly less performant than the gossip approach but will be more optimal in memory as nodes will only cache schema information that they themselves need. Note that at the time of this writing every node will likely need all schema information due to the current uniform distribution of ranges to nodes. We could have a special metadata range which all nodes have a replica of. This would probably result in unacceptable read and write times and induce lots of network traffic. We could implement this on top of non-voting replicas (which we don't yet support). That would give us eventual consistency without having to go outside of raft, but enforcement of schema freshness remains an open question. How do we measure the performance gain? What should we set the TTL to?
Project: KICS (Provisioning / Security & Compliance)
File: 5572cc5e-1e4c-4113-92a6-7a8a3bd25e6d.md

title: Privilege Escalation Allowed hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 5572cc5e-1e4c-4113-92a6-7a8a3bd25e6d Query name: Privilege Escalation Allowed Platform: Kubernetes Severity: <span style="color:#bb2124">High</span> Category: Insecure Configurations URL: Containers should not run with allowPrivilegeEscalation in order to prevent them from gaining more privileges than their parent process<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="10 21" apiVersion: v1 kind: Pod metadata: name: pod2 spec: containers: name: app image: images.my-company.example/app:v4 securityContext: allowPrivilegeEscalation: true resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" name: log-aggregator image: images.my-company.example/log-aggregator:v6 securityContext: runAsUser: 2000 resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="9 13 17" apiVersion: v1 kind: Pod metadata: name: example-priv spec: containers: name: payment image: nginx securityContext: capabilities: drop: SYS_ADMIN name: payment2 image: nginx name: payment4 image: nginx securityContext: capabilities: add: NETBINDSERVICE name: payment3 image: nginx securityContext: allowPrivilegeEscalation: false ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: v1 kind: Pod metadata: name: pod1 spec: containers: name: app image: images.my-company.example/app:v4 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" name: log-aggregator image: images.my-company.example/log-aggregator:v6 securityContext: allowPrivilegeEscalation: false resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m" ```
Project: TiDB (App Definition and Development / Database)
File: COMPATIBILITY_TEST.md

We had some incompatibility issues in the past, which made BR cannot restore backed up data in some situations. So we need a test workflow to check the compatibility. Ensure backward compatibility for restoring data from the previous 3 minor versions This workflow needs previous backup data. To get this data. we perform the following steps Run a TiDB cluster with previous version. Run backup jobs with corresponding BR version, with different storages (s3, gcs). Given we test for the previous 3 versions, and there are 2 different storage systems, we will produce 6 backup archives for 6 separate compatibility tests. Start TiDB cluster with nightly version. Build BR binary with current directory. Use BR to restore different version backup data one by one. Make sure restore data is expected. Start a cluster with docker-compose and Build br with latest version. ```sh docker-compose -f docker-compose.yaml rm -s -v && \ docker-compose -f docker-compose.yaml build && \ docker-compose -f docker-compose.yaml up --remove-orphans ``` ```sh docker-compose -f docker-compose.yaml control make compatibility_test ```
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_cleanup_local-registry.md

title: "devspace cleanup local-registry --help" sidebar_label: devspace cleanup local-registry Deletes the local image registry ``` devspace cleanup local-registry [flags] ``` ``` Deletes the local image registry ``` ``` -h, --help help for local-registry ``` ``` --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems --kube-context string The kubernetes context to use --kubeconfig string The kubeconfig path to use -n, --namespace string The kubernetes namespace to use --no-colors Do not show color highlighting in log output. This avoids invisible output with different terminal background colors --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before --override-name string If specified will override the DevSpace project name provided in the devspace.yaml -p, --profile strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.5.0-rc-5g.md

layout: release date: 2022-03-27 tag: v0.5.0-rc-5g Fix: failing deployement of argo-rollout due to invalid name @Abhishek-kumar09 (#5272) Fix empty dependson @Revolyssup (#5271) Fix falsy error message in bash script @Revolyssup (#5246) [DDE] Failing build for UI @sudo-NithishKarthik (#5268) initial ui for DDE @warunicorn19 (#5265) [Fix] Use relative path for build files generated by react @sudo-NithishKarthik (#5261) ui-dde to ui @warunicorn19 (#5259) Correcting UI build @hershd23 (#5256) Bump minimist from 1.2.5 to 1.2.6 in /install/docker-desktop-extension/ui-dde @dependabot (#5253) [DDE] Reinitialize Extension @leecalcote (#5252) Reduces Dockerfile for DDE to only build dde-ui @hershd23 (#5251) Fixed routing to Lifecycle menu @MUzairS15 (#5276) [UI]Resolved ui bug of lagging side list Navs on hovering @Harshit-Dandriyal (#5275) [UI/RJSF] remove custom memoized i/p fields and use widgets instead @Abhishek-kumar09 (#5263) [UI] fixed meshery-ui not showing up after following make build-ui(Meshery docs) @Harshit-Dandriyal (#5237) [Chore] Security: vulnerability patches in dependencies @leecalcote (#5258) Bump minimist from 1.2.5 to 1.2.6 in /provider-ui @dependabot (#5254) Sanitize the pattern before validation for failing K8s components @Revolyssup (#5273) Fix: retrieve the cytoscape element Id from extenstion interface @Abhishek-kumar09 (#5248) [Chore] Reducing noise level of info log @leecalcote (#5257) [CI] Docker Desktop Extension: refactor for DDE build only @leecalcote (#5264) Bump minimist from 1.2.5 to 1.2.6 in /provider-ui @dependabot (#5254) [CI] Chore: remove make command for go1.16 @leecalcote (#5247) [Docs]Added top margin so that in-page anchor tags align with menu bar @Harshit-Dandriyal (#5266) [Docs] Promote oam REST endpoint from experimental @alceil (#5233) [Chore] Security: vulnerability patches in dependencies @leecalcote (#5258) [Chore] Security: vulnerability patches in dependencies @leecalcote (#5258) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @Harshit-Dandriyal, @MUzairS15, @Revolyssup, @alceil, @dependabot, @dependabot[bot], @hershd23, @l5io, @leecalcote, @sudo-NithishKarthik and @warunicorn19
Project: Trivy-Operator (Provisioning / Security & Compliance)
File: lens.md

provides the full situational awareness for everything that runs in Kubernetes. It's lowering the barrier of entry for people just getting started and radically improving productivity for people with more experience. Lens Extensions API is used to add custom visualizations and functionality to accelerate development workflows for all the technologies and services that integrate with Kubernetes. provides visibility into vulnerability assessment reports for Kubernetes workloads stored as custom resources.