Vincent Riesop
Vincent Riesop
With PR #477, technical documentation will be written in ```docs``` folder of gardenlinux/gardenlinux repo, and published on https://gardenlinux.io/documentation.
+1 for the structures @gyptazy proposed as TOC. I agree with @nanory to usethe proposed TOC as folder structure for `docs/`. Can we also align on where to put troubleshooting...
This issue must have slipped my mind. Sorry for the late reply. > MHO we should just place a Troubleshooting.md file on the same level like FAQ within the first...
@gyptazy @dnan0s: I will start with a draft documentation refactor. Will assign you again if it is ready for review. Let me know if this does not work for you....
We need to remove libdb and add tests to check if libdb is not included in the container image.
Hi, We have a `bpftool` package available, this `bpftool` package is build from the `linux:src` in our kernel pipelines. EDIT: bpftool is included in our repo.gardenlinux.io. We could include it...
Added openstack to **definition of done**
I suggest to run integration tests automatically for pushes to a release branch ``` on: push: branches: - 'releases/**' ```
Additionally, we can add the option to manually run integration tests. Would look like this: ``` on: push: branches: - 'releases/**' workflow_dispatch: ```
related #246