Support services that reference an external service about enhancements

[aglassman]

Thanks for working on this feature, it's been very helpful.

[therc]

I'm also working on node-local services, so perhaps I can help with this. That way, I can blame myself for the ensuing rebases. :-)

[thockin]

The CLI did not, but the API change is in 1.4. http://kubernetes.io/docs/user-guide/services/ - search for "ExternalName"

…

On Mon, Dec 12, 2016 at 6:28 PM, Jimmy Cuadra ***@***.***> wrote: This is stable in 1.5? Are there docs? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#33 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFVgVKpwQ33RKcvMjd5az7o6_WdQP_VUks5rHgLcgaJpZM4JQHJ2> .

[ncdc]

@rata do you think you'll be able to code this in time for 1.4?

[rata]

On Mon, Jul 25, 2016 at 07:58:11AM -0700, Andy Goldstein wrote:

@rata do you think you'll be able to code this in time for 1.4?

My plan was to start working on this on Tuesday, as I have an exam on Tuesday at
university. IS this too late?

I think the change can be not so hard, for the quick look I had at th code (it
seems we just created a skydns backend in kube-dns, and seems is easy to add
another type response, CNAME, for what I looked).

But if you are concerned about this, please go ahead and work on this! I can
maybe join later and test or something :-)

[ncdc]

@rata that should be fine. I was just checking in. Thanks!

[idvoretskyi]

@smarterclayton @rata which SIG is responsible for this feature?

[ncdc]

I would assume network

[idvoretskyi]

@ncdc thanks

[rata]

@ncdc @smarterclayton @thockin I'm more busy than I expected (at $DAYJOB and university) and I'm not sure I'll make it on time on this. Do you want to start working on this, and if I have some time maybe jump on this later?

[rata]

I'm really really sorry, and I wish I could work on this, but I'm already late (planned to start 2 days ago) and more busy than I expected. I think it's better to say this early so this gets implemented in 1.4. But I'm really really sorry :-/

[aronchick]

@smarterclayton Do you think you can find someone else to tackle? Or should we just punt to 1.5.

[rata]

@therc thanks again! :)

[idvoretskyi]

@therc thank you for your help, assigned you as an assignee.

[goltermann]

In a meeting today, it was mentioned that this is missing v1.4. I'm moving to the v1.5 milestone. Please bring back to v1.4 if that's not accurate.

[therc]

Two more things needed: rejecting Ports (as already agreed with @thockin) and teaching kubectl about the new field.

[thockin]

@therc Can you make sure the last few tickboxes are OK to be checked?

[idvoretskyi]

Targeting GA in 1.5.

[therc]

This is mostly working already in 1.4, but it occurred to me that there's no way to create such a service from the command line without using a YAML/JSON file.

kubectl expose doesn't feel exactly right, because the whole point of ExternalName services is that there are no pods to be exposed. If that's still the way it's going to be done, the command line syntax will have to be changed from (-f FILENAME | TYPE NAME) ... to (-f FILENAME | --external-name NAME | TYPE NAME) ....

Opening an issue for that.

[thockin]

kubectl create service is the correct command tree to explore

On Thu, Oct 13, 2016 at 9:04 AM, Rudi C [email protected] wrote:

This is mostly working already in 1.4, but it occurred to me that there's
no way to create such a service from the command line without using a
YAML/JSON file.

kubectl expose doesn't feel exactly right, because the whole point of
ExternalName services is that there are no pods to be exposed. If that's
still the way it's going to be done, the command line syntax will have to
be changed from (-f FILENAME | TYPE NAME) ... to (-f FILENAME |
--external-name NAME | TYPE NAME) ....

Opening an issue for that.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#33 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFVgVPmK08AXwK1Yw0eao88qgktxZ2Qiks5qzlaXgaJpZM4JQHJ2
.

[thockin]

@therc I don't think the CLI for this went in, did it? Any reason to not call what we have GA, anyway? Are you active on the CLI part or should we just open a new issue for it?

[jimmycuadra]

This is stable in 1.5? Are there docs?

[idvoretskyi]

@smarterclayton @therc can you confirm the feature development has been completed and issue can be closed?

[thockin]

@therc Can we count on you for CLI wrapup? would love to close this...

[idvoretskyi]

@thockin @therc sooo, any final decision?

[thockin]

@therc ping?

…

On Thu, Jan 5, 2017 at 9:24 AM, Ihor Dvoretskyi ***@***.***> wrote: @thockin <https://github.com/thockin> @therc <https://github.com/therc> sooo, any final decision? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#33 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFVgVB2ih9pim5d_LqxYdYzkyz-NZe7fks5rPSdKgaJpZM4JQHJ2> .

[therc]

Just got back from vacation and a hectic office move, working my way through email backlog.
I can pick up any leftover items, but I think kubectl create support was implemented by @adohe in kubernetes/kubernetes#34789
Was there anything else you had in mind? My next related step was allowing the built-in kubernetes.default service to also be an ExternalName service, to pave the way for a migration to api.kube-system or something along those lines. But if you have something else that's higher priority, I can tackle that first.

[thockin]

Oh, great, I missed that :) Can you cross-check the un-ticked boxes on here, and if everything is done, we can close this out?

…

On Tue, Jan 24, 2017 at 9:27 AM, Rudi C ***@***.***> wrote: Just got back from vacation and a hectic office move, working my way through email backlog. I can pick up any leftover items, but I think kubectl create support was implemented by @adohe <https://github.com/AdoHe> in kubernetes/kubernetes#34789 <kubernetes/kubernetes#34789> Was there anything else you had in mind? My next related step was allowing the built-in kubernetes.default service to also be an ExternalName service, to pave the way for a migration to api.kube-system or something along those lines. But if you have something else that's higher priority, I can tackle that first. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#33 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFVgVF0ojvj2dhIgnMo1TSq-xF7Qmqvzks5rVjSBgaJpZM4JQHJ2> .

[therc]

Unfortunately, I think only Clayton or another owner can edit the issue description. I just went through the checklist and it looks to me like everything can be ticked off.

Regarding "detailed docs and examples", I have something with more use cases, originally for internal use, that I have almost entirely re-purposed as a blog post. I'm not sure how kosher it is to add links from Kubernetes docs to random external blog posts; I suspect not very, given link rot and the like. Perhaps I could re-adapt it again as a tutorial in the docs repo? This issue can be closed anyway.

[thockin]

DONE

[idvoretskyi]

@therc @thockin does this feature target 1.6 (as per @mdelio modified milestone) or it has been finally implemented in 1.5 yet?

If this is still 1.6, I'd like to reopen it and keep in this state during the release.

[therc]

The main feature is in 1.5 already and can be used through YAML files. It's the kubectl support that will land in 1.6. I think it'd be worthy of a 1.5 cherrypick.

[adohe-zz]

@idvoretskyi @therc yes, the kubectl support land in 1.6, shall we cherrypick it against 1.5?

[liggitt]

We don't typically backport new features

[adohe-zz]

Get it~