apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 20eaa170-51d6-4ddd-8b49-1f8347464e55
    resourceVersion: "14238"
    uid: d590751c-c429-4914-b7f0-9beabf82998f
  spec:
    sourcePod: network-check-source-869dcfcdcd-4vknj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:02:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.246355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:59Z"
    - latency: 1.283894ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:59Z"
    - latency: 1.134051ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:59Z"
    - latency: 1.4504ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:59:59Z"
    - latency: 1.973432ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:58:59Z"
    - latency: 1.563725ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:57:59Z"
    - latency: 1.270764ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:56:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 20eaa170-51d6-4ddd-8b49-1f8347464e55
    resourceVersion: "13886"
    uid: aaad038f-a47e-4e07-b313-da0d0bf66171
  spec:
    sourcePod: network-check-source-869dcfcdcd-4vknj
    targetEndpoint: af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:01:59Z"
      message: 'load-balancer-api-external: tcp connection to af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.070249ms
      message: 'load-balancer-api-external: tcp connection to af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:59Z"
    - latency: 9.674314ms
      message: 'load-balancer-api-external: resolved host name af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:01:59Z"
    - latency: 6.69396ms
      message: 'load-balancer-api-external: tcp connection to af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:59Z"
    - latency: 8.45229ms
      message: 'load-balancer-api-external: resolved host name af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:00:59Z"
    - latency: 6.195681ms
      message: 'load-balancer-api-external: tcp connection to af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:59:59Z"
    - latency: 10.575317ms
      message: 'load-balancer-api-external: resolved host name af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:59:59Z"
    - latency: 3.874961ms
      message: 'load-balancer-api-external: tcp connection to af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:58:59Z"
    - latency: 13.859201ms
      message: 'load-balancer-api-external: resolved host name af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:58:59Z"
    - latency: 5.361152ms
      message: 'load-balancer-api-external: tcp connection to af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:57:59Z"
    - latency: 9.815497ms
      message: 'load-balancer-api-external: resolved host name af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:57:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 20eaa170-51d6-4ddd-8b49-1f8347464e55
    resourceVersion: "13885"
    uid: 36753389-7a69-4f5a-823d-612ff10443d6
  spec:
    sourcePod: network-check-source-869dcfcdcd-4vknj
    targetEndpoint: af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:01:59Z"
      message: 'load-balancer-api-internal: tcp connection to af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.810703ms
      message: 'load-balancer-api-internal: tcp connection to af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:59Z"
    - latency: 9.714222ms
      message: 'load-balancer-api-internal: resolved host name af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:01:59Z"
    - latency: 6.437221ms
      message: 'load-balancer-api-internal: tcp connection to af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:59Z"
    - latency: 8.437982ms
      message: 'load-balancer-api-internal: resolved host name af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:00:59Z"
    - latency: 6.234944ms
      message: 'load-balancer-api-internal: tcp connection to af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:59:59Z"
    - latency: 10.548139ms
      message: 'load-balancer-api-internal: resolved host name af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:59:59Z"
    - latency: 4.55757ms
      message: 'load-balancer-api-internal: tcp connection to af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:58:59Z"
    - latency: 13.94265ms
      message: 'load-balancer-api-internal: resolved host name af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:58:59Z"
    - latency: 5.286435ms
      message: 'load-balancer-api-internal: tcp connection to af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:57:59Z"
    - latency: 9.828653ms
      message: 'load-balancer-api-internal: resolved host name af1641e8b5dbb4d50b1c308f91dceb3d-c8793752bc4ba3e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:57:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-network-check-target-ip-10-0-134-91
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 20eaa170-51d6-4ddd-8b49-1f8347464e55
    resourceVersion: "14235"
    uid: 7b8613f0-8653-4745-82b3-b0900dd364e5
  spec:
    sourcePod: network-check-source-869dcfcdcd-4vknj
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:02:59Z"
      message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.337822ms
      message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:59Z"
    - latency: 2.590775ms
      message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:59Z"
    - latency: 2.40773ms
      message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:59Z"
    - latency: 2.450209ms
      message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:59:59Z"
    - latency: 3.836962ms
      message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:58:59Z"
    - latency: 2.765829ms
      message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:57:59Z"
    - latency: 2.795235ms
      message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:56:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-network-check-target-ip-10-0-136-145
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 20eaa170-51d6-4ddd-8b49-1f8347464e55
    resourceVersion: "14237"
    uid: e62c657f-0d5f-4082-b011-872c69099e66
  spec:
    sourcePod: network-check-source-869dcfcdcd-4vknj
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:02:59Z"
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.378043ms
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:59Z"
    - latency: 2.719362ms
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:59Z"
    - latency: 2.46828ms
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:59Z"
    - latency: 2.950511ms
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:59:59Z"
    - latency: 3.036058ms
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:58:59Z"
    - latency: 2.907389ms
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:57:59Z"
    - latency: 2.482456ms
      message: 'network-check-target-ip-10-0-136-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:56:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-network-check-target-ip-10-0-140-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 20eaa170-51d6-4ddd-8b49-1f8347464e55
    resourceVersion: "14236"
    uid: 5a021e6a-f961-4196-ae25-091b9ba30ad2
  spec:
    sourcePod: network-check-source-869dcfcdcd-4vknj
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:02:59Z"
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.56292ms
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:59Z"
    - latency: 1.0573ms
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:59Z"
    - latency: 873.847µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:59Z"
    - latency: 876.753µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:59:59Z"
    - latency: 2.167415ms
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:58:59Z"
    - latency: 1.784572ms
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:57:59Z"
    - latency: 1.959589ms
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:56:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 20eaa170-51d6-4ddd-8b49-1f8347464e55
    resourceVersion: "13884"
    uid: 757eadd7-9c22-4e4a-8549-9610f8831aec
  spec:
    sourcePod: network-check-source-869dcfcdcd-4vknj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:01:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 959.139µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:59Z"
    - latency: 2.030249ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:01:59Z"
    - latency: 972.193µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:59Z"
    - latency: 1.878036ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:00:59Z"
    - latency: 1.271035ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:59:59Z"
    - latency: 1.868119ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:59:59Z"
    - latency: 1.275477ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:58:59Z"
    - latency: 2.843044ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:58:59Z"
    - latency: 1.019296ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:57:59Z"
    - latency: 2.63539ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:57:59Z"
kind: List
metadata:
  resourceVersion: ""