Skip to content

Add simple test with kind #98

Closed
Closed

Description

@kvaps

Let's add simple CI test with kind and paas-hosted bundle

This should cover at least Cozystack installation process

Activity

  1. dosubot commented on Oct 17, 2025

    @dosubot

    Hi, Andrei Kvapil (@kvaps). I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.

    Issue Summary:

    • You proposed adding a basic test using kind and the paas-hosted bundle to the CI pipeline.
    • The goal is to verify the Cozystack installation process and improve testing coverage.
    • There has been no further activity or comments on this suggestion since it was opened.
    • The issue remains unresolved and no implementation has been started.

    Next Steps:

    • Please let me know if this enhancement is still relevant for the latest version of cozystack by commenting on this issue.
    • If I don’t hear back within 7 days, I will automatically close this issue.

    Thanks for your understanding and contribution!

  2. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale
    on Oct 17, 2025
  3. kvaps commented on Oct 17, 2025

    @kvaps
    MemberAuthor

    Yes, this still on a row

  4. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale
    on Oct 17, 2025
  5. myasnikovdaniil commented on Jun 8, 2026

    @myasnikovdaniil
    Contributor

    Superseded by #2847 (the diff-driven & scenario-based E2E testing epic). The install-process coverage requested here is now provided by hack/e2e-install-cozystack.bats (full Talos-based install on the E2E runner), tracked in #2847; the original kind + paas-hosted approach predates the current Package/bundle install model. Closing in favor of the epic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions