Zookeeper service accessed by shortname #184
Comments
michaeljmarshall
added a commit
that referenced
this issue
Apr 22, 2022
* Use FQDN for service names * Make cluster domain configurable * Clean up missed hard coded suffixes * Remove last hard coded references to cluster.local Fixes: #184. Hostname verification relies on the initial DNS named targeted. In order to support stricter requirements with DNS hostnames, we'll default to using the fully qualified service names when configuring Pulsar components. Note: because the DNS names are part of the cluster initialization, you'll need to create a new cluster to take advantage of this feature or you'll need to run the admin command to update the cluster: `bin/pulsar-admin clusters update ...`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is only possible to access Zookeeper service via shortname (
pulsar-zookeeper-ca:2181)pulsar-helm-chart/helm-chart-sources/pulsar/templates/bookkeeper/bookkeeper-configmap.yaml
Line 31 in db0c121
I understand that this works for DNS resolution since the brokers live in the same namespace and the domain is present in the
searchoption of the/etc/resolv.conf. However, we'd like to avoid having to generate certificates using short-names. Is it possible to add an option to add a full domain for the zookeeper service?For example something like:
{{ template "pulsar.fullname" . }}-{{ .Values.zookeeper.component }}-ca{{- if .Values.zookeeper.domain -}}.{{ .Values.zookeeper.domain }}{{- end -}}:2281Thanks
The text was updated successfully, but these errors were encountered: