apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:58:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-61-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-61.ec2.internal
      uid: c4fe39f7-b7c3-4dc5-9937-bfc6e59957dc
    resourceVersion: "14407"
    uid: 61b2722d-7422-472f-9de7-941ec95c97f0
  spec:
    sourcePod: network-check-source-6f8b768455-jhngq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:05:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 971.654µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:20Z"
    - latency: 1.119084ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:20Z"
    - latency: 823.62µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:20Z"
    - latency: 1.24735ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:02:20Z"
    - latency: 1.167735ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:01:20Z"
    - latency: 938.901µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:00:20Z"
    - latency: 1.043937ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:59:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:58:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-61-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-61.ec2.internal
      uid: c4fe39f7-b7c3-4dc5-9937-bfc6e59957dc
    resourceVersion: "14052"
    uid: 28cb6433-e03b-4a62-80bd-7fc2e1360864
  spec:
    sourcePod: network-check-source-6f8b768455-jhngq
    targetEndpoint: af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:04:20Z"
      message: 'load-balancer-api-external: tcp connection to af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.386959ms
      message: 'load-balancer-api-external: tcp connection to af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:20Z"
    - latency: 6.51457ms
      message: 'load-balancer-api-external: resolved host name af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:04:20Z"
    - latency: 5.991134ms
      message: 'load-balancer-api-external: tcp connection to af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:20Z"
    - latency: 6.676699ms
      message: 'load-balancer-api-external: resolved host name af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:03:20Z"
    - latency: 5.587098ms
      message: 'load-balancer-api-external: tcp connection to af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:02:20Z"
    - latency: 5.881097ms
      message: 'load-balancer-api-external: resolved host name af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:02:20Z"
    - latency: 4.662258ms
      message: 'load-balancer-api-external: tcp connection to af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:01:20Z"
    - latency: 8.464767ms
      message: 'load-balancer-api-external: resolved host name af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:01:20Z"
    - latency: 4.498748ms
      message: 'load-balancer-api-external: tcp connection to af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:00:20Z"
    - latency: 7.450868ms
      message: 'load-balancer-api-external: resolved host name af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:00:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:58:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-61-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-61.ec2.internal
      uid: c4fe39f7-b7c3-4dc5-9937-bfc6e59957dc
    resourceVersion: "14051"
    uid: 5b44bfa3-008f-4f1f-b140-36c1fae5b776
  spec:
    sourcePod: network-check-source-6f8b768455-jhngq
    targetEndpoint: af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:04:20Z"
      message: 'load-balancer-api-internal: tcp connection to af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.375619ms
      message: 'load-balancer-api-internal: tcp connection to af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:20Z"
    - latency: 6.568156ms
      message: 'load-balancer-api-internal: resolved host name af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:04:20Z"
    - latency: 5.977414ms
      message: 'load-balancer-api-internal: tcp connection to af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:20Z"
    - latency: 6.605843ms
      message: 'load-balancer-api-internal: resolved host name af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:03:20Z"
    - latency: 4.871427ms
      message: 'load-balancer-api-internal: tcp connection to af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:02:20Z"
    - latency: 5.82431ms
      message: 'load-balancer-api-internal: resolved host name af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:02:20Z"
    - latency: 4.644431ms
      message: 'load-balancer-api-internal: tcp connection to af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:01:20Z"
    - latency: 8.52541ms
      message: 'load-balancer-api-internal: resolved host name af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:01:20Z"
    - latency: 4.490488ms
      message: 'load-balancer-api-internal: tcp connection to af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:00:20Z"
    - latency: 7.485459ms
      message: 'load-balancer-api-internal: resolved host name af8d6bef345074738b0a905126066ef2-c185d574d834b0cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:00:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:58:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-61-to-network-check-target-ip-10-0-133-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-61.ec2.internal
      uid: c4fe39f7-b7c3-4dc5-9937-bfc6e59957dc
    resourceVersion: "14405"
    uid: 609bdd2c-61ae-4b0f-bbd3-529424a7e0b0
  spec:
    sourcePod: network-check-source-6f8b768455-jhngq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:05:20Z"
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.459714ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:20Z"
    - latency: 2.610105ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:20Z"
    - latency: 2.273893ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:20Z"
    - latency: 2.662003ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:02:20Z"
    - latency: 2.451819ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:01:20Z"
    - latency: 2.28054ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:00:20Z"
    - latency: 2.334179ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:59:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:58:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-61-to-network-check-target-ip-10-0-138-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-61.ec2.internal
      uid: c4fe39f7-b7c3-4dc5-9937-bfc6e59957dc
    resourceVersion: "14404"
    uid: b459ec00-76ef-455d-8f73-ea7489a66fb7
  spec:
    sourcePod: network-check-source-6f8b768455-jhngq
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:05:20Z"
      message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 935.525µs
      message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:20Z"
    - latency: 1.169171ms
      message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:20Z"
    - latency: 1.114749ms
      message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:20Z"
    - latency: 916.884µs
      message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:02:20Z"
    - latency: 856.699µs
      message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:01:20Z"
    - latency: 825.326µs
      message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:00:20Z"
    - latency: 1.474644ms
      message: 'network-check-target-ip-10-0-138-61: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:59:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:58:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-61-to-network-check-target-ip-10-0-143-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-61.ec2.internal
      uid: c4fe39f7-b7c3-4dc5-9937-bfc6e59957dc
    resourceVersion: "14406"
    uid: 42adfbb4-1694-4d32-aa52-b551bf635b4a
  spec:
    sourcePod: network-check-source-6f8b768455-jhngq
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:05:20Z"
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.56485ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:05:20Z"
    - latency: 2.323069ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:20Z"
    - latency: 1.914472ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:20Z"
    - latency: 2.311436ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:02:20Z"
    - latency: 2.292319ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:01:20Z"
    - latency: 2.402001ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:00:20Z"
    - latency: 2.107908ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:59:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:58:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-61-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-61.ec2.internal
      uid: c4fe39f7-b7c3-4dc5-9937-bfc6e59957dc
    resourceVersion: "14050"
    uid: 289a7ab5-e2f5-4c97-b30c-8b177ecdef11
  spec:
    sourcePod: network-check-source-6f8b768455-jhngq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T10:04:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 975.183µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:04:20Z"
    - latency: 1.714565ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:04:20Z"
    - latency: 775.44µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:03:20Z"
    - latency: 1.627972ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:03:20Z"
    - latency: 1.058792ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:02:20Z"
    - latency: 1.769107ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:02:20Z"
    - latency: 827.103µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:01:20Z"
    - latency: 1.996541ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:01:20Z"
    - latency: 867.369µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T10:00:20Z"
    - latency: 1.777377ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T10:00:20Z"
kind: List
metadata:
  resourceVersion: ""