apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T10:55:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-241-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-241.ec2.internal
      uid: e0198a8f-276d-480b-867e-2bcd657fa915
    resourceVersion: "15083"
    uid: 24c5448c-de49-4e7a-91a0-aef619e5f811
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4klsn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T11:02:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.198348ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:02:37Z"
    - latency: 841.186µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:01:37Z"
    - latency: 776.627µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:00:37Z"
    - latency: 833.03µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:59:37Z"
    - latency: 809.127µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:58:37Z"
    - latency: 991.311µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:57:37Z"
    - latency: 1.017884ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:56:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T10:55:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-241-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-241.ec2.internal
      uid: e0198a8f-276d-480b-867e-2bcd657fa915
    resourceVersion: "14571"
    uid: 97d29612-17fe-460e-93f4-27dea79754f8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4klsn
    targetEndpoint: a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T11:01:37Z"
      message: 'load-balancer-api-external: tcp connection to a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.002298ms
      message: 'load-balancer-api-external: tcp connection to a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:01:37Z"
    - latency: 6.02734ms
      message: 'load-balancer-api-external: resolved host name a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T11:01:37Z"
    - latency: 4.336518ms
      message: 'load-balancer-api-external: tcp connection to a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:00:37Z"
    - latency: 8.103286ms
      message: 'load-balancer-api-external: resolved host name a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T11:00:37Z"
    - latency: 5.210051ms
      message: 'load-balancer-api-external: tcp connection to a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:59:37Z"
    - latency: 7.78515ms
      message: 'load-balancer-api-external: resolved host name a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:59:37Z"
    - latency: 5.735383ms
      message: 'load-balancer-api-external: tcp connection to a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:58:37Z"
    - latency: 9.652268ms
      message: 'load-balancer-api-external: resolved host name a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:58:37Z"
    - latency: 5.35529ms
      message: 'load-balancer-api-external: tcp connection to a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:57:37Z"
    - latency: 7.850727ms
      message: 'load-balancer-api-external: resolved host name a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:57:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T10:55:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-241-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-241.ec2.internal
      uid: e0198a8f-276d-480b-867e-2bcd657fa915
    resourceVersion: "14572"
    uid: 884a2d0f-a140-48ee-aa0f-ecb38f603149
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4klsn
    targetEndpoint: a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T11:01:37Z"
      message: 'load-balancer-api-internal: tcp connection to a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.148058ms
      message: 'load-balancer-api-internal: tcp connection to a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:01:37Z"
    - latency: 5.980024ms
      message: 'load-balancer-api-internal: resolved host name a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T11:01:37Z"
    - latency: 4.304299ms
      message: 'load-balancer-api-internal: tcp connection to a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:00:37Z"
    - latency: 8.087594ms
      message: 'load-balancer-api-internal: resolved host name a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T11:00:37Z"
    - latency: 5.235148ms
      message: 'load-balancer-api-internal: tcp connection to a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:59:37Z"
    - latency: 7.748238ms
      message: 'load-balancer-api-internal: resolved host name a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:59:37Z"
    - latency: 5.850336ms
      message: 'load-balancer-api-internal: tcp connection to a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:58:37Z"
    - latency: 9.601294ms
      message: 'load-balancer-api-internal: resolved host name a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:58:37Z"
    - latency: 4.792428ms
      message: 'load-balancer-api-internal: tcp connection to a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:57:37Z"
    - latency: 7.810194ms
      message: 'load-balancer-api-internal: resolved host name a868612c6ad574e98befee4eedd5122e-40c30da0a4c7781f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:57:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T10:55:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-241-to-network-check-target-ip-10-0-135-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-241.ec2.internal
      uid: e0198a8f-276d-480b-867e-2bcd657fa915
    resourceVersion: "15082"
    uid: 40d4400e-8c0e-4bdc-9fdf-b8522e5e6d42
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4klsn
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T11:02:37Z"
      message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.348045ms
      message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:02:37Z"
    - latency: 2.690325ms
      message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:01:37Z"
    - latency: 2.312689ms
      message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:00:37Z"
    - latency: 2.032313ms
      message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:59:37Z"
    - latency: 2.942321ms
      message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:58:37Z"
    - latency: 2.48708ms
      message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:57:37Z"
    - latency: 2.545508ms
      message: 'network-check-target-ip-10-0-135-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:56:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T10:55:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-241-to-network-check-target-ip-10-0-136-218
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-241.ec2.internal
      uid: e0198a8f-276d-480b-867e-2bcd657fa915
    resourceVersion: "15081"
    uid: de730766-2aeb-41e9-8e58-114974ad1344
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4klsn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T11:02:37Z"
      message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.121693ms
      message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:02:37Z"
    - latency: 2.132128ms
      message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:01:37Z"
    - latency: 2.469078ms
      message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:00:37Z"
    - latency: 2.226563ms
      message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:59:37Z"
    - latency: 1.973271ms
      message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:58:37Z"
    - latency: 2.504482ms
      message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:57:37Z"
    - latency: 2.484214ms
      message: 'network-check-target-ip-10-0-136-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:56:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T10:55:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-241-to-network-check-target-ip-10-0-141-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-241.ec2.internal
      uid: e0198a8f-276d-480b-867e-2bcd657fa915
    resourceVersion: "15080"
    uid: 1fd6133e-bf8f-4458-aede-c403720a6431
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4klsn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T11:02:37Z"
      message: 'network-check-target-ip-10-0-141-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.434538ms
      message: 'network-check-target-ip-10-0-141-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:02:37Z"
    - latency: 801.17µs
      message: 'network-check-target-ip-10-0-141-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:01:37Z"
    - latency: 697.061µs
      message: 'network-check-target-ip-10-0-141-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:00:37Z"
    - latency: 835.863µs
      message: 'network-check-target-ip-10-0-141-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:59:37Z"
    - latency: 813.899µs
      message: 'network-check-target-ip-10-0-141-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:58:37Z"
    - latency: 739.977µs
      message: 'network-check-target-ip-10-0-141-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:57:37Z"
    - latency: 919.582µs
      message: 'network-check-target-ip-10-0-141-241: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:56:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T10:55:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-241-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-241.ec2.internal
      uid: e0198a8f-276d-480b-867e-2bcd657fa915
    resourceVersion: "14569"
    uid: 38a22dad-886c-45e7-8a5c-af65af9247b0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4klsn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T11:01:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.137919ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:01:37Z"
    - latency: 1.597026ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T11:01:37Z"
    - latency: 735.841µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T11:00:37Z"
    - latency: 1.678666ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T11:00:37Z"
    - latency: 1.279605ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:59:37Z"
    - latency: 1.648718ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:59:37Z"
    - latency: 749.238µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:58:37Z"
    - latency: 2.442387ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:58:37Z"
    - latency: 794.495µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T10:57:37Z"
    - latency: 1.621834ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T10:57:37Z"
kind: List
metadata:
  resourceVersion: ""