apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T17:23:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-162-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-162.ec2.internal
      uid: c2ddc697-2177-4d65-9110-aa17854ffd74
    resourceVersion: "15254"
    uid: 3da9cafb-36f5-4a63-843a-cdbc11b6229b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9z7bg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T17:30:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.325156ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:30:39Z"
    - latency: 954.028µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:29:39Z"
    - latency: 911.395µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:28:39Z"
    - latency: 962.448µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:27:39Z"
    - latency: 1.047008ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:26:39Z"
    - latency: 1.429852ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:25:39Z"
    - latency: 1.390776ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:24:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T17:23:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-162-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-162.ec2.internal
      uid: c2ddc697-2177-4d65-9110-aa17854ffd74
    resourceVersion: "14736"
    uid: a7f1cc83-c20c-40e9-b89e-de878d49e7f5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9z7bg
    targetEndpoint: a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T17:29:39Z"
      message: 'load-balancer-api-external: tcp connection to a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.88212ms
      message: 'load-balancer-api-external: tcp connection to a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:29:39Z"
    - latency: 8.318822ms
      message: 'load-balancer-api-external: resolved host name a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:29:39Z"
    - latency: 4.223324ms
      message: 'load-balancer-api-external: tcp connection to a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:28:39Z"
    - latency: 8.623008ms
      message: 'load-balancer-api-external: resolved host name a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:28:39Z"
    - latency: 4.842953ms
      message: 'load-balancer-api-external: tcp connection to a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:27:39Z"
    - latency: 8.913479ms
      message: 'load-balancer-api-external: resolved host name a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:27:39Z"
    - latency: 4.179987ms
      message: 'load-balancer-api-external: tcp connection to a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:26:39Z"
    - latency: 8.527895ms
      message: 'load-balancer-api-external: resolved host name a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:26:39Z"
    - latency: 4.518767ms
      message: 'load-balancer-api-external: tcp connection to a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:25:39Z"
    - latency: 10.367255ms
      message: 'load-balancer-api-external: resolved host name a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:25:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T17:23:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-162-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-162.ec2.internal
      uid: c2ddc697-2177-4d65-9110-aa17854ffd74
    resourceVersion: "14735"
    uid: 0c5754fb-e348-4a66-80d6-43b1ecf2e55e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9z7bg
    targetEndpoint: a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T17:29:39Z"
      message: 'load-balancer-api-internal: tcp connection to a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.898036ms
      message: 'load-balancer-api-internal: tcp connection to a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:29:39Z"
    - latency: 8.234064ms
      message: 'load-balancer-api-internal: resolved host name a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:29:39Z"
    - latency: 4.385988ms
      message: 'load-balancer-api-internal: tcp connection to a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:28:39Z"
    - latency: 8.755898ms
      message: 'load-balancer-api-internal: resolved host name a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:28:39Z"
    - latency: 3.604089ms
      message: 'load-balancer-api-internal: tcp connection to a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:27:39Z"
    - latency: 8.881733ms
      message: 'load-balancer-api-internal: resolved host name a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:27:39Z"
    - latency: 4.181573ms
      message: 'load-balancer-api-internal: tcp connection to a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:26:39Z"
    - latency: 8.654501ms
      message: 'load-balancer-api-internal: resolved host name a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:26:39Z"
    - latency: 4.495917ms
      message: 'load-balancer-api-internal: tcp connection to a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:25:39Z"
    - latency: 10.331707ms
      message: 'load-balancer-api-internal: resolved host name a7fd212a1017f4a709b1b523ad826be3-c6bd17c13df462d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:25:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T17:23:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-162-to-network-check-target-ip-10-0-129-220
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-162.ec2.internal
      uid: c2ddc697-2177-4d65-9110-aa17854ffd74
    resourceVersion: "15252"
    uid: 4f38bd27-659e-4b90-ac1c-b4c79f9adb97
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9z7bg
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T17:30:39Z"
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.092656ms
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:30:39Z"
    - latency: 1.714702ms
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:29:39Z"
    - latency: 1.750774ms
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:28:39Z"
    - latency: 1.987364ms
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:27:39Z"
    - latency: 1.857416ms
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:26:39Z"
    - latency: 1.858526ms
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:25:39Z"
    - latency: 2.044229ms
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:24:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T17:23:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-162-to-network-check-target-ip-10-0-140-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-162.ec2.internal
      uid: c2ddc697-2177-4d65-9110-aa17854ffd74
    resourceVersion: "15253"
    uid: 915ec1f9-6764-47be-8123-5f2cd3cb7dc7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9z7bg
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T17:30:39Z"
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.398758ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:30:39Z"
    - latency: 2.177737ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:29:39Z"
    - latency: 2.553101ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:28:39Z"
    - latency: 2.497448ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:27:39Z"
    - latency: 2.309645ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:26:39Z"
    - latency: 2.222541ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:25:39Z"
    - latency: 2.318471ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:24:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T17:23:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-162-to-network-check-target-ip-10-0-142-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-162.ec2.internal
      uid: c2ddc697-2177-4d65-9110-aa17854ffd74
    resourceVersion: "15251"
    uid: bfc03ccd-8c05-4b50-992e-ecd8386b4735
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9z7bg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T17:30:39Z"
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.485048ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:30:39Z"
    - latency: 898.634µs
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:29:39Z"
    - latency: 955.953µs
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:28:39Z"
    - latency: 1.175502ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:27:39Z"
    - latency: 959.865µs
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:26:39Z"
    - latency: 955.333µs
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:25:39Z"
    - latency: 1.325114ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:24:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T17:23:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-162-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-162.ec2.internal
      uid: c2ddc697-2177-4d65-9110-aa17854ffd74
    resourceVersion: "14734"
    uid: f1aa5bb1-a644-44b9-8b17-d5a9c2800855
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9z7bg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T17:29:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 797.873µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:29:39Z"
    - latency: 1.694008ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:29:39Z"
    - latency: 1.027495ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:28:39Z"
    - latency: 1.739672ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:28:39Z"
    - latency: 825.506µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:27:39Z"
    - latency: 2.061419ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:27:39Z"
    - latency: 972.903µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:26:39Z"
    - latency: 1.936847ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:26:39Z"
    - latency: 1.009111ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:25:39Z"
    - latency: 1.98547ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:25:39Z"
kind: List
metadata:
  resourceVersion: ""