containers

Presumably this would occur when changing the default from one class to another. E.g.

• Class X exists and is marked default
• Class Y is created
• Class Y is marked as default
• Uh oh!! 2 defaults
• Class X is marked as not default

At the case in point, when there are 2 defaults, we currently do not assign default values to new PVCs.

We should change this semantic - while there a

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.

Related kubernetes/minikube#14257

This isn't currently supported, the flag was put in for future proofing to make it easier if we do implement it.

If the user tries to use the flag we should output a message to the user saying the flag is not yet supported and the flag value should be ignored.

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

In what area(s)?

/area runtime

/area operator

/area placement

/area docs

/area test-and-release

Describe the proposal

Today, a PR can break perf tests without maintainers being aware. Running /ok-to-pe

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

How can I pass the --clear-cache argument to the buildpacks in skaffold.yaml ?

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

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

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.