Skip to content

Extend testing after migration #801

@salasberryfin

Description

@salasberryfin

Description

This issue is part of the follow-up tasks after migrating to CAPI v1.11 and adopting the v1beta2 contract. Together with these changes, a new CAPRKE2 API version v1bea2 was added.

As a developer I would like to have test coverage adapted to the latest changes, this includes, but is not limited to:

  • Conversion: many new fields were added and others removed. There are multiple changes in the structure of the existing structs. Current testing covers basic conversion between API versions but we should also extend this to specific changes that could create conflicts.
  • Verify new conditions: we may need to validate conditions that were not tested before.
  • Check if there are extra rules required by webhooks or any of the existing can be removed, and add testing for bootstrap (RKE2Config) webhooks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/testingIndicates an issue related to testkind/enhancementNew feature or request

    Type

    No fields configured for Task.

    Projects

    Status

    Team Backlog

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions