Rogerio Machado

Addon registry doesn't follow Minikube DNS name configuration (--dns-domain)

1

### What Happened? The addon named registry only works with "minikube --dns-domain cluster.local" . The file "registry-proxy.yaml.tmpl" has a hard coded service DNS domain registry.kube-system.svc.cluster.local, it must follow the "--dns-domain...

Fix addon registry doesn't follow Minikube DNS domain name configuration (--dns-domain)

6

- Registry bug minikube-with-bug-registry version minikube-with-bug-registry -p cluster-unfixed start --dns-domain cluster.xpt minikube-with-bug-registry -p cluster-unfixed status minikube-with-bug-registry -p cluster-unfixed addons enable registry kubectl -n kube-system get pods | grep registry-proxy- kubectl...

zeppelin | Apache Zeppelin requires either Java 8 update 151 or newe

1

zeppelin | - Setting hadoop.proxyuser.hue.groups=* zeppelin | Configuring hdfs zeppelin | - Setting dfs.webhdfs.enabled=true zeppelin | - Setting dfs.permissions.enabled=false zeppelin | Configuring yarn zeppelin | - Setting yarn.timeline-service.enabled=true zeppelin |...

FIX Add at line 33: ENV ZEPPELIN_ADDR="0.0.0.0" https://github.com/DrSnowbird/docker-spark-bde2020-zeppelin/blob/1a1ff9b478dcc4c1f98ed6dc722b75a1865a536d/Dockerfile#L33