Skip to content

Clean up features for SIG Node e2e tests #134172

@SergeyKanzhelev

Description

@SergeyKanzhelev

We use features to indicate the environment that is "not standard" for e2e tests - i.e. requires extra configuration beyond feature gates.

This is uber issue to review sig-node features and clean them up:

  1. If the Feature is used to indicate just a "category" of tests - remove it
  2. If the Feature is used when FeatureGate must be used - replace with the FeatureGate
  3. If the Feature truly indicate a special environment, make sure it is well documented and corresponding test lanes are marked appropriately

Once we clear things up we may decide to pass the Feature as an argument for the test lane (similar to kubernetes/test-infra#35531 idea) and have more automated validation that the test requiring the Feature are only run in the test lane implementing this special environment

/sig node
/area test
/kind cleanup
/priority important-longterm
/cc @mariafromano-25 @esotsal

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/testkind/cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.sig/nodeCategorizes an issue or PR as relevant to SIG Node.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    Status

    Issues - In progress

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions