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
PetSet Documentation #510
Comments
@chrislovecnm what do you need, the c* example from contrib is insufficient? |
Short term I would really like the definitions for volumeClaimTemplates:
# These are converted to volume claims by the controller
# and mounted at the paths mentioned above.
- metadata:
name: cass_datadir
annotations:
volume.alpha.kubernetes.io/storage-class: anything
spec:
accessModes: [ "ReadWriteOnce" ]
resources:
requests:
storage: 10Gi I have a demo for the product launch... so just trying to get the example correct, so that I can build the demo off of it. |
jump on slack. will take notes from there and distil into docs. |
@bprashanth any word on ETA? |
For those watching, see the bottom of: |
E2Es are getting pushed in now. Docs will follow. |
@bgrant0607 what branch/tag should we use for PetSet or it is already in master ? |
The examples in https://github.com/kubernetes/contrib/tree/master/pets will work against HEAD |
Make sure that we get
In the documentation. Also should we be able to edit that field with a cc @paralin |
Yes. |
Nice, cassandra works great, petset seems like it's really coming along well! I'll try to contribute with more dogfooding/testing in the coming days. |
I'm basically staying away from C* assuming Chris and you are going to write up a good example so please do |
@bprashanth ... @paralin is actually filing bugs on my project about C*, so yes we will have examples. I just wanted to make sure that his questions, which are about Petsets, get into the docs. |
Nudge ... It would be good to get some of this done, by next Monday. I am going to be presenting, and helping with a hack night on PetSet. There shall be questions, unless @bprashanth you want to be there 😁 |
Not sure whether this is your question, but docs should be in the release-1.3 branch. |
ETA is Tuesday. Thought I'd have something by this morning but software happened. |
But software happened... Gotta remember that one. Awesome ... Thanks |
@bprashanth we done?? Shall we close this? |
Closing this out. |
I know it will be worked on before the 1.3 release. Just let me know when ...
I kinda need it ...
cc: @bgrant0607
The text was updated successfully, but these errors were encountered: