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.

Sign up for GitHub

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

Jump to bottom

Get kubeconfig (admin.conf) from master without SSH #91

Closed
karan opened this issue May 2, 2018 · 6 comments
Closed

Get kubeconfig (admin.conf) from master without SSH #91

karan opened this issue May 2, 2018 · 6 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone
Next

Comments

@karan
Copy link

karan commented May 2, 2018

Don't know how.

kops seems to build the kubeconfig from raw information (CA, certs etc). Duplicating the CA locally seems not so safe.
@rsdcastro
Copy link

For now, SSH is a dependency so it seems fine to fetch it using it. This should be considered as a future improvement.

@dims
Copy link
Member

dims commented Jun 11, 2018

duplicate of https://github.com/kubernetes-sigs/cluster-api/issues/160 ?

@roberthbailey roberthbailey transferred this issue from kubernetes-sigs/cluster-api Jan 10, 2019
@roberthbailey roberthbailey added this to the Next milestone Jan 11, 2019
@roberthbailey roberthbailey added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Jan 11, 2019
@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 Apr 28, 2019
@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

@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 May 28, 2019
@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

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

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

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.

richardchen-db added a commit to databricks/cluster-api-provider-gcp-1 that referenced this issue May 16, 2024
@richardchen-db
Fix replicas count (kubernetes-sigs#91)
a8d9471 
* update

* Use math.Ceil

* update
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
Next
Development

No branches or pull requests
6 participants
@dims @rsdcastro @karan @roberthbailey @k8s-ci-robot @fejta-bot