containers

Nowadays, when the kube-scheduler is initialized, the provided component config (via --config flag) is logged. E.g.

I0404 08:35:16.471898       1 configfile.go:96] Using component config
-------------------------Configuration File Contents Start Here---------------------- 
apiVersion: kubescheduler.config.k8s.io/v1beta3
clientConnection:
  acceptContentTypes: ""
  burst: 100
  conten

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

It would be good to add an --audit flag to minikube logs that only shows the audit logs.

Currently, if you run minikube logs the audit logs are all the way at the top (after last start logs and such) which can be time consuming to scroll up to.

Example of that the audit logs look like:

==> Audit <==
|---------|---------------------|----------|--------------|---------|-----------

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.

In what area(s)?

/area runtime

What version of Dapr?

All versions -- tested since 1.4.2.

Expected Behavior

The Dapr sidecar / daprd should not start when dapr-app-port and dapr-http-port are identical and return a meaningful error.

Actual Behavior

Dapr sidecar starts, but upon service invocation returns an error unrelated to the problem.

`{"errorCode":"ERR

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

Description

Podman uses Dockerfile as well as Containerfile as filenames for the container build (ref), but at the moment, trivy does not detect Containerfile as a valid config file to be analyzed.

Since the same syntax is used for the image building, it would be interesting to add Containerfile as a "synonym" of `Docker

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.