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

Bug description

netdatacli has limit for output size of 4096

Expected behavior

do we just increase this limit or make it transfer arbitrary message sizes?

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.

We should add a GitHub maintainer field to the addons (below):
https://github.com/kubernetes/minikube/blob/044fe4c1fd2779b5ac3e4974556c3ff7b4d26792/pkg/minikube/assets/addons.go#L37-L47

An empty field should be added for each addon, and for each addon that has an empty field, when the user tries to enable the addon it should give a warning to the user that there's not a verified maintainer for

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

The feature ask - expose Dapr runtime version in the Metadata API: https://docs.dapr.io/reference/api/metadata_api/

There are certain scenarios where apps would like to check that they are running within a tested Dapr version.

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

Background

Currently, as per the doc:

... The profile is auto-activated if any one of the activations are triggered.

In my case, we have different profiles for different environments and tenants. Say, we have the following

• Environments: ENV=stag and ENV=prod
• Tenants: ORG=us and ORG=eu

meaning we hav

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.