apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:42:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-15-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-15.ec2.internal
      uid: 4b73aa8e-a44c-47a2-ad21-b742f4f55a2d
    resourceVersion: "22650"
    uid: c7e09678-a7b2-4a18-abb4-3c242a2d1185
  spec:
    sourcePod: network-check-source-56499946bc-rtl6m
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:49:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.229467ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:49:59Z"
    - latency: 984.569µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:48:59Z"
    - latency: 1.268967ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:47:59Z"
    - latency: 1.255887ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:46:59Z"
    - latency: 1.098007ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:45:59Z"
    - latency: 1.012998ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:44:59Z"
    - latency: 1.121848ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:43:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:42:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-15-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-15.ec2.internal
      uid: 4b73aa8e-a44c-47a2-ad21-b742f4f55a2d
    resourceVersion: "21640"
    uid: cccb8cca-448d-4489-8bfa-51998d48e1d1
  spec:
    sourcePod: network-check-source-56499946bc-rtl6m
    targetEndpoint: a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:48:59Z"
      message: 'load-balancer-api-external: tcp connection to a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.657402ms
      message: 'load-balancer-api-external: tcp connection to a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:48:59Z"
    - latency: 9.076083ms
      message: 'load-balancer-api-external: resolved host name a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:48:59Z"
    - latency: 6.518306ms
      message: 'load-balancer-api-external: tcp connection to a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:47:59Z"
    - latency: 9.395049ms
      message: 'load-balancer-api-external: resolved host name a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:47:59Z"
    - latency: 3.329953ms
      message: 'load-balancer-api-external: tcp connection to a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:46:59Z"
    - latency: 7.213248ms
      message: 'load-balancer-api-external: resolved host name a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:46:59Z"
    - latency: 4.246822ms
      message: 'load-balancer-api-external: tcp connection to a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:45:59Z"
    - latency: 7.315546ms
      message: 'load-balancer-api-external: resolved host name a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:45:59Z"
    - latency: 5.072773ms
      message: 'load-balancer-api-external: tcp connection to a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:44:59Z"
    - latency: 7.147648ms
      message: 'load-balancer-api-external: resolved host name a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:44:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:42:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-15-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-15.ec2.internal
      uid: 4b73aa8e-a44c-47a2-ad21-b742f4f55a2d
    resourceVersion: "21641"
    uid: 0c79de54-7c27-490d-9516-dd19b1e3f631
  spec:
    sourcePod: network-check-source-56499946bc-rtl6m
    targetEndpoint: a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:48:59Z"
      message: 'load-balancer-api-internal: tcp connection to a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.662592ms
      message: 'load-balancer-api-internal: tcp connection to a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:48:59Z"
    - latency: 9.03502ms
      message: 'load-balancer-api-internal: resolved host name a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:48:59Z"
    - latency: 5.611044ms
      message: 'load-balancer-api-internal: tcp connection to a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:47:59Z"
    - latency: 9.448752ms
      message: 'load-balancer-api-internal: resolved host name a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:47:59Z"
    - latency: 3.16724ms
      message: 'load-balancer-api-internal: tcp connection to a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:46:59Z"
    - latency: 7.229966ms
      message: 'load-balancer-api-internal: resolved host name a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:46:59Z"
    - latency: 3.776251ms
      message: 'load-balancer-api-internal: tcp connection to a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:45:59Z"
    - latency: 7.393167ms
      message: 'load-balancer-api-internal: resolved host name a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:45:59Z"
    - latency: 5.07202ms
      message: 'load-balancer-api-internal: tcp connection to a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:44:59Z"
    - latency: 7.131577ms
      message: 'load-balancer-api-internal: resolved host name a6f84290a05b14069aa359cdc63d35bf-84045238e72e2f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:44:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:42:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-15-to-network-check-target-ip-10-0-130-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-15.ec2.internal
      uid: 4b73aa8e-a44c-47a2-ad21-b742f4f55a2d
    resourceVersion: "22648"
    uid: 85a57a7c-cb25-4bf4-a379-d50de6e8c820
  spec:
    sourcePod: network-check-source-56499946bc-rtl6m
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:49:59Z"
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.465386ms
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:49:59Z"
    - latency: 2.117175ms
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:48:59Z"
    - latency: 2.485091ms
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:47:59Z"
    - latency: 2.298709ms
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:46:59Z"
    - latency: 2.242742ms
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:45:59Z"
    - latency: 2.057073ms
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:44:59Z"
    - latency: 2.653535ms
      message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:43:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:42:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-15-to-network-check-target-ip-10-0-135-210
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-15.ec2.internal
      uid: 4b73aa8e-a44c-47a2-ad21-b742f4f55a2d
    resourceVersion: "22649"
    uid: 820df57a-b1e5-4495-a930-1b7f348e99be
  spec:
    sourcePod: network-check-source-56499946bc-rtl6m
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:49:59Z"
      message: 'network-check-target-ip-10-0-135-210: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.47694ms
      message: 'network-check-target-ip-10-0-135-210: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:49:59Z"
    - latency: 1.914145ms
      message: 'network-check-target-ip-10-0-135-210: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:48:59Z"
    - latency: 2.096856ms
      message: 'network-check-target-ip-10-0-135-210: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:47:59Z"
    - latency: 1.895557ms
      message: 'network-check-target-ip-10-0-135-210: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:46:59Z"
    - latency: 2.018226ms
      message: 'network-check-target-ip-10-0-135-210: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:45:59Z"
    - latency: 2.244791ms
      message: 'network-check-target-ip-10-0-135-210: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:44:59Z"
    - latency: 2.195256ms
      message: 'network-check-target-ip-10-0-135-210: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:43:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:42:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-15-to-network-check-target-ip-10-0-143-15
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-15.ec2.internal
      uid: 4b73aa8e-a44c-47a2-ad21-b742f4f55a2d
    resourceVersion: "22647"
    uid: 54d3ca97-385d-4d71-8122-ab3363c7d02d
  spec:
    sourcePod: network-check-source-56499946bc-rtl6m
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:49:59Z"
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.062204ms
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:49:59Z"
    - latency: 826.077µs
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:48:59Z"
    - latency: 941.724µs
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:47:59Z"
    - latency: 956.672µs
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:46:59Z"
    - latency: 1.464394ms
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:45:59Z"
    - latency: 1.2003ms
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:44:59Z"
    - latency: 1.523576ms
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:43:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T16:42:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-15-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-15.ec2.internal
      uid: 4b73aa8e-a44c-47a2-ad21-b742f4f55a2d
    resourceVersion: "21639"
    uid: d684fd4d-99d2-4d0c-abf0-647293aaab7c
  spec:
    sourcePod: network-check-source-56499946bc-rtl6m
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T16:48:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 876.336µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:48:59Z"
    - latency: 1.967697ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:48:59Z"
    - latency: 1.128211ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:47:59Z"
    - latency: 1.95297ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:47:59Z"
    - latency: 942.958µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:46:59Z"
    - latency: 2.039772ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:46:59Z"
    - latency: 927.307µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:45:59Z"
    - latency: 1.776401ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:45:59Z"
    - latency: 1.10507ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T16:44:59Z"
    - latency: 1.826349ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T16:44:59Z"
kind: List
metadata:
  resourceVersion: ""