Score:0

Can EFS claims live longer than the Kubernetes cluster?

pl flag

We have been writing scripts for setting up an application on AWS via Pulumi, trying to automate everything from scratch to a running application (but via different intermediate stages). The idea was to be able to shut down everything to save costs when the (interactive) application is not needed. The application data should be persisted over EFS however.

Now, it seems that our goal of shutting everything down conflicts with the idea of keeping the data available for next time, because accessing the data requires a "claim" that can only be created with an empty directory on EFS? My understanding is that this would require us to either

  • set up a claim to work with EFS, and then rsync the data into that empty directory, or to
  • keep the claim and thus the Kubernetes cluster.

Is this impression / understanding correct?

At around 1$/day, keeping the cluster up is an option, of course, although it just feels like a waste of resources conceptually.

pl flag
Maybe this question was phrased badly, because it assumed that I need longer-lived EFS PV claims. I have opened a new one focusing on the use case at https://serverfault.com/questions/1084488/can-one-pre-populate-a-directory-e-g-on-efs-for-an-eks-cluster instead.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.