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

Many people store configuration files in toml format and it will be useful to add support for this format

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.

Describe the bug
nacos面板新建配置页面 配置内容输入框长度异常 只有一条黑色的线并不是正常的输入框

Expected behavior
新建配置页面的 配置内容旁边应该是一个输入框 而不是一条黑线

Acutally behavior
我想要新建配置

How to Reproduce
Steps to reproduce the behavior:

1. 打开控制面板 使用默认账号登入
2. 在配置列表点击加号 进入新建配置页面
3. 看见异常

Desktop (please complete the following information):

• OS: windows10
• Version nacos-server 1.4.3
• Module config
• SD

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?

dapr --version
CLI version: 1.7.0
Runtime version: 1.7.0

Expected Behavior

API methods to be logged without any errors

Actual Behavior

When I start my dapr actor host application like this:

dapr run --app-id myapp --app-port 5000 --dapr-http-port 3500 --log-level debug --enable-api-logging -- dotnet run

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

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