kubernetes / kubernetes/kops

document .kops file - does VIPER work

Open
#2,435 10 comments 0 reactions 0 assignees View on GitHub
lifecycle/frozen
Dominant language
Go
Stars
16.7k
Forks
4.7k
Avg merge
17h 21m
Merged PRs (30d)
68

Description

I have the following config file installed and run:

```
$cat $HOME/.kops
KOPS_STATE_STORE=s3://aws.k8spro.com
$ kops toolbox inventory -f in-v1alpha2.yaml
unable to load client set State Store: Required value: Please set the --state flag or export KOPS_STATE_STORE.
A valid value follows the format s3://.
A s3 bucket is required to store cluster state information.

```
And that does not work. We have https://github.com/spf13/viper installed, but I do not know if it is actually wired in correctly ....

Contributor guide

Open the contributing guide

Research direction

Start with the `kops toolbox inventory` command and the reported `$HOME/.kops` configuration. Check how Viper is wired into configuration loading and whether `KOPS_STATE_STORE` is read from that file. Done means documenting the supported configuration method and correcting the example or behavior if needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.