Merge pull request #1573 from fluxcd/install-v2

Reorganise and improve the installation docs

Author: stefanprodan

content/en/blog/2021-01-06-january-update.md

@@ -112,7 +112,7 @@ Azure DevOps users will have to specify to use libgit2 in their
 GitRepository resources.
 
 Follow [the generic git server
-guide](/flux/installation/#generic-git-server)
+guide](/flux/installation/bootstrap/generic-git-server/)
 for further instructions in how to use Flux with Azure DevOps.
 
 Upcoming events

content/en/blog/2021-03-08-flux-is-a-cncf-incubation-project/index.md

@@ -70,7 +70,7 @@ users migrate to Flux v2.
 
 Now is the perfect time to familiarise yourself with [Flux
 v2](/) - the Get Started guide only takes a couple of minutes to complete.
-If you prefer a video, check out [our resources section](/#resources).
+If you prefer a video, check out [our resources section](/resources/).
 
 Migrating from v1 will require some work, but it will definitely be
 worth it: in this iteration you are going to get

content/en/blog/2021-04-29-may-update/index.md

@@ -67,7 +67,7 @@ The Flux v2 CLI and the GitOps Toolkit controllers are now CII Best
 Practices certified.
 
 Checkout the [new bootstrap
-procedure](/flux/installation/_index.md#generic-git-server).
+procedure](/flux/installation/bootstrap/generic-git-server/).
 
 0.13 comes with **breaking changes to image automation** and has the
 following highlights:
@@ -95,7 +95,7 @@ Please follow the [upgrade procedure for image
 automation](https://github.com/fluxcd/flux2/discussions/1333).
 
 Checkout the [new bootstrap customisation
-feature](/flux/installation/_index.md#customize-flux-manifests).
+feature](/flux/installation/configuration/boostrap-customization/).
 
 The [Image automation guide](/flux/guides/image-update/) has been updated
 to the new APIs, and also includes a reference to a

content/en/blog/2021-05-31-june-update/index.md

@@ -37,7 +37,7 @@ The highlights are:
 Docs:
 
 - 📔 [GitRepository include
-  documentation](/flux/components/source/gitrepositories/#including-gitrepository)
+  documentation](/flux/components/source/gitrepositories/#include)
 - 🎁 Checkout the new [guide on ways of structuring your
   repositories](/flux/guides/repository-structure/)
 

content/en/blog/2021-08-02-august-update/index.md

@@ -165,7 +165,7 @@ scheduling information available on the [CNCF Flux Dev
 Calendar](https://lists.cncf.io/g/cncf-flux-dev/calendar),
 usually scheduled opposite the CNCF Flux Project Meeting. You can
 [subscribe to the
-calendar](/community/#subscribing-to-the-flux-dev-calendar)
+calendar](/community/#subscribing-to-the-flux-calendar)
 to receive notifications about upcoming events and schedule changes. The
 Bug Scrub is an opportunity to meet with other Flux contributors in
 another setting besides the Dev meeting, where we try to identify "Good

content/en/blog/2021-08-30-september-update/index.md

@@ -76,7 +76,7 @@ Some of the highlights in this release are:
   Prometheus Operator and others.
 - The Notification controller can now send alerts to Telegram, Lark
   and Matrix in addition to [many
-  others](/flux/components/notification/provider/#specification).
+  others](/flux/components/notification/provider/#writing-a-provider-spec).
 - Kustomize controller has been updated to on a par with the latest
   Kustomize release v4.3.0.
 
@@ -167,7 +167,7 @@ accessible than ever before.
 The Zoom link is broadcast via Slack a few minutes before the
 meeting start time. For more event details, subscribe to the [CNCF Flux
 Dev
-calendar](/community/#subscribing-to-the-flux-dev-calendar).
+calendar](/community/#subscribing-to-the-flux-calendar).
 Attendees all are asked to RSVP in advance, which can be done by posting
 on the Slack thread for Bug Scrub, and introducing yourself briefly in
 case you are new to the Flux contributor team.
@@ -201,7 +201,7 @@ section - directly on the home page:
 
 For this we re-use Flux's calendar that is provided by CNCF
 infrastructure, so if you [subscribed to
-it](/community/#subscribing-to-the-flux-dev-calendar)
+it](/community/#subscribing-to-the-flux-calendar)
 in the past, you will continue to receive all the information there.
 
 **🤝 Thanks everyone!** In the last month, 15 people contributed to the

content/en/blog/2021-10-29-november-update/index.md

@@ -234,7 +234,7 @@ Here is an update from Kingdon and the rest of the Flux team:
 > calendar](/#calendar), which has the Zoom
 > link and is in UTC time, or get reminded in your own time zone by
 > [subscribing to the flux-dev
-> calendar](/community/#subscribing-to-the-flux-dev-calendar).
+> calendar](/community/#subscribing-to-the-flux-calendar).
 >
 > Hope to see you there!
 

content/en/blog/2021-11-30-december-update/index.md

@@ -74,14 +74,14 @@ And finally **0.24** comes with security updates for Alpine CVEs. We are
 also happy to bring you
 
 - New bootstrap command for [Bitbucket Server and Data
-  Center](/flux/installation/#bitbucket-server-and-data-center)
+  Center](/flux/installation/bootstrap/bitbucket/)
   repositories (CLI).
 - Add support for self-signed certificates when bootstrapping Flux
   with on-prem GitHub, GitLab and BitBucket servers (CLI).
 - Improved performance when building Helm charts and introduced limits
   for Helm index and chart files. (source-controller).
 - Add support for [Slack Apps
-  bot](/flux/components/notification/provider/#slack-app)
+  bot](/flux/components/notification/provider/#slack)
   alerting provider (notification-controller).
 
 Please note that this version comes with breaking changes to Helm users.
@@ -98,7 +98,7 @@ Big shout-out to Soulé Ba for adding Bitbucket support to Flux. This
 will make lots of Flux users happy. Thank you very much!
 
 To find out how to bootstrap Flux on Bitbucket Server, please review
-[our documentation](/flux/installation/#bitbucket-server-and-data-center).
+[our documentation](/flux/installation/bootstrap/bitbucket/).
 We love feedback, so please reach out if you have any questions or are
 missing anything. We are also working on support for BitBucket Cloud,
 for which we might need some help testing, documentation or wherever

content/en/blog/2022-01-31-january-update/index.md

@@ -39,7 +39,7 @@ previously the controllers ignored the service account.
 #### :lock: Security enhancements
 
 - Platform admins have the option to [lock down Flux on multi-tenant
-  clusters](/flux/installation/#multi-tenancy-lockdown)
+  clusters](/flux/installation/configuration/multitenancy/)
   and enforce tenant isolation at namespace level without having to
   use a 3rd party admission controller.
 - The Flux installation conforms to the Kubernetes [restricted pod
@@ -289,7 +289,7 @@ are less random and we can attract more interest. Look to the schedule
 for information about how to join at
 [https://fluxcd.io/\#calendar](/#calendar)
 or [add the Flux events to your own
-calendar](/community/#subscribing-to-the-flux-dev-calendar)
+calendar](/community/#subscribing-to-the-flux-calendar)
 if you want to participate, and be sure you don't miss out on the new
 Flux Bug Scrub, Special Edition!
 

content/en/blog/2022-02-09-security-the-value-of-sboms/index.md

@@ -14,7 +14,7 @@ resources:
 
 You don't get to re-architect a successful project very often, but we
 did about two years ago. The Flux project was already off to a great
-start and had [many happy adopters](/adopters/#flux-v1) and many of
+start and had [many happy adopters](/adopters/#flux-legacy) and many of
 its design principles we kept at the forefront of our mind:
 
 - Pull vs Push: if you haven't read this [great blog