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 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 <==
|---------|---------------------|----------|--------------|---------|-----------

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] 

Feature Suggestion

Backstage maintainers should actively keep their core packages up-to-date. If upgrades are left ignored for months, the updates can be really painful with all the

Requirement - what kind of business use case are you trying to solve?

Actual the windows executables (jaeger-agent.exe, jaeger-collector.exe, ...) don't have a version set. It is hard to identify the current used version and check if the actual used version is outdated.

Probl

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

Summary

We could add a beacon endpoint that could by the UI to track usage of the UI

<TrackEvent event='viewNodeSummary'/>

This just makes a HTTP request to /api/v1/collect?t=trackEvent&event=viewNodeSummary, similar to:

https://developers.google.com/analytics/devguides/collection/protocol/v1/reference

This event could be logged, with the SSO subject/email so Splunk

The idea originated from this comment, see for full context thanos-io/thanos#4908 (comment)

Basically, we could improve the user experience by providing more information on how the stores are being queried, beyond providing just min / max time or just showing that the min / max time is not available, which does not in fact tell users if that store will be que

Add a network option in creating workload

like rancher‘s Networking tab

** During workload creation, user can customize own hosts and DNS search doma

Description

• If the backend response is missing "Content-Type" header , try to perform MIME sniffing and fix the response header.

Reference

• http://mimesniff.spec.whatwg.org/
• https://github.com/bfenetworks/bfe/blob/develop/bfe_http/sniff.go

Now the helm is related in build, let's move it to root dir.

kubeedge/build/helm -> kubeedge/helm

The library controller-runtime requires setting a logger (by log.SetLogger()) at the first 30s when the application starts, or it would use the default NullLogSink. We should also call it in testing codes.

When we test with ginkgo, ginkgo provides a helpful GinkgoWriter, which hides the output as default, only prints it when the test failed. We'd better use it to keep our testing output

Spent the morning debugging what I thought was a goroutine leak, but turned out to be just a huge number of goroutines being created in a short period of time. However, it seems a lot of the unit tests do leak goroutines. Most of these might just be issues with tests not cleaning up properly, but it makes testing/debugging real leaks quite difficult. Or in my case, the leaks were a red herring - t

Describe the bug
certain pods are missing "standard" labels which are useful for certain scenarios:

app.kubernetes.io/name
app.kubernetes.io/instance

To Reproduce
Steps to reproduce the behaviour:

1. Deploy longhorn
2. Check labels

default labels are missing on:

all csi-.* pods
engine-image
instance-manager
longhorn-csi-plugin

Expected behavior
app.kubernetes.io

Is your feature request related to a problem? Please describe.

There are KubeAPI and MongoDB database drivers, some users want to use Mysql.

Describe the solution you'd like

https://github.com/oam-dev/kubevela/blob/master/pkg/apiserver/datastore/datastore.go#L142

Here define a database interface, you only need to implement it for Mysql.

Additional context

Exist data