You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*The ConfigMap always has the same name as cluster resource.* Which allows Stackable operators as well as users to look up service connection information simply by the name of the product instance.
38
+
The information needed to connect can be a string like above, for example a JDBC connect string: `jdbc:postgresql://localhost:12345`. But a ConfigMap can also contain whole configuration files which can then be mounted into a Pod. This is the case for xref:hdfs::discovery.adoc[HDFS], where the `core-site.xml` and `hdfs-site.xml` files are put into the discovery ConfigMap.
39
+
40
+
*The ConfigMap always has the same name as cluster resource.* Which allows Stackable operators as well as users to look up service connection information simply by the name of the product instance they want to connect to.
39
41
40
42
== Usage of the service discovery ConfigMap
41
43
@@ -67,7 +69,7 @@ spec:
67
69
...
68
70
----
69
71
70
-
With the HdfsCluster name simple-hdfs, the hbase-operator looks up the discovery ConfigMap for the simple-hdfs HdfsCluster, retrieves the information it needs to configure Hbase and configures the simple-hbase instance.
72
+
With the HdfsCluster name simple-hdfs, the HBase Operator looks up the discovery ConfigMap for the simple-hdfs HdfsCluster, retrieves the information it needs to configure Hbase and configures the simple-hbase instance.
71
73
72
74
=== Connect third-party products
73
75
@@ -82,4 +84,10 @@ If you are already operating an HDFS instance, you can simply provide a ConfigMa
82
84
[#whats-next]
83
85
== What's next
84
86
85
-
Consult discovery ConfigMap documentation for specific products: HDFS, Hive, Kafka, OPA, ZooKeeper.
87
+
Consult discovery ConfigMap documentation for specific products:
0 commit comments