apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T18:38:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-87-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-87.ec2.internal
      uid: efd138d2-5892-46d6-88ed-81c97cdcb58e
    resourceVersion: "23916"
    uid: 39f4cf44-6517-4eab-a671-ba48fafe3e43
  spec:
    sourcePod: network-check-source-685456655f-4m5dh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T18:45:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.09126ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:45:53Z"
    - latency: 888.113µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:44:53Z"
    - latency: 944.24µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:43:53Z"
    - latency: 1.082068ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:42:53Z"
    - latency: 983.453µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:41:53Z"
    - latency: 1.257022ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:40:53Z"
    - latency: 1.369369ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:39:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T18:38:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-87-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-87.ec2.internal
      uid: efd138d2-5892-46d6-88ed-81c97cdcb58e
    resourceVersion: "22759"
    uid: 7bf8e151-8170-452a-9523-2b532cfd834f
  spec:
    sourcePod: network-check-source-685456655f-4m5dh
    targetEndpoint: a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T18:44:53Z"
      message: 'load-balancer-api-external: tcp connection to a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.772844ms
      message: 'load-balancer-api-external: tcp connection to a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:44:53Z"
    - latency: 6.575556ms
      message: 'load-balancer-api-external: resolved host name a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:44:53Z"
    - latency: 4.997611ms
      message: 'load-balancer-api-external: tcp connection to a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:43:53Z"
    - latency: 7.443545ms
      message: 'load-balancer-api-external: resolved host name a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:43:53Z"
    - latency: 5.680486ms
      message: 'load-balancer-api-external: tcp connection to a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:42:53Z"
    - latency: 7.54293ms
      message: 'load-balancer-api-external: resolved host name a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:42:53Z"
    - latency: 5.175373ms
      message: 'load-balancer-api-external: tcp connection to a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:41:53Z"
    - latency: 6.940711ms
      message: 'load-balancer-api-external: resolved host name a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:41:53Z"
    - latency: 5.447603ms
      message: 'load-balancer-api-external: tcp connection to a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:40:53Z"
    - latency: 8.260704ms
      message: 'load-balancer-api-external: resolved host name a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:40:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T18:38:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-87-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-87.ec2.internal
      uid: efd138d2-5892-46d6-88ed-81c97cdcb58e
    resourceVersion: "22761"
    uid: b0072e1e-090c-4645-8325-b53b03df2828
  spec:
    sourcePod: network-check-source-685456655f-4m5dh
    targetEndpoint: a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T18:44:53Z"
      message: 'load-balancer-api-internal: tcp connection to a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.013668ms
      message: 'load-balancer-api-internal: tcp connection to a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:44:53Z"
    - latency: 6.551677ms
      message: 'load-balancer-api-internal: resolved host name a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:44:53Z"
    - latency: 4.432632ms
      message: 'load-balancer-api-internal: tcp connection to a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:43:53Z"
    - latency: 7.39881ms
      message: 'load-balancer-api-internal: resolved host name a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:43:53Z"
    - latency: 5.649924ms
      message: 'load-balancer-api-internal: tcp connection to a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:42:53Z"
    - latency: 7.580676ms
      message: 'load-balancer-api-internal: resolved host name a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:42:53Z"
    - latency: 5.173963ms
      message: 'load-balancer-api-internal: tcp connection to a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:41:53Z"
    - latency: 6.913766ms
      message: 'load-balancer-api-internal: resolved host name a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:41:53Z"
    - latency: 5.440678ms
      message: 'load-balancer-api-internal: tcp connection to a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:40:53Z"
    - latency: 8.22902ms
      message: 'load-balancer-api-internal: resolved host name a136b9a506ba24a1c80d5e0b489a2063-64a9dea75762d001.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:40:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T18:38:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-87-to-network-check-target-ip-10-0-130-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-87.ec2.internal
      uid: efd138d2-5892-46d6-88ed-81c97cdcb58e
    resourceVersion: "23915"
    uid: d66fd77e-c646-4fc6-b8db-e02bbaaa8488
  spec:
    sourcePod: network-check-source-685456655f-4m5dh
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T18:45:53Z"
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.394895ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:45:53Z"
    - latency: 2.434785ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:44:53Z"
    - latency: 2.129778ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:43:53Z"
    - latency: 2.282221ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:42:53Z"
    - latency: 2.37404ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:41:53Z"
    - latency: 2.605773ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:40:53Z"
    - latency: 2.52382ms
      message: 'network-check-target-ip-10-0-130-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:39:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T18:38:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-87-to-network-check-target-ip-10-0-134-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-87.ec2.internal
      uid: efd138d2-5892-46d6-88ed-81c97cdcb58e
    resourceVersion: "23914"
    uid: 4e5d0f0f-a61d-4826-bbcf-791e8eee98e9
  spec:
    sourcePod: network-check-source-685456655f-4m5dh
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T18:45:53Z"
      message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.252899ms
      message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:45:53Z"
    - latency: 2.24097ms
      message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:44:53Z"
    - latency: 2.217216ms
      message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:43:53Z"
    - latency: 2.57655ms
      message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:42:53Z"
    - latency: 2.200926ms
      message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:41:53Z"
    - latency: 2.175781ms
      message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:40:53Z"
    - latency: 2.271977ms
      message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:39:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T18:38:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-87-to-network-check-target-ip-10-0-138-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-87.ec2.internal
      uid: efd138d2-5892-46d6-88ed-81c97cdcb58e
    resourceVersion: "23913"
    uid: e279be9a-a40b-4083-9f59-5366514c2a76
  spec:
    sourcePod: network-check-source-685456655f-4m5dh
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T18:45:53Z"
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 852.157µs
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:45:53Z"
    - latency: 1.378627ms
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:44:53Z"
    - latency: 989.875µs
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:43:53Z"
    - latency: 793.577µs
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:42:53Z"
    - latency: 931.475µs
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:41:53Z"
    - latency: 1.292012ms
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:40:53Z"
    - latency: 1.272267ms
      message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:39:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T18:38:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-87-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-87.ec2.internal
      uid: efd138d2-5892-46d6-88ed-81c97cdcb58e
    resourceVersion: "22757"
    uid: 3dad712c-73c1-445f-8c5c-3c02365f6418
  spec:
    sourcePod: network-check-source-685456655f-4m5dh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T18:44:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 944.796µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:44:53Z"
    - latency: 1.550595ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:44:53Z"
    - latency: 852.891µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:43:53Z"
    - latency: 1.815407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:43:53Z"
    - latency: 1.010923ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:42:53Z"
    - latency: 2.049835ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:42:53Z"
    - latency: 884.46µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:41:53Z"
    - latency: 1.661895ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:41:53Z"
    - latency: 928.748µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:40:53Z"
    - latency: 2.234448ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:40:53Z"
kind: List
metadata:
  resourceVersion: ""