apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:36:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-228-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-228.ec2.internal
      uid: 774f348e-70bd-419d-ae46-7bc07484780c
    resourceVersion: "22646"
    uid: c23646a0-9fe5-4b64-8cd5-6c3dd15c75b1
  spec:
    sourcePod: network-check-source-685456655f-djzb9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:43:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.212326ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:43:31Z"
    - latency: 1.561618ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:42:31Z"
    - latency: 1.048989ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:41:31Z"
    - latency: 1.672134ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:40:31Z"
    - latency: 929.31µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:39:31Z"
    - latency: 1.034538ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:38:31Z"
    - latency: 1.487127ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:37:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:36:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-228-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-228.ec2.internal
      uid: 774f348e-70bd-419d-ae46-7bc07484780c
    resourceVersion: "26381"
    uid: 448b1ec6-ed52-4133-aa47-bfd1b7592ab2
  spec:
    sourcePod: network-check-source-685456655f-djzb9
    targetEndpoint: afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:42:31Z"
      message: 'load-balancer-api-external: tcp connection to afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.195571ms
      message: 'load-balancer-api-external: tcp connection to afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:48:31Z"
    - latency: 6.550803ms
      message: 'load-balancer-api-external: resolved host name afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:48:31Z"
    - latency: 5.339395ms
      message: 'load-balancer-api-external: tcp connection to afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:47:31Z"
    - latency: 5.970646ms
      message: 'load-balancer-api-external: resolved host name afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:47:31Z"
    - latency: 3.852803ms
      message: 'load-balancer-api-external: tcp connection to afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:46:31Z"
    - latency: 6.740852ms
      message: 'load-balancer-api-external: resolved host name afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:46:31Z"
    - latency: 4.464705ms
      message: 'load-balancer-api-external: tcp connection to afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:45:31Z"
    - latency: 7.31566ms
      message: 'load-balancer-api-external: resolved host name afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:45:31Z"
    - latency: 5.05376ms
      message: 'load-balancer-api-external: tcp connection to afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:44:31Z"
    - latency: 7.009324ms
      message: 'load-balancer-api-external: resolved host name afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:44:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:36:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-228-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-228.ec2.internal
      uid: 774f348e-70bd-419d-ae46-7bc07484780c
    resourceVersion: "26380"
    uid: 46e9d027-99f3-4c8a-895e-4f8ddb309725
  spec:
    sourcePod: network-check-source-685456655f-djzb9
    targetEndpoint: afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:42:31Z"
      message: 'load-balancer-api-internal: tcp connection to afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.179744ms
      message: 'load-balancer-api-internal: tcp connection to afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:48:31Z"
    - latency: 6.523431ms
      message: 'load-balancer-api-internal: resolved host name afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:48:31Z"
    - latency: 5.405724ms
      message: 'load-balancer-api-internal: tcp connection to afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:47:31Z"
    - latency: 5.939201ms
      message: 'load-balancer-api-internal: resolved host name afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:47:31Z"
    - latency: 3.80927ms
      message: 'load-balancer-api-internal: tcp connection to afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:46:31Z"
    - latency: 6.691878ms
      message: 'load-balancer-api-internal: resolved host name afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:46:31Z"
    - latency: 4.510622ms
      message: 'load-balancer-api-internal: tcp connection to afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:45:31Z"
    - latency: 7.29469ms
      message: 'load-balancer-api-internal: resolved host name afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:45:31Z"
    - latency: 5.203841ms
      message: 'load-balancer-api-internal: tcp connection to afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:44:31Z"
    - latency: 6.979672ms
      message: 'load-balancer-api-internal: resolved host name afd80efa841d34cba974e53076aaa8d3-659703704012cbcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:44:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:36:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-228-to-network-check-target-ip-10-0-137-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-228.ec2.internal
      uid: 774f348e-70bd-419d-ae46-7bc07484780c
    resourceVersion: "22645"
    uid: 4fdca5b8-23d6-4da5-a680-850969f7c724
  spec:
    sourcePod: network-check-source-685456655f-djzb9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:43:31Z"
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.291361ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:43:31Z"
    - latency: 2.151975ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:42:31Z"
    - latency: 2.296891ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:41:31Z"
    - latency: 2.172885ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:40:31Z"
    - latency: 2.260216ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:39:31Z"
    - latency: 1.996068ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:38:31Z"
    - latency: 2.01024ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:37:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:36:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-228-to-network-check-target-ip-10-0-143-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-228.ec2.internal
      uid: 774f348e-70bd-419d-ae46-7bc07484780c
    resourceVersion: "22643"
    uid: 2094474c-0bda-46b7-97e7-d8a0f9bcac80
  spec:
    sourcePod: network-check-source-685456655f-djzb9
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:43:31Z"
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.635µs
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:43:31Z"
    - latency: 1.137391ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:42:31Z"
    - latency: 1.526804ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:41:31Z"
    - latency: 1.321357ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:40:31Z"
    - latency: 805.795µs
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:39:31Z"
    - latency: 1.204036ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:38:31Z"
    - latency: 1.340975ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:37:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:36:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-228-to-network-check-target-ip-10-0-143-27
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-228.ec2.internal
      uid: 774f348e-70bd-419d-ae46-7bc07484780c
    resourceVersion: "22644"
    uid: 66667b19-586b-4190-9fcd-e717f1ad6597
  spec:
    sourcePod: network-check-source-685456655f-djzb9
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:43:31Z"
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.042327ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:43:31Z"
    - latency: 1.804459ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:42:31Z"
    - latency: 1.99124ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:41:31Z"
    - latency: 1.773598ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:40:31Z"
    - latency: 2.176643ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:39:31Z"
    - latency: 1.742015ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:38:31Z"
    - latency: 2.143596ms
      message: 'network-check-target-ip-10-0-143-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:37:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T02:36:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-228-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-228.ec2.internal
      uid: 774f348e-70bd-419d-ae46-7bc07484780c
    resourceVersion: "26378"
    uid: 6f76bf54-8bb9-4b99-94a4-cd3624889fbc
  spec:
    sourcePod: network-check-source-685456655f-djzb9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T02:42:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 790.113µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:48:31Z"
    - latency: 1.748522ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:48:31Z"
    - latency: 1.148045ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:47:31Z"
    - latency: 1.806653ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:47:31Z"
    - latency: 884.415µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:46:31Z"
    - latency: 1.878772ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:46:31Z"
    - latency: 714.982µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:45:31Z"
    - latency: 2.248355ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:45:31Z"
    - latency: 1.227134ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T02:44:31Z"
    - latency: 1.891145ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T02:44:31Z"
kind: List
metadata:
  resourceVersion: ""