apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:11:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-217-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-217.ec2.internal
      uid: 2af1db01-fabb-4f1c-b5dd-84159eb461a5
    resourceVersion: "24683"
    uid: c06db436-cb1b-4967-9fb4-b1ee7d51b073
  spec:
    sourcePod: network-check-source-685456655f-p2sfk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:18:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 876.552µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:28Z"
    - latency: 1.193554ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:28Z"
    - latency: 1.413182ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:28Z"
    - latency: 1.532467ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:15:28Z"
    - latency: 994.405µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:14:28Z"
    - latency: 933.349µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:13:28Z"
    - latency: 894.894µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:12:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:11:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-217-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-217.ec2.internal
      uid: 2af1db01-fabb-4f1c-b5dd-84159eb461a5
    resourceVersion: "23523"
    uid: 1c423c69-c1ce-48b9-9cae-74dac57886f4
  spec:
    sourcePod: network-check-source-685456655f-p2sfk
    targetEndpoint: ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:17:28Z"
      message: 'load-balancer-api-external: tcp connection to ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.464396ms
      message: 'load-balancer-api-external: tcp connection to ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:28Z"
    - latency: 7.365174ms
      message: 'load-balancer-api-external: resolved host name ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:17:28Z"
    - latency: 3.622567ms
      message: 'load-balancer-api-external: tcp connection to ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:28Z"
    - latency: 9.049567ms
      message: 'load-balancer-api-external: resolved host name ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:16:28Z"
    - latency: 4.780216ms
      message: 'load-balancer-api-external: tcp connection to ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:15:28Z"
    - latency: 10.060442ms
      message: 'load-balancer-api-external: resolved host name ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:15:28Z"
    - latency: 4.999021ms
      message: 'load-balancer-api-external: tcp connection to ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:14:28Z"
    - latency: 8.372349ms
      message: 'load-balancer-api-external: resolved host name ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:14:28Z"
    - latency: 5.798544ms
      message: 'load-balancer-api-external: tcp connection to ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:13:28Z"
    - latency: 6.900077ms
      message: 'load-balancer-api-external: resolved host name ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:13:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:11:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-217-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-217.ec2.internal
      uid: 2af1db01-fabb-4f1c-b5dd-84159eb461a5
    resourceVersion: "23522"
    uid: 67702e01-825e-421b-b762-c5dea764b92d
  spec:
    sourcePod: network-check-source-685456655f-p2sfk
    targetEndpoint: ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:17:28Z"
      message: 'load-balancer-api-internal: tcp connection to ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.497792ms
      message: 'load-balancer-api-internal: tcp connection to ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:28Z"
    - latency: 7.233514ms
      message: 'load-balancer-api-internal: resolved host name ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:17:28Z"
    - latency: 3.572375ms
      message: 'load-balancer-api-internal: tcp connection to ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:28Z"
    - latency: 9.106954ms
      message: 'load-balancer-api-internal: resolved host name ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:16:28Z"
    - latency: 4.806425ms
      message: 'load-balancer-api-internal: tcp connection to ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:15:28Z"
    - latency: 9.99244ms
      message: 'load-balancer-api-internal: resolved host name ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:15:28Z"
    - latency: 5.032916ms
      message: 'load-balancer-api-internal: tcp connection to ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:14:28Z"
    - latency: 8.272171ms
      message: 'load-balancer-api-internal: resolved host name ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:14:28Z"
    - latency: 5.881687ms
      message: 'load-balancer-api-internal: tcp connection to ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:13:28Z"
    - latency: 6.864505ms
      message: 'load-balancer-api-internal: resolved host name ab9238d58ed6d46f9b5af5f470c90e45-54c90de7293f36f9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:13:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:11:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-217-to-network-check-target-ip-10-0-131-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-217.ec2.internal
      uid: 2af1db01-fabb-4f1c-b5dd-84159eb461a5
    resourceVersion: "24681"
    uid: 08a96715-f624-4237-9390-d4846fc3c611
  spec:
    sourcePod: network-check-source-685456655f-p2sfk
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:18:28Z"
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.394747ms
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:28Z"
    - latency: 2.440595ms
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:28Z"
    - latency: 2.161631ms
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:28Z"
    - latency: 2.139651ms
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:15:28Z"
    - latency: 2.480572ms
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:14:28Z"
    - latency: 2.075279ms
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:13:28Z"
    - latency: 2.52472ms
      message: 'network-check-target-ip-10-0-131-73: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:12:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:11:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-217-to-network-check-target-ip-10-0-140-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-217.ec2.internal
      uid: 2af1db01-fabb-4f1c-b5dd-84159eb461a5
    resourceVersion: "24682"
    uid: 59d33884-4767-4fc6-a083-d6e105505710
  spec:
    sourcePod: network-check-source-685456655f-p2sfk
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:18:28Z"
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.329849ms
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:28Z"
    - latency: 2.009378ms
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:28Z"
    - latency: 2.407957ms
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:28Z"
    - latency: 2.269498ms
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:15:28Z"
    - latency: 2.276505ms
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:14:28Z"
    - latency: 2.452003ms
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:13:28Z"
    - latency: 2.238564ms
      message: 'network-check-target-ip-10-0-140-137: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:12:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:11:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-217-to-network-check-target-ip-10-0-142-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-217.ec2.internal
      uid: 2af1db01-fabb-4f1c-b5dd-84159eb461a5
    resourceVersion: "24680"
    uid: 574d800d-84b7-4f99-af16-75036a2af12e
  spec:
    sourcePod: network-check-source-685456655f-p2sfk
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:18:28Z"
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 909.562µs
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:28Z"
    - latency: 1.0532ms
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:28Z"
    - latency: 909.014µs
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:28Z"
    - latency: 943.43µs
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:15:28Z"
    - latency: 1.299959ms
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:14:28Z"
    - latency: 1.061461ms
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:13:28Z"
    - latency: 1.325965ms
      message: 'network-check-target-ip-10-0-142-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:12:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:11:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-217-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-217.ec2.internal
      uid: 2af1db01-fabb-4f1c-b5dd-84159eb461a5
    resourceVersion: "23521"
    uid: 981690d8-0f44-493e-8255-26774d965924
  spec:
    sourcePod: network-check-source-685456655f-p2sfk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:17:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 958.191µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:28Z"
    - latency: 1.871381ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:17:28Z"
    - latency: 772.452µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:28Z"
    - latency: 1.751ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:16:28Z"
    - latency: 1.189969ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:15:28Z"
    - latency: 1.918896ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:15:28Z"
    - latency: 745.389µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:14:28Z"
    - latency: 1.618431ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:14:28Z"
    - latency: 869.309µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:13:28Z"
    - latency: 1.826965ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:13:28Z"
kind: List
metadata:
  resourceVersion: ""