bumpy-keyboard-50565
03/23/2020, 2:01 PM/admin
endpoint that returns OK
. Frontend also has the same route: https://github.com/linkedin/datahub/blob/master/datahub-frontend/conf/routes#L9brash-airplane-35511
06/12/2020, 9:18 AMvictorious-dawn-14920
08/31/2020, 10:17 AMsilly-apple-97303
09/03/2020, 8:10 PMjava.lang.UnsatisfiedLinkError: /tmp/snappy-1.1.7-bb847a5e-21b5-4d9b-babd-f31afc7109a7-libsnappyjava.so: Error loading shared library ld-linux-x86-64.so.2: No such file or directory (needed by /tmp/snappy-1.1.7-bb847a5e-21b5-4d9b-babd-f31afc7109a7-libsnappyjava.so)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
high-hospital-85984
10/01/2020, 7:12 PMhigh-hospital-85984
11/12/2020, 5:47 PMworried-orange-11965
02/15/2021, 10:38 PMmammoth-bear-12532
icy-easter-2378
04/06/2021, 6:29 PMpi@raspberrypi:~/workspace/datahub $ ./docker/quickstart.sh
Pulling zookeeper ... done
Pulling neo4j ... pulling from library/neo4j
Pulling mysql ... pulling from library/mysql
Pulling broker ... done
Pulling schema-registry ... done
Pulling kafka-setup ... done
Pulling elasticsearch ... pulling from library/elasticsearch
Pulling kibana ... pulling from library/kibana
Pulling elasticsearch-setup ... done
Pulling datahub-gms ... done
Pulling datahub-mce-consumer ... done
Pulling datahub-frontend-react ... done
Pulling datahub-mae-consumer ... done
Pulling kafka-rest-proxy ... done
Pulling kafka-topics-ui ... done
Pulling schema-registry-ui ... done
ERROR: for elasticsearch no matching manifest for unknown in the manifest list entries
ERROR: for mysql no matching manifest for unknown in the manifest list entries
ERROR: for neo4j no matching manifest for unknown in the manifest list entries
ERROR: for kibana no matching manifest for unknown in the manifest list entries
ERROR: no matching manifest for unknown in the manifest list entries
little-france-72098
04/13/2021, 11:24 AMacceptable-football-40437
04/16/2021, 1:27 PMcontrib
, and I have a few questions:
1. I saw that these are on the roadmap to be in the main line DataHub very soon, is that still the case?
2. Looking at the README, there is a line that says Also, these can be installed on-prem or can be leveraged as managed service on any cloud platform.
(referring to Kafka, Elasticsearch, MySQL, and Neo4j). My team is a small one, so we're really interested in leveraging managed services wherever possible! I'd love to hear people's experiences doing this and more details on how that setup process works. Do you set up managed instances and then modify the charts' values.yaml
to point at those instances? Thanks in advance, I'm still new to Helm!calm-addition-66352
04/18/2021, 10:44 PMquickstart.sh
to setup the installation.
kibana | {"type":"log","@timestamp":"2021-04-18T14:30:23Z","tags":["warning","elasticsearch","data"],"pid":7,"message":"No living connections"}
kibana | {"type":"log","@timestamp":"2021-04-18T14:30:23Z","tags":["warning","elasticsearch","data"],"pid":7,"message":"Unable to revive connection: <http://elasticsearch:9200/>"}
kibana | {"type":"log","@timestamp":"2021-04-18T14:30:23Z","tags":["warning","elasticsearch","data"],"pid":7,"message":"No living connections"}
acceptable-football-40437
04/19/2021, 7:48 PMkubernetes/README.md
are all broken, since it seems Helm Hub
is deprecated. Where should these point now?modern-nest-69826
04/20/2021, 7:17 AMimportant-television-65295
04/23/2021, 3:49 AMincalculable-ocean-74010
04/23/2021, 9:13 AMhigh-hospital-85984
04/23/2021, 1:33 PMhigh-hospital-85984
04/23/2021, 1:57 PMearly-lamp-41924
04/23/2021, 3:51 PMimportant-television-65295
04/27/2021, 5:33 AMlittle-france-72098
05/11/2021, 7:34 AMdefaultMode: 256
in the deployment.yaml
files, but the docker containers are not run as root anymore according to their dockerfiles. Of course, if I delete the default mode (or set it less restricting) I can deploy without a problem.
I was wondering if there is a other solution to solve this without editing the official helm chart or if this is some inconsistency remaining from the switch to run the containers with a non-root user?gifted-art-69474
05/12/2021, 11:35 AMcurl
in the base image (openjdk:8-jre-alpine
) contains a vulnerability that we would like to mitigate. However, the newest version of the base image is 2 years old so maybe time to switch out that one?white-beach-27328
05/14/2021, 6:20 PMdatahub-kubernetes
fail to identify the dependent charts such as datahub-gms
? We are pushing the datahub chart to a chart museum and when attempting to deploy that chart into our K8's cluster, I’m getting an error like this:
resource-helm>>> Updating dependencies in /tmp/build/put/stg-chart/datahub...
Saving 5 charts
Save error occurred: directory charts/datahub-gms not found
white-beach-27328
05/17/2021, 5:35 PMtest-connection.yaml
files in the helm charts? I’m noticing that there are some odd bugs in them like:
• The gms test hitting a different endpoint than /health
which causes the service to 404 and fail (https://github.com/linkedin/datahub/blob/master/datahub-kubernetes/datahub/charts/datahub-gms/templates/tests/test-connection.yaml#L14)
• The mae consumer is expecting there is a service to provide dns resolution for the test: https://github.com/linkedin/datahub/blob/master/datahub-kubernetes/datahub/charts/datahub-mae-consumer/templates/tests/test-connection.yaml. No service exists.
• Similarly as above, the mce consumer is expecting there is a service to provide dns resolution for the test: https://github.com/linkedin/datahub/blob/master/datahub-kubernetes/datahub/charts/datahub-mce-consumer/templates/tests/test-connection.yaml#L14. No service exists.
I was initially going to submit a PR fixing this, but tbh I’m not seeing their value given that there are now readiness and liveliness probes on the different deployments which are effectively doing these tests anyway. Happy to just PR a delete on these files since they seem like duplicates. Thoughts?proud-jelly-46237
05/18/2021, 9:13 PMacoustic-midnight-64606
06/04/2021, 9:41 PMproud-jelly-46237
06/08/2021, 4:05 PMdatahub-prerequisites-cp-schema-registry
pod. I am trying to install it in EKS.
[main] WARN org.apache.kafka.clients.ClientUtils - Couldn't resolve server prerequisites-kafka:9092 from bootstrap.servers as DNS resolution failed for prerequisites-kafka
[main] ERROR io.confluent.admin.utils.cli.KafkaReadyCommand - Error while running kafka-ready.
org.apache.kafka.common.KafkaException: Failed to create new KafkaAdminClient
at org.apache.kafka.clients.admin.KafkaAdminClient.createInternal(KafkaAdminClient.java:499)
at org.apache.kafka.clients.admin.Admin.create(Admin.java:73)
at org.apache.kafka.clients.admin.AdminClient.create(AdminClient.java:49)
at io.confluent.admin.utils.ClusterStatus.isKafkaReady(ClusterStatus.java:138)
at io.confluent.admin.utils.cli.KafkaReadyCommand.main(KafkaReadyCommand.java:150)
Caused by: org.apache.kafka.common.config.ConfigException: No resolvable bootstrap urls given in bootstrap.servers
at org.apache.kafka.clients.ClientUtils.parseAndValidateAddresses(ClientUtils.java:89)
at org.apache.kafka.clients.ClientUtils.parseAndValidateAddresses(ClientUtils.java:48)
at org.apache.kafka.clients.admin.KafkaAdminClient.createInternal(KafkaAdminClient.java:455)
Just wanted to double check if you faced this before and in case have a resolution for this, before I start the debug process.proud-jelly-46237
06/09/2021, 9:15 PMdatahub-frontend
with a service type loadbalancer
creates a public internet facing LB. is there any way we can have an option for a internal load balancer
e.g.https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer probably just having an annotation
option in service.yaml will do the trick. which can always be optional and read from Values.yamlrich-policeman-92383
06/14/2021, 12:50 PMgifted-bird-57147
06/15/2021, 11:45 AM