docs: restructure deployment guide#310
Conversation
✅ Deploy Preview for metal-stack-io ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
ma-hartma
force-pushed
the
deployment-guide-restructure
branch
from
c534aa8 to
bdb6362
Compare
ma-hartma
force-pushed
the
deployment-guide-restructure
branch
from
82b6b06 to
a2164b5
Compare
|
Still working on the guide, now streamlining and connecting this to an overhauled concepts section PR. |
| :::info | ||
| If you do not want to use Ansible for deployment, you need to come up with a deployment mechanism by yourself. However, you will probably be able to re-use some of our contents from our [metal-roles](https://github.com/metal-stack/metal-roles) repository, e.g. the Helm chart for deploying the metal control plane. | ||
| ::: |
There was a problem hiding this comment.
Am I missing something here? What can be re-used from the metal-roles repo when not using ansible?
For example the metal-control-plane helm chart is in https://github.com/metal-stack/helm-charts/ not metal-roles.
There was a problem hiding this comment.
Made it more explicit, please re-check!
|
I am now ready for a nitpicky review. @vknabel @majst01 @simcod @l0wl3vel I tried to improve depth and consistency. There are still blind spots like the deployment guide, but there are separate issues for that, like #247. Just imagine a great concepts part already to be there, explaining the birds-eye-view - because this is what I am now working on. It will be the next PR to review. This PR focuses on deployment and tries not to double information, that should be under concepts. |
4 participants
Description
We had a discussion in the team about restructuring the deployment guide.
Parts of the concept area do not belong there, but should go under the deployment guide.
For the guide not to get too bloated, this PR splits the guide into sub pages and moves parts from the concepts area to the regarding sub pages.
The concepts should come before the deployment guide, so there is a separate issue:
#312
Used AI-Tools ✨
References: