Issue Description

Type: bug report

Describe what happened

java.lang.IllegalStateException: failed to req API:/nacos/v1/ns/instance/beat after all servers([minion-register:8848]) tried: failed to req API:minion-register:8848/nacos/v1/ns/instance/beat. code:400 msg: java.lang.IllegalArgumentException: dom name can only have these characters: 0-9a-zA-Z-._:, current: DEFAULT_GROU

I actually saw this in code review but then I noticed the old PNGs were also around 1-2 MB. Probably a little room for improvement if we pass these to online PNG optimizers. It seems like the main issue is that the resolution is simply too large.

Expected Behavior

Documented install procedure at https://knative.dev/docs/serving/installing-cert-manager/ works fine.

Actual Behavior

~/knative-workspace/cert-manager-0.6.1$ kubectl apply -f deploy/manifests/cert-manager.yaml
unable to recognize "deploy/manifests/cert-manager.yaml": no matches for kind "Deployment" in version "apps/v1beta1"
unable to recognize "deploy/manifests

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

There's a non-deterministic test in client_factory_test.go that sometimes fail. Most of the time it seems ok, so it hasn't harmed so much and would be low priority at first glance... but it would be nice to see if there's a better way to write that.

Incriminated code line 54 I think:

time.Sleep(time.Millisecond * 100)

Example of failure: https://travis-ci.org/github/kiali/ki

环境：

• Mac
• vagrant 2.1.2
• virtualBox: 5.2.16
• Kubernetes 1.11.0

遇到了几个问题：

1. 在系统自动挂起之后vm 的时间会不对，没有自动同步，导致 Prometheus 监控数据显示不出来，应该同步时间就可以，不过我没有，而是使用的 vagrant halt ，就导致了另一个问题。
2. 执行 vagrant halt 按照【重启】 的操作后，之前配置的 Istio 相关所有东西都不见了，包括 istio-system namespace 。
3. 按照[文档](

When I visit http://www.servicemesher.com/istio-handbook,
the navigation links on the page left are invalid with 404 error.

All links have lost the /istio-handbook prefix.

Is your feature request related to a problem? Please describe.
Investigate github.com/google/go-containerregistry to replace the heroku/docker-registry-client which seems to be unmaintained.

Describe the solution you'd like
Check the go-containerregistry library and see if it fits our needs.

Describe alternatives you've considered
We already use a forked version of the docker-

Currently the Jaeger variables are added as ENV in Docker file:

  ENV JAEGER_SERVICE_NAME=customer\
  JAEGER_ENDPOINT=http://jaeger-collector.istio-system.svc:14268/api/traces\
  JAEGER_PROPAGATION=b3\
  JAEGER_SAMPLER_TYPE=const\
  JAEGER_SAMPLER_PARAM=1

We could avoid this and add them to Kubernetes Deployment YAML

(OR)

Except for JAEGER_SERVICE_NAME other variables

Description

Add --helm3 flag to chart app

The arkade install chart command should have helm3 support and use it by default.

我刚看了一下其他人都好像有这个问题，不过还是看见有人数可以用renew的办法，我也尝试了一下
kubeadm alpha phase all
初步看好像是续期了一年的样子，但由于我是vmware的1master 3node的。。没有环境测试高可用情况下这样renew证书的话，其他master要怎么操作。

另外贴一下下面的help信息
[root@t0 etcd]# kubeadm alpha phase --help
This command is not meant to be run on its own. See list of available subcommands.

[root@t0 etcd]# kubeadm alpha certs renew --help
This command is not meant to be run on its ow

Current State:
Project section of docs navigation is indented too far.

Desired State:
Should be shifted left (outdented).