Add tutorial for headless install of SlackerNews with EC #3519
Conversation
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
replicated-ci
added
type::docs
paigecalvert
changed the title
|
Moved helm cli tutorial to new pr #3524 |
| cd ../../ | ||
| ``` | ||
|
|
||
| 1. Download the release manifests: |
There was a problem hiding this comment.
hosted the release manifests so that people don't have to do all the copy and pasting. let's the focus on the install part
There was a problem hiding this comment.
that's a good idea. i'm curious about the two part approach, download the chart separately from the manifests. is there a reason to do that versus just hosting the full release in a tarball and then they just untar and can proceed?
There was a problem hiding this comment.
That's a good point...maybe just having them step through it to be a little more aware what all the files are, but there could still be a step to list everything the release to see what's included
There was a problem hiding this comment.
updated to put these in a single tarball
| type: 'category', | ||
| label: 'Tutorials', | ||
| items: [ | ||
| 'vendor/tutorial-embedded-cluster-automation', |
There was a problem hiding this comment.
^ this will get one more item once I finish #3524
|
|
||
| * Download the Helm chart and release manifests for the sample SlackerNews application | ||
| * Create a release for SlackerNews in the Replicated Platform | ||
| * Create a ConfigValues file to pass application-specific configuration values to the installation from the command line |
There was a problem hiding this comment.
note: this branch is out of date with main, but I plan on linking to the new configvalues reference topic here and probably in the tutorial as well
| cd ../../ | ||
| ``` | ||
|
|
||
| 1. Download the release manifests: |
There was a problem hiding this comment.
that's a good idea. i'm curious about the two part approach, download the chart separately from the manifests. is there a reason to do that versus just hosting the full release in a tarball and then they just untar and can proceed?
https://deploy-preview-3519--replicated-docs.netlify.app/vendor/tutorial-embedded-cluster-automation