kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Mention about possible state store vendors in error message

This commit is contained in:
Kenjiro Nakayama 2018-11-25 11:12:00 +09:00
parent 4eeba152cd
commit 60c152c89d
2 changed files with 7 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
cmd/kops/util/factory.go
View File

@ -53,12 +53,12 @@ func NewFactory(options *FactoryOptions) *Factory {
const (
STATE_ERROR = `Please set the --state flag or export KOPS_STATE_STORE.
A valid value follows the format s3://<bucket>.
A s3 bucket is required to store cluster state information.`
For example, a valid value follows the format s3://<bucket>.
You can find the supported stores in https://github.com/kubernetes/kops/blob/master/docs/state.md.`
INVALID_STATE_ERROR = `Unable to read state store s3 bucket.
Please use a valid s3 bucket uri when setting --state or KOPS_STATE_STORE env var.
A valid value follows the format s3://<bucket>.
INVALID_STATE_ERROR = `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.`
)

6
docs/philosophy.md
View File

@ -32,9 +32,7 @@ There are two primary types:
## State Store
The API objects are currently stored in an abstraction called a "state store", and currently the only implemented
storage is an S3 bucket. The storage of files in the S3 bucket is an implementation detail. Expect more state
stores soon. For example, it might be convenient to put the InstanceGroup into the kubernetes API itself.
The API objects are currently stored in an abstraction called a "state store". [state.md](/docs/state.md) has more detail.
## Configuration inference
@ -53,4 +51,4 @@ single source of truth and it is practical to implement alternatives to nodeup &
such as kubelet might read their configuration directly from the state store in future, eliminating the need to
have a management process that copies values around.
Currently the 'completed' cluster specification is stored in the state store in a file called `cluster.spec`
Currently the 'completed' cluster specification is stored in the state store in a file called `cluster.spec`