apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T04:10:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.ec2.internal
      uid: 8a459ec9-f9d8-4bba-8413-cb86880d7817
    resourceVersion: "24251"
    uid: d37e3e8a-546b-4dd1-8a92-8e4a128ee724
  spec:
    sourcePod: network-check-source-7cbc45fddc-mhm87
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T04:17:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 881.864µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:17:20Z"
    - latency: 1.306727ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:16:20Z"
    - latency: 1.830332ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:15:20Z"
    - latency: 8.53193ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:14:20Z"
    - latency: 1.176247ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:13:20Z"
    - latency: 822.247µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:12:20Z"
    - latency: 1.049471ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:11:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T04:10:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.ec2.internal
      uid: 8a459ec9-f9d8-4bba-8413-cb86880d7817
    resourceVersion: "27427"
    uid: 7f4f7e84-5f5d-4ed6-a94a-c5609fff396d
  spec:
    sourcePod: network-check-source-7cbc45fddc-mhm87
    targetEndpoint: a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T04:16:20Z"
      message: 'load-balancer-api-external: tcp connection to a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.496961ms
      message: 'load-balancer-api-external: tcp connection to a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:22:20Z"
    - latency: 6.98667ms
      message: 'load-balancer-api-external: resolved host name a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:22:20Z"
    - latency: 5.204897ms
      message: 'load-balancer-api-external: tcp connection to a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:21:20Z"
    - latency: 6.041599ms
      message: 'load-balancer-api-external: resolved host name a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:21:20Z"
    - latency: 4.91578ms
      message: 'load-balancer-api-external: tcp connection to a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:20:20Z"
    - latency: 7.281722ms
      message: 'load-balancer-api-external: resolved host name a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:20:20Z"
    - latency: 4.956136ms
      message: 'load-balancer-api-external: tcp connection to a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:19:20Z"
    - latency: 6.634902ms
      message: 'load-balancer-api-external: resolved host name a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:19:20Z"
    - latency: 4.235638ms
      message: 'load-balancer-api-external: tcp connection to a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:18:20Z"
    - latency: 7.141485ms
      message: 'load-balancer-api-external: resolved host name a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:18:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T04:10:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.ec2.internal
      uid: 8a459ec9-f9d8-4bba-8413-cb86880d7817
    resourceVersion: "27428"
    uid: e42cbf2b-ade2-4359-be3a-c061fcdf7e5a
  spec:
    sourcePod: network-check-source-7cbc45fddc-mhm87
    targetEndpoint: a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T04:16:20Z"
      message: 'load-balancer-api-internal: tcp connection to a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.862803ms
      message: 'load-balancer-api-internal: tcp connection to a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:22:20Z"
    - latency: 6.893853ms
      message: 'load-balancer-api-internal: resolved host name a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:22:20Z"
    - latency: 5.22761ms
      message: 'load-balancer-api-internal: tcp connection to a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:21:20Z"
    - latency: 6.002147ms
      message: 'load-balancer-api-internal: resolved host name a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:21:20Z"
    - latency: 4.929733ms
      message: 'load-balancer-api-internal: tcp connection to a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:20:20Z"
    - latency: 7.221954ms
      message: 'load-balancer-api-internal: resolved host name a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:20:20Z"
    - latency: 4.699926ms
      message: 'load-balancer-api-internal: tcp connection to a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:19:20Z"
    - latency: 6.605872ms
      message: 'load-balancer-api-internal: resolved host name a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:19:20Z"
    - latency: 4.272546ms
      message: 'load-balancer-api-internal: tcp connection to a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:18:20Z"
    - latency: 7.06201ms
      message: 'load-balancer-api-internal: resolved host name a77325a051ace40cfa7c4e94ed457d89-08cd461fafd2c6ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:18:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T04:10:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-network-check-target-ip-10-0-129-207
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.ec2.internal
      uid: 8a459ec9-f9d8-4bba-8413-cb86880d7817
    resourceVersion: "24248"
    uid: a3674505-dda8-4f93-960a-0be6244a6366
  spec:
    sourcePod: network-check-source-7cbc45fddc-mhm87
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T04:17:20Z"
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.045847ms
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:17:20Z"
    - latency: 832.371µs
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:16:20Z"
    - latency: 1.389704ms
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:15:20Z"
    - latency: 8.852727ms
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:14:20Z"
    - latency: 875.482µs
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:13:20Z"
    - latency: 963.605µs
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:12:20Z"
    - latency: 1.762484ms
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:11:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T04:10:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-network-check-target-ip-10-0-132-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.ec2.internal
      uid: 8a459ec9-f9d8-4bba-8413-cb86880d7817
    resourceVersion: "24249"
    uid: e23fa262-d3a8-4c25-9e43-a2a672fc3a00
  spec:
    sourcePod: network-check-source-7cbc45fddc-mhm87
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T04:17:20Z"
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.29642ms
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:17:20Z"
    - latency: 2.541528ms
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:16:20Z"
    - latency: 2.468761ms
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:15:20Z"
    - latency: 7.373856ms
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:14:20Z"
    - latency: 2.195039ms
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:13:20Z"
    - latency: 2.135769ms
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:12:20Z"
    - latency: 2.589652ms
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:11:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T04:10:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-network-check-target-ip-10-0-143-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.ec2.internal
      uid: 8a459ec9-f9d8-4bba-8413-cb86880d7817
    resourceVersion: "24250"
    uid: af490f32-a79f-499d-b52c-bafc810ee2b1
  spec:
    sourcePod: network-check-source-7cbc45fddc-mhm87
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T04:17:20Z"
      message: 'network-check-target-ip-10-0-143-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.286625ms
      message: 'network-check-target-ip-10-0-143-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:17:20Z"
    - latency: 2.586522ms
      message: 'network-check-target-ip-10-0-143-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:16:20Z"
    - latency: 3.251071ms
      message: 'network-check-target-ip-10-0-143-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:15:20Z"
    - latency: 7.196491ms
      message: 'network-check-target-ip-10-0-143-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:14:20Z"
    - latency: 3.026608ms
      message: 'network-check-target-ip-10-0-143-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:13:20Z"
    - latency: 2.297978ms
      message: 'network-check-target-ip-10-0-143-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:12:20Z"
    - latency: 2.590426ms
      message: 'network-check-target-ip-10-0-143-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:11:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T04:10:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.ec2.internal
      uid: 8a459ec9-f9d8-4bba-8413-cb86880d7817
    resourceVersion: "27426"
    uid: 1d358779-7205-4a1a-b599-e263aaa9d3c9
  spec:
    sourcePod: network-check-source-7cbc45fddc-mhm87
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T04:16:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 882.497µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:22:20Z"
    - latency: 1.693324ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:22:20Z"
    - latency: 967.487µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:21:20Z"
    - latency: 1.493945ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:21:20Z"
    - latency: 840.11µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:20:20Z"
    - latency: 1.50932ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:20:20Z"
    - latency: 795.602µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:19:20Z"
    - latency: 2.778217ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:19:20Z"
    - latency: 803.918µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T04:18:20Z"
    - latency: 1.773519ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T04:18:20Z"
kind: List
metadata:
  resourceVersion: ""