Kubernetes

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

What happened?

If you don't pass a --name argument to your etcd processes, they will all have the name default and the cluster will operate normally. However, when you add a member, the generated ETCD_INITIAL_CLUSTER variable will have multiple entries with the name "default". When this environment variable is used, etcd will parse these into a mapping under a single key ("defau

expected result:
example.com?param=abc -> will become example.com
example.com/?param=abc -> will stay example.com/

actual result:
example.com?param=abc -> become example.com
example.com/?param=abc -> stays example.com/?param=abc

overview

Today, the RequestRecorder records service RPC calls. If those take less than < 0ms, the recorder marks them as 0ms.

proposal

Make the RequestRecorder report the elapsed time for service calls that take less than < 0ms as decimal values, instead of 0.

notes

testing

If you take this on, I'd kindly advise to start in a TDD fashion. Write a test

It would be good to add an --audit flag to minikube logs that only shows the audit logs.

Currently, if you run minikube logs the audit logs are all the way at the top (after last start logs and such) which can be time consuming to scroll up to.

Example of that the audit logs look like:

==> Audit <==
|---------|---------------------|----------|--------------|---------|-----------

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.

这样很方便查看

I have a harbor server hosting my cilium chart with self-signed certificate. However, helm template seems to be doesn't respect the --insecure-skip-tls-verify

Commands

export HELM_EXPERIMENTAL_OCI=1
helm template oci://core.harbor.g4k.io/cilium-chart/cilium --version 1.9.13-eksa.2 --debug --insecure-skip-tls-verify --namespace kube-system -f -

Outputs

install.go:178: [debug] 

In the application details view, we list the ports an application deployment is listening on, but there is no "quick launch" or even a "copy" button..

We should add a "copy" button next to the port to copy to clipboard.

In what area(s)?

/area runtime

What version of Dapr?

All versions -- tested since 1.4.2.

Expected Behavior

The Dapr sidecar / daprd should not start when dapr-app-port and dapr-http-port are identical and return a meaningful error.

Actual Behavior

Dapr sidecar starts, but upon service invocation returns an error unrelated to the problem.

`{"errorCode":"ERR

What would you like to be added:

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

Is your feature request related to a problem? Please describe.
Logs are shown in UTC. IT is frustrating when trying to troubleshoot an issue and need to keep converting timestamps to determine which logs are relevant.

**Describe the sol

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

Scenario:

• Single vttablet, connecting to external MySQL (happens to be RDS Aurora, but I doubt it matters).
• Single unsharded keyspace (keyspace3), no vschema, with a single table, containing a single row
• Test program using the Python pymysql driver, using the CLIENT.FOUND_ROWS flag, and updating a single row to it's current key value (i.e. no rows are updated, but a single row

Discussed in verdaccio/verdaccio#2853