What would you like to be added:
I would like debug logging to show the heart of the processing of a patch request. For example, showing the inputs and outputs of https://github.com/kubernetes/apiserver/blob/fa3c8ad6d7aff4ba13bf7296583ed2815db1be44/pkg/endpoints/handlers/patch.go#L620 .

Why is this needed:

I'm using TLS on etcd 3.3.12 and have a mix of etcd proxies and masters. The proxies don't seem to honour the --cipher-suites setting, as it ends up with ECDHE-RSA-AES256-GCM-SHA384 despite --cipher-suites=TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 being set.

$ pgrep -laf /usr/bin/etcd
21968 /usr/bin/etcd --listen-client-urls https://0.0.0.0:4000 --adv

Do you want to request a feature or report a bug?

Documentation improvement

In digestAuth documentation, Kubernetes section does not contain any useful example explaining how to put credentials into a file. The given example is same as users(using base

Summary

Currently Kong supports writing configuration in a file, in YAML or JSON.
To provide a more flexible configuration, especially for those running Kong in different environments (dev, staging, production), an option to write configuration in lua can be very useful.

Additional Details

There are many use-cases that come to mind:

• Using environment variables inside the d

Currently at 66.1%.

Sorry in advance but the issue template really does not apply at all to my issue.

Abstract

When using the none driver in a linux environment I get issues with PVCs after restarting. This is due to the /tmp directory being a tmpfs filesystem.

Details

Many mainstream linux distributions adopted systemd as the init system quite a while ago, and under this system, the /tmp director

Given the stable and incubator support plan and Deprecation Timeline, the community (chart OWNERS, organizations, groups or individuals who want to host charts) are moving charts to new Helm repos, and will list these new repos on the [Helm Hub]

Some documentation could be improved by adding some options to runsc spec to allow users to specify the command and some other common OCI options. This could also improve the getting started experience for folks who are kicking the tires with runsc.

I'm thinking of the following options:

• Option to specify the command
• Option to specify working directory
• Option to specify network names

Expected behavior

Before Skaffold supported parallel local builds, we used profiles for that matter, building profiles concurrently.
That allows us to stream build log for each profile (one profile per image) to file named like {LOGS_DIR}/build/{PROFILE_NAME}.log.

Is your feature request related to a problem? Please describe.
Because manipulating kubernetes often requires changing configmap and/or secrets, it is fair to presume that one would use the create/edit feature to enter sensitive informatio