-
Notifications
You must be signed in to change notification settings - Fork 8
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
docs: describe secure persistent volumes #932
Conversation
37c58ed
to
a1be10a
Compare
|
Co-authored-by: Thomas Tendyck <[email protected]>
b20ac4b
to
e32c66f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, LGTM!
We're mixing (and probably have been before) workflows into the architecture section.
Maybe we should have a dedicated workflow section as in Constellation at one point?
Not urgent and I'm open to suggestions:-)
I agree that workflows should not go into the architecture section, but I did not mean to write a workflow here. How about creating follow-up tickets that replace this section with a working example, similar to the Emojivoto-servicemesh experience? |
Sounds good! |
No description provided.