Skip to content

Fixing quickstart guide to make it function as expected.#78

Draft
sjwaight wants to merge 2 commits intokubefleet-dev:mainfrom
sjwaight:getting-started-updates
Draft

Fixing quickstart guide to make it function as expected.#78
sjwaight wants to merge 2 commits intokubefleet-dev:mainfrom
sjwaight:getting-started-updates

Conversation

@sjwaight
Copy link
Member

This pull request updates the getting started guide for using kind clusters with KubeFleet, replacing references to "Fleet" with "KubeFleet" and modernizing the instructions for clarity and accuracy. The guide now reflects current best practices, simplifies setup steps, and improves consistency in terminology and resource names.

Relates to improvements tracked on #471 on main KubeFleet site.

Key changes include:

Rebranding and Terminology Updates:

  • Renamed all references from "Fleet" to "KubeFleet" throughout the tutorial, including file titles, descriptions, cluster roles, and command outputs.
  • Updated API group names and resource names to use the new KubeFleet naming conventions (e.g., placement.kubernetes-KubeFleet.io/v1).

Setup and Installation Improvements:

  • Simplified the process for setting up hub and member clusters by removing manual image build/push steps and using the official KubeFleet Helm chart from the OCI registry.
  • Added instructions for selecting the KubeFleet version and clarified the usage of environment variables for cluster names.

Quickstart Script and Automation:

  • Replaced manual member cluster join steps with a reference to the new join-member-clusters.sh quickstart script, making it easier to add member clusters.

Resource Placement Example Updates:

  • Updated resource and namespace names (e.g., from work to kubefleet-sample) for consistency with KubeFleet examples. [1] [2]
  • Revised the sample ClusterResourcePlacement YAML to match the new API version and naming.

Cleanup and Uninstallation Instructions:

  • Updated cleanup commands to use the new resource names and provided clearer instructions for uninstalling KubeFleet from both hub and member clusters.

Signed-off-by: Simon Waight <simon.waight@microsoft.com>
Signed-off-by: Simon Waight <simon.waight@microsoft.com>
@sjwaight sjwaight requested a review from michaelawyu March 24, 2026 04:29

In this tutorial you will create two kind clusters; one of which serves as the Fleet
hub cluster, and the other the Fleet member cluster. Run the commands below to create them:
If you want to control the Kubernetes version of your kind clusters, see [kind releases](https://github.com/kubernetes-sigs/kind/releases) and set the Kuberentes version by passing the correct value to `--image` parameter. For example `--image kindest/node:v1.32.8` will create a Kubernetes cluster running 1.32.8.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Simon! Just a nit: should we give users a recommended version? This might be a less relevant concern, but KubeFleet might not work with some of the earlier KubeFleet versions.


### Select KubeFleet version

Next, select the KubeFleet version to run by looking at the [KubeFleet GitHub Releases page](https://github.com/kubefleet-dev/kubefleet/releases) and picking a version - for example 0.2.2.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Simon! Also a similar nit here: would it be better to just recommend users with a version to avoid confusion?

(Of course I understand that a downside would be that we need to update this doc all the time... or shall we just recommend the latest official release as seen on GitHub?)

Copy link
Member

@michaelawyu michaelawyu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a few minor comments, PTAL.

--version 0.2.2 \
--namespace fleet-system \
--create-namespace \
--set logFileMaxSize=100000
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not related to this PR, but we should really fix the charts to drop this requirement 😞 I will create an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants