Describe the bug
In the naming module, ServiceController's "create" method has an optional

Feature Description

Kubersphere integrate the velero based on the k8s CRD extensions

How does it work
It's like monitoring component

In lieu of #283, implement Stackdriver Canary Analysis for use in GKE.

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).

The buildkit (client) and buildkitd (builder daemon) can both be used with faasd or k3s hosts for building images without installing Docker onto the machine.

There is a tar that can be downloaded like we do with inletsctl, however, we need to make sure we extract both binaries. I'm fairly sure that this will "just work"

See more:

https://github.com/moby/buildkit/releases

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 v1beta1 canary implementation has been changed from traffic split at knative service to revision level, we need to document an new example and implementation details can be found from the RFC.

**Anything else you would like to

Current Behavior
The individual service mesh management pages have a namespace field with "default" prepopulated.

Desired Behavior
The namespace field should not only show "default" as an option, but should also include the list of namespaces that are currently present in the user's Kubernetes environment. Pre-populating this text field will be a UX improvement and it will also help