istio

Describe the bug
A clear and concise description of what the bug is.

`/nacos/v1/ns/inst

• #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

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

After upgrade node to the latest one I got the message that node engine must be >=12.22.0 and < 16. this is great because we set in the package.json:

"node": ">=12.22.0 && <16"

So I installed the latest 15.X 15.14.0 (latest one of 15) and I got :

`error npmlog@6.0.2: The engine "node" is incompatible with this

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

See mesheryctl Command Tracker for current status of commands.

Current Behavior

If I have an ill-formatted config.yaml inside .meshery directory and I try to execute any mesheryctl command, it results in the err

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: