aks-store-demo VS aks-store-demo

For example, I'm working on some Helm charts for the AKS Store Demo project. My working branch is currently behind the state of the project source. I can bring my project current with git rebase and make it easier for the project maintainers to accept my contribution.

Step one is to add the chart repository. We'll use my fork of the AKS Store Demo as an example. We'll use the helm repo add command and provide it a (local) name for the repository, as well as the URL to the published chart repository.

The dev-app Kustomization deploys the GitRepository resource which points to the flux-k8s-ext branch in my AKS Store Demo Manifests repo, and Kustomization resource to deploy the AKS Store Demo application

We'll move really fast through the AKS cluster provisioning, bootstrapping process, and deploying the AKS Store Demo sample app.

# navigate to the home directory or wherever you want to clone the repo cd ~ # fork and clone the repo to your local machine gh repo fork https://github.com/azure-samples/aks-store-demo.git --clone # make sure you are in the aks-store-demo directory cd aks-store-demo # since we are in a forked repo, we need to set the default to be our fork gh repo set-default

We'll deploy my new favorite demo app, AKS Store Demo to our AKS cluster and then make some changes to the application and see how FluxCD handles them.

> git clone https://github.com/smurawski/aks-store-demo > cd aks-store-demo > git checkout origin/helm > git checkout -b helm > git remote add upstream https://github.com/Azure-Samples/aks-store-demo > git fetch upstream > git rebase upstream/main Successfully rebased and updated refs/heads/helm.