mcs-api icon indicating copy to clipboard operation
mcs-api copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Conformance test: DNS

Open skitt opened this issue 1 year ago • 1 comments

https://github.com/kubernetes/enhancements/blob/master/keps/sig-multicluster/1645-multi-cluster-services-api/README.md#dns

Check that:

  • [ ] Exported services are accessible using service.ns.svc.clusterset.local
  • [ ] Headless services are represented by multiple A/AAAA records
  • [ ] SRV records are available
  • [ ] Headless services’ individual pods are accessible through hostname.clusterid.svc.ns.svc.clusterset.local
  • [ ] The cluster.local zone is unchanged, and accessing services there only accesses local services
  • [ ] Since .clusterset.local may be customized, the tests should allow it to be overridden

skitt avatar Sep 03 '24 15:09 skitt

/assign @tpantelis

tpantelis avatar Oct 06 '24 02:10 tpantelis

@skitt These tasks can be checked as complete (I don't have privs):

  • Exported services are accessible using service.ns.svc.clusterset.local
  • SRV records are available
  • The cluster.local zone is unchanged, and accessing services there only accesses local services

tpantelis avatar Dec 05 '24 14:12 tpantelis

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Mar 05 '25 15:03 k8s-triage-robot

/remove-lifecycle stale

tpantelis avatar Mar 05 '25 19:03 tpantelis

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jun 03 '25 20:06 k8s-triage-robot

/remove-lifecycle stale

skitt avatar Jun 04 '25 07:06 skitt

@skitt https://github.com/kubernetes-sigs/mcs-api/pull/103 covered A records for headless :

  • Headless services are represented by multiple A/AAAA records

I think we can marked this task as complete. AAAA records will be handled later for both service types.

tpantelis avatar Jun 14 '25 01:06 tpantelis

#109 tracks AAAA records, thanks. I’ll open another issue regarding .clusterset.local.

skitt avatar Jun 18 '25 13:06 skitt