apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:12:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-104-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-104.ec2.internal
      uid: d710b391-ee2a-4831-a700-aca4ee9e46dd
    resourceVersion: "22343"
    uid: d0ccc64c-a058-45ef-98bd-24b3bf899894
  spec:
    sourcePod: network-check-source-685456655f-gndjx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:19:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.179064ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:19:04Z"
    - latency: 1.063699ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:18:04Z"
    - latency: 1.02955ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:17:04Z"
    - latency: 960.703µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:16:04Z"
    - latency: 1.224917ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:15:04Z"
    - latency: 973.886µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:14:04Z"
    - latency: 895.889µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:13:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:12:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-104-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-104.ec2.internal
      uid: d710b391-ee2a-4831-a700-aca4ee9e46dd
    resourceVersion: "26367"
    uid: 68fdf1ec-d835-4873-bd23-97a1e28b0b12
  spec:
    sourcePod: network-check-source-685456655f-gndjx
    targetEndpoint: a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:18:04Z"
      message: 'load-balancer-api-external: tcp connection to a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.695824ms
      message: 'load-balancer-api-external: tcp connection to a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:24:04Z"
    - latency: 6.729658ms
      message: 'load-balancer-api-external: resolved host name a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:24:04Z"
    - latency: 4.779993ms
      message: 'load-balancer-api-external: tcp connection to a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:23:04Z"
    - latency: 6.884952ms
      message: 'load-balancer-api-external: resolved host name a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:23:04Z"
    - latency: 5.107813ms
      message: 'load-balancer-api-external: tcp connection to a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:22:04Z"
    - latency: 6.6546ms
      message: 'load-balancer-api-external: resolved host name a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:22:04Z"
    - latency: 3.958037ms
      message: 'load-balancer-api-external: tcp connection to a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:21:04Z"
    - latency: 6.676368ms
      message: 'load-balancer-api-external: resolved host name a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:21:04Z"
    - latency: 5.783024ms
      message: 'load-balancer-api-external: tcp connection to a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:20:04Z"
    - latency: 8.118418ms
      message: 'load-balancer-api-external: resolved host name a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:20:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:12:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-104-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-104.ec2.internal
      uid: d710b391-ee2a-4831-a700-aca4ee9e46dd
    resourceVersion: "26368"
    uid: ab18a1ec-8e85-4e36-881c-56d7c248422d
  spec:
    sourcePod: network-check-source-685456655f-gndjx
    targetEndpoint: a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:18:04Z"
      message: 'load-balancer-api-internal: tcp connection to a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.661128ms
      message: 'load-balancer-api-internal: tcp connection to a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:24:04Z"
    - latency: 6.797475ms
      message: 'load-balancer-api-internal: resolved host name a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:24:04Z"
    - latency: 6.107705ms
      message: 'load-balancer-api-internal: tcp connection to a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:23:04Z"
    - latency: 6.844205ms
      message: 'load-balancer-api-internal: resolved host name a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:23:04Z"
    - latency: 5.09837ms
      message: 'load-balancer-api-internal: tcp connection to a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:22:04Z"
    - latency: 6.560156ms
      message: 'load-balancer-api-internal: resolved host name a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:22:04Z"
    - latency: 4.401247ms
      message: 'load-balancer-api-internal: tcp connection to a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:21:04Z"
    - latency: 6.764402ms
      message: 'load-balancer-api-internal: resolved host name a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:21:04Z"
    - latency: 5.794334ms
      message: 'load-balancer-api-internal: tcp connection to a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:20:04Z"
    - latency: 8.028249ms
      message: 'load-balancer-api-internal: resolved host name a95dd6388bc61401ea24bdf94f25d8cb-324f3895124f1a0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:20:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:12:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-104-to-network-check-target-ip-10-0-131-104
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-104.ec2.internal
      uid: d710b391-ee2a-4831-a700-aca4ee9e46dd
    resourceVersion: "22340"
    uid: 995c821b-d131-4faf-83b6-ef6ccd2075b2
  spec:
    sourcePod: network-check-source-685456655f-gndjx
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:19:04Z"
      message: 'network-check-target-ip-10-0-131-104: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.122905ms
      message: 'network-check-target-ip-10-0-131-104: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:19:04Z"
    - latency: 1.49357ms
      message: 'network-check-target-ip-10-0-131-104: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:18:04Z"
    - latency: 987.951µs
      message: 'network-check-target-ip-10-0-131-104: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:17:04Z"
    - latency: 900.555µs
      message: 'network-check-target-ip-10-0-131-104: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:16:04Z"
    - latency: 954.734µs
      message: 'network-check-target-ip-10-0-131-104: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:15:04Z"
    - latency: 1.294144ms
      message: 'network-check-target-ip-10-0-131-104: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:14:04Z"
    - latency: 1.756991ms
      message: 'network-check-target-ip-10-0-131-104: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:13:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:12:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-104-to-network-check-target-ip-10-0-133-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-104.ec2.internal
      uid: d710b391-ee2a-4831-a700-aca4ee9e46dd
    resourceVersion: "22341"
    uid: bb9f0187-05ce-48fe-8329-91a11f10ab27
  spec:
    sourcePod: network-check-source-685456655f-gndjx
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:19:04Z"
      message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.24973ms
      message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:19:04Z"
    - latency: 2.646837ms
      message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:18:04Z"
    - latency: 2.32467ms
      message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:17:04Z"
    - latency: 3.181827ms
      message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:16:04Z"
    - latency: 2.350014ms
      message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:15:04Z"
    - latency: 2.429166ms
      message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:14:04Z"
    - latency: 2.52573ms
      message: 'network-check-target-ip-10-0-133-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:13:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:12:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-104-to-network-check-target-ip-10-0-142-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-104.ec2.internal
      uid: d710b391-ee2a-4831-a700-aca4ee9e46dd
    resourceVersion: "22342"
    uid: 61ebe18c-986c-4f94-9229-1048c426cde6
  spec:
    sourcePod: network-check-source-685456655f-gndjx
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:19:04Z"
      message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.547525ms
      message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:19:04Z"
    - latency: 2.385794ms
      message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:18:04Z"
    - latency: 2.179449ms
      message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:17:04Z"
    - latency: 1.950749ms
      message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:16:04Z"
    - latency: 2.261258ms
      message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:15:04Z"
    - latency: 1.865362ms
      message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:14:04Z"
    - latency: 2.696675ms
      message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:13:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:12:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-104-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-104.ec2.internal
      uid: d710b391-ee2a-4831-a700-aca4ee9e46dd
    resourceVersion: "26365"
    uid: f6b944e5-29f5-43a8-9f64-d7c8e25ccf43
  spec:
    sourcePod: network-check-source-685456655f-gndjx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:18:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.285016ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:24:04Z"
    - latency: 1.750741ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:24:04Z"
    - latency: 1.063604ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:23:04Z"
    - latency: 2.032995ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:23:04Z"
    - latency: 936.222µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:22:04Z"
    - latency: 1.802301ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:22:04Z"
    - latency: 1.005399ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:21:04Z"
    - latency: 2.060527ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:21:04Z"
    - latency: 843.747µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:20:04Z"
    - latency: 1.734486ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:20:04Z"
kind: List
metadata:
  resourceVersion: ""