BUG REPORT (helm-converter) : problem when parsing datasource section when converting to VMAlert object

[ccaillet1974]

Hi,

I've got the following error:

cannot unmarshal input file: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal object into Go struct field VMAlertDatasourceSpec.server.datasource.HTTPAuth.headers of type []string
exit status 1

The corresponding datasource section of my values file is:

datasource:
    url: "http://lyo0-sfr-int-unify-vmauth.kube-vlogs.svc:8427"
    # url: "http://lyo0-int-cdn-cvlogs-vlselect.kube-vlogs.svc:9471/select/multitenant"
    # -- Basic auth for datasource
    # basicAuth:
    #   username: ""
    #   password: ""
    #   # -- Auth based on Bearer token for datasource
    bearer:
      # -- Token with Bearer token. You can use one of token or tokenFile. You don't need to add "Bearer" prefix string
      token: "Nzqh1+ow0l4N6MFkxV2kAFtXBen1v/R6nuWlv3xVO04="
    #   # -- Token Auth file with Bearer token. You can use one of token or tokenFile
    #   tokenFile: ""

[AndrewChubatiuk]

thanks for an issue. fix was merged

[ccaillet1974]

Seems to be fixed for datasource, except the fact that my token is ignored. More important it seems that there some trouble with helm-converter or maybe vmalert is totally unfinished because I've got this manifest from my helm values file which is already deployed :

apiVersion: operator.victoriametrics.com/v1beta1
kind: VMAlert
metadata:
  name: victoria-metrics-alert
  namespace: kube-vmetrics
spec:
  affinity: {}
  configReloaderResources: {}
  datasource:
    url: http://lyo0-sfr-int-unify-vmauth.kube-vlogs.svc:8427
  extraArgs:
    clusterMode: "true"
    envflag.enable: "true"
    envflag.prefix: VM_
    httpListenAddr: :8880
    license.forceOffline: "true"
    loggerFormat: json
    remoteWrite.disablePathAppend: "true"
    rule: '[/config/alert-rules.yaml]'
  image:
    pullPolicy: IfNotPresent
    repository: victoriametrics/vmalert
  notifier: {}
  remoteRead:
    url: ""
  remoteWrite:
    url: ""
  replicaCount: 1
  resources: {}
  securityContext: {}
status: {}

According to this result I see that remoteRead, remoteWrite resources, securityContext and of course the main thing the rules configured are ignored.

There is something rotten in the Denmark realm :)