When we first added SCTP tests, we thought that we weren't going to be able to do actual tests of SCTP network connectivity within kubernetes CI, so we came up with a plan involving a split between tests that involve actual SCTP network connectivity (which require the SCTP kernel module to be available) and tests that don't do SCTP network traffic and so can run anywhere. That way we could still t

Feature idea summary

Cgroups plugin supports only proportional and max Block IO policies. We should support BFQ scheduler as well. Disk stats for the scheduler are in blkio.bfq.io_service_bytes and blkio.bfq.io_serviced files.

It is mentioned that there is an error code page for v2 protocol:
https://github.com/etcd-io/etcd/blob/ae7862e8bc8007eb396099db4e0e04ac026c8df5/server/etcdserver/api/v2error/error.go#L16

However, I can't find Documentation/v2/errorcode.md in this repo. Is the comment stale?

Next line returns 200 as status https://github.com/Kong/kong/blob/c817fada7a514d84f6e0aab7461605c71bf3a841/kong/plugins/cors/handler.lua#L13

Internet says it should return 204:

• https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request
• https://docs.microsoft.com/en-us/aspnet/core/security/cors?view=aspnetcore-3.1#preflight-requests

Internet changed its mind since 2018 https://

The environment file is missing:

● minikube-scheduled-stop.service - m/var/lib/minikube/scheduled-stop/environmentinikube scheduled stop
     Loaded: loaded (/lib/systemd/system/minikube-scheduled-stop.service; enabled; vendor preset: enabled)
     Active: failed (Result: resources)

Dec 05 16:01:44 docker systemd[1]: minikube-scheduled-stop.service: Failed to load environment files: N

Move all Dockerfile samples to non-root user

Expected Behaviour

As an OpenFaaS end-user, I want to run all samples on my OpenFaaS cluster, even with the new non-root feature enabled.

Current Behaviour

Helm documentation states the following:
-1) (k8s) metadata.name is restricted to a maximum length of 63 characters because of limitations to the DNS system
-2) For that reasons, release names are (DNS labels that are) limited to 53 characters

Statement 1) is not correct.
k8s does not impose a max length of 63 characters on resource names.
The actual max length for a resource name is 253 c

Describe the bug
In the naming module, ServiceController's "create" method has an optional

1. Describe IN DETAIL the feature/behavior/change you would like to see.

Using AWS GovCloud is a bit different from the regular AWS.
https://github.com/kubernetes/kops/blob/master/docs/getting_started/aws.md

2. Feel free to provide a design supporting your feature request.

Kops v1.18.2 improves the support for AWS GovCloud and should work without any additional tweaks, except for

Problem Statement

There are users who would like to secure the http port exported by the vitess servers with TLS. However, some of the health check and monitoring URLs (like /debug/vars) still need to be accessed without TLS. For example, Kubernetes prefers the health check URLs to not require TLS.

We require the ability to specify a separate (optional) TLS http port, and the ability to s

https://github.com/verdaccio/monorepo/blob/9.x/core/types/index.d.ts defines

type AuthAccessCallback = (error: string | null, access: boolean) => void;

interface IPluginAuth<T> extends IPlugin<T> {
  authenticate(user: string, password: string, cb: AuthCallback): void;
  adduser?(user: string, password: string, cb: AuthCallback): void;
  changePassword?(user: string, password: stri

Currently validating checksums requires lots of knowledge on the part of the caller. We should expose optional checksum validation in our existing validation functions e.g. IPv4.IsValid.

header.UDP and header.TCP don't currently have these functions; we should add them.

https://github.com/GoogleContainerTools/skaffold/blob/331da68e249ff6db83038f64513da33fd944ecd5/pkg/skaffold/runner/deploy.go#L160

My preference would be for it to say "5.2 seconds" since 0.1 sec is enough precision for this step. I don't care if it switches to stuff like "821 milliseconds" for short times.

Describe the bug
See screenshot. Should be don't not don't

To Reproduce
Steps to reproduce the behavior:

1. Install latest 4.0 windows client
2. Add cluster
3. Go to cluster settings
4. Read text for "accessible Napespaces"

Expected behavior
Escaped cor

What would you like to be added:
Support for deploying vSphere storage Container Storage Interface (CSI).
It' GA already.

https://github.com/kubernetes-sigs/vsphere-csi-driver
https://cloud-provider-vsphere.sigs.k8s.io/

It requires vSphere 6.7u3+

Why is this needed:

• The in-tree cloud provider for vSphere is deprecated.
• The CSI is the standard way to implement the Storage

Every kubeflow image should be scanned for security vulnerabilities.
It would be great to have a periodic security report.
Each of these images with vulnerability should be patched and updated.