Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a warning that kops is not AWS free tier friendly #5880

Closed
prabhu opened this issue Oct 5, 2018 · 5 comments

Comments

@prabhu
Copy link

@prabhu prabhu commented Oct 5, 2018

1. Describe IN DETAIL the feature/behavior/change you would like to see.
It appears like kops is storing several files in the s3 store and making numerous calls in the process to burn out the 2000 free API calls in just 2 or 3 attempts.

kops version: 1.10.0

2. Feel free to provide a design supporting your feature request.
Consider using tar.gz for s3 or suggestion on a local filesystem only mode for dev purposes. If this mode already exist please improve the README.md or point me to the right direction so that I can send a PR

Thanks

@fejta-bot

This comment has been minimized.

Copy link

@fejta-bot fejta-bot commented Jan 3, 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@joffreypannequin

This comment has been minimized.

Copy link

@joffreypannequin joffreypannequin commented Jan 6, 2019

I am hitting the same issue described by @prabhu . I am trying to host a small kubernetes installation within AWS free tier. I was trying the local storage approach.

According to the documentation in https://github.com/kubernetes/kops/blob/master/docs/state.md we should be able to use local file storage with

local filesystem (file://)

But when trying that, i get:

$ kops -v9 create cluster --state=file:///var/lib/kops-state-store
I0106 20:32:09.482495    4268 factory.go:68] state store file:///var/lib/kops-state-store

State Store: Invalid value: "file:///var/lib/kops-state-store": 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.

This error message is coming from

if !vfs.IsClusterReadable(basePath) {
return nil, field.Invalid(field.NewPath("State Store"), registryPath, INVALID_STATE_ERROR)
}

Because of

kops/util/pkg/vfs/vfs.go

Lines 114 to 115 in af4df08

case *FSPath:
return false

So a local filesystem is not Cluster Readable and as such cannot be used for kops state store, if i understand correctly. So the documentation does not seem correct. Unless i am missing something.

Thanks for the help.

@fejta-bot

This comment has been minimized.

Copy link

@fejta-bot fejta-bot commented Feb 5, 2019

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@fejta-bot

This comment has been minimized.

Copy link

@fejta-bot fejta-bot commented Mar 7, 2019

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

@k8s-ci-robot k8s-ci-robot commented Mar 7, 2019

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.