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

Provide a consistent DNS name for EC PODs #26

Closed
palokam opened this issue Jun 23, 2020 · 4 comments · Fixed by #28 or #30
Closed

Provide a consistent DNS name for EC PODs #26

palokam opened this issue Jun 23, 2020 · 4 comments · Fixed by #28 or #30
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request k8s spec

Comments

@palokam
Copy link

palokam commented Jun 23, 2020

We have to provide a consistent DNS name for EC PODs for TC/any POD to interact with

Problem : As it stands looks like we do not have any SVC attached to the pod, it is difficult and impossible to know the POD DNS for developer, it is also subjected to change if POD restarts that will break the TC integration or anybody who had the original POD name used for their connectivity...

Solution : We need provide a consist DNS name for EC POD (Client, Server, GW etc), Via K8S Service

@ayasuda2OO3 ayasuda2OO3 added documentation Improvements or additions to documentation enhancement New feature or request spec labels Jun 23, 2020
@ayasuda2OO3 ayasuda2OO3 added this to the v0.1.1 milestone Jun 23, 2020
@ayasuda2OO3
Copy link
Contributor

ayasuda2OO3 commented Jun 23, 2020

Proposal acknowledged. PR in progress. @palokam @sheshankgujjari @simran3695

@ayasuda2OO3 ayasuda2OO3 linked a pull request Jun 23, 2020 that will close this issue
@ayasuda2OO3 ayasuda2OO3 removed a link to a pull request Jun 24, 2020
@ayasuda2OO3 ayasuda2OO3 linked a pull request Jun 24, 2020 that will close this issue
@ayasuda2OO3
Copy link
Contributor

The service spec has been added to the agent char in #28 for review. @palokam

@ayasuda2OO3
Copy link
Contributor

ayasuda2OO3 commented Jun 24, 2020

FYI the release (v1.0.0-v1.1beta) is ready for the usage. @palokam @simran3695 @sheshankgujjari please share the feedback for closing. Thanks!

@ayasuda2OO3
Copy link
Contributor

Closed solution accepted #33 #33 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request k8s spec
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants