SDN-4481: Set up NetPolicyTimeoutsHostNetworkedPodTraffic

[petr-muller]

Current understanding of the issue:

• 4.12.48+ potentially affected, so we may block upgrades from all 4.11 and 4.12.x<48
• 4.13.30+ confirmed affected, so we should block upgrades from <4.12.x<48 and k
• 4.14.9+ potentially affected, so we may block upgrades from 4.13.x<30 and 4.14.x<9
• 4.15.0-rc.1+ potentially affected, so we may block upgrades from 4.14.x<9 (I guess we can ignore rc0)
• 4.16.0-ec.0+ potentially affected but there's no relevant unaffected 4.16 or 4.15 so there is nothing to block.

Using PromQL to apply only on clusters that use NetworkPolicy objects.

I have handrafted a file for each minor version and then copied the
rest:

$ for fifteen in 2 3 4 5
    cp blocked-edges/4.15.0-rc.1-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml blocked-edges/4.15.0-rc.$fifteen-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml
    sed -i -e "s|4.15.0-rc.1|4.15.0-rc.$fifteen|" blocked-edges/4.15.0-rc.$fifteen-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml
  end

$ for fourteen in 10 11 12
    cp blocked-edges/4.14.9-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml  blocked-edges/4.14.$fourteen-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml
    sed -i -e "s|4.14.9|4.14.$fourteen|" blocked-edges/4.14.$fourteen-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml
  end

$ for thirteen in 31 32 33
    cp blocked-edges/4.13.30-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml  blocked-edges/4.13.$thirteen-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml
    sed -i -e "s|4.13.30|4.13.$thirteen|" blocked-edges/4.13.$thirteen-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml
  end

$ for twelve in 49
    cp blocked-edges/4.12.48-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml  blocked-edges/4.12.$twelve-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml
    sed -i -e "s|4.12.48|4.12.$twelve|" blocked-edges/4.12.$twelve-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml
  end

[openshift-ci-robot]

@petr-muller: This pull request references SDN-4481 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.16.0" version, but no target version was set.

In response to this:

Current understanding of the issue:

• 4.12.48+ potentially affected, so we may block upgrades from all 4.11 and 4.12.x<48
• 4.13.30+ confirmed affected, so we should block upgrades from <4.12.x<48 and k
• 4.14.9+ potentially affected, so we may block upgrades from 4.13.x<30 and 4.14.x<9
• 4.15.0-rc.1+ potentially affected, so we may block upgrades from 4.14.x<9 (I guess we can ignore rc0)
• 4.16.0-ec.0+ potentially affected but there's no relevant unaffected 4.16 or 4.15 so there is nothing to block.

Currently we have no good PromQL to filter the affected clusters, so Always for now. I have not yet copied for each affected releases, just for each initial in given minor. Will create copies once we agree on how we proceed.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@petr-muller: This pull request references SDN-4481 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.16.0" version, but no target version was set.

In response to this:

Current understanding of the issue:

• 4.12.48+ potentially affected, so we may block upgrades from all 4.11 and 4.12.x<48
• 4.13.30+ confirmed affected, so we should block upgrades from <4.12.x<48 and k
• 4.14.9+ potentially affected, so we may block upgrades from 4.13.x<30 and 4.14.x<9
• 4.15.0-rc.1+ potentially affected, so we may block upgrades from 4.14.x<9 (I guess we can ignore rc0)
• 4.16.0-ec.0+ potentially affected but there's no relevant unaffected 4.16 or 4.15 so there is nothing to block.

Using PromQL to apply only on clusters that use NetworkPolicy objects.

I have handrafted a file for each minor version and then copied the
rest:

$ for fifteen in 2 3 4 5
   cp blocked-edges/4.15.0-rc.1-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml blocked-edges/4.15.0-rc.$fifteen-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml
   sed -i -e "s|4.15.0-rc.1|4.15.0-rc.$fifteen|" blocked-edges/4.15.0-rc.$fifteen-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml
 end

$ for fourteen in 10 11 12
   cp blocked-edges/4.14.9-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml  blocked-edges/4.14.$fourteen-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml
   sed -i -e "s|4.14.9|4.14.$fourteen|" blocked-edges/4.14.$fourteen-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml
 end

$ for thirteen in 31 32 33
   cp blocked-edges/4.13.30-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml  blocked-edges/4.13.$thirteen-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml
   sed -i -e "s|4.13.30|4.13.$thirteen|" blocked-edges/4.13.$thirteen-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml
 end

$ for twelve in 49
   cp blocked-edges/4.12.48-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml  blocked-edges/4.12.$twelve-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml
   sed -i -e "s|4.12.48|4.12.$twelve|" blocked-edges/4.12.$twelve-NetPolicyTimeoutsHostNetworkedPodTraffic.yaml
 end

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 openshift-eng/jira-lifecycle-plugin repository.

[LalatenduMohanty]

/assign @wking

[LalatenduMohanty]

Lets drop 4.13.33 from this PR as signatures are missing for this build which is causing the tests to fail.

[LalatenduMohanty]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: LalatenduMohanty, petr-muller

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 [LalatenduMohanty,petr-muller]

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

[LalatenduMohanty]

/hold to sanity check the promql

[wking]

I'm not clear on which clusters have NetworkPolicies, but:

is an OCP 4.16.0-ec.2 GCP TechPreviewNoUpgrade cluster where the CRD doesn't exist at all understanding that it is not exposed, and:

is an OSD 4.15.0-rc.5 AWS cluster where the CRD and some CRs exist understanding that it might be exposed.