cloud-provider-azure icon indicating copy to clipboard operation
cloud-provider-azure copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Add support for dualstack service

Open feiskyer opened this issue 3 years ago • 5 comments

What would you like to be added:

Only single stack service (either ipv4 or ipv6) is supported today as service.Spec.ClusterIP is used to determine the public IP family. We should add support for dualstack services and allocate both ipv4 and ipv6 public IPs.

Why is this needed:

feiskyer avatar Sep 24 '21 01:09 feiskyer

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR 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 Dec 23 '21 02:12 k8s-triage-robot

/remove-lifecycle stale

feiskyer avatar Dec 24 '21 01:12 feiskyer

/milestone v1.24

feiskyer avatar Jan 18 '22 02:01 feiskyer

related: https://github.com/kubernetes-sigs/cluster-api-provider-azure/pull/2154

MartinForReal avatar May 07 '22 03:05 MartinForReal

/assign

lzhecheng avatar Jul 28 '22 03:07 lzhecheng

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR 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 Oct 26 '22 03:10 k8s-triage-robot

/remove-lifecycle stale

lzhecheng avatar Oct 26 '22 05:10 lzhecheng

/milestone v1.27

feiskyer avatar Jan 12 '23 02:01 feiskyer

Developing in this branch https://github.com/lzhecheng/cloud-provider-azure/tree/support-ds.dev

lzhecheng avatar Jan 21 '23 00:01 lzhecheng

/close

lzhecheng avatar Jun 26 '23 06:06 lzhecheng

@lzhecheng: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot avatar Jun 26 '23 06:06 k8s-ci-robot