Output of linode-cli lke kubeconfig-view is not a yaml.
See original GitHub issueTo reproduce:
Create example lke cluster with linode-cli:
linode-cli lke cluster-create --label kubtest --region us-central --k8s_version 1.21 --node_pools.type g6-standard-1 --node_pools.count 3
Wait until all is provisioned and running.
Find cluster id:
linode-cli lke clusters-list
Get kubeconfig:
linode-cli lke kubeconfig-view <cluster ID>
Appears encrypted, but there is minimal documentation on this. Downloading from dashboard works as expected.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
How can I obtain the kubeconfig file for my LKE cluster using ...
Kubeconfig output from API/CLI. The most important detail to mention first is that our API and Linode CLI provide the Kubeconfig file as...
Read more >Provisioning Kubernetes clusters on Linode with Terraform
TL;DR: In this article, you will learn how to create Kubernetes clusters on Linode Kubernetes Engine (LKE) with the Linode CLI and Terraform....
Read more >linode-api-docs/openapi.yaml at development - GitHub
Source for the Linode API v4 Docs. Contribute to linode/linode-api-docs development by creating an account on GitHub.
Read more >LKE: A solid k8s offering from Linode - Fresh/Brewed
The UI appears to allow us to create a cluster of several node pool sizes which sets it apart from the standard offering...
Read more >https://raw.githubusercontent.com/linode/linode-ap...
<a target="_top" href="/docs/api/openapi.yaml">Download the Linode OpenAPI ... lang: CLI source: > linode-cli lke kubeconfig-view 12345 delete: operationId: ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Perhaps a more accurate issue report would be regarding the feedback of --help in this case:
As opposed to docs, which provide the adequate: “The Base64-encoded Kubeconfig file for this Cluster.”
The docs say that this operation returns a base64-encoded kubeconfig - you should be able to retrieve the yaml by decoding the output blob. You can do that in all one step like this:
I do agree that it would be nice if this operation returned the YAML without needing manual decoding, though; I’ll look into it. Thanks for the report 👍