Welcome to the Linux Foundation Forum!

Updated procedure for lab 9B

Posts: 4
edited February 8 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

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Comments

  • Posts: 1,265

    Hi @danilogranadosg,

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

    Regards,
    Luis.

  • Hi @danilogranadosg,

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

    Regards,
    Luis.

  • 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:

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

    And then create a Kustomization to deploy Prometheus and Grafana:

    1. flux create kustomization kube-prometheus-stack \
    2. --interval=1h \
    3. --prune \
    4. --source=flux-monitoring \
    5. --path="./manifests/monitoring/kube-prometheus-stack" \
    6. --health-check-timeout=5m \
    7. --wait
    1. flux create kustomization monitoring-config \
    2. --depends-on=kube-prometheus-stack \
    3. --interval=1h \
    4. --prune=true \
    5. --source=flux-monitoring \
    6. --path="./manifests/monitoring/monitoring-config" \
    7. --health-check-timeout=1m \
    8. --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.

  • 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.

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training