Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

O11y-Op testing #3615

Closed
Tracked by #3565
Rotfuks opened this issue Jul 30, 2024 · 7 comments
Closed
Tracked by #3565

O11y-Op testing #3615

Rotfuks opened this issue Jul 30, 2024 · 7 comments
Assignees
Labels
team/atlas Team Atlas

Comments

@Rotfuks
Copy link
Contributor

Rotfuks commented Jul 30, 2024

Motivation

In order to raise our confidence in the stability of our observability platform and be sure that our ongoing work and releases won't negatively impact our observability platform operations we need to create extensive tests giving us early feedback loops.

Todo

  • Investigate some good initial test cases to give us feedback on the stability of a release on mimir on CI. This can be:
    • Validate Helm chart templating
    • Deploy chart on Kind (single instance)
    • Implement those CI test cases
  • Investigate how we can setup an e2e test case for the o11y-op
    • We can just check if the configmaps are created and if the content makes sense

Outcome

  • We have early, automatic feedback about the impact of a release of the o11y-op before releasing.
@QuantumEnigmaa
Copy link

✔️ Helm chart CI tests done.

@QuentinBisson
Copy link

@QuantumEnigmaa anything we still have to do here?

@QuantumEnigmaa
Copy link

Yeah, as discussed during refinement, we'll have to create a "e2e" testing framework on our own :

  • We will update the PR message to empower the user to perform the required tests before asking reviews for its PR.
  • A dedicated directory will be created at the repo's root with a file describing the test procedure and possible scripts to run manually after deploying the custom branch version on a MC.
  • Concerning olly-op specifically, the testing procedure might consist in creating a WC after having deployed olly-op custom branch's version on a testing MC let it run a bit and check on if the remote-write secret for the WC has been created.

Sorry I only updated Loki issue but that will be the same thing for all MC-only app.

@QuentinBisson
Copy link

No worries :)

@Rotfuks
Copy link
Contributor Author

Rotfuks commented Sep 5, 2024

Here's the ticket of the new @giantswarm/team-tenet for tests of apps only running on MC: #2930
have you taken the considerations in there into account?

@QuantumEnigmaa
Copy link

Yes but as even Marcus isn't sure on how or when this will eventually end, I'd prefer that we craft something on our own for now that will still be usable if tenet's framework become available, even if it's a bit more "manual".

@QuantumEnigmaa
Copy link

Manual e2e testing procedure and script now available in the app's repo + PR message updated.

@github-project-automation github-project-automation bot moved this from Inbox 📥 to Done ✅ in Roadmap Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team/atlas Team Atlas
Projects
Archived in project
Development

No branches or pull requests

3 participants