apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T16:06:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-55-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-55.ec2.internal
      uid: 03d7a1b6-6dc1-473d-9e03-b31444d7033b
    resourceVersion: "10997"
    uid: 19e680d6-63ad-47e1-b8aa-79df59ae5e7c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wnpcf
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T16:06:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-55-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-55.ec2.internal
      uid: 03d7a1b6-6dc1-473d-9e03-b31444d7033b
    resourceVersion: "14588"
    uid: 2512c854-21fe-4bc2-a617-3243692d7ab9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wnpcf
    targetEndpoint: ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T16:12:40Z"
      message: 'load-balancer-api-external: tcp connection to ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.361983ms
      message: 'load-balancer-api-external: tcp connection to ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:12:40Z"
    - latency: 8.173718ms
      message: 'load-balancer-api-external: resolved host name ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:12:40Z"
    - latency: 6.032615ms
      message: 'load-balancer-api-external: tcp connection to ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:11:40Z"
    - latency: 8.28668ms
      message: 'load-balancer-api-external: resolved host name ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:11:40Z"
    - latency: 6.138181ms
      message: 'load-balancer-api-external: tcp connection to ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:10:40Z"
    - latency: 8.45081ms
      message: 'load-balancer-api-external: resolved host name ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:10:40Z"
    - latency: 5.973664ms
      message: 'load-balancer-api-external: tcp connection to ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:09:40Z"
    - latency: 7.31976ms
      message: 'load-balancer-api-external: resolved host name ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:09:40Z"
    - latency: 4.753875ms
      message: 'load-balancer-api-external: tcp connection to ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:08:40Z"
    - latency: 7.391171ms
      message: 'load-balancer-api-external: resolved host name ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:08:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T16:06:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-55-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-55.ec2.internal
      uid: 03d7a1b6-6dc1-473d-9e03-b31444d7033b
    resourceVersion: "14589"
    uid: cdd28049-372c-4732-a4e2-e081e93720e3
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wnpcf
    targetEndpoint: ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T16:12:40Z"
      message: 'load-balancer-api-internal: tcp connection to ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.372545ms
      message: 'load-balancer-api-internal: tcp connection to ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:12:40Z"
    - latency: 8.129979ms
      message: 'load-balancer-api-internal: resolved host name ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:12:40Z"
    - latency: 6.031221ms
      message: 'load-balancer-api-internal: tcp connection to ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:11:40Z"
    - latency: 8.263359ms
      message: 'load-balancer-api-internal: resolved host name ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:11:40Z"
    - latency: 6.154382ms
      message: 'load-balancer-api-internal: tcp connection to ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:10:40Z"
    - latency: 8.418061ms
      message: 'load-balancer-api-internal: resolved host name ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:10:40Z"
    - latency: 5.990546ms
      message: 'load-balancer-api-internal: tcp connection to ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:09:40Z"
    - latency: 7.288134ms
      message: 'load-balancer-api-internal: resolved host name ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:09:40Z"
    - latency: 4.742763ms
      message: 'load-balancer-api-internal: tcp connection to ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:08:40Z"
    - latency: 7.334782ms
      message: 'load-balancer-api-internal: resolved host name ab8b59dd95abe4eee899d5e93f968dda-ec605efca1683879.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:08:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T16:06:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-55-to-network-check-target-ip-10-0-129-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-55.ec2.internal
      uid: 03d7a1b6-6dc1-473d-9e03-b31444d7033b
    resourceVersion: "11004"
    uid: 875f53fc-ac59-4bf9-a841-2806dc40cf25
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wnpcf
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T16:06:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-55-to-network-check-target-ip-10-0-139-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-55.ec2.internal
      uid: 03d7a1b6-6dc1-473d-9e03-b31444d7033b
    resourceVersion: "11003"
    uid: 307b6824-076f-41a6-b319-e5fcc3a641a6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wnpcf
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T16:06:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-55-to-network-check-target-ip-10-0-142-181
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-55.ec2.internal
      uid: 03d7a1b6-6dc1-473d-9e03-b31444d7033b
    resourceVersion: "11005"
    uid: c6d4c142-9dd1-411e-97e4-05839f7e624a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wnpcf
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T16:06:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-55-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-55.ec2.internal
      uid: 03d7a1b6-6dc1-473d-9e03-b31444d7033b
    resourceVersion: "14587"
    uid: 5eb764a8-28ab-4a65-920e-61e92d585304
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wnpcf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T16:12:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 956.78µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:12:40Z"
    - latency: 1.867005ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:12:40Z"
    - latency: 906.288µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:11:40Z"
    - latency: 1.789466ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:11:40Z"
    - latency: 882.27µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:10:40Z"
    - latency: 1.992986ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:10:40Z"
    - latency: 1.11271ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:09:40Z"
    - latency: 1.792703ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:09:40Z"
    - latency: 1.001431ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:08:40Z"
    - latency: 2.071404ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:08:40Z"
kind: List
metadata:
  resourceVersion: ""