apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:56:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-61-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-61.ec2.internal
      uid: 74023bc1-e5f3-4ada-bd01-86594a17a2fb
    resourceVersion: "11090"
    uid: 6b51b11f-d2fe-4596-814f-a88a8a2de3ea
  spec:
    sourcePod: network-check-source-7d88cb55d8-bqxb5
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:56:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-61-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-61.ec2.internal
      uid: 74023bc1-e5f3-4ada-bd01-86594a17a2fb
    resourceVersion: "14708"
    uid: c865c842-e5d7-40ff-ab35-84dc06087adb
  spec:
    sourcePod: network-check-source-7d88cb55d8-bqxb5
    targetEndpoint: a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T15:02:15Z"
      message: 'load-balancer-api-external: tcp connection to a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.484636ms
      message: 'load-balancer-api-external: tcp connection to a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:02:15Z"
    - latency: 8.332844ms
      message: 'load-balancer-api-external: resolved host name a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:02:15Z"
    - latency: 4.369071ms
      message: 'load-balancer-api-external: tcp connection to a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:01:15Z"
    - latency: 9.943485ms
      message: 'load-balancer-api-external: resolved host name a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:01:15Z"
    - latency: 4.843531ms
      message: 'load-balancer-api-external: tcp connection to a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:00:15Z"
    - latency: 8.376251ms
      message: 'load-balancer-api-external: resolved host name a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:00:15Z"
    - latency: 5.2715ms
      message: 'load-balancer-api-external: tcp connection to a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:59:15Z"
    - latency: 8.906739ms
      message: 'load-balancer-api-external: resolved host name a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:59:15Z"
    - latency: 5.377993ms
      message: 'load-balancer-api-external: tcp connection to a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:58:15Z"
    - latency: 8.30588ms
      message: 'load-balancer-api-external: resolved host name a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:58:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:56:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-61-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-61.ec2.internal
      uid: 74023bc1-e5f3-4ada-bd01-86594a17a2fb
    resourceVersion: "14707"
    uid: d6fcbdf7-0625-410e-822c-35e523039023
  spec:
    sourcePod: network-check-source-7d88cb55d8-bqxb5
    targetEndpoint: a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T15:02:15Z"
      message: 'load-balancer-api-internal: tcp connection to a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.455597ms
      message: 'load-balancer-api-internal: tcp connection to a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:02:15Z"
    - latency: 8.197044ms
      message: 'load-balancer-api-internal: resolved host name a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:02:15Z"
    - latency: 4.40042ms
      message: 'load-balancer-api-internal: tcp connection to a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:01:15Z"
    - latency: 9.837279ms
      message: 'load-balancer-api-internal: resolved host name a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:01:15Z"
    - latency: 4.887861ms
      message: 'load-balancer-api-internal: tcp connection to a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:00:15Z"
    - latency: 8.349087ms
      message: 'load-balancer-api-internal: resolved host name a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:00:15Z"
    - latency: 4.517691ms
      message: 'load-balancer-api-internal: tcp connection to a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:59:15Z"
    - latency: 8.748232ms
      message: 'load-balancer-api-internal: resolved host name a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:59:15Z"
    - latency: 4.956626ms
      message: 'load-balancer-api-internal: tcp connection to a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:58:15Z"
    - latency: 8.397106ms
      message: 'load-balancer-api-internal: resolved host name a3eb741d7061f4c21a503f51d1790924-42009465ddff03d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:58:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:56:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-61-to-network-check-target-ip-10-0-129-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-61.ec2.internal
      uid: 74023bc1-e5f3-4ada-bd01-86594a17a2fb
    resourceVersion: "11095"
    uid: 9a6e8c4c-b6d7-4f30-bef6-8cfccc07df7c
  spec:
    sourcePod: network-check-source-7d88cb55d8-bqxb5
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:56:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-61-to-network-check-target-ip-10-0-135-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-61.ec2.internal
      uid: 74023bc1-e5f3-4ada-bd01-86594a17a2fb
    resourceVersion: "11096"
    uid: d87b3fd8-f9ca-4508-b160-ddde087cdaa9
  spec:
    sourcePod: network-check-source-7d88cb55d8-bqxb5
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:56:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-61-to-network-check-target-ip-10-0-143-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-61.ec2.internal
      uid: 74023bc1-e5f3-4ada-bd01-86594a17a2fb
    resourceVersion: "11094"
    uid: efe077b7-2cbf-4343-adda-09daf8e533c3
  spec:
    sourcePod: network-check-source-7d88cb55d8-bqxb5
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:56:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-61-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-61.ec2.internal
      uid: 74023bc1-e5f3-4ada-bd01-86594a17a2fb
    resourceVersion: "14706"
    uid: e884cbcb-b980-45d5-a935-cbae7dedc12c
  spec:
    sourcePod: network-check-source-7d88cb55d8-bqxb5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T15:02:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 777.967µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:02:15Z"
    - latency: 1.815347ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:02:15Z"
    - latency: 929.072µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:01:15Z"
    - latency: 1.962949ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:01:15Z"
    - latency: 923.468µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T15:00:15Z"
    - latency: 1.824697ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T15:00:15Z"
    - latency: 939.691µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:59:15Z"
    - latency: 2.051791ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:59:15Z"
    - latency: 1.199269ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:58:15Z"
    - latency: 1.484153ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:58:15Z"
kind: List
metadata:
  resourceVersion: ""