apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:10:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-213-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-213.us-west-2.compute.internal
      uid: 520164c0-049b-429e-b898-931c052991af
    resourceVersion: "11866"
    uid: a56701c3-74b4-4f5d-b9fa-6145b277150d
  spec:
    sourcePod: network-check-source-6f78d59f99-d2565
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:17:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.030619ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:17:01Z"
    - latency: 954.776µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:01Z"
    - latency: 907.209µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 1.06435ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 898.541µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 993.758µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:01Z"
    - latency: 976.983µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:10:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-213-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-213.us-west-2.compute.internal
      uid: 520164c0-049b-429e-b898-931c052991af
    resourceVersion: "11478"
    uid: 34bcb591-3937-4738-a12c-d5121111f877
  spec:
    sourcePod: network-check-source-6f78d59f99-d2565
    targetEndpoint: a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:16:01Z"
      message: 'load-balancer-api-external: tcp connection to a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 56.410546ms
      message: 'load-balancer-api-external: tcp connection to a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:01Z"
    - latency: 8.28836ms
      message: 'load-balancer-api-external: resolved host name a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:16:01Z"
    - latency: 58.377653ms
      message: 'load-balancer-api-external: tcp connection to a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 10.673897ms
      message: 'load-balancer-api-external: resolved host name a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 57.894492ms
      message: 'load-balancer-api-external: tcp connection to a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 9.102407ms
      message: 'load-balancer-api-external: resolved host name a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 52.700489ms
      message: 'load-balancer-api-external: tcp connection to a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 8.234295ms
      message: 'load-balancer-api-external: resolved host name a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 49.783848ms
      message: 'load-balancer-api-external: tcp connection to a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:01Z"
    - latency: 9.075837ms
      message: 'load-balancer-api-external: resolved host name a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:12:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:10:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-213-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-213.us-west-2.compute.internal
      uid: 520164c0-049b-429e-b898-931c052991af
    resourceVersion: "11477"
    uid: 59d69742-5d73-4384-bbfb-962b24289538
  spec:
    sourcePod: network-check-source-6f78d59f99-d2565
    targetEndpoint: a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:16:01Z"
      message: 'load-balancer-api-internal: tcp connection to a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 56.434528ms
      message: 'load-balancer-api-internal: tcp connection to a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:01Z"
    - latency: 8.326248ms
      message: 'load-balancer-api-internal: resolved host name a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:16:01Z"
    - latency: 58.385348ms
      message: 'load-balancer-api-internal: tcp connection to a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 10.613898ms
      message: 'load-balancer-api-internal: resolved host name a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 57.53013ms
      message: 'load-balancer-api-internal: tcp connection to a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 9.143075ms
      message: 'load-balancer-api-internal: resolved host name a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 50.233333ms
      message: 'load-balancer-api-internal: tcp connection to a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 8.201036ms
      message: 'load-balancer-api-internal: resolved host name a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 49.886933ms
      message: 'load-balancer-api-internal: tcp connection to a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:01Z"
    - latency: 9.041271ms
      message: 'load-balancer-api-internal: resolved host name a0ef1e737f8eb467baa3f9fe550887be-b21f26380dee9f90.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:12:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:10:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-213-to-network-check-target-ip-10-0-128-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-213.us-west-2.compute.internal
      uid: 520164c0-049b-429e-b898-931c052991af
    resourceVersion: "11863"
    uid: 57285baa-3d15-4c44-904d-7a5ec696030d
  spec:
    sourcePod: network-check-source-6f78d59f99-d2565
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:17:01Z"
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.543756ms
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:17:01Z"
    - latency: 2.417122ms
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:01Z"
    - latency: 2.38648ms
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 2.460796ms
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 2.365603ms
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 2.223122ms
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:01Z"
    - latency: 2.315857ms
      message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:10:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-213-to-network-check-target-ip-10-0-138-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-213.us-west-2.compute.internal
      uid: 520164c0-049b-429e-b898-931c052991af
    resourceVersion: "11861"
    uid: b22b165e-9b29-47d9-a51e-7b230b065688
  spec:
    sourcePod: network-check-source-6f78d59f99-d2565
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:17:01Z"
      message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.430872ms
      message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:17:01Z"
    - latency: 958.694µs
      message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:01Z"
    - latency: 1.343134ms
      message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 1.66757ms
      message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 1.087369ms
      message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 1.402378ms
      message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:01Z"
    - latency: 1.621883ms
      message: 'network-check-target-ip-10-0-138-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:10:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-213-to-network-check-target-ip-10-0-142-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-213.us-west-2.compute.internal
      uid: 520164c0-049b-429e-b898-931c052991af
    resourceVersion: "11862"
    uid: 7660db3b-6690-4dd1-8111-7604b537d976
  spec:
    sourcePod: network-check-source-6f78d59f99-d2565
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:17:01Z"
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.421846ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:17:01Z"
    - latency: 2.313581ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:01Z"
    - latency: 2.312538ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 2.527345ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 2.231411ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 2.145589ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:01Z"
    - latency: 2.487665ms
      message: 'network-check-target-ip-10-0-142-155: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:11:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:10:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-213-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-213.us-west-2.compute.internal
      uid: 520164c0-049b-429e-b898-931c052991af
    resourceVersion: "11475"
    uid: c13099e3-8476-4dc3-a11f-bd4acb9681f1
  spec:
    sourcePod: network-check-source-6f78d59f99-d2565
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:16:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 814.363µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:01Z"
    - latency: 1.726614ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:16:01Z"
    - latency: 830.313µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 1.709393ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:15:01Z"
    - latency: 1.193599ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 2.085833ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:14:01Z"
    - latency: 887.151µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 1.75692ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:13:01Z"
    - latency: 919.762µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:01Z"
    - latency: 2.406764ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:12:01Z"
kind: List
metadata:
  resourceVersion: ""