apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:04:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.ec2.internal
      uid: accef7fb-9924-4a36-9b5b-a7cc832aafcf
    resourceVersion: "14049"
    uid: ed7c2d05-08b3-437d-8ae7-086ef9298621
  spec:
    sourcePod: network-check-source-7d88cb55d8-wggpq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:11:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 890.201µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:11:36Z"
    - latency: 1.151295ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:10:36Z"
    - latency: 876.343µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:09:36Z"
    - latency: 1.277477ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:08:36Z"
    - latency: 1.288417ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:07:36Z"
    - latency: 1.045205ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:06:36Z"
    - latency: 867.799µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:05:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:04:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.ec2.internal
      uid: accef7fb-9924-4a36-9b5b-a7cc832aafcf
    resourceVersion: "15780"
    uid: c06aa7da-5967-4eb9-85a4-bc8c21ff9755
  spec:
    sourcePod: network-check-source-7d88cb55d8-wggpq
    targetEndpoint: ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:10:36Z"
      message: 'load-balancer-api-external: tcp connection to ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.379817ms
      message: 'load-balancer-api-external: tcp connection to ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:16:36Z"
    - latency: 6.493666ms
      message: 'load-balancer-api-external: resolved host name ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:16:36Z"
    - latency: 4.749945ms
      message: 'load-balancer-api-external: tcp connection to ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:15:36Z"
    - latency: 6.374467ms
      message: 'load-balancer-api-external: resolved host name ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:15:36Z"
    - latency: 5.336252ms
      message: 'load-balancer-api-external: tcp connection to ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:14:36Z"
    - latency: 6.108591ms
      message: 'load-balancer-api-external: resolved host name ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:14:36Z"
    - latency: 5.223614ms
      message: 'load-balancer-api-external: tcp connection to ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:13:36Z"
    - latency: 6.726213ms
      message: 'load-balancer-api-external: resolved host name ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:13:36Z"
    - latency: 4.666144ms
      message: 'load-balancer-api-external: tcp connection to ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:12:36Z"
    - latency: 6.452377ms
      message: 'load-balancer-api-external: resolved host name ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:12:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:04:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.ec2.internal
      uid: accef7fb-9924-4a36-9b5b-a7cc832aafcf
    resourceVersion: "15781"
    uid: bdc8a2f0-d99d-4a57-a147-1faf5a542bff
  spec:
    sourcePod: network-check-source-7d88cb55d8-wggpq
    targetEndpoint: ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:10:36Z"
      message: 'load-balancer-api-internal: tcp connection to ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.760768ms
      message: 'load-balancer-api-internal: tcp connection to ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:16:36Z"
    - latency: 6.52857ms
      message: 'load-balancer-api-internal: resolved host name ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:16:36Z"
    - latency: 4.725669ms
      message: 'load-balancer-api-internal: tcp connection to ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:15:36Z"
    - latency: 6.458133ms
      message: 'load-balancer-api-internal: resolved host name ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:15:36Z"
    - latency: 4.761053ms
      message: 'load-balancer-api-internal: tcp connection to ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:14:36Z"
    - latency: 6.210259ms
      message: 'load-balancer-api-internal: resolved host name ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:14:36Z"
    - latency: 5.210744ms
      message: 'load-balancer-api-internal: tcp connection to ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:13:36Z"
    - latency: 6.783336ms
      message: 'load-balancer-api-internal: resolved host name ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:13:36Z"
    - latency: 4.609754ms
      message: 'load-balancer-api-internal: tcp connection to ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:12:36Z"
    - latency: 6.487109ms
      message: 'load-balancer-api-internal: resolved host name ae9b50dddd88d439881b615d336ad634-f76863b34f218a85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:12:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:04:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-network-check-target-ip-10-0-132-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.ec2.internal
      uid: accef7fb-9924-4a36-9b5b-a7cc832aafcf
    resourceVersion: "14047"
    uid: d061da15-0956-417d-ae24-e45be91f3859
  spec:
    sourcePod: network-check-source-7d88cb55d8-wggpq
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:11:36Z"
      message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.972798ms
      message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:11:36Z"
    - latency: 1.967533ms
      message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:10:36Z"
    - latency: 2.023164ms
      message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:09:36Z"
    - latency: 2.031227ms
      message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:08:36Z"
    - latency: 1.664939ms
      message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:07:36Z"
    - latency: 1.926401ms
      message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:06:36Z"
    - latency: 2.209559ms
      message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:05:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:04:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-network-check-target-ip-10-0-134-214
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.ec2.internal
      uid: accef7fb-9924-4a36-9b5b-a7cc832aafcf
    resourceVersion: "14048"
    uid: c2f1bce1-5954-4eee-93b2-30b12de9e162
  spec:
    sourcePod: network-check-source-7d88cb55d8-wggpq
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:11:36Z"
      message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.984596ms
      message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:11:36Z"
    - latency: 2.276013ms
      message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:10:36Z"
    - latency: 2.056777ms
      message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:09:36Z"
    - latency: 2.356325ms
      message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:08:36Z"
    - latency: 1.887029ms
      message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:07:36Z"
    - latency: 2.464715ms
      message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:06:36Z"
    - latency: 2.101314ms
      message: 'network-check-target-ip-10-0-134-214: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:05:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:04:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-network-check-target-ip-10-0-143-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.ec2.internal
      uid: accef7fb-9924-4a36-9b5b-a7cc832aafcf
    resourceVersion: "14046"
    uid: a186f3e3-eedc-4f55-82bb-77de1c64472a
  spec:
    sourcePod: network-check-source-7d88cb55d8-wggpq
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:11:36Z"
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.137418ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:11:36Z"
    - latency: 1.480221ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:10:36Z"
    - latency: 1.318522ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:09:36Z"
    - latency: 1.487783ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:08:36Z"
    - latency: 858.559µs
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:07:36Z"
    - latency: 977.179µs
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:06:36Z"
    - latency: 1.54872ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:05:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:04:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-101-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-101.ec2.internal
      uid: accef7fb-9924-4a36-9b5b-a7cc832aafcf
    resourceVersion: "15779"
    uid: 50186989-c65d-4a83-a724-41bc921bdab9
  spec:
    sourcePod: network-check-source-7d88cb55d8-wggpq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:10:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.084175ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:16:36Z"
    - latency: 1.574529ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:16:36Z"
    - latency: 740.047µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:15:36Z"
    - latency: 1.655713ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:15:36Z"
    - latency: 1.195116ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:14:36Z"
    - latency: 1.697036ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:14:36Z"
    - latency: 925.818µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:13:36Z"
    - latency: 1.717908ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:13:36Z"
    - latency: 802.501µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:12:36Z"
    - latency: 1.67661ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:12:36Z"
kind: List
metadata:
  resourceVersion: ""