Welcome to the Linux Foundation Forum!

Updated procedure for lab 9B

danilogranadosg
danilogranadosg Posts: 4
edited February 2025 in LFS269 Class Forum

I'm running lab 9B and I noticed this removal notice in the fluxcd git repo:

So I tried following the new instructions here and here but they were not as clear to me as they were before. So this is what I did to make it work:

  1. Cloned flux2-monitoring-example git repo:

    git clone https://github.com/fluxcd/flux2-monitoring-example.git

  2. Copied the monitoring folder in flux2-monitoring-example with all its content to my flux-infra folder

  3. copied the ./clusters/test/monitoring.yaml file from flux2-monitoring-example to my flux-infra/clusters/staging folder

  4. Commited everything, pushed to main remote, and reconciled.

  5. After some time the kube-prometheus-stack and the loki-stack are deployed in the monitoring namespace:

After this point the lab instructions can be resumed, taking into account that the service that has to be modified from clusterip to nodeport is kube-prometheus-stack-grafana, and the kustomization that needs to be suspended is called monitoring-controllers

Comments

  • luisviveropena
    luisviveropena Posts: 1,347

    Hi @danilogranadosg,

    Thanks for informing us of the Flux change! We'll check on it and modify the documentation accordingly.

    Regards,
    Luis.

  • luisviveropena
    luisviveropena Posts: 1,347

    Hi @danilogranadosg,

    Did you get any warning or issue when running the Flux commands or going through the lab?

    Regards,
    Luis.

  • danilogranadosg
    danilogranadosg Posts: 4

    Hi @luisviveropena

    Yes I did. That's what led me to check the ./manifests/monitoring path in the fluxcd/flux2 repo. I'm sorry I don't have a screenshot or the error message. If you check the procedure, the first step in the lab document makes a direct reference to this path in the following commands:

    flux create source git flux-monitoring \
--interval=30m \
--url=https://github.com/fluxcd/flux2 \
--branch=main

    And then create a Kustomization to deploy Prometheus and Grafana:

    flux create kustomization kube-prometheus-stack \
--interval=1h \
--prune \
--source=flux-monitoring \
--path="./manifests/monitoring/kube-prometheus-stack" \
--health-check-timeout=5m \
--wait

    flux create kustomization monitoring-config \
--depends-on=kube-prometheus-stack \
--interval=1h \
--prune=true \
--source=flux-monitoring \
--path="./manifests/monitoring/monitoring-config" \
--health-check-timeout=1m \
--wait

    The deployment of the kube-prometheus-stack never finishes because the following paths do not exist anymore:

    --path="./manifests/monitoring/kube-prometheus-stack
    --path="./manifests/monitoring/monitoring-config" \

    I hope that helps.

  • luisviveropena
    luisviveropena Posts: 1,347

    Hi @danilogranadosg,

    Ok, thanks for the information. I'll try to reproduce the issue and will take the corresponding actions in regards the material.

    Regards,
    Luis.

Categories

Upcoming Training