Skip to content

E2E tests of disabling ingressFiltering #2770

@jaroslaw-pieszka

Description

@jaroslaw-pieszka

Following scenarios are not covered:

Plan supports ingress filtering GA ingress filtering parameter outcome
no * false 400 - ingress filtering option is not available
yes internal false 202 - accepted
yes external false 202 - accepted

NOTE

  • two additional steps in reusable workflow are needed
  • fourth testing mode is needed, let us call it external_disable
  • at least one new workflow is needed

Proposed solution

  • add step expecting failure while provisioning with --disableIngressFiltering, this step will be run if the mode is not unsupported
  • add step expecting failure while provisioning with --disableIngressFiltering --license_type=CUSTOMER, this step will be run if the mode is not unsupported
  • if the mode is external_disable we provision the cluster with --disableIngressFiltering --license_type=CUSTOMER (successfully)

AC

  • these three scenarios are covered in E2E test

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions