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
I deployed a cluster in a Kubernetes environment and used the command bin/pulsar-admin sinks create in the existing cluster to create an HTTP sink. However, the domain name of the generated pod is the default cluster.local rather than the custom domain of the cluster, resulting in the 'Unable to resolve host' issue. How can this problem be resolved?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I deployed a cluster in a Kubernetes environment and used the command bin/pulsar-admin sinks create in the existing cluster to create an HTTP sink. However, the domain name of the generated pod is the default cluster.local rather than the custom domain of the cluster, resulting in the 'Unable to resolve host' issue. How can this problem be resolved?
Beta Was this translation helpful? Give feedback.
All reactions