Kube-burner v1.6.0

[rsevilla87]

Type of change

• Refactor
• New feature
• Bug fix
• Optimization
• Documentation Update

Description

The version v1.5.1 of kube-burner was regressing due to this change and we had to revert it in prow

Moving forward with v1.6.0:

Changes:

network policy workload by @venkataanil in kube-burner/kube-burner-ocp#117
Add explicit alert for ClusterOperatorDown by @rsevilla87 in kube-burner/kube-burner-ocp#156
Update the udn-density-pods metadata by @krishvoor in kube-burner/kube-burner-ocp#155
Removing workers-scale out from kube-burner by @vishnuchalla in kube-burner/kube-burner-ocp#153
Update kube-burner version by @rsevilla87 in kube-burner/kube-burner-ocp#157
preload images in the nodes for the udn workload by @mohit-sheth in kube-burner/kube-burner-ocp#159
Revert "Decrease readinessProbe period" by @rsevilla87 in kube-burner/kube-burner-ocp#163
kube-burner v1.11.3 by @rsevilla87 in kube-burner/kube-burner-ocp#165

/cc @afcollins @jtaleric

[krishvoor]

/test ?

[openshift-ci]

@krishvoor: The following commands are available to trigger required jobs:

/test e2e-cluster-density-v2-single-node

/test e2e-conc-builds-single-node

/test e2e-ingress-perf-single-node

/test e2e-network-policy-single-node

/test e2e-network-smoke-single-node

/test e2e-node-density-cni-single-node

/test e2e-node-density-heavy-single-node

/test e2e-node-density-single-node

/test e2e-router-perf-single-node

/test e2e-udn-density-pods-l2

/test e2e-udn-density-pods-l3

In response to this:

/test ?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[krishvoor]

/test e2e-cluster-density-v2-single-node

[krishvoor]

/test e2e-network-smoke-single-node

[afcollins]

lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afcollins, rsevilla87

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [afcollins,rsevilla87]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment