cwielenb/CNCF-Dataset huggingface dataset:
Project: SRPC (Orchestration & Management / Remote Procedure Call)
File: CODE_OF_CONDUCT.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the project or its community in public spaces. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at liyingxin@sogou-inc.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the projects leadership. This Code of Conduct is adapted from the , version 1.4, available at
Project: Fluid (Orchestration & Management / Scheduling & Orchestration)
File: s3_configuration.md

If AWS S3 is selected as the underlying storage system of Alluxio, additional configuration is required for Alluxio to properly access the mounted S3 storage system. This document shows how to do the special configuration required for Alluxio in Fluid in a declarative manner. For more information, see . The S3 bucket has been configured and the AWS certificate that has permission to access the bucket. Please refer to the to complete the installation. For security, Fluid recommends using Secret to configure sensitive information such as`aws.accessKeyId` and `aws.secretKey`For more information about Secret's use in Fluid, see Create Dataset Resource Object ```yaml $ cat << EOF > dataset.yaml apiVersion: data.fluid.io/v1alpha1 kind: Dataset metadata: name: my-s3 spec: mounts: mountPoint: s3://<bucket-name>/<path-to-data>/ name: s3 options: alluxio.underfs.s3.region: <s3-bucket-region> alluxio.underfs.s3.endpoint: <s3-endpoint> encryptOptions: name: aws.accessKeyId valueFrom: secretKeyRef: name: mysecret key: aws.accessKeyId name: aws.secretKey valueFrom: secretKeyRef: name: mysecret key: aws.secretKey EOF ``` Note: For object storage of different cloud vendors, the region configuration must be replaced with`alluxio.underfs.s3.endpoint.region=<S3ENDPOINTREGION>`,For details, see ``` $ kubectl create -f dataset.yaml ``` Create Secret In the Secret to be created, specify the sensitive information that needs to be configured when the Dataset is created above. ```yaml $ cat<<EOF >mysecret.yaml apiVersion: v1 kind: Secret metadata: name: mysecret stringData: aws.accessKeyId: <AWSACESSKEY_ID> aws.secretKey: <AWSSECRETKEY> EOF ``` Create AlluxioRuntime Resource Object ```yaml $ cat << EOF > runtime.yaml apiVersion: data.fluid.io/v1alpha1 kind: AlluxioRuntime metadata: name: my-s3 spec: ... EOF ``` ``` $ kubectl create -f runtime.yaml ``` The bucket specified in 'dataset.yaml' will be mounted to the '/s3' directory in Alluxio.
Project: gRPC (Orchestration & Management / Remote Procedure Call)
File: README-CFSTREAM.md

](https://cocoapods.org/pods/gRPC) gRPC now provides the option to use Apple's CFStream API (rather than TCP sockets) for networking. Using CFStream resolves a bunch of network connectivity transition issues (see the for more information). 
CFStream integration is now in experimental state. You will need explicit opt-in to use it to get the benefits of resolving the issues above. We expect to make CFStream the default networking interface that gRPC uses when it is ready for production.
 As of v1.21.0, CFStream integration is now the default networking stack being used by gRPC Objective-C on iOS layer. You get to use it automatically without special configuration needed. See below on how to disable CFStream in case of problem. As of v1.23.0, CFStream is enabled by default on iOS for all wrapped languages. See below on how to disable CFStream in case of a problem. If you use gRPC on iOS, CFStream is on automatically. If you use it on other platforms, you can turn it on with macro `GRPC_CFSTREAM=1` for the pod 'gRPC-Core' and 'gRPC'. In case of problem and you want to disable CFStream on iOS, you can set environment variable "grpc\_cfstream=0". It is known to us that the CFStream API has some bug (FB6162039) which will cause gRPC's CFStream networking layer to stall occasionally. The issue mostly occur on MacOS systems (including iOS simulators on MacOS); iOS may be affected too but we have not seen issue there. gRPC provides a workaround to this problem with an alternative poller based on CFRunLoop. The poller can be enabled by setting environment variable `GRPCCFSTREAMRUN_LOOP=1`. Note that the poller is a client side only poller that does not support running a server on it. That means if an app opts in to the CFRunLoop-based poller, the app cannot host a gRPC server (gRPC Objective-C does not support running a server but other languages running on iOS do support it). Currently we do not support platforms other than iOS, although it is likely that this integration can run on MacOS targets with Apple's compiler. Let us know if you meet any issue by filing issue and ping @stanleycheung.
Project: Traefik Mesh (Orchestration & Management / Service Mesh)
File: submitting-issues.md

title: "Submitting Issues in Traefik Mesh" description: "This documentation article describes the process of sorting and checking issues in Traefik Mesh." We use the to keep track of Traefik Mesh issues. The process of sorting and checking the issues requires a lot of work. To save us some time and get quicker feedback, be sure to follow the guidelines below. !!! Important "Getting Help" The issue tracker is not a general support forum, but a place to report bugs and asks for new features. For end-user related support questions, use the . The title must be short and descriptive. (~60 characters) Follow the as much as possible. Explain in which context you encountered the issue. Remain clear and concise. Take time to polish the format of your message so we'll enjoy reading it and working on it. Help the readers focus on what matters, and help them understand the structure of your message (see the ). Remember, when asking for new features, they must be useful to the majority (and not only useful in edge case scenarios, or hack-like setups). Do your best to explain what you're looking for, and why it would improve Traefik Mesh for everyone. Traefik Mesh maintainers/users are not all native English speakers, so if you sometimes feel that some messages sound rude, remember that it's probably a language barrier problem from someone willing to help you.
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_proxy_logs.md

title: "glooctl proxy logs" weight: 5 dump Envoy logs from one of the proxy instancesNote: this will enable verbose logging on Envoy ``` glooctl proxy logs [flags] ``` ``` -d, --debug enable debug logging on the proxy as part of this command (default true) -f, --follow enable debug logging on the proxy as part of this command -h, --help help for logs ``` ``` -c, --config string set the path to the glooctl config file (default "<home_directory>/.gloo/glooctl-config.yaml") --consul-address string address of the Consul server. Use with --use-consul (default "127.0.0.1:8500") --consul-allow-stale-reads Allows reading using Consul's stale consistency mode. --consul-datacenter string Datacenter to use. If not provided, the default agent datacenter is used. Use with --use-consul --consul-root-key string key prefix for for Consul key-value storage. (default "gloo") --consul-scheme string URI scheme for the Consul server. Use with --use-consul (default "http") --consul-token string Token is used to provide a per-request ACL token which overrides the agent's default token. Use with --use-consul -i, --interactive use interactive mode --kube-context string kube context to use when interacting with kubernetes --kubeconfig string kubeconfig to use, if not standard one --name string the name of the proxy service/deployment to use (default "gateway-proxy") -n, --namespace string namespace for reading or writing resources (default "gloo-system") --port string the name of the service port to connect to (default "http") --use-consul use Consul Key-Value storage as the backend for reading and writing config (VirtualServices, Upstreams, and Proxies) ``` - interact with proxy instances managed by Gloo
Project: Avro (Orchestration & Management / Remote Procedure Call)
File: avro-1.11.3-released.md

title: "Avro 1.11.3" linkTitle: "Avro 1.11.3" date: 2023-09-22 <!-- 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 https://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. --> The Apache Avro community is pleased to announce the release of Avro 1.11.3! All signed release artifacts, signatures and verification instructions can be found <a href="{{< relref "/project/download" >}}">here</a> This release . Java : Comparing maps in GenericData is wrong for certain combinations and fails for empty maps : Thread scalability problem with the use of SynchronizedMap : Protocol namespace not parsed correctly if protocol is defined by full name : Allow having Error in a Record : Rationalize the system properties that limit allocation Python : Rationalize the system properties that limit allocation : Generate documentation for Python with Sphinx Rust : Support local-timestamp logical types for the Rust SDK : Validate default value for record fields and enums on parsing : Record field doesn't accept default value if field type is union and the type of default value is pre-defined name : Race condition can happen among serde tests : Replace regex crate with regex-lite : Disallow invalid namespaces for the Rust binding : Get rid of byteorder and zerocopy dependencies : Handle namespace properly if a name starts with dot : Disallow duplicate field names : Deserialization fails to use default if an enum in a record in a union is given an unknown symbol : Deserialization results in FindUnionVariant error if the writer and reader have the same symbol but at different positions In addition: Upgrade dependencies to latest versions, including CVE fixes. Testing and build improvements. Performance fixes, other bug fixes, better documentation and more. Known issues: C#: https://www.nuget.org/packages/Apache.Avro/1.11.3 Java: https://repo1.maven.org/maven2/org/apache/avro/avro/1.11.3/ Javascript: https://www.npmjs.com/package/avro-js/v/1.11.3 Perl: https://metacpan.org/release/Avro Python 3: https://pypi.org/project/avro/1.11.3 Ruby: https://rubygems.org/gems/avro/versions/1.11.3 Rust: https://crates.io/crates/apache-avro/0.16.0 Thanks to everyone for contributing!
Project: Contour (Orchestration & Management / Service Proxy)
File: CHANGELOG-v1.26.2.md

We are delighted to present version v1.26.2 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters. Updates Envoy to v1.27.3. See the release notes for v1.27.3 . For a fresh install of Contour, consult the . To upgrade an existing Contour installation, please consult the . Contour v1.26.2 is tested against Kubernetes 1.26 through 1.28. If you're using Contour and want to add your organization to our adopters list, please visit this . If you prefer to keep your organization name anonymous but still give us feedback into your usage and scenarios for Contour, please post on this .
Project: MetalLB (Orchestration & Management / Service Proxy)
File: example.md

title: Full example weight: 10 As an example of how to use all of MetalLB's options, consider an ecommerce site that runs a production environment and multiple developer sandboxes side by side. The production environment needs public IP addresses, but the sandboxes can use private IP space, routed to the developer offices through a VPN. Additionally, because the production IPs end up hardcoded in various places (DNS, security scans for regulatory compliance...), we want specific services to have specific addresses in production. On the other hand, sandboxes come and go as developers bring up and tear down environments, so we don't want to manage assignments by hand. We can translate these requirements into MetalLB. First, we define two address pools, and set BGP attributes to control the visibility of each set of addresses: ```yaml apiVersion: metallb.io/v1beta1 kind: IPAddressPool metadata: name: production namespace: metallb-system spec: addresses: 42.176.25.64/30 ``` ```yaml apiVersion: metallb.io/v1beta1 kind: IPAddressPool metadata: name: sandbox namespace: metallb-system spec: addresses: 192.168.144.0/20 ``` Then we advertise them, and set BGP attributes to control the visibility of each set of addresses: ```yaml apiVersion: metallb.io/v1beta1 kind: BGPAdvertisement metadata: name: external namespace: metallb-system spec: ipAddressPools: production ``` ```yaml apiVersion: metallb.io/v1beta1 kind: BGPAdvertisement metadata: name: local namespace: metallb-system spec: ipAddressPools: sandbox communities: vpn-only ``` ```yaml apiVersion: metallb.io/v1beta1 kind: Community metadata: name: communities namespace: metallb-system spec: communities: name: vpn-only value: 1234:1 ``` In our Helm charts for sandboxes, we tag all services with the annotation `metallb.universe.tf/address-pool: sandbox`. Now, whenever developers spin up a sandbox, it'll come up on some IP address within 192.168.144.0/20. For production, we set `spec.loadBalancerIP` to the exact IP address that we want for each service. MetalLB will check that it makes sense given its configuration, but otherwise will do exactly as it's told.
Project: KubeBrain (Orchestration & Management / Coordination & Service Discovery)
File: benchmark.md

Tests are carried out using physical machines of the following | Hardware | Properties | |-|| | CPU | Intel(R) Xeon(R) Gold 5118 CPU @ 2.30GHz | | MEM | 187 GB | | DISK | 2TB SSD | | NET | 10 Gbps | 3-node "etcd" cluster: Use 3-node "KubeBrain" cluster, "TiKV" uses "TiUP" to deploy "3 PD + 3 KV" cluster. "KubeBrain", "PD", "KV" are mixed deployed. In the test case, the Key's length is fixed at 70 Bytes, generated with a "fixed prefix + random suffix". The Value is a randomly generated 512 Bytes, with a concurrent output load of 300 etcd clients. Each test case is executed 3 times. "KubeBrain on TiKV" can outperform "etcd" in read and write performance, while deletion performance needs to be further optimized. However, the actual load of "Kubernetes" storage has a low percentage of deletion operations, and the overall performance can be greater than "etcd". Moreover, "etcd" will have some performance degradation with usage, while "TiKV" can be horizontally scaled to achieve better performance.
Project: MetalLB (Orchestration & Management / Service Proxy)
File: imageeffects.en.md

+++ title = "Image Effects" weight = 5 +++ The theme supports non-standard . | Name | Description | | -- | -- | | border | Draws a light thin border around the image | | lazy | Lets the image be lazy loaded | | lightbox | The image will be clickable to show it enlarged | | shadow | Draws a shadow around the image to make it appear hovered/glowing | As , you can add this to the URL query parameter, but this may be cumbersome to be done consistently for the whole page. Instead, you can configure the defaults in your `hugo.toml` aswell as overriding these default in the pages frontmatter. Explicitly set URL query parameter will override the defaults in effect for a page. Without any settings in your `hugo.toml` this defaults to {{< multiconfig file=hugo >}} [params] [params.imageEffects] border = false lazy = true lightbox = true shadow = false {{< /multiconfig >}} This can be overridden in a pages frontmatter by eg. {{< multiconfig fm=true >}} [imageEffects] border = true {{< /multiconfig >}} Or by explicitly override settings by URL query parameter ````md {title="URL"} ```` The settings applied to the above image would be {{< multiconfig >}} border = true lazy = true lightbox = false shadow = false bg-white = true {{< /multiconfig >}} This ends up in the following HTML where the parameter are converted to CSS classes. ````html {title="HTML"} <img src="https://octodex.github.com/images/minion.png?lightbox=false&bg-white=true" loading="lazy" alt="Minion" class="bg-white border lazy nolightbox noshadow"> ```` As you can see in the above example, the `bg-white` parameter is not initially supported in the themes default settings. Nevertheless you are free to define arbitrary parameter by just adding them to the URL query parameter or set them in your `hugo.toml` or pages frontmatter. {{% notice note %}} If no extended parameter like `bg-white` in the example is set on the URL, a `class="nobg-white"` in the HTML will only be generated if a default value was set in the `hugo.toml` or pages frontmatter. {{% /notice %}}
Project: Open Cluster Management (Orchestration & Management / Scheduling & Orchestration)
File: CHANGELOG-v0.6.md

Add API AddOnPlacementScore. ( ) Support taint & toleration. ( ) Add status feedback fields to work api. ( ) Add detached mode spec fields in clusterManager ( ) Add detached deploy mode for klusterlet ( ) Add HealthCheck spec to managedclusteraddon ( ) Add const ScoreCoordinate type. ( ) Addon observed generation in managedclusteraddon api. ( ) Add PlacementConditionMisconfigured. ( ) Update docs for cluster join process. ( ) Set managedcluster leaseduration seconds value with 60. ( ) Bump the go version to 1.17. ( ) Fixed issue #112 separated types.go. ( ) Update validation rule of taint.timeAdded. ( ) Make timeAdded of taint nullable. ( ) Update fedora version to 34. ( ) Update securitymd to refer to the OCM community security md file. ( ) Upgrade CONTROLLERGENVERSION to v0.6.0. ( ) Fix ci verify. ( ) Change default value of deleteOption. ( ) Bugfix: health check mode empty. ( ) N/A
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_proxy_url.md

title: "glooctl proxy url" weight: 5 print the http endpoint for a proxy Use this command to view the HTTP URL of a Proxy reachable from outside the cluster. You can connect to this address from a host on the same network (such as the host machine, in the case of minikube/minishift). ``` glooctl proxy url [flags] ``` ``` -h, --help help for url -l, --local-cluster use when the target kubernetes cluster is running locally, e.g. in minikube or minishift. this will default to true if LoadBalanced services are not assigned external IPs by your cluster -p, --local-cluster-name string name of the locally running minikube cluster. (default "minikube") ``` ``` -c, --config string set the path to the glooctl config file (default "<home_directory>/.gloo/glooctl-config.yaml") --consul-address string address of the Consul server. Use with --use-consul (default "127.0.0.1:8500") --consul-allow-stale-reads Allows reading using Consul's stale consistency mode. --consul-datacenter string Datacenter to use. If not provided, the default agent datacenter is used. Use with --use-consul --consul-root-key string key prefix for for Consul key-value storage. (default "gloo") --consul-scheme string URI scheme for the Consul server. Use with --use-consul (default "http") --consul-token string Token is used to provide a per-request ACL token which overrides the agent's default token. Use with --use-consul -i, --interactive use interactive mode --kube-context string kube context to use when interacting with kubernetes --kubeconfig string kubeconfig to use, if not standard one --name string the name of the proxy service/deployment to use (default "gateway-proxy") -n, --namespace string namespace for reading or writing resources (default "gloo-system") --port string the name of the service port to connect to (default "http") --use-consul use Consul Key-Value storage as the backend for reading and writing config (VirtualServices, Upstreams, and Proxies) ``` - interact with proxy instances managed by Gloo