How to run rally against an existing on-premise cluster

[anoopkv (Anoop Venugopalan)]

I am running my elasticsearch (version 7.11) cluster on an on-premise kubernetes cluster. security is enabled in the cluster. to run rally i have created a separate pod

--chart.yaml--
apiVersion: v1

    kind: Pod

    metadata:

      name: {{ template "fullname" . }}

    spec:

      containers:

      - name: esrally

        image: {{ .Values.image }}

        command:

          - "sleep"

          - "604800"

      {{- if .Values.reportDir }}

        volumeMounts:

        - name: report

          mountPath: {{ .Values.reportDir }}

      restartPolicy: Never

      volumes:

      - name: report

        hostPath:

          path: {{ .Values.reportDir }}

      {{ end }}

--values.yaml

image: elastic/rally
reportDir: /tmp
reportFile: report-mem-lock.csv

---rally-ini-------

[meta]
config.version = 17

[system]
env.name = local

[node]
root.dir = /rally/.rally/benchmarks
src.root.dir = /rally/.rally/benchmarks/src

[source]
remote.repo.url = https://github.com/elastic/elasticsearch.git
elasticsearch.src.subdir = elasticsearch

[benchmarks]
local.dataset.cache = /rally/.rally/benchmarks/data

[reporting]
datastore.type = in-memory
datastore.host =
datastore.port =
datastore.secure = False
datastore.user =
datastore.password =


[tracks]
default.url = https://github.com/elastic/rally-tracks

[teams]
default.url = https://github.com/elastic/rally-teams

[defaults]
preserve_benchmark_candidate = false

[distributions]
release.cache = true

We are running behind a proxy, so i have set up http_proxy and verified that rally is able to get tracks
proxy setting
Command -
esrally race --track=geonames --target-hosts=example.elasticsearch.com --pipeline=benchmark-only --test-mode --kill-running-processes --client-options="timeout:60,use_ssl:true,verify_certs:false,basic_auth_user:'elastic',basic_auth_password:'password'"

Getting the following error -

[WARNING] No Internet connection detected. Automatic download of track data sets etc. is disabled.
[ERROR] Cannot race. Error in race control (ConnectionError(<urllib3.connection.HTTPSConnection object at 0x7f621b4bca60>: Failed to establish a new connection: [Errno -2] Name or service not known) caused by: NewConnectionError(<urllib3.connection.HTTPSConnection object at 0x7f621b4bca60>: Failed to establish a new connection: [Errno -2] Name or service not known))

[RickBoyd]

Hi! Name or service not known should indicate that your pod cannot resolve the address you gave to --target-hosts. Without going too deep here, consider:

Is there a defined Service name that you're hitting?
Is the service for ES in the same namespace as the rally pod?
If not, are you using the FQDN for the target service?