apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T02:13:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-24-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-24.ec2.internal
      uid: 185cd0e0-94eb-4ee6-b5b4-f683b64c14b7
    resourceVersion: "22840"
    uid: 81c7772b-9343-4546-ae54-07a4bf82d4b6
  spec:
    sourcePod: network-check-source-685456655f-29z6m
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T02:20:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.148917ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:20:24Z"
    - latency: 1.033378ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:19:24Z"
    - latency: 917.491µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:18:24Z"
    - latency: 1.250269ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:17:24Z"
    - latency: 1.074679ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:16:24Z"
    - latency: 1.08928ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:15:24Z"
    - latency: 1.039667ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:14:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T02:13:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-24-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-24.ec2.internal
      uid: 185cd0e0-94eb-4ee6-b5b4-f683b64c14b7
    resourceVersion: "21580"
    uid: f34b12e3-6e51-421b-a9e3-58ac69049b14
  spec:
    sourcePod: network-check-source-685456655f-29z6m
    targetEndpoint: a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T02:19:24Z"
      message: 'load-balancer-api-external: tcp connection to a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.848019ms
      message: 'load-balancer-api-external: tcp connection to a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:19:24Z"
    - latency: 8.72972ms
      message: 'load-balancer-api-external: resolved host name a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T02:19:24Z"
    - latency: 3.308166ms
      message: 'load-balancer-api-external: tcp connection to a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:18:24Z"
    - latency: 8.289508ms
      message: 'load-balancer-api-external: resolved host name a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T02:18:24Z"
    - latency: 3.744745ms
      message: 'load-balancer-api-external: tcp connection to a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:17:24Z"
    - latency: 7.193238ms
      message: 'load-balancer-api-external: resolved host name a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T02:17:24Z"
    - latency: 4.114473ms
      message: 'load-balancer-api-external: tcp connection to a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:16:24Z"
    - latency: 8.322728ms
      message: 'load-balancer-api-external: resolved host name a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T02:16:24Z"
    - latency: 3.409227ms
      message: 'load-balancer-api-external: tcp connection to a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:15:24Z"
    - latency: 8.578942ms
      message: 'load-balancer-api-external: resolved host name a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T02:15:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T02:13:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-24-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-24.ec2.internal
      uid: 185cd0e0-94eb-4ee6-b5b4-f683b64c14b7
    resourceVersion: "21579"
    uid: 86968be0-1377-4117-a80f-2757f757a7cf
  spec:
    sourcePod: network-check-source-685456655f-29z6m
    targetEndpoint: a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T02:19:24Z"
      message: 'load-balancer-api-internal: tcp connection to a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.886402ms
      message: 'load-balancer-api-internal: tcp connection to a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:19:24Z"
    - latency: 8.681337ms
      message: 'load-balancer-api-internal: resolved host name a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T02:19:24Z"
    - latency: 4.000623ms
      message: 'load-balancer-api-internal: tcp connection to a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:18:24Z"
    - latency: 8.309726ms
      message: 'load-balancer-api-internal: resolved host name a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T02:18:24Z"
    - latency: 4.79066ms
      message: 'load-balancer-api-internal: tcp connection to a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:17:24Z"
    - latency: 7.135586ms
      message: 'load-balancer-api-internal: resolved host name a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T02:17:24Z"
    - latency: 4.091501ms
      message: 'load-balancer-api-internal: tcp connection to a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:16:24Z"
    - latency: 8.295401ms
      message: 'load-balancer-api-internal: resolved host name a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T02:16:24Z"
    - latency: 3.427952ms
      message: 'load-balancer-api-internal: tcp connection to a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:15:24Z"
    - latency: 8.56475ms
      message: 'load-balancer-api-internal: resolved host name a7de9671446e3468497db8922078c79e-2d2867a89f04cf69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T02:15:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T02:13:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-24-to-network-check-target-ip-10-0-128-218
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-24.ec2.internal
      uid: 185cd0e0-94eb-4ee6-b5b4-f683b64c14b7
    resourceVersion: "22839"
    uid: 47157b60-45bb-40e7-8186-43bee722510b
  spec:
    sourcePod: network-check-source-685456655f-29z6m
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T02:20:24Z"
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.926957ms
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:20:24Z"
    - latency: 1.881147ms
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:19:24Z"
    - latency: 1.987455ms
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:18:24Z"
    - latency: 2.035751ms
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:17:24Z"
    - latency: 1.86864ms
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:16:24Z"
    - latency: 1.877631ms
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:15:24Z"
    - latency: 2.031133ms
      message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:14:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T02:13:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-24-to-network-check-target-ip-10-0-130-24
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-24.ec2.internal
      uid: 185cd0e0-94eb-4ee6-b5b4-f683b64c14b7
    resourceVersion: "22837"
    uid: cc6ac7eb-d1f2-41d0-b3e7-f76aed820575
  spec:
    sourcePod: network-check-source-685456655f-29z6m
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T02:20:24Z"
      message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 909.41µs
      message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:20:24Z"
    - latency: 900.018µs
      message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:19:24Z"
    - latency: 1.430886ms
      message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:18:24Z"
    - latency: 1.639167ms
      message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:17:24Z"
    - latency: 858.382µs
      message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:16:24Z"
    - latency: 878.325µs
      message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:15:24Z"
    - latency: 1.21129ms
      message: 'network-check-target-ip-10-0-130-24: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:14:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T02:13:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-24-to-network-check-target-ip-10-0-137-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-24.ec2.internal
      uid: 185cd0e0-94eb-4ee6-b5b4-f683b64c14b7
    resourceVersion: "22838"
    uid: b0850af2-c30c-4a97-9a85-9c6b868de69f
  spec:
    sourcePod: network-check-source-685456655f-29z6m
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T02:20:24Z"
      message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.125271ms
      message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:20:24Z"
    - latency: 2.011534ms
      message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:19:24Z"
    - latency: 2.214709ms
      message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:18:24Z"
    - latency: 2.208854ms
      message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:17:24Z"
    - latency: 2.115904ms
      message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:16:24Z"
    - latency: 2.036084ms
      message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:15:24Z"
    - latency: 2.605774ms
      message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:14:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T02:13:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-24-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-24.ec2.internal
      uid: 185cd0e0-94eb-4ee6-b5b4-f683b64c14b7
    resourceVersion: "21577"
    uid: d1cd159a-edc1-47b9-aa5d-cd15716d33d2
  spec:
    sourcePod: network-check-source-685456655f-29z6m
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T02:19:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 961.18µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:19:24Z"
    - latency: 1.737311ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T02:19:24Z"
    - latency: 942.045µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:18:24Z"
    - latency: 1.85552ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T02:18:24Z"
    - latency: 920.958µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:17:24Z"
    - latency: 2.004944ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T02:17:24Z"
    - latency: 840.063µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:16:24Z"
    - latency: 1.775698ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T02:16:24Z"
    - latency: 809.912µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T02:15:24Z"
    - latency: 1.929602ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T02:15:24Z"
kind: List
metadata:
  resourceVersion: ""