Skip to content
This repository has been archived by the owner on Apr 21, 2019. It is now read-only.

Enable federation apiserver connect to external etcd #30

Closed
irfanurrehman opened this issue Oct 30, 2017 · 9 comments
Closed

Enable federation apiserver connect to external etcd #30

irfanurrehman opened this issue Oct 30, 2017 · 9 comments
Labels
area/federation kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/multicluster Categorizes an issue or PR as relevant to sig-multicluster.

Comments

@irfanurrehman
Copy link
Contributor

Issue by gyliu513
Wednesday Aug 16, 2017 at 06:15 GMT
Originally opened as kubernetes/kubernetes#50737

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
If I want to enable the federation control panel, then I need to use kubefed init to install etcd and control panel. For etcd, as the kubernetes already have etcd running, so I want to re-use the existing etcd in my kubernetes cluster and do not want to install a new etcd for federation only.

What you expected to happen:
I can specify external etcd when using kubefed init.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration**:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:

/sig federation

/cc @kubernetes/sig-federation-feature-requests
@irfanurrehman irfanurrehman added area/federation kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/multicluster Categorizes an issue or PR as relevant to sig-multicluster. labels Oct 30, 2017
@irfanurrehman
Copy link
Contributor Author

Comment by gyliu513
Wednesday Aug 16, 2017 at 09:46 GMT

/cc @liqlin2015

@irfanurrehman
Copy link
Contributor Author

Comment by lukaszo
Wednesday Aug 30, 2017 at 14:32 GMT

As the workaround, after init, you can edit deployment federation-apiserver, change --etcd-servers line and delete etcd container.

Other projects, like kubeadm, are using --config option to pass the whole configuration. @madhusudancs are there any plans to move to config based configuration?

Another option is to add --etcd-servers to kubefed join but such option was removed from kubeadm and only --config is accepted.

@irfanurrehman
Copy link
Contributor Author

Comment by gyliu513
Thursday Aug 31, 2017 at 02:17 GMT

How about enabling connect to external etcd when kubefed init? @lukaszo

@irfanurrehman
Copy link
Contributor Author

Comment by quinton-hoole
Saturday Sep 02, 2017 at 00:19 GMT

#50815

@irfanurrehman
Copy link
Contributor Author

cc @gyliu513

@irfanurrehman irfanurrehman mentioned this issue Oct 30, 2017
Closed
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 24, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 23, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area/federation kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/multicluster Categorizes an issue or PR as relevant to sig-multicluster.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@irfanurrehman @k8s-ci-robot @fejta-bot