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

K8SSAND-703 ⁃ Create script to copy contexts from one kubeconfig into another #37

Closed
jsanda opened this issue Jul 13, 2021 · 1 comment
Closed

K8SSAND-703 ⁃ Create script to copy contexts from one kubeconfig into another #37

jsanda opened this issue Jul 13, 2021 · 1 comment
Labels
component: multi-cluster

Comments

@jsanda
Copy link
Contributor

jsanda commented Jul 13, 2021 •
edited by sync-by-unito bot
Loading

I have written the setup-kind-multicluster.sh script that creates kind clusters. It also generates a kubeconfig file that consists of entries only for the created clusters. This file is written to <project-root>/build/kubeconfig.

It would be useful to have another script that could copy the context, cluster, and user objects from one kubeconfig file into another one. This would make it easy to build test kubeconfig files from arbitrary clusters, not just the ones created with setup-kind-multicluster.sh.

┆Issue is synchronized with this Jira Task by Unito
┆Epic: CI/CD Environment Bootstrap
┆Fix Versions: k8ssandra-operator-1.0.0-alpha.1
┆Issue Number: K8SSAND-703
┆Priority: Medium
@jsanda
Copy link
Contributor Author

jsanda commented Sep 11, 2021

Closed by #89

@jsanda jsanda closed this as completed Sep 11, 2021
@sync-by-unito sync-by-unito bot changed the title Create script to copy contexts from one kubeconfig into another K8SSAND-703 ⁃ Create script to copy contexts from one kubeconfig into another Nov 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component: multi-cluster
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jsanda