[Federation] Remove FEDERATIONS_DOMAIN_MAP references

[shashidharatd]

Remove all references to FEDERATIONS_DOMAIN_MAP as this method is no longer is used and is replaced by adding federation domain map to kube-dns configmap.

cc @madhusudancs @kubernetes/sig-federation-pr-reviews

Release note:

[Federation] Mechanism of adding `federation domain maps` to kube-dns deployment via `--federations` flag is superseded by adding/updating `federations` key in `kube-system/kube-dns` configmap. If user is using kubefed tool to join cluster federation, adding federation domain maps to kube-dns is already taken care by `kubefed join` and does not need further action.

[k8s-reviewable]

This change is 

[madhusudancs]

Reviewed 15 of 15 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

---

cluster/common.sh, line 873 at r1 (raw file):

EOF
  fi
  if [ -n "${FEDERATIONS_DOMAIN_MAP:-}" ]; then

Removes the if without removing the corresponding fi.

---

Comments from Reviewable

[madhusudancs]

Thanks for removing this.

[shashidharatd]

Review status: 14 of 15 files reviewed at latest revision, 1 unresolved discussion.

---

cluster/common.sh, line 873 at r1 (raw file):

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

Removes the if without removing the corresponding fi.

missed it :) thanks madhu, fixed it now

---

Comments from Reviewable

[madhusudancs]

/lgtm
/approve

[madhusudancs]

@shashidharatd this is a user facing change. You might need a release note.

[mikedanese]

/approve

[shashidharatd]

Release note:

[Federation] Mechanism of adding `federation domain maps` to kube-dns deployment via `--federations` flag is superseded by adding/updating `federations` key in `kube-system/kube-dns` configmap. If user is using kubefed tool to join cluster federation, adding federation domain maps to kube-dns is already taken care by `kubefed join` and does not need further action.

[madhusudancs]

@shashidharatd I thought that the bot read the release notes only from the PR description. Do you know for sure that the bot can read the release notes from other comments as well?

[shashidharatd]

@madhusudancs, i thought it might read it, but it didn't :) added now in PR description. is the release notes explanation good enough?

[madhusudancs]

@shashidharatd yeah the note looks good.

Thanks for moving it to the PR description.

[shashidharatd]

Thanks @madhusudancs, can you please remove do-not-merge label?
Also request an lgtm from @jbeda

[mikedanese]

/approve

[shashidharatd]

@jbeda, request an approve label for "hack" related changes.

[shashidharatd]

@jbeda seems busy, @fejta can you please approve this for hack

[shashidharatd]

@k8s-bot non-cri e2e test this

[shashidharatd]

@k8s-bot non-cri e2e test this

[fejta]

/lgtm

Sorry for the delay.

Please /assign @fejta whenever you want my attention. I depend on the PR dashboard to tell me when/where my attention is needed.

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fejta, madhusudancs, mikedanese, shashidharatd

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

• cluster/OWNERS [mikedanese]
• cmd/kubeadm/OWNERS [mikedanese]
• federation/OWNERS [madhusudancs]
• hack/OWNERS [fejta]

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-bot test this [submit-queue is verifying that this PR is safe to merge]

[k8s-github-robot]

Automatic merge from submit-queue