istio

携带Data ID查询条件切换namespace时，Data ID条件不生效

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

The documentation and some tests uses gw.ns(.svc.cluster.local) for gateways.

I think this is the correct format for istio gateways: <gateway namespace>/<gateway name>

Like here:

https://github.com/fluxcd/flagger/blob/273b05fb24d467c10939389218e6a8ec26d4c70e/test/istio/test-delegation.sh#L41

re. https://istio.io/latest/docs/reference/config/networking/virtua

Some pages give React warnings when you visit them and inspect the dev console. This is probably minor but would be good to resolve.

Services page:

Istio Config details page:
![Screenshot from 2022-03-04 12-15-03](https://user-images.githubusercontent

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

See mesheryctl Command Tracker for current status of commands.

Current Behavior

Invalid platforms passed to Meshery's bash script installer are not handled as well as they could be:

➜  ~ curl -L https://git.io/meshery | PLATFORM=bob bash -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 

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 a mount 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: