Hello, I deployed Datahub on a K8S cluster. We hav...
# all-things-deployment
b
Hello, I deployed Datahub on a K8S cluster. We have another POC environment that is a local docker deployement. Both are the same version v0.10.4 Howver the navigation is different in the K8S cluster. the new navigation features are visible in the docker deployement, but now int the K8S cluster Ex : on docker :

https://plik.ovh/file/gIhnBLb6ZyXUFTxt/BkRyTrlaCMTTLif0/docker%20-%20advance%20filter.png

on k8s :

https://plik.ovh/file/gIhnBLb6ZyXUFTxt/DpenyWVBIfy7P3Bu/k8s%20no%20advance%20filter.png

I guess it comes from an elasticsearch index ? Is there something to add in the values.yaml ?
1
a
I assume you've deployed the main branch into your local Docker environment. That means you've actually deployed functionality that will be released probably with 0.10.5. On k8s you've deployed the actual 0.10.4 release. That could explain the difference you see. See a similar conversation: https://datahubspace.slack.com/archives/CV2KB471C/p1689147223754659
b
thank you for the reply. I deployed the quickstart. It means that we needs to secure the version when deploying the docker environnement in order avoid a mix.
a
No worries, you can use the --version option when running the
datahub docker quickstart
command. For example:
datahub docker quickstart --quickstart-compose-file .\docker-compose-without-neo4j.quickstart.yml --version v0.10.4