apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:38:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-125-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-125.ec2.internal
      uid: f9d26b8a-4d82-45aa-8cf9-4985b7c51d35
    resourceVersion: "14205"
    uid: 867ade30-bb6d-442d-9886-827ee4c6c74c
  spec:
    sourcePod: network-check-source-869dcfcdcd-bqtzg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:45: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.0107ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:45:31Z"
    - latency: 1.063551ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:31Z"
    - latency: 928.336µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:31Z"
    - latency: 860.078µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:31Z"
    - latency: 887.524µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:31Z"
    - latency: 908.888µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:31Z"
    - latency: 744.872µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:38:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-125-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-125.ec2.internal
      uid: f9d26b8a-4d82-45aa-8cf9-4985b7c51d35
    resourceVersion: "15798"
    uid: 906a2acb-9d3e-483b-8bb9-c5c1afd15687
  spec:
    sourcePod: network-check-source-869dcfcdcd-bqtzg
    targetEndpoint: af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:44:31Z"
      message: 'load-balancer-api-external: tcp connection to af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.877686ms
      message: 'load-balancer-api-external: tcp connection to af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:50:31Z"
    - latency: 8.810001ms
      message: 'load-balancer-api-external: resolved host name af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:50:31Z"
    - latency: 4.654676ms
      message: 'load-balancer-api-external: tcp connection to af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:49:31Z"
    - latency: 7.73611ms
      message: 'load-balancer-api-external: resolved host name af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:49:31Z"
    - latency: 4.803398ms
      message: 'load-balancer-api-external: tcp connection to af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:48:31Z"
    - latency: 9.12905ms
      message: 'load-balancer-api-external: resolved host name af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:48:31Z"
    - latency: 5.873769ms
      message: 'load-balancer-api-external: tcp connection to af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:47:31Z"
    - latency: 8.880852ms
      message: 'load-balancer-api-external: resolved host name af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:47:31Z"
    - latency: 5.425848ms
      message: 'load-balancer-api-external: tcp connection to af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:46:31Z"
    - latency: 9.143841ms
      message: 'load-balancer-api-external: resolved host name af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:46:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:38:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-125-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-125.ec2.internal
      uid: f9d26b8a-4d82-45aa-8cf9-4985b7c51d35
    resourceVersion: "15797"
    uid: 6fe6700c-9182-4448-a958-ec6cdb6addf2
  spec:
    sourcePod: network-check-source-869dcfcdcd-bqtzg
    targetEndpoint: af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:44:31Z"
      message: 'load-balancer-api-internal: tcp connection to af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.87918ms
      message: 'load-balancer-api-internal: tcp connection to af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:50:31Z"
    - latency: 8.766569ms
      message: 'load-balancer-api-internal: resolved host name af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:50:31Z"
    - latency: 4.361752ms
      message: 'load-balancer-api-internal: tcp connection to af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:49:31Z"
    - latency: 7.655541ms
      message: 'load-balancer-api-internal: resolved host name af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:49:31Z"
    - latency: 4.81475ms
      message: 'load-balancer-api-internal: tcp connection to af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:48:31Z"
    - latency: 9.088612ms
      message: 'load-balancer-api-internal: resolved host name af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:48:31Z"
    - latency: 4.063071ms
      message: 'load-balancer-api-internal: tcp connection to af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:47:31Z"
    - latency: 8.94216ms
      message: 'load-balancer-api-internal: resolved host name af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:47:31Z"
    - latency: 5.4659ms
      message: 'load-balancer-api-internal: tcp connection to af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:46:31Z"
    - latency: 9.091952ms
      message: 'load-balancer-api-internal: resolved host name af8799be1964f42d7a86190b18500cd2-2b5bd24b34d060a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:46:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:38:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-125-to-network-check-target-ip-10-0-131-242
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-125.ec2.internal
      uid: f9d26b8a-4d82-45aa-8cf9-4985b7c51d35
    resourceVersion: "14203"
    uid: 5983b3f5-6a84-4d83-a3d5-d07dca3a6ec7
  spec:
    sourcePod: network-check-source-869dcfcdcd-bqtzg
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:45:31Z"
      message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.321027ms
      message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:45:31Z"
    - latency: 2.27379ms
      message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:31Z"
    - latency: 2.225041ms
      message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:31Z"
    - latency: 2.289841ms
      message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:31Z"
    - latency: 2.392051ms
      message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:31Z"
    - latency: 2.214853ms
      message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:31Z"
    - latency: 2.071582ms
      message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:38:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-125-to-network-check-target-ip-10-0-137-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-125.ec2.internal
      uid: f9d26b8a-4d82-45aa-8cf9-4985b7c51d35
    resourceVersion: "14204"
    uid: 9ba46b9a-ddbe-4500-a55f-2cf6d151b0d1
  spec:
    sourcePod: network-check-source-869dcfcdcd-bqtzg
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:45:31Z"
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.292833ms
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:45:31Z"
    - latency: 2.404552ms
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:31Z"
    - latency: 2.609697ms
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:31Z"
    - latency: 2.337289ms
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:31Z"
    - latency: 2.326949ms
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:31Z"
    - latency: 2.156775ms
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:31Z"
    - latency: 2.372738ms
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:38:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-125-to-network-check-target-ip-10-0-143-125
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-125.ec2.internal
      uid: f9d26b8a-4d82-45aa-8cf9-4985b7c51d35
    resourceVersion: "14202"
    uid: b3ea64f6-183a-4b23-8236-61707d066532
  spec:
    sourcePod: network-check-source-869dcfcdcd-bqtzg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:45:31Z"
      message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.443132ms
      message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:45:31Z"
    - latency: 921.867µs
      message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:44:31Z"
    - latency: 844.114µs
      message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:43:31Z"
    - latency: 1.112413ms
      message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:42:31Z"
    - latency: 730.026µs
      message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:41:31Z"
    - latency: 685.153µs
      message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:40:31Z"
    - latency: 1.172077ms
      message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:39:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T14:38:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-125-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-125.ec2.internal
      uid: f9d26b8a-4d82-45aa-8cf9-4985b7c51d35
    resourceVersion: "15796"
    uid: 97a3ea20-7f0a-4412-a94d-43c71ad1b1a7
  spec:
    sourcePod: network-check-source-869dcfcdcd-bqtzg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T14:44:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.638µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:50:31Z"
    - latency: 1.826996ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:50:31Z"
    - latency: 850.361µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:49:31Z"
    - latency: 1.639946ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:49:31Z"
    - latency: 1.120852ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:48:31Z"
    - latency: 1.839948ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:48:31Z"
    - latency: 816.629µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:47:31Z"
    - latency: 1.752717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:47:31Z"
    - latency: 899.065µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T14:46:31Z"
    - latency: 1.897705ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T14:46:31Z"
kind: List
metadata:
  resourceVersion: ""