apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T22:12:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-78-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-78.ec2.internal
      uid: 8651c92e-3967-4d1f-8b12-bd9cc3d2ca64
    resourceVersion: "23427"
    uid: a251953e-c295-44e0-9d8d-393865a16807
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cw2sg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T22:19:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.016074ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:19:05Z"
    - latency: 933.869µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:18:05Z"
    - latency: 1.091959ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:17:05Z"
    - latency: 1.43089ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:16:05Z"
    - latency: 1.033938ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:15:05Z"
    - latency: 1.925962ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:14:05Z"
    - latency: 966.884µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:13:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T22:12:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-78-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-78.ec2.internal
      uid: 8651c92e-3967-4d1f-8b12-bd9cc3d2ca64
    resourceVersion: "21836"
    uid: c822f544-90d9-4c1c-8cba-ce2be70e7a01
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cw2sg
    targetEndpoint: a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T22:18:05Z"
      message: 'load-balancer-api-external: tcp connection to a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.835292ms
      message: 'load-balancer-api-external: tcp connection to a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:18:05Z"
    - latency: 10.669598ms
      message: 'load-balancer-api-external: resolved host name a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:18:05Z"
    - latency: 4.627971ms
      message: 'load-balancer-api-external: tcp connection to a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:17:05Z"
    - latency: 9.164734ms
      message: 'load-balancer-api-external: resolved host name a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:17:05Z"
    - latency: 4.618452ms
      message: 'load-balancer-api-external: tcp connection to a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:16:05Z"
    - latency: 8.46726ms
      message: 'load-balancer-api-external: resolved host name a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:16:05Z"
    - latency: 4.626709ms
      message: 'load-balancer-api-external: tcp connection to a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:15:05Z"
    - latency: 8.981865ms
      message: 'load-balancer-api-external: resolved host name a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:15:05Z"
    - latency: 5.556837ms
      message: 'load-balancer-api-external: tcp connection to a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:14:05Z"
    - latency: 8.748602ms
      message: 'load-balancer-api-external: resolved host name a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:14:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T22:12:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-78-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-78.ec2.internal
      uid: 8651c92e-3967-4d1f-8b12-bd9cc3d2ca64
    resourceVersion: "21835"
    uid: 2e8bde85-3627-4f9c-82dc-2ca6c1896204
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cw2sg
    targetEndpoint: a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T22:18:05Z"
      message: 'load-balancer-api-internal: tcp connection to a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.836596ms
      message: 'load-balancer-api-internal: tcp connection to a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:18:05Z"
    - latency: 10.629544ms
      message: 'load-balancer-api-internal: resolved host name a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:18:05Z"
    - latency: 4.600951ms
      message: 'load-balancer-api-internal: tcp connection to a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:17:05Z"
    - latency: 9.05227ms
      message: 'load-balancer-api-internal: resolved host name a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:17:05Z"
    - latency: 4.573662ms
      message: 'load-balancer-api-internal: tcp connection to a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:16:05Z"
    - latency: 8.374706ms
      message: 'load-balancer-api-internal: resolved host name a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:16:05Z"
    - latency: 4.71791ms
      message: 'load-balancer-api-internal: tcp connection to a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:15:05Z"
    - latency: 8.879411ms
      message: 'load-balancer-api-internal: resolved host name a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:15:05Z"
    - latency: 5.605121ms
      message: 'load-balancer-api-internal: tcp connection to a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:14:05Z"
    - latency: 8.554622ms
      message: 'load-balancer-api-internal: resolved host name a4fd39104181d42b184aaed6d15a68df-10fe1813aabd4989.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:14:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T22:12:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-78-to-network-check-target-ip-10-0-128-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-78.ec2.internal
      uid: 8651c92e-3967-4d1f-8b12-bd9cc3d2ca64
    resourceVersion: "23425"
    uid: 78de14ac-050a-4f71-9ec3-b50314e4da73
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cw2sg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T22:19:05Z"
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.290741ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:19:05Z"
    - latency: 2.06098ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:18:05Z"
    - latency: 2.071872ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:17:05Z"
    - latency: 2.282403ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:16:05Z"
    - latency: 2.291217ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:15:05Z"
    - latency: 2.434795ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:14:05Z"
    - latency: 2.441852ms
      message: 'network-check-target-ip-10-0-128-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:13:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T22:12:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-78-to-network-check-target-ip-10-0-130-150
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-78.ec2.internal
      uid: 8651c92e-3967-4d1f-8b12-bd9cc3d2ca64
    resourceVersion: "23426"
    uid: 5d876c64-b50a-4439-92a5-857bfc2f3c15
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cw2sg
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T22:19:05Z"
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.313591ms
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:19:05Z"
    - latency: 2.372073ms
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:18:05Z"
    - latency: 2.290937ms
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:17:05Z"
    - latency: 2.297788ms
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:16:05Z"
    - latency: 1.98019ms
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:15:05Z"
    - latency: 2.193148ms
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:14:05Z"
    - latency: 2.247595ms
      message: 'network-check-target-ip-10-0-130-150: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:13:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T22:12:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-78-to-network-check-target-ip-10-0-142-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-78.ec2.internal
      uid: 8651c92e-3967-4d1f-8b12-bd9cc3d2ca64
    resourceVersion: "23424"
    uid: 7f9901d3-c142-46ca-9ca7-9da12837fe3a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cw2sg
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T22:19:05Z"
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 995.933µs
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:19:05Z"
    - latency: 1.055035ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:18:05Z"
    - latency: 1.079683ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:17:05Z"
    - latency: 1.200757ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:16:05Z"
    - latency: 916.037µs
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:15:05Z"
    - latency: 1.486512ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:14:05Z"
    - latency: 1.348515ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:13:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T22:12:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-78-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-78.ec2.internal
      uid: 8651c92e-3967-4d1f-8b12-bd9cc3d2ca64
    resourceVersion: "21834"
    uid: 50055c6e-20bf-4f51-9c1d-985de15fd0dd
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cw2sg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T22:18:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 823.304µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:18:05Z"
    - latency: 2.665292ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:18:05Z"
    - latency: 793.222µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:17:05Z"
    - latency: 1.717381ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:17:05Z"
    - latency: 935.852µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:16:05Z"
    - latency: 1.805521ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:16:05Z"
    - latency: 862.622µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:15:05Z"
    - latency: 1.74262ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:15:05Z"
    - latency: 1.267601ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:14:05Z"
    - latency: 1.892746ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:14:05Z"
kind: List
metadata:
  resourceVersion: ""