Cant access vmui after creating VMSingle

[hasanawad94]

Created this VMSingle resource and it seems fine and its scraping from the logs:

apiVersion: operator.victoriametrics.com/v1beta1
kind: VMSingle
metadata:
  name: vmsingle-example
spec:
  configMaps:
         - vmstorage-exporter-config-map
  image:
    repository: victoriametrics/victoria-metrics
    tag: v1.101.0
    pullPolicy: IfNotPresent
  retentionPeriod: "12"
  removePvcAfterDelete: true
  storage:
    accessModes:
      - ReadWriteOnce
    resources:
      requests:
        storage: 50Gi
  extraArgs:
    dedup.minScrapeInterval: 60s
    promscrape.config.strictParse: "false"
    promscrape.config: /etc/vm/configs/vmstorage-exporter-config-map/vmstorage-exporter.yml
  resources:
    requests:
      memory: 500Mi
      cpu: 500m
    limits:
      memory: 10Gi
      cpu: 5

2024-08-08T09:30:48.710Z        info    VictoriaMetrics/lib/logger/flag.go:12   build version: victoria-metrics-20240425-145715-tags-v1.101.0-0-g5334f0c2c
2024-08-08T09:30:48.710Z        info    VictoriaMetrics/lib/logger/flag.go:13   command-line flags
2024-08-08T09:30:48.710Z        info    VictoriaMetrics/lib/logger/flag.go:20     -dedup.minScrapeInterval="1m0s"
2024-08-08T09:30:48.710Z        info    VictoriaMetrics/lib/logger/flag.go:20     -httpListenAddr=":8429"
2024-08-08T09:30:48.710Z        info    VictoriaMetrics/lib/logger/flag.go:20     -promscrape.config="/etc/vm/configs/vmstorage-exporter-config-map/vmstorage-exporter.yml"
2024-08-08T09:30:48.710Z        info    VictoriaMetrics/lib/logger/flag.go:20     -promscrape.config.strictParse="false"
2024-08-08T09:30:48.710Z        info    VictoriaMetrics/lib/logger/flag.go:20     -retentionPeriod="12"
2024-08-08T09:30:48.710Z        info    VictoriaMetrics/lib/logger/flag.go:20     -storageDataPath="/victoria-metrics-data"
2024-08-08T09:30:48.711Z        info    VictoriaMetrics/app/victoria-metrics/main.go:73 starting VictoriaMetrics at "[:8429]"...
2024-08-08T09:30:48.711Z        info    VictoriaMetrics/app/vmstorage/main.go:106       opening storage at "/victoria-metrics-data" with -retentionPeriod=12
2024-08-08T09:30:48.763Z        info    VictoriaMetrics/lib/memory/memory.go:42 limiting caches to 6442450944 bytes, leaving 4294967296 bytes to the OS according to -memory.allowedPercent=60
2024-08-08T09:30:48.784Z        info    VictoriaMetrics/lib/storage/storage.go:967      discarding /victoria-metrics-data/cache/curr_hour_metric_ids, since it contains outdated hour; got 478640; want 478641
2024-08-08T09:30:48.785Z        info    VictoriaMetrics/lib/storage/storage.go:967      discarding /victoria-metrics-data/cache/prev_hour_metric_ids, since it contains outdated hour; got 478639; want 478640
2024-08-08T09:30:49.083Z        info    VictoriaMetrics/app/vmstorage/main.go:120       successfully opened storage "/victoria-metrics-data" in 0.372 seconds; partsCount: 0; blocksCount: 0; rowsCount: 0; sizeBytes: 0
2024-08-08T09:30:49.151Z        info    VictoriaMetrics/app/vmselect/promql/rollup_result_cache.go:126  loading rollupResult cache from "/victoria-metrics-data/cache/rollupResult"...
2024-08-08T09:30:49.156Z        info    VictoriaMetrics/app/vmselect/promql/rollup_result_cache.go:155  loaded rollupResult cache from "/victoria-metrics-data/cache/rollupResult" in 0.006 seconds; entriesCount: 0, sizeBytes: 0
2024-08-08T09:30:49.157Z        info    VictoriaMetrics/app/victoria-metrics/main.go:84 started VictoriaMetrics in 0.446 seconds
2024-08-08T09:30:49.157Z        info    VictoriaMetrics/lib/promscrape/scraper.go:113   reading scrape configs from "/etc/vm/configs/vmstorage-exporter-config-map/vmstorage-exporter.yml"
2024-08-08T09:30:49.157Z        info    VictoriaMetrics/lib/httpserver/httpserver.go:119        starting server at http://127.0.0.1:8429/
2024-08-08T09:30:49.157Z        info    VictoriaMetrics/lib/httpserver/httpserver.go:120        pprof handlers are exposed at http://127.0.0.1:8429/debug/pprof/
2024-08-08T09:30:49.159Z        info    VictoriaMetrics/lib/promscrape/config.go:140    starting service discovery routines...
2024-08-08T09:30:49.159Z        info    VictoriaMetrics/lib/promscrape/config.go:146    started 1 service discovery routines in 0.000 seconds
2024-08-08T09:30:49.161Z        info    VictoriaMetrics/lib/promscrape/scraper.go:430   static_configs: added targets: 3, removed targets: 0; total targets: 3
2024-08-08T09:31:04.622Z        info    VictoriaMetrics/lib/storage/partition.go:203    creating a partition "2024_08" with smallPartsPath="/victoria-metrics-data/data/small/2024_08", bigPartsPath="/victoria-metrics-data/data/big/2024_08"
2024-08-08T09:31:04.749Z        info    VictoriaMetrics/lib/storage/partition.go:212    partition "2024_08" has been created

I was expecting to be able to simply access vmui from the service that VMSingle generated but its not working:
curl http://vmsingle-vmsingle-example.ncms.svc.cluster.local:8429/vmui

Should this just work or do I need to do something extra?
I deployed cluster version and was able to access vmui at vmselect.

[AndrewChubatiuk]

hey @hasanawad94
what response do you get during attempt to query vmsingle endpoint?