Skip to content
This repository has been archived by the owner on Mar 26, 2018. It is now read-only.

Improve persistence of IPAM data #27

Closed
bboreham opened this issue Oct 6, 2016 · 6 comments
Closed

Improve persistence of IPAM data #27

bboreham opened this issue Oct 6, 2016 · 6 comments

Comments

@bboreham
Copy link
Contributor

bboreham commented Oct 6, 2016

Currently weave-daemonset.yaml specifies an emptyDir volume which is deleted when the pod is deleted. Since upgrading weave-kube require deleting the pods, this is unsafe.

Reading http://kubernetes.io/docs/user-guide/volumes/, I don't see an obviously better choice.

@Bregor
Copy link

Bregor commented Oct 6, 2016

I think regular hostPath will suit this as well.
Example:

      volumeMounts:
        - mountPath: /weave_data
          name: data
...
  volumes:
    - name: data
      hostPath:
        path: /var/lib/weave-kube

@bboreham
Copy link
Contributor Author

bboreham commented Oct 6, 2016

Sure, but is there a hostPath we can guarantee to be able to write to on every Linux distro?

CoreOS, for instance, mounts loads of things read-only.

@Bregor
Copy link

Bregor commented Oct 6, 2016

CoreOS mounts /usr for read-only, but /var and /opt are available to be overwritten.

@awh awh removed the enhancement label Oct 7, 2016
@awh
Copy link
Contributor

awh commented Oct 12, 2016

@Bregor
Copy link

Bregor commented Oct 12, 2016

Petset without "normal" network fs is bloody hell. Regular hostPath will be much better for this task I mean.

@awh
Copy link
Contributor

awh commented Nov 8, 2016

This issue was moved to weaveworks/weave#2610

@awh awh closed this as completed Nov 8, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants