Skip to content
#

cloud-native

Here are 981 public repositories matching this topic...

joshkping
joshkping commented Nov 16, 2021

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-

jmilktea
jmilktea commented Nov 12, 2021

Which Component
Sentinel

Describe what problem you have encountered
在hystrix和resilience4j中,我们可以配置default,对所有的feign client生效,例如熔断规则,隔离策略。在sentinel中我找不到类似的配置,似乎需要单个url去配置,这非常麻烦,请问怎么做。

In hystrix and resilience4j, we can configure "default", which will take effect for all feign clients, such as circuit breaker rules and isolation strategies. I can't find a similar configuration in sen

jina
alexcg1
alexcg1 commented Oct 13, 2021

Describe the bug
I'm having major trouble with from_csv.

Context: I'm writing tutorial for build simple text search engine with Jina + Hub. I don't want to include a whole section of processing datasets, hence just passing a CSV into from_csv. I tried with meme dataset (converted tsv) before, and now using [superhero dataset](https://www.kaggle.com/jonathanbesomi/superheroes-nlp-datas

scravy
scravy commented Nov 26, 2021

Summary

It is possible to access individual parameters, labels, or annotations from within a workflow via

  • workflow.parameters.<NAME>,
  • workflow.labels.<NAME>,
  • and workflow.annotations.<NAME> respectively.

It is also possible to get all parameters as a JSON string:

  • workflow.parameters

It would be great if also labels and annotations could be exposed that way:

ia3andy
ia3andy commented Nov 23, 2021

Description

Continuing on quarkusio/quarkus#20849

The current implementation (👆) uses the shell java version to determine a compatible version (11 or 17 for now) in generated project.

We need to add this as a parameter (11 or 17, default still being automatic based on shell java version) in the CLI and Maven plugin.

Implementation ideas

See comment ht

milvus
zhu733756
zhu733756 commented Nov 11, 2021

Support importing Grafana templates to the workspace level. Currently, this function only can be accessed by the cluster lever.

Solution

See https://github.com/kubesphere/kubesphere/blob/511d0d02fffc766c0ee218dab15d399888681672/pkg/kapis/monitoring/v1alpha3/handler.go#L404 for detail. Maybe we need to add a namespace parameter as an optional to determine to convert it to Dashboard struct

thomas-riccardi
thomas-riccardi commented Nov 26, 2021

Bug Report

What is the issue?

CLI: dynamic autocompletion of context wongly completes with cluster names

How can it be reproduced?

  • have a KUBECONFIG with a context with a different name than its cluster, e.g. context=mycontext, cluster=mycluster
  • kubectl --context=[TAB] : proposes mycontext
  • linkerd --context=[TAB] : proposes mycluster, then fails when us
spacewander
spacewander commented Nov 30, 2021

Improved or typo fixed.

Currently, the README claims that the WASM extension is the modern way. However, it is an experimental feature.

Solution

Need to fix it with:

diff --git README.md README.md
index d14aae9c..8e11456c 100644
--- README.md
+++ README.md
@@ -146,10 +146,10 @@ A/B testing, canary release, blue-green deployment, limit rate, defense against
   - Custom routing
kmova
kmova commented Apr 6, 2020

Local PV (device) provisioner leaves a stale BDC in the following case:

  • On PVC request, creates a BDC
  • If the system doesn't have a matching BD, then PVC request keeps retrying, and so does the NDM operator that keeps retrying
  • Now if the user deletes the PVC, then Local PV (device) provisioner doesn't get the trigger to process delete, as there was no PVC.

This causes the stale BDC

fission
swaroopnuli
swaroopnuli commented Sep 19, 2020

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

Missing functionality to update min/max cpu/mem of an exiting ENV. Currently, to update, we are forced to delete and re-create the env. This also has a risk of dependent functions being erratic. It also de-couple resource utilization independent of function creation and be useful to update the resource in a quick to respond situ

yugabyte-db
sanketkedia
sanketkedia commented Nov 2, 2021

Description

Currently, for e.g. say that out of 3 copies of a tablet, we want to have 2 copies in C1.R1.Z1 and 1 copy in C2.R2.Z2 then we would specify it as below:

./bin/yb-admin \
    -master_addresses $MASTER_RPC_ADDRS \
    modify_placement_info  \
    C1.R1.Z1,C1.R1.Z1,C2.R2.Z2 3

However, this is somewhat complex and hard to follow. We don't need to necessarily r

wrannaman
wrannaman commented Mar 23, 2019

How are you planning on using kubeedge?

I've been looking for something like this for a long time (Currently our team uses Rancher although their product wasn't really meant for edge computing.) I'd love to hear how others in the community would like to use this so I can compile a list of use cases that kubeedge can support out of the box.

Thanks!

Improve this page

Add a description, image, and links to the cloud-native topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the cloud-native topic, visit your repo's landing page and select "manage topics."

Learn more