website restructuring [1/N] #1362
Conversation
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
content/en/docs/setup/kubernetes.md
Outdated
|
|
||
| If you wish to upgrade Falco to a new version, you need to find the corresponding version in the [Falco Helm Chart repository](https://github.com/falcosecurity/charts/blob/master/charts/falco) (e.g. `4.8.1` is for Falco `0.38.2` ) then run: | ||
|
|
||
| ```sh | ||
| helm upgrade falco -n falco --version 4.8.1 | ||
| ``` | ||
|
|
||
| {{% pageinfo color="warning" %}} | ||
| To avoid any possible disruption, before upgrading to a new version, consult the [Falco Helm chart Breaking Changes page](https://github.com/falcosecurity/charts/blob/master/charts/falco/BREAKING-CHANGES.md). | ||
| {{% /pageinfo %}} |
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
Signed-off-by: Leonardo Grasso <[email protected]>
|
I believe there are some missing aliases that can be reached via a Google search: https://deploy-preview-1362--falcosecurity.netlify.app/docs/install-operate/ https://www.google.com/search?q=%22falco.org%2Fdocs%2Finstall-operate%22+-site%3Afalco.org Also, there is a gRPC alias issue I think (too many |
|
Thanks @leogr ! It's a lot of content and I think the structure makes sense. My main concern is alias consistency because it'll break links from searches, websites, presentations and so forth. The details can always be improved incrementally. |
Good catch, thank you! I tried to do my best, but it was still manual and error-prone. Fixing. |
Co-authored-by: Luca Guerra <[email protected]> Signed-off-by: Leonardo Grasso <[email protected]>
Co-authored-by: Luca Guerra <[email protected]> Signed-off-by: Leonardo Grasso <[email protected]>
Co-authored-by: Luca Guerra <[email protected]> Signed-off-by: Leonardo Grasso <[email protected]>
Co-authored-by: Luca Guerra <[email protected]> Co-authored-by: Federico Di Pierro <[email protected]> Signed-off-by: Leonardo Grasso <[email protected]>
Co-authored-by: Luca Guerra <[email protected]> Co-authored-by: Thomas Labarussias <[email protected]> Signed-off-by: Leonardo Grasso <[email protected]>
Co-authored-by: Thomas Labarussias <[email protected]> Signed-off-by: Leonardo Grasso <[email protected]>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Issif, leogr The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
After the changes made by the following PR to the Falco docs falcosecurity/falco-website#1362 this commit updates a broken link. Signed-off-by: Aldo Lacuku <[email protected]>
After the changes made by the following PR to the Falco docs falcosecurity/falco-website#1362 this commit updates a broken link. Signed-off-by: Aldo Lacuku <[email protected]>
What type of PR is this?
/kind cleanup
/kind design
/kind user-interface
/kind content
Any specific area of the project related to this PR?
/area blog
/area documentation
What this PR does / why we need it:
This is the first step of the action plan described in #1365
This PR specifically focuses on reorganizing the first two sections:
In the work of moving content to new places, this PR also anticipates the Developer Guide section which, however, needs more work (this will be addressed in followup PRs).
Which issue(s) this PR fixes:
Help with #1365
Special notes for your reviewer:
Some content is still temporary and must be fixed once all the new sections are placed.
Notably, we miss an installation scenario for the non-kernel-instrumentation use case. As a temporary solution, we will forward users to the Plugins section.