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

In what area(s)?

/area actor runtime

What version of Dapr?

v1.6

Expected Behavior

See this doc issues that was raised dapr/docs#2184

This is to add more detail to the error message when you try to save and actor and the statestore has not been configured for actors. It would be good to provide and indic

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

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

We should add integration tests to make sure that skaffold doesn't break when these flags get passed without a value

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

Hi,

it would be nice, if pod annotations would be configurable via values file. E.g:

values.yaml:

.
.
.
podAnnotations: {}
.
.
.

statefulset.yaml:

  template:
    metadata:
      {{- with .Values.podAnnotations }}
      annotations:
        {{- . | toYaml | nindent 8 }}
      {{- end }}

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.