istio

Both versions of nacos2.0.0 and nacos2.0.2 were tried, unable to cluster successfully under mac and centos, the log output service is being restarted, unable to start normally, and cannot complete the election.
尝试了nacos2.0.0和nacos2.0.2两个版本，在mac和centos下都无法集群成功，日志一直输出服务在重启，无法正常启动，也无法完成选举.

What's it about?
When you want to select the drop-down menu box in the console, you can search by regular expression or sort by the letters A-Z
What's the reason why we need it?
Can improve the development efficiency, shorten the search time
I believe this is an important feature for Kubesphere. There're a few use cases:
For example, if I have 200 services on a project, I have to manu

Describe the feature

I was testing a blue/green strategie within my Kubernetes cluster using flagger and the kubernetes provider.

In the documentation, in the blue/green usage strategie steps, we can see that the traffic should be routed to canary while the primary is promoted https://docs.flagger.app/usage/deployment-strategies#blue-green-deployments

I was assuming that using

Kiali uses tooltip in multiple locations, in some cases style difers even for the same concepts.

I noticed some changes on this kiali/kiali-ui#1884 but it would require some global issue to review all tooltips and check that they look like similar (at least for the same concept).

Expected Behaviour

When using K8s 1.22 and newer, use the new namespace for ingress, for older use the deprecated API (apiVersion: extensions/v1beta1)

Several apps gener

Is your feature request related to a problem? Please describe.
Vault has backends for AWS like dynamo and s3. However to use them you should provide credentials. AWS support 2 solutions to eliminate this. IAM roles for Service Accounts and Instance profile roles.
Due to some unknown reason vault requires more time to start when using dynamic creds than explicit definition keys in s3 block o

/kind feature

Describe the solution you'd like

In pkg/apis/serving/v1beta1/inference_service_defaults.go the default InferenceService resource requests and limits are hard coded to be 1 cpu and 2Gi memory. These are reasonable defaults. However, the entire existence of these defaults should be disablable. Moreover, administrators should be able to quickly adjust defaults globally via t

See mesheryctl Command Tracker for current status of commands.

Current Behavior

Global flag -c not honored in system context view

➜  ~ mesheryctl system context view -c docker
Error: unknown shorthand flag: 'c' in -c
➜  ~ mesheryctl system context view --context docker

Current C

What would you like to be added:

https://github.com/pipe-cd/pipe/blob/2fda7c82def6c81aff29ab08d1283851f5f49f06/pkg/app/piped/cloudprovider/ecs/task.go#L45-L54

Why is this needed: