apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-242-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-242.us-east-2.compute.internal
      uid: 371a8c1c-b20e-4e76-8308-b3f6a7550ba7
    resourceVersion: "11846"
    uid: 799b174e-5c97-4e7e-840e-44593126ab16
  spec:
    sourcePod: network-check-source-6f78d59f99-lbwz4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:47:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 939.125µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:47:06Z"
    - latency: 843.689µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:46:06Z"
    - latency: 946.48µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:45:06Z"
    - latency: 1.447306ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:44:06Z"
    - latency: 968.211µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:43:06Z"
    - latency: 990.218µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:42:06Z"
    - latency: 1.088192ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:41:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-242-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-242.us-east-2.compute.internal
      uid: 371a8c1c-b20e-4e76-8308-b3f6a7550ba7
    resourceVersion: "12800"
    uid: 7b51ec39-ac69-4fc7-a1c2-f11c848ebb79
  spec:
    sourcePod: network-check-source-6f78d59f99-lbwz4
    targetEndpoint: a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:10Z"
      message: 'load-balancer-api-external: tcp connection to a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.278525ms
      message: 'load-balancer-api-external: tcp connection to a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:52:06Z"
    - latency: 7.989387ms
      message: 'load-balancer-api-external: resolved host name a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:52:06Z"
    - latency: 5.521764ms
      message: 'load-balancer-api-external: tcp connection to a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:51:06Z"
    - latency: 7.930816ms
      message: 'load-balancer-api-external: resolved host name a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:51:06Z"
    - latency: 7.853018ms
      message: 'load-balancer-api-external: tcp connection to a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:50:06Z"
    - latency: 8.089006ms
      message: 'load-balancer-api-external: resolved host name a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:50:06Z"
    - latency: 5.469229ms
      message: 'load-balancer-api-external: tcp connection to a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:49:06Z"
    - latency: 7.198423ms
      message: 'load-balancer-api-external: resolved host name a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:49:06Z"
    - latency: 4.983733ms
      message: 'load-balancer-api-external: tcp connection to a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:48:06Z"
    - latency: 7.76041ms
      message: 'load-balancer-api-external: resolved host name a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:48:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-242-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-242.us-east-2.compute.internal
      uid: 371a8c1c-b20e-4e76-8308-b3f6a7550ba7
    resourceVersion: "12801"
    uid: 0c3c69ca-99ac-48bf-8b53-33d716c9049f
  spec:
    sourcePod: network-check-source-6f78d59f99-lbwz4
    targetEndpoint: a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:06Z"
      message: 'load-balancer-api-internal: tcp connection to a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 9.034878ms
      message: 'load-balancer-api-internal: tcp connection to a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:52:06Z"
    - latency: 7.926419ms
      message: 'load-balancer-api-internal: resolved host name a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:52:06Z"
    - latency: 5.00607ms
      message: 'load-balancer-api-internal: tcp connection to a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:51:06Z"
    - latency: 7.855625ms
      message: 'load-balancer-api-internal: resolved host name a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:51:06Z"
    - latency: 5.341242ms
      message: 'load-balancer-api-internal: tcp connection to a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:50:06Z"
    - latency: 8.112893ms
      message: 'load-balancer-api-internal: resolved host name a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:50:06Z"
    - latency: 12.300462ms
      message: 'load-balancer-api-internal: tcp connection to a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:49:06Z"
    - latency: 7.243872ms
      message: 'load-balancer-api-internal: resolved host name a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:49:06Z"
    - latency: 4.974327ms
      message: 'load-balancer-api-internal: tcp connection to a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:48:06Z"
    - latency: 7.68574ms
      message: 'load-balancer-api-internal: resolved host name a548a510de0f44ab5a14f37a71a31957-a9c61003cc252b9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:48:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-242-to-network-check-target-ip-10-0-131-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-242.us-east-2.compute.internal
      uid: 371a8c1c-b20e-4e76-8308-b3f6a7550ba7
    resourceVersion: "11844"
    uid: 01be6cff-305f-4a63-a2d9-7c1c121c1a91
  spec:
    sourcePod: network-check-source-6f78d59f99-lbwz4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:47:06Z"
      message: 'network-check-target-ip-10-0-131-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.019663ms
      message: 'network-check-target-ip-10-0-131-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:47:06Z"
    - latency: 1.884755ms
      message: 'network-check-target-ip-10-0-131-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:46:06Z"
    - latency: 2.041671ms
      message: 'network-check-target-ip-10-0-131-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:45:06Z"
    - latency: 2.282892ms
      message: 'network-check-target-ip-10-0-131-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:44:06Z"
    - latency: 2.197588ms
      message: 'network-check-target-ip-10-0-131-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:43:06Z"
    - latency: 2.177049ms
      message: 'network-check-target-ip-10-0-131-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:42:06Z"
    - latency: 2.151746ms
      message: 'network-check-target-ip-10-0-131-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:41:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-242-to-network-check-target-ip-10-0-137-242
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-242.us-east-2.compute.internal
      uid: 371a8c1c-b20e-4e76-8308-b3f6a7550ba7
    resourceVersion: "11843"
    uid: 98d65d66-8f68-4212-8ec4-0321d3faf7da
  spec:
    sourcePod: network-check-source-6f78d59f99-lbwz4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:47:06Z"
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 761.381µs
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:47:06Z"
    - latency: 874.817µs
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:46:06Z"
    - latency: 912.208µs
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:45:06Z"
    - latency: 940.492µs
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:44:06Z"
    - latency: 1.032275ms
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:43:06Z"
    - latency: 971.131µs
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:42:06Z"
    - latency: 1.346421ms
      message: 'network-check-target-ip-10-0-137-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:41:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-242-to-network-check-target-ip-10-0-141-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-242.us-east-2.compute.internal
      uid: 371a8c1c-b20e-4e76-8308-b3f6a7550ba7
    resourceVersion: "11845"
    uid: f8a681d1-97e6-46f2-8342-53c41a8c9402
  spec:
    sourcePod: network-check-source-6f78d59f99-lbwz4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:47:06Z"
      message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.127921ms
      message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:47:06Z"
    - latency: 2.196075ms
      message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:46:06Z"
    - latency: 2.43434ms
      message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:45:06Z"
    - latency: 2.522092ms
      message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:44:06Z"
    - latency: 2.396149ms
      message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:43:06Z"
    - latency: 2.287946ms
      message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:42:06Z"
    - latency: 2.269309ms
      message: 'network-check-target-ip-10-0-141-76: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:41:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-242-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-242.us-east-2.compute.internal
      uid: 371a8c1c-b20e-4e76-8308-b3f6a7550ba7
    resourceVersion: "12799"
    uid: 8812b2ea-81d1-4dd6-bf63-1a4a77b121be
  spec:
    sourcePod: network-check-source-6f78d59f99-lbwz4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 837.239µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:52:06Z"
    - latency: 1.74177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:52:06Z"
    - latency: 868.35µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:51:06Z"
    - latency: 1.618812ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:51:06Z"
    - latency: 928.242µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:50:06Z"
    - latency: 2.087285ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:50:06Z"
    - latency: 783.807µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:49:06Z"
    - latency: 1.853144ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:49:06Z"
    - latency: 1.02211ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:48:06Z"
    - latency: 1.983789ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:48:06Z"
kind: List
metadata:
  resourceVersion: ""