SovereignCloudStack / SovereignCloudStack/standards

[EPIC] Make sonobuoy golang framework useable for production

Open
#735 1 comment 0 reactions 1 assignee View on GitHub

@tonifinger is already working on this.

Since Sep 4, 2024.

  • #761 by @tonifinger — merged
enhancement SCS-VP10
Dominant language
Python
Stars
47
Forks
38
Avg merge
1d 16h
Merged PRs (30d)
8

Description

As described in DR, scs-0200-v1-using-sonobuoy-for-kaas-conformance-tests.md, it was decided to use sonobuoy as framework to deploy tests to Kubernetes clusters.

The current Sonobuoy setup within the repository was merely a PoC. We want to make it ready for production use.

The following must therefore be adjusted/implemented:

PREREQUISITES:
  • Implementation of the Golang test framework in accordance with the PoC (see: kaas-sonobuoy-go-example-e2e-framework ) #761
  • CI job to create the Sonobuoy image and upload it to the Github container registry #793
    • check go sum file
    • Versioning of the test images
TASKS
  • multi-arch support for arm64 and amd64 #758
  • Upgrade golang version: #747
  • apply golangci-lint: #771
  • Write documentation on how you can contribute new tests. As part of docs/issues/201
  • Zuul job to run the conformance test:
    • Plugin to create k8s clusters with cluster stack #710 #831
BACKLOG
  • Write documentation on how a User(not a developer) can run the sonobuoy tests on its own.
    • currently blocked by the image not beeing build so far.
  • Versioning the development environment (tools used for development)
  • append kind config to choose k8s version.
  • BUG: NS_PREFIX not set lets make test-function crash with a lowercase RFC 1123 label must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character
  • Update the DR to describe the current setup

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.