istio

 Nacos Server:  2.1.0
 Model: standalone

我启动Nacos server后，启动过程中提示config_info表中缺少encrypted_data_key字段，然后我就手动加了这个字段encrypted_data_key(varchar(255)).但是无法创建新的配置

• #574 was completed in Sept 2021.
• Related to #574, the Cymbal team suggested a few additional improvements in Oct 2021 that might be worth adding:
  • "Hover" and "press" states for buttons (see Google-internal Figma comment)
  • "Online Boutique" logo color change (see [Google-i

Add a network option in creating workload

like rancher‘s Networking tab

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

Describe the bug

We have activated the event and post-rollout webhook and canary analysis is skipped so far. However, we never get triggered by the post-rollout webhook. With the event webhook we get this message "Promotion completed! Canary analysis was skipped for my-test-app". But no post-rollout webhook call.

To Reproduce

Our canaries YAML:

apiVersion: flagger.a

After the PF4 update, some styles would need an adjustment, this issue is to track a minor change in the trace details labels:

On green/red labels, the font color should h

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
[A clear and concise description of what you want to happen.]
Add a sample of MMS using a custom model server similar to sklearn and triton that will reside [in

Expected Behavior

It should show up as it used to be.

Screenshots/Logs

Currently

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem

The kiali-operator may require higher memory limits for clusters with bigger amount of nodes. Thus resource limits shall be configurable via values.

Describe the solution you'd like A clear and concise description of what you want to happen.
Enrich schema for Kiali-operator

What would you like to be added:

This error is shown in the stage log. Need to found out and update error format for all error like this

 (%!w(*fmt.wrapError=&{failed to apply:  (signal: killed) 0xc0090b8dc0}))

Why is this needed: