containers

What happened:

imagePullSecrets can added to a pod manifest to reference a secret containing registry cre

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

What Happened?

https://github.com/kubernetes/minikube/blob/9f96701d8f751d5dfce72f2fb762833f4c396747/pkg/minikube/registry/drvs/hyperv/hyperv.go#L94

Get-WmiObject is deprecated and has been superseded by [Get-CimInstance](https://docs.microsoft.com/en-us/powershell/mod

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 would you like to be added:

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

In what area(s)?

/area runtime

/area operator

/area placement

/area docs

/area test-and-release

Describe the proposal

In the context of apps with multiple instances (PODs in K8s):

In addition to support {uuid} for ConsumerID, we should

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

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.

You might have a compose file that doesn't reference the exact version of the container image you want to minified (e.g., the target service might reference the latest tag and you want to minify v1.2.3 for your target image).

The --target-compose-svc-image command parameter (for build and profile commands) should provide a way to use the desired image version without having to rewrite

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

Background:
The official Trivy images are labeled following the org.label-schema Label Schema. That schema has been deprecated in favor of the superseeding OCI image spec annotations.

The first tools rely on the org.opencontainers.image and ignore `

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.