8000 v1.42.1 removes service port · Issue #212 · coredns/helm · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

v1.42.1 removes service port #212

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
rwong2888 opened this issue May 6, 2025 · 4 comments
Open

v1.42.1 removes service port #212

rwong2888 opened this issue May 6, 2025 · 4 comments

Comments

@rwong2888
Copy link

Service "coredns" is invalid: spec.ports: Required value

Image
@alemairebe
Copy link

to be precise ; the above, is what I get too via ArgoCD but running helm template locally, I get :
on the service

  ports:
  - {"name":"udp-53","port":53,"protocol":"UDP","targetPort":53}

and on the pod :

        ports:
        - {"containerPort":53,"name":"udp-53","protocol":"UDP"}
        - {"containerPort":53,"name":"tcp-53","protocol":"TCP"}
        - {"containerPort":9153,"name":"tcp-9153","protocol":"TCP"}

which are removed as they do not match the api specification

@Kariton
Copy link
Kariton commented May 7, 2025

flux diff on my end:

--- HelmRelease: kube-system/coredns Service: kube-system/kube-dns

+++ HelmRelease: kube-system/coredns Service: kube-system/kube-dns

@@ -19,12 +19,8 @@

   clusterIP: 10.96.0.10
   ports:
   - name: udp-53
     port: 53
     protocol: UDP
     targetPort: 53
-  - name: tcp-53
-    port: 53
-    protocol: TCP
-    targetPort: 53
   type: ClusterIP

values:

---
priorityClassName: system-cluster-critical
k8sAppLabelOverride: kube-dns

replicaCount: 2

service:
  name: kube-dns
  clusterIP: 10.96.0.10

affinity:
  nodeAffinity:
    requiredDuringSchedulingIgnoredDuringExecution:
      nodeSelectorTerms:
        - matchExpressions:
            - key: node-role.kubernetes.io/control-plane
              operator: Exists

tolerations:
  - key: CriticalAddonsOnly
    operator: Exists
  - key: node-role.kubernetes.io/control-plane
    operator: Exists
    effect: NoSchedule
  - key: node.kubernetes.io/unschedulable
    operator: Exists
    effect: NoSchedule

topologySpreadConstraints:
  - maxSkew: 1
    topologyKey: kubernetes.io/hostname
    whenUnsatisfiable: DoNotSchedule
    labelSelector:
      matchLabels:
        app.kubernetes.io/instance: coredns

@IdlePhysicist
Copy link

Looks to be related to this commit.

d579bfc

@maxim-mityutko
Copy link
maxim-mityutko commented May 8, 2025 •
edited
Loading

Got exactly the same issue with ArgoCD when the zone was configured like that (basically default values):

- zones:
  - zone: .

Explicitly added the scheme and use TCP:

- zones:
  - zone: .
    scheme: dns://
    use_tcp: true

No more error, service manifest seems to be correct.

@maxim-mityutko maxim-mityutko mentioned this issue May 8, 2025
Merged
@ironashram ironashram mentioned this issue May 9, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@alemairebe @IdlePhysicist @maxim-mityutko @rwong2888 @Kariton
0