Kubernetes

https://github.com/kubernetes/kubernetes/blob/5bafc8306a7b622e292746aec8a9e9212b755071/staging/src/k8s.io/apimachinery/pkg/runtime/serializer/versioning/versioning.go#L225

I0225 16:19:15.424936 1416311 versioning.go:225] a memory allocator was provided but the encoder %!T(MISSING) doesn't implement the runtime.EncoderWithAllocator, using regular encoder.Encode method

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?

Not really a bug, but maybe unexpected behavior. Since etcdctl del accepts an optional second parameter which deletes all keys in a range, these are very easy mistakes to make:

# Oh no, there was a space in the key I copied!
etcdctl del /registry/persistentvolumes/pvc-eef4ec4b-326d-47e6- f11c-6474a5fd4d89
# <deletes thousands of keys>

etcdctl put 'key s

Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

2.5.1.0

Current Behavior

When calling kong.response.exit(), the function automatically sets the Content-Length header on the response even if the Transfer-Encoding header is present. This is in violation of RFC 7230 3.3.2:

A sender MUST NOT send a Content-

Overview

I think it's time to start iterating on hashicorp/consul#11536 . Since, I've gathered some feedback from folks that we can implement.

Suggestions

Let's look at an errored check:

PR seems to modify metrics behavior. It seems no tests or test behavior has been modified.
Please update the PR with any relevant updated testing or add a pr/no-m

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.

Noticed in chartmuseum test failure:

Pushing binaries to Azure
ERROR: The specified blob already exists.
...
ErrorCode:BlobAlreadyExists
If you want to overwrite the existing one, please add --overwrite in your command.

Chartmuseum copies script from Helm to upload canary artifacts.

In this script we need to add an --overwrite flag to az storage blob upload-batch:
https:/

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.

Today, Dapr supports unix domain sockets on self-hosted mode only. We should add a dapr.io/unix-domain-socket-path or similar annotation on Kubernetes and mount a volume (if possible; if not, instruct users to do so in the deployment YAML) for the

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