Ask questionsUnable to use a local filesystem state store
kops version are you running? The command
kops version, will display
2. What Kubernetes version are you running?
kubectl version will print the
version if a cluster is running or provide the Kubernetes version specified as
3. What cloud provider are you using?
4. What commands did you run? What is the simplest way to reproduce this issue?
kops create cluster --state 'file:///tmp/kops-state' --zones us-east-1a foo.cluster.k8s.local
5. What happened after the commands executed?
State Store: Invalid value: "file:///tmp/kops-state": Unable to read state store. Please use a valid state store when setting --state or KOPS_STATE_STORE env var. For example, a valid value follows the format s3://<bucket>. Trailing slash will be trimmed.
Issue is caused by
vfs.IsClusterReadable returning false for all filesystem state storage as called by
6. What did you expect to happen?
Not to get an error about being unable to read the state store.
7. Please provide your cluster manifest. Execute
kops get --name my.example.com -o yaml to display your cluster manifest.
You may want to remove your cluster name and other sensitive information.
8. Please run the commands with most verbose logging by adding the
-v 10 flag.
Paste the logs into this report, or in a gist and provide the gist link here.
I0213 14:25:54.779621 34407 factory.go:68] state store file:///tmp/kops-state State Store: Invalid value: "file:///tmp/kops-state": Unable to read state store. Please use a valid state store when setting --state or KOPS_STATE_STORE env var. For example, a valid value follows the format s3://<bucket>. Trailing slash will be trimmed.
9. Anything else do we need to know?
The bug was triggered when attempting to build a CI workflow around:
.spec.configBaseto refer to the local directory
kops replace -f <candidate.yaml> --state file:///path/to/local/state/dir
kops update cluster <cluster_name> --state file:///path/to/local/state/dir
In a CI workflow, this would allow us to preview (for example, during a pull request) how a
kops update cluster would run, without touching the actual remote S3 state bucket (from running
Answer questions qrilka
The docs https://github.com/kubernetes/kops/blob/master/docs/state.md list many supported state stores but the source code looks like SSH, local FS and MemFS are explicitly not allowed