containers

Which jobs are flaking?

we saw this in a sig-windows test today, blob:https://prow.k8s.io/789c15e1-3869-4a8a-b8ef-ef8394f5be0a

from this family

https://testgrid.k8s.io/sig-windows-1.22-release#aks-engine-windows-dockershim-1.22

Jul 10 02:49:49.489: INFO: Pod statscollectiontest-69785fa8-1d35-4253-a720-9c8acc39c08a-1 is Failed, but it's not controlled by a controller
Jul 1

Bug description

netdatacli has limit for output size of 4096

Expected behavior

do we just increase this limit or make it transfer arbitrary message sizes?

We already have some scripts in the scripts directory. It would be good to run them for every PR.
This is also a great task for beginners.

The files deploy/addons/aliyun_mirror.json and pkg/minikube/assets/addons.go should be updated to use the fully qualified image names docker.io/org/image instead of just org/image.

This should be done after https://github.

Pod tolerations number is sticked to the start of the line, causing text overflow.

The feature ask - expose Dapr runtime version in the Metadata API: https://docs.dapr.io/reference/api/metadata_api/

There are certain scenarios where apps would like to check that they are running within a tested Dapr version.

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

Implement WarmPool.RenderTerraform()

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

/kind feature
/area terraform
/lifecycle frozen

Need to have a global flag to control the console output mode (--json-output or something like that).

Actual behavior

It looks like running skaffold run fails when the docker socket isn't in the default location of /var/run/docker.sock. Even when setting the options in the skaffold.yaml to use useDockerCLI: true the build still fails.

Expected behavior

That the docker socket file location is can be anywhere when the options in the skaffold.yaml file are set to use the dock

currently we have a version selector for every git tag, which is unnecessary overhead on the user. It is not needed from documentation perspective as there aren't (shouldn't be) any docs change in patch versions, only for new/changed features.

before:
v0.27.0, v0.27.1, v0.27.2, v0.28.0
after
v0.27, v0.28

Now that we have the checklocks analyzer, we should annotate values that are lock-protected with an appropriate checklocks attribute.

Maybe new warnings after upgrading ErrorProne in #3355.

/home/runner/work/jib/jib/jib-core/src/main/java/com/google/cloud/tools/jib/image/json/JsonToImageTranslator.java:250: warning: [UnrecognisedJavadocTag] This Javadoc tag wasn't recognised by the parser. Is it malformed somehow, perhaps with mismatched braces?
58

59
   * Converts a map of volumes strings to a set of {@link Absolut

Hi

I assumed kaniko would work with an on-premise blob store using Azurite Blob Storage, but it looks like it's tied to the Cloud Azure Blob Storage domain name

Would it be difficult to support this? It should be the same API.