containers

There is a strong and growing consensus in sig-node about the need of increasing the test coverage in the kubelet, improving the current testsuite about coverage and reliability. See for example the April 26 sig-node meeting notes and the [April 27 sig-node CI subgroup meeting notes](http

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

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.

What Happened?

if you have 3 clusters and you make one of them active
all minikube commands will run against that cluster,

$ minikube profile p1
✅  minikube profile was successfully set to p1
15:16:37 medya
$ minikube status
p1
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured

this should be reflected in the minikube profile l

In what area(s)?

/area runtime

What version of Dapr?

dapr --version
CLI version: 1.7.0
Runtime version: 1.7.0

Expected Behavior

API methods to be logged without any errors

Actual Behavior

When I start my dapr actor host application like this:

dapr run --app-id myapp --app-port 5000 --dapr-http-port 3500 --log-level debug --enable-api-logging -- dotnet run

What would you like to be added:

• a function (checkbox?) to use the helm switc

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).

It should be more clear for users (and people trying to offer support by looking at logs!) which kube-context and cluster is being used.

$ skaffold dev
Listing files to watch...
 - skaffold-example
Generating tags...
 - skaffold-example -> skaffold-example:v1.34.0-60-gef8185519
Checking cache...
 - skaffold-example: Not found. Building
Starting build...
Building [skaffold-example]...

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, when will Ubuntu 22.04 be supported for APT?

Attempting to install on Jammy using APT shows an error:

E: The repository 'https://aquasecurity.github.io/trivy-repo/deb jammy Release' does not have a Release file.

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.