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

It's not possible to enable addons with --no-kubernetes passed because the addons in their current state are deployed to Kubernetes. So if a user tries to enable an addon with --no-kubernetes output a message notifying them that it's not possible without Kubernetes and exit execution.

Related kubernetes/minikube#13461

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.

Dapr suddenly appeared inaccessible, check the debug logs found that it is due to the deployment of the selector property change, dapr service is not updated caused

time="2022-02-23T14:51:58.728682736Z" level=debug msg="retry count: 3, grpc call failed, ns: dev, addr: melan

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

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.

We need a flag (compose-svc-start-wait ) to control how long docker-slim should wait before starting each service when there's a compose file (build, profile, run commands though the run command doesn't have support for compose yet).

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

Container scanning schemas below 14.0.0 have been deprecated.

blob/main/contrib/gitlab.tpl:3 is using a deprecated version:

"version": "2.3",

The latest version of the schema is [14.1.0](https://gitlab.com/gitlab-org/gitla

At the moment the directory /kaniko is hard coded in constants.go as

KanikoDir = "/kaniko"

kaniko stores snapshots in this directory. this is a problem, if the volume storage is limited in the build environment. we use gitlab-ci in a k8s environment and connect the default /builds directory to a ephemeral volume, so when running a ci job, the build directory has >10GB storage