apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-137-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-137.ec2.internal
      uid: 81386376-07d3-4ba7-8b1f-505720e2758e
    resourceVersion: "22742"
    uid: badfa636-0e01-487c-bbcb-8512804a9fdd
  spec:
    sourcePod: network-check-source-685456655f-6jffs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:57:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.415236ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:57:51Z"
    - latency: 1.257464ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:56:51Z"
    - latency: 1.132016ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:55:51Z"
    - latency: 874.38µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:54:51Z"
    - latency: 1.480885ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:53:51Z"
    - latency: 1.219714ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:52:51Z"
    - latency: 1.217664ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:51:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-137-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-137.ec2.internal
      uid: 81386376-07d3-4ba7-8b1f-505720e2758e
    resourceVersion: "26660"
    uid: 4922a1dc-3545-4e73-8893-658e39d00883
  spec:
    sourcePod: network-check-source-685456655f-6jffs
    targetEndpoint: a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:56:51Z"
      message: 'load-balancer-api-external: tcp connection to a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.986958ms
      message: 'load-balancer-api-external: tcp connection to a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:02:51Z"
    - latency: 6.361924ms
      message: 'load-balancer-api-external: resolved host name a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:02:51Z"
    - latency: 4.716857ms
      message: 'load-balancer-api-external: tcp connection to a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:01:51Z"
    - latency: 7.191458ms
      message: 'load-balancer-api-external: resolved host name a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:01:51Z"
    - latency: 3.882075ms
      message: 'load-balancer-api-external: tcp connection to a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:00:51Z"
    - latency: 6.333509ms
      message: 'load-balancer-api-external: resolved host name a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:00:51Z"
    - latency: 4.61091ms
      message: 'load-balancer-api-external: tcp connection to a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:59:51Z"
    - latency: 7.215909ms
      message: 'load-balancer-api-external: resolved host name a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:59:51Z"
    - latency: 4.856045ms
      message: 'load-balancer-api-external: tcp connection to a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:58:51Z"
    - latency: 6.171447ms
      message: 'load-balancer-api-external: resolved host name a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:58:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-137-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-137.ec2.internal
      uid: 81386376-07d3-4ba7-8b1f-505720e2758e
    resourceVersion: "26659"
    uid: d312061a-2f58-480d-942b-436688b587a8
  spec:
    sourcePod: network-check-source-685456655f-6jffs
    targetEndpoint: a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:56:51Z"
      message: 'load-balancer-api-internal: tcp connection to a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.951386ms
      message: 'load-balancer-api-internal: tcp connection to a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:02:51Z"
    - latency: 6.39846ms
      message: 'load-balancer-api-internal: resolved host name a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:02:51Z"
    - latency: 4.735962ms
      message: 'load-balancer-api-internal: tcp connection to a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:01:51Z"
    - latency: 7.261744ms
      message: 'load-balancer-api-internal: resolved host name a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:01:51Z"
    - latency: 3.908123ms
      message: 'load-balancer-api-internal: tcp connection to a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:00:51Z"
    - latency: 6.378245ms
      message: 'load-balancer-api-internal: resolved host name a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:00:51Z"
    - latency: 4.469002ms
      message: 'load-balancer-api-internal: tcp connection to a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:59:51Z"
    - latency: 7.252782ms
      message: 'load-balancer-api-internal: resolved host name a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:59:51Z"
    - latency: 4.814462ms
      message: 'load-balancer-api-internal: tcp connection to a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:58:51Z"
    - latency: 6.195272ms
      message: 'load-balancer-api-internal: resolved host name a602ff13d4ace4be7a65ffb3f6af9577-13c35f97582cc782.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:58:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-137-to-network-check-target-ip-10-0-129-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-137.ec2.internal
      uid: 81386376-07d3-4ba7-8b1f-505720e2758e
    resourceVersion: "22740"
    uid: ebd928f1-ed2d-4915-b1de-4f6bf44915f2
  spec:
    sourcePod: network-check-source-685456655f-6jffs
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:57:51Z"
      message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.091473ms
      message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:57:51Z"
    - latency: 2.583575ms
      message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:56:51Z"
    - latency: 2.138926ms
      message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:55:51Z"
    - latency: 1.790986ms
      message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:54:51Z"
    - latency: 2.070043ms
      message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:53:51Z"
    - latency: 2.212848ms
      message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:52:51Z"
    - latency: 2.472301ms
      message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:51:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-137-to-network-check-target-ip-10-0-131-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-137.ec2.internal
      uid: 81386376-07d3-4ba7-8b1f-505720e2758e
    resourceVersion: "22741"
    uid: 87bd8f50-5c86-4a4b-a407-175327275524
  spec:
    sourcePod: network-check-source-685456655f-6jffs
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:57:51Z"
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.207599ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:57:51Z"
    - latency: 2.045759ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:56:51Z"
    - latency: 1.927721ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:55:51Z"
    - latency: 1.741832ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:54:51Z"
    - latency: 2.050909ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:53:51Z"
    - latency: 1.717554ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:52:51Z"
    - latency: 2.133861ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:51:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-137-to-network-check-target-ip-10-0-142-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-137.ec2.internal
      uid: 81386376-07d3-4ba7-8b1f-505720e2758e
    resourceVersion: "22739"
    uid: 7440f5e0-11f6-43a2-b4ae-0a065b92ac93
  spec:
    sourcePod: network-check-source-685456655f-6jffs
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:57:51Z"
      message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 986.616µs
      message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:57:51Z"
    - latency: 1.412671ms
      message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:56:51Z"
    - latency: 858.618µs
      message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:55:51Z"
    - latency: 1.219159ms
      message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:54:51Z"
    - latency: 929.601µs
      message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:53:51Z"
    - latency: 1.005236ms
      message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:52:51Z"
    - latency: 1.578296ms
      message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:51:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-137-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-137.ec2.internal
      uid: 81386376-07d3-4ba7-8b1f-505720e2758e
    resourceVersion: "26658"
    uid: b2dac0ac-6571-411a-a937-8e9f9a2717f6
  spec:
    sourcePod: network-check-source-685456655f-6jffs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:56:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.000567ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:02:51Z"
    - latency: 1.665788ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:02:51Z"
    - latency: 732.633µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:01:51Z"
    - latency: 2.338894ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:01:51Z"
    - latency: 990.843µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:00:51Z"
    - latency: 1.628331ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:00:51Z"
    - latency: 987.719µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:59:51Z"
    - latency: 2.233403ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:59:51Z"
    - latency: 1.036862ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:58:51Z"
    - latency: 1.643208ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:58:51Z"
kind: List
metadata:
  resourceVersion: ""