apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:28:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-148-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-148.ec2.internal
      uid: 330a25a6-e79d-49ec-8310-b1afa4ac9ca5
    resourceVersion: "15087"
    uid: 7c2f4006-6cff-49dc-babd-cf94101f610d
  spec:
    sourcePod: network-check-source-6f8b768455-z6jr4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:35:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.318187ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:35:41Z"
    - latency: 1.031872ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:34:41Z"
    - latency: 1.114593ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:33:41Z"
    - latency: 1.331932ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:32:41Z"
    - latency: 909.697µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:31:41Z"
    - latency: 826.499µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:30:41Z"
    - latency: 939.011µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:29:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:28:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-148-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-148.ec2.internal
      uid: 330a25a6-e79d-49ec-8310-b1afa4ac9ca5
    resourceVersion: "14739"
    uid: 4c75449e-9ece-49d7-9ce1-1b57680bf0cd
  spec:
    sourcePod: network-check-source-6f8b768455-z6jr4
    targetEndpoint: ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:34:41Z"
      message: 'load-balancer-api-external: tcp connection to ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.350754ms
      message: 'load-balancer-api-external: tcp connection to ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:34:41Z"
    - latency: 9.389345ms
      message: 'load-balancer-api-external: resolved host name ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:34:41Z"
    - latency: 12.993018ms
      message: 'load-balancer-api-external: tcp connection to ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:33:41Z"
    - latency: 8.678322ms
      message: 'load-balancer-api-external: resolved host name ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:33:41Z"
    - latency: 5.266575ms
      message: 'load-balancer-api-external: tcp connection to ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:32:41Z"
    - latency: 8.351911ms
      message: 'load-balancer-api-external: resolved host name ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:32:41Z"
    - latency: 7.260456ms
      message: 'load-balancer-api-external: tcp connection to ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:31:41Z"
    - latency: 10.382694ms
      message: 'load-balancer-api-external: resolved host name ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:31:41Z"
    - latency: 5.961167ms
      message: 'load-balancer-api-external: tcp connection to ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:30:41Z"
    - latency: 8.206253ms
      message: 'load-balancer-api-external: resolved host name ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:30:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:28:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-148-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-148.ec2.internal
      uid: 330a25a6-e79d-49ec-8310-b1afa4ac9ca5
    resourceVersion: "14740"
    uid: 5750a5fc-671d-47dd-bb31-c47e9223495d
  spec:
    sourcePod: network-check-source-6f8b768455-z6jr4
    targetEndpoint: ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:34:41Z"
      message: 'load-balancer-api-internal: tcp connection to ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.247087ms
      message: 'load-balancer-api-internal: tcp connection to ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:34:41Z"
    - latency: 9.647383ms
      message: 'load-balancer-api-internal: resolved host name ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:34:41Z"
    - latency: 5.176854ms
      message: 'load-balancer-api-internal: tcp connection to ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:33:41Z"
    - latency: 8.730604ms
      message: 'load-balancer-api-internal: resolved host name ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:33:41Z"
    - latency: 5.260205ms
      message: 'load-balancer-api-internal: tcp connection to ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:32:41Z"
    - latency: 8.425622ms
      message: 'load-balancer-api-internal: resolved host name ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:32:41Z"
    - latency: 7.250121ms
      message: 'load-balancer-api-internal: tcp connection to ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:31:41Z"
    - latency: 10.423433ms
      message: 'load-balancer-api-internal: resolved host name ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:31:41Z"
    - latency: 5.076358ms
      message: 'load-balancer-api-internal: tcp connection to ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:30:41Z"
    - latency: 8.171534ms
      message: 'load-balancer-api-internal: resolved host name ab239c4f108dc45d395287edb7cd2527-d0125e52905b6023.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:30:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:28:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-148-to-network-check-target-ip-10-0-133-249
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-148.ec2.internal
      uid: 330a25a6-e79d-49ec-8310-b1afa4ac9ca5
    resourceVersion: "15086"
    uid: b85a0fd6-8d22-415b-9006-189cfface5be
  spec:
    sourcePod: network-check-source-6f8b768455-z6jr4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:35:41Z"
      message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.269141ms
      message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:35:41Z"
    - latency: 2.638713ms
      message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:34:41Z"
    - latency: 2.13226ms
      message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:33:41Z"
    - latency: 2.057518ms
      message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:32:41Z"
    - latency: 2.076063ms
      message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:31:41Z"
    - latency: 2.285496ms
      message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:30:41Z"
    - latency: 2.282735ms
      message: 'network-check-target-ip-10-0-133-249: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:29:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:28:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-148-to-network-check-target-ip-10-0-140-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-148.ec2.internal
      uid: 330a25a6-e79d-49ec-8310-b1afa4ac9ca5
    resourceVersion: "15085"
    uid: 59662247-c155-4c27-b474-6baa7b9cfe3e
  spec:
    sourcePod: network-check-source-6f8b768455-z6jr4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:35:41Z"
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.294826ms
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:35:41Z"
    - latency: 1.492664ms
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:34:41Z"
    - latency: 929.69µs
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:33:41Z"
    - latency: 816.102µs
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:32:41Z"
    - latency: 852.849µs
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:31:41Z"
    - latency: 1.258646ms
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:30:41Z"
    - latency: 1.413434ms
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:29:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:28:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-148-to-network-check-target-ip-10-0-143-106
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-148.ec2.internal
      uid: 330a25a6-e79d-49ec-8310-b1afa4ac9ca5
    resourceVersion: "15084"
    uid: a5c39eec-bd70-428a-9135-1da3652a4e55
  spec:
    sourcePod: network-check-source-6f8b768455-z6jr4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:35:41Z"
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.252737ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:35:41Z"
    - latency: 2.217721ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:34:41Z"
    - latency: 2.20225ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:33:41Z"
    - latency: 1.985046ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:32:41Z"
    - latency: 2.087342ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:31:41Z"
    - latency: 2.076341ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:30:41Z"
    - latency: 2.0767ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:29:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:28:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-148-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-148.ec2.internal
      uid: 330a25a6-e79d-49ec-8310-b1afa4ac9ca5
    resourceVersion: "14738"
    uid: 676e8198-a758-4350-a283-0decef99494b
  spec:
    sourcePod: network-check-source-6f8b768455-z6jr4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:34:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 962.343µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:34:41Z"
    - latency: 1.902734ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:34:41Z"
    - latency: 805.135µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:33:41Z"
    - latency: 1.894981ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:33:41Z"
    - latency: 1.127745ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:32:41Z"
    - latency: 2.067205ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:32:41Z"
    - latency: 829.758µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:31:41Z"
    - latency: 2.06176ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:31:41Z"
    - latency: 773.597µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:30:41Z"
    - latency: 2.174155ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:30:41Z"
kind: List
metadata:
  resourceVersion: ""