Skip to content
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.

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

How to Verify the peering is established ? #14211

Closed
gowrisankar22 opened this issue Jan 23, 2021 · 4 comments
Closed

How to Verify the peering is established ? #14211

gowrisankar22 opened this issue Jan 23, 2021 · 4 comments
Labels
AKS Container Service customer-reported Issues that are reported by GitHub users external to the Azure organization. Network - Virtual Network question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@gowrisankar22
Copy link

gowrisankar22 commented Jan 23, 2021

I have a below scenario, to check peering is established. Can you help me with how easily we can do it?

  1. I have a first vnet called Vnet-A
  2. I have a second vnet called Vnet-B where my Kubernetes operator is running.
    Using golang SDK from my Vnet-B I want to check to peer with Vnet-A is established so that I can implement the same in my k8s operator. I am not sure currently how can I do it?

BRs, Gowrisankar

@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jan 23, 2021
@ArcturusZhang ArcturusZhang added Peering Service Attention Workflow: This issue is responsible by Azure service team. labels Jan 25, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jan 25, 2021
@ArcturusZhang ArcturusZhang removed Peering Service Attention Workflow: This issue is responsible by Azure service team. labels Jan 25, 2021
@ghost ghost added the needs-team-triage Workflow: This issue needs the team to triage. label Jan 25, 2021
@ArcturusZhang ArcturusZhang added Network AKS Container Service and removed needs-team-triage Workflow: This issue needs the team to triage. Network labels Jan 25, 2021
@ArcturusZhang
Copy link
Member

Hi @gowrisankar22 thanks for this issue!

I have tagged this issue so that someone from the corresponding service team might take a look at this issue and give you an API how to do it.

@ArcturusZhang ArcturusZhang added the Service Attention Workflow: This issue is responsible by Azure service team. label Jan 25, 2021
@ghost
Copy link

ghost commented Jan 25, 2021

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/aks-pm.

Issue Details

I have a below scenario, to check peering is established. Can help me with how easily we can do it?

  1. I have a first vnet called Vnet-A
  2. I have a second vnet called Vnet-B where my Kubernetes operator is running.
    Using golang SDK from my Vnet-B I want to check to peering with Vnet-A is established so that I can implement the same in my k8s operator. I am not sure currently how can I do it?

BRs, Gowrisankar

Author: gowrisankar22
Assignees: -
Labels:

AKS, Container Service, Service Attention, customer-reported, question

Milestone: -

@ghost
Copy link

ghost commented Jan 25, 2021

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @vnetsuppgithub.

Issue Details

I have a below scenario, to check peering is established. Can help me with how easily we can do it?

  1. I have a first vnet called Vnet-A
  2. I have a second vnet called Vnet-B where my Kubernetes operator is running.
    Using golang SDK from my Vnet-B I want to check to peering with Vnet-A is established so that I can implement the same in my k8s operator. I am not sure currently how can I do it?

BRs, Gowrisankar

Author: gowrisankar22
Assignees: -
Labels:

AKS, Container Service, Network - Virtual Network, Service Attention, customer-reported, question

Milestone: -

@gowrisankar22
Copy link
Author

any update on this ?

@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
AKS Container Service customer-reported Issues that are reported by GitHub users external to the Azure organization. Network - Virtual Network question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants