Skip to content
This repository has been archived by the owner on Jun 29, 2022. It is now read-only.

Use kubeconfig content rather than kubeconfig path between functions #623

Closed
invidian opened this issue Jun 15, 2020 · 0 comments · Fixed by #631
Closed

Use kubeconfig content rather than kubeconfig path between functions #623

invidian opened this issue Jun 15, 2020 · 0 comments · Fixed by #631

Comments

@invidian
Copy link
Member

invidian commented Jun 15, 2020

To resolve #608, we should change the way we use kubeconfig in our code from using it as a path to use the content of this file, to decouple it from requiring a file on the disk, as then we would be able to pull this content from any place, e.g. Terraform output/state.

Ideally, kubeconfig content should become a context for all operations we use it for, perhaps in a cluster context, so all operations don't need to accept it explicitly. However, this might be out of scope for this task. See also #603.

invidian added a commit that referenced this issue Jun 15, 2020
As part of #623, which is about using kubeconfig file content rather
than kubeconfig path around, this commits adds Terraform output with
content of kubeconfig file, which can be then pulled during execution
using 'terraform output' command.

Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian added a commit that referenced this issue Jun 16, 2020
As part of #623, which is about using kubeconfig file content rather
than kubeconfig path around, this commits adds Terraform output with
content of kubeconfig file, which can be then pulled during execution
using 'terraform output' command.

Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian added a commit that referenced this issue Jun 23, 2020
As part of #623, which is about using kubeconfig file content rather
than kubeconfig path around, this commits adds Terraform output with
content of kubeconfig file, which can be then pulled during execution
using 'terraform output' command.

Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian added a commit that referenced this issue Jul 1, 2020
As part of #623, which is about using kubeconfig file content rather
than kubeconfig path around, this commits adds Terraform output with
content of kubeconfig file, which can be then pulled during execution
using 'terraform output' command.

Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian added a commit that referenced this issue Jul 1, 2020
As part of #623, which is about using kubeconfig file content rather
than kubeconfig path around, this commits adds Terraform output with
content of kubeconfig file, which can be then pulled during execution
using 'terraform output' command.

Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian added a commit that referenced this issue Jul 3, 2020
As part of #623, which is about using kubeconfig file content rather
than kubeconfig path around, this commits adds Terraform output with
content of kubeconfig file, which can be then pulled during execution
using 'terraform output' command.

Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian added a commit that referenced this issue Aug 4, 2020
As part of #623, which is about using kubeconfig file content rather
than kubeconfig path around, this commits adds Terraform output with
content of kubeconfig file, which can be then pulled during execution
using 'terraform output' command.

Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian added a commit that referenced this issue Aug 4, 2020
As part of #623, which is about using kubeconfig file content rather
than kubeconfig path around, this commits adds Terraform output with
content of kubeconfig file, which can be then pulled during execution
using 'terraform output' command.

Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian added a commit that referenced this issue Aug 21, 2020
As part of #623, which is about using kubeconfig file content rather
than kubeconfig path around, this commits adds Terraform output with
content of kubeconfig file, which can be then pulled during execution
using 'terraform output' command.

Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian added a commit that referenced this issue Aug 27, 2020
As part of #623, which is about using kubeconfig file content rather
than kubeconfig path around, this commits adds Terraform output with
content of kubeconfig file, which can be then pulled during execution
using 'terraform output' command.

Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
invidian added a commit that referenced this issue Sep 2, 2020
As part of #623, which is about using kubeconfig file content rather
than kubeconfig path around, this commits adds Terraform output with
content of kubeconfig file, which can be then pulled during execution
using 'terraform output' command.

Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant