Re-titleing for release note

Also add a TODO at the definitions of the old annotations to remove them after v1.3 is released.

Mostly pretty minor issues. Yay!

We need corresponding docs on this. Both the DNS related docs and the pod-related docs.

@ArtfulCoder sorry if this is in the docs, I couldn't find it.
What would be the behavior when scaling up an RC when the pod template includes the hostname field?

The docs talk about a hostname foo in a subdomain bar can be accessed via foo.bar...etc, but what if there are 2+ replicas of the same pod?

@ArtfulCoder
You must link to the test flake issue which caused you to request this manual re-test.
Re-test requests should be in the form of: k8s-bot test this issue: #<number>
Here is the list of open test flakes.

@ArtfulCoder
You must link to the test flake issue which caused you to request this manual re-test.
Re-test requests should be in the form of: k8s-bot test this issue: #<number>
Here is the list of open test flakes.

Great point - docs pls.
On Apr 28, 2016 5:32 AM, "Rodolfo Carvalho" notifications@github.com
wrote:

@ArtfulCoder https://github.com/ArtfulCoder sorry if this is in the
docs, I couldn't find it.
What would be the behavior when scaling up an RC when the pod template
includes the hostname field?

The docs talk about a hostname foo in a subdomain bar can be accessed via
foo.bar...etc, but what if there are 2+ replicas of the same pod?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#24362 (comment)

GCE e2e build/test passed for commit 8a3ed48.

• Build Log
• Test Artifacts
• Internal Jenkins Results

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

GCE e2e build/test passed for commit 8a3ed48.

• Build Log
• Test Artifacts
• Internal Jenkins Results

Automatic merge from submit-queue

Great point - docs pls.

@ArtfulCoder @thockin I didn't find any mention to the case when the number of replicas of a pod >1 in the code that got merged. I expected it somewhere in cluster/addons/dns/README.md.

Are the docs coming in a follow up? Could you please share a link? Thanks!

@rhcarvalho , for the case of replicas of a pod > 1, we are planning to introduce petsets, that will have some form of templatization for hostname field.
@bprashanth to elaborate further since he is working on petsets.

@ArtfulCoder thanks for the reply. Currently, is it an error to specify a hostname and scale to 2+ replicas? What would the FQDN "foo.bar.my-namespace.svc.cluster.local" point to in the documented example?

I'm following the PetSets PR (#18016), though I thought that was focused on persistent volumes.

I'd like to have both scalable persistent storage and pod addressability by hostname to support MongoDB replica sets with persistent storage.

@rhcarvalho If multiple pods have the same hostname, it is not an error.
You should ideally get back multiple A records. The way I have it right now, causes only one A record to be returned. I will change that behavior to return multiple A records.