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

[Federation] Fix the comments on FederationNameAnnotation #44472

Merged
merged 1 commit into from
Apr 25, 2017

Conversation

perotinus
Copy link
Contributor

Follow-up for minor issues raised in #42683

NONE

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Apr 13, 2017
@k8s-ci-robot
Copy link
Contributor

Hi @perotinus. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with @k8s-bot ok to test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

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. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Apr 13, 2017
// applied to all API objects associated with that federation.
// the federation that that a federation control plane component is associated
// with. It must be applied to all the API types that represent that federation
// control plane components in the host cluster.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@madhusudancs Currently, I've been annotating objects in both the host and joining clusters. Do we just want to annotate objects in the joining cluster?

@k8s-reviewable
Copy link

This change is Reviewable

@k8s-github-robot k8s-github-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. release-note-none Denotes a PR that doesn't merit a release note. labels Apr 13, 2017
@perotinus
Copy link
Contributor Author

cc @madhusudancs

@madhusudancs
Copy link
Contributor

A minor nit.


Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions.


federation/apis/federation/annotations.go, line 20 at r1 (raw file):

// FederationNameAnnotation is the annotation which holds the name of
// the federation that that a federation control plane component is associated

s/that that/that/


federation/apis/federation/annotations.go, line 22 at r1 (raw file):

Previously, perotinus (Jonathan MacMillan) wrote…

@madhusudancs Currently, I've been annotating objects in both the host and joining clusters. Do we just want to annotate objects in the joining cluster?

We definitely want to annotate objects in the host cluster. We create a number of objects in the host cluster and we want to keep track of them.

Annotating objects in the joining cluster is useful too, esp. if the cluster is part of multiple federations. Feel free to fix the doc string accordingly.


Comments from Reviewable

@perotinus
Copy link
Contributor Author

Review status: 0 of 1 files reviewed at latest revision, 2 unresolved discussions.


federation/apis/federation/annotations.go, line 20 at r1 (raw file):

Previously, madhusudancs (Madhusudan.C.S) wrote…

s/that that/that/

D'oh. Fixed.


federation/apis/federation/annotations.go, line 22 at r1 (raw file):

Previously, madhusudancs (Madhusudan.C.S) wrote…

We definitely want to annotate objects in the host cluster. We create a number of objects in the host cluster and we want to keep track of them.

Annotating objects in the joining cluster is useful too, esp. if the cluster is part of multiple federations. Feel free to fix the doc string accordingly.

Oh, yes, of course! I think that's what I meant to say.


Comments from Reviewable

@nikhiljindal
Copy link
Contributor

@k8s-bot ok to test

@k8s-ci-robot k8s-ci-robot removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Apr 19, 2017
@madhusudancs
Copy link
Contributor

/lgtm
/approve


Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 2 unresolved discussions.


Comments from Reviewable

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 25, 2017
@k8s-github-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: madhusudancs, perotinus

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@k8s-github-robot k8s-github-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 25, 2017
@k8s-github-robot
Copy link

Automatic merge from submit-queue (batch tested with PRs 44607, 44472, 44482)

@k8s-github-robot k8s-github-robot merged commit d059c32 into kubernetes:master Apr 25, 2017
@perotinus perotinus deleted the annotation_fixes branch May 10, 2017 20:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants