spec.ports required value

[bandwiches]

Maybe I'm missing something, but it looks like use_tcp: true is require rather than optional? When left off or set to false, it results in error. Note that isClusterService: false is set for what it's worth.

Reproduce

servers:
- zones:
  - zone: .
    # use_tcp: true
  port: 53

Error: UPGRADE FAILED: cannot patch "xyz" with kind Service: Service "xyz" is invalid: spec.ports: Required value

Workaround

Only way to fix is to require use_tcp: true, using false results in the same error above.

servers:
- zones:
  - zone: .
    use_tcp: true
  port: 53

[abcdegorov]

having the same issue, but specifying use_tcp: true and options described in #224 didn't work for me. for now I had to resort to rewriting the entire ports section of the service using Kustomize post renderer patches in Flux CD

[lholota]

I have also stumbled upon this issue. Based on my trial and error "investigation", this issue was introduced in the version 1.42.1 and is still in the latest version (1.43.3 at the time of writing).

This is my original config prior to the upgrade to 1.42.1 or higher which was working correctly with older versions:

 - zones:
      - zone: .
    port: 53
    plugins:
      - name: log
      # ...

Prior to 1.42.1 this config rendered the service ports correctly (i.e. 53 for both UDP and TCP). After the upgrade, the chart renders the ports as an empty array. Below is a config which I used to work around the issue. Both of the scheme and use_tcp fields must be set otherwise the chart renders the ports as an empty array which is both wrong and not backward compatible.

- zones:
    - zone: .
      scheme: dns://   # This MUST be set
      use_tcp: true.    # This MUST be set
  port: 53
  plugins:
    - name: log
    # ...

Happy to help with testing the fix if you tag me :)

[abcdegorov]

@lholota, I have tried setting both scheme and use_tcp values, but this didn't help. did you re-install the helm release?