-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[WIP] Dev guide #1104
[WIP] Dev guide #1104
Conversation
Signed-off-by: JENNIFER RONDEAU <[email protected]>
Signed-off-by: JENNIFER RONDEAU <[email protected]>
Signed-off-by: JENNIFER RONDEAU <[email protected]>
4728100
to
27f5003
Compare
Signed-off-by: JENNIFER RONDEAU <[email protected]>
Signed-off-by: JENNIFER RONDEAU <[email protected]>
|
||
For detailed examples, see the YAML files in the [examples directory][6]. | ||
|
||
TODO FROM JFR: how much introductory/explanatory material should be provided here? This is an audience question. To date, it seems as though outside contributors to Ark have been primarily folks deeply familiar with K8s and the dev environment it requires. PR #1131 got me started wondering about k8s newcomers -- although that user seems not to have been a potential code contributor (at least, not yet). IFF y'all want to support newcomer contributions, I think there's quite a bit of material missing. See also TODOs in other files. |
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.
Add some refs to CRDs/controllers as relevant pre-req knowledge
@@ -0,0 +1,3 @@ | |||
* Test your build |
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.
Add some general guidelines on getting your build deployed, some standard flows to go through, where to look for success/failure/diagnostic info
Signed-off-by: JENNIFER RONDEAU <[email protected]>
n.b. please long TODO in new |
Sorry @Bradamant3 but I'm going to close this PR as it's stale :) We have xrefs to it in the relevant issues so we can mine it for content if/when we work on those issues. |
Current state: content reorg only begun. Not sure it's quite right. Questions for reviewers: