lll
lll
基本没有考虑多主架构的场景 这方向有很多东西可以做
we will add documentation later
1. if lazyload deployed in your local cluster more info .. 2. consumer cnofigdump 3. attach accesslog in consumer's envoy
> kubectl -n nacos exec -it consumer-demo-6478988b9b-bggks -c consumer-demo kubectl -n nacos exec -it consumer-demo-6478988b9b-bggks -c istio-proxy
看configdump, provider 的所有配置都下发了 但是consumer的accesslog里怎么没有访问记录呢 你们只能dns开了吗 lds  cds  rds 
> @MouceL Can you help confirm that vs+dr cannot take effect? I think this is a bug, ServiceEntry does the host need to fill in the FQDN. the meshregistry is...
> Contributor > @MouceL Can you help confirm that vs+dr cannot take effect? I think this is a bug, ServiceEntry does the host need to fill in the FQDN. you...
由于ownerreference无法跨命名空间 slimeboot的删除也无法导致由slimeboot生成的envoyfilter删除 所以合适的方式还是通过脚本方式删除 需要结合 https://github.com/slime-io/slime/blob/master/staging/src/slime.io/slime/modules/lazyload/install/samples/lazyload/easy_uninstall_lazyload.sh 删除