apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T03:56:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-224-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-224.ec2.internal
      uid: 105dc9f5-963b-45d4-9a4b-724b32bb9863
    resourceVersion: "24464"
    uid: 69d63d4e-75c7-48fb-856b-a6290152bbca
  spec:
    sourcePod: network-check-source-7bc5b6bf85-hcwqn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T04:03:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.140985ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:03:19Z"
    - latency: 1.036519ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:02:19Z"
    - latency: 1.307388ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:01:19Z"
    - latency: 2.05718ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:00:19Z"
    - latency: 1.044481ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:59:19Z"
    - latency: 1.677348ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:58:19Z"
    - latency: 1.054029ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:57:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T03:56:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-224-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-224.ec2.internal
      uid: 105dc9f5-963b-45d4-9a4b-724b32bb9863
    resourceVersion: "23021"
    uid: a82a6bcb-be68-4a14-a94f-a7c02842fad5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-hcwqn
    targetEndpoint: aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T04:02:19Z"
      message: 'load-balancer-api-external: tcp connection to aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.046306ms
      message: 'load-balancer-api-external: tcp connection to aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:02:19Z"
    - latency: 8.70765ms
      message: 'load-balancer-api-external: resolved host name aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T04:02:19Z"
    - latency: 5.115513ms
      message: 'load-balancer-api-external: tcp connection to aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:01:19Z"
    - latency: 9.065511ms
      message: 'load-balancer-api-external: resolved host name aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T04:01:19Z"
    - latency: 4.303484ms
      message: 'load-balancer-api-external: tcp connection to aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:00:19Z"
    - latency: 10.594993ms
      message: 'load-balancer-api-external: resolved host name aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T04:00:19Z"
    - latency: 3.546073ms
      message: 'load-balancer-api-external: tcp connection to aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:59:19Z"
    - latency: 7.820571ms
      message: 'load-balancer-api-external: resolved host name aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:59:19Z"
    - latency: 3.811452ms
      message: 'load-balancer-api-external: tcp connection to aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:58:19Z"
    - latency: 8.627467ms
      message: 'load-balancer-api-external: resolved host name aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:58:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T03:56:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-224-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-224.ec2.internal
      uid: 105dc9f5-963b-45d4-9a4b-724b32bb9863
    resourceVersion: "23022"
    uid: a365d927-5551-4eed-b9ac-72050f1f05b4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-hcwqn
    targetEndpoint: aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T04:02:19Z"
      message: 'load-balancer-api-internal: tcp connection to aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.99218ms
      message: 'load-balancer-api-internal: tcp connection to aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:02:19Z"
    - latency: 8.646762ms
      message: 'load-balancer-api-internal: resolved host name aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T04:02:19Z"
    - latency: 4.200041ms
      message: 'load-balancer-api-internal: tcp connection to aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:01:19Z"
    - latency: 9.126923ms
      message: 'load-balancer-api-internal: resolved host name aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T04:01:19Z"
    - latency: 4.256258ms
      message: 'load-balancer-api-internal: tcp connection to aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:00:19Z"
    - latency: 10.776083ms
      message: 'load-balancer-api-internal: resolved host name aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T04:00:19Z"
    - latency: 4.81082ms
      message: 'load-balancer-api-internal: tcp connection to aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:59:19Z"
    - latency: 7.942451ms
      message: 'load-balancer-api-internal: resolved host name aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:59:19Z"
    - latency: 5.440436ms
      message: 'load-balancer-api-internal: tcp connection to aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:58:19Z"
    - latency: 8.6898ms
      message: 'load-balancer-api-internal: resolved host name aa4ae65a8b31d49beaaae1532f99e9cf-777ad5593d89af16.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:58:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T03:56:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-224-to-network-check-target-ip-10-0-130-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-224.ec2.internal
      uid: 105dc9f5-963b-45d4-9a4b-724b32bb9863
    resourceVersion: "24463"
    uid: f9188da6-1831-4924-9b65-eda8e38bb3c9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-hcwqn
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T04:03:19Z"
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.643288ms
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:03:19Z"
    - latency: 2.355352ms
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:02:19Z"
    - latency: 2.168521ms
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:01:19Z"
    - latency: 3.223481ms
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:00:19Z"
    - latency: 2.227456ms
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:59:19Z"
    - latency: 2.158444ms
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:58:19Z"
    - latency: 2.524068ms
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:57:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T03:56:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-224-to-network-check-target-ip-10-0-133-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-224.ec2.internal
      uid: 105dc9f5-963b-45d4-9a4b-724b32bb9863
    resourceVersion: "24462"
    uid: f0cfd1c8-c847-48d2-be46-146ed875ec83
  spec:
    sourcePod: network-check-source-7bc5b6bf85-hcwqn
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T04:03:19Z"
      message: 'network-check-target-ip-10-0-133-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.169658ms
      message: 'network-check-target-ip-10-0-133-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:03:19Z"
    - latency: 2.011923ms
      message: 'network-check-target-ip-10-0-133-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:02:19Z"
    - latency: 2.681204ms
      message: 'network-check-target-ip-10-0-133-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:01:19Z"
    - latency: 2.527674ms
      message: 'network-check-target-ip-10-0-133-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:00:19Z"
    - latency: 2.138176ms
      message: 'network-check-target-ip-10-0-133-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:59:19Z"
    - latency: 2.119518ms
      message: 'network-check-target-ip-10-0-133-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:58:19Z"
    - latency: 2.227374ms
      message: 'network-check-target-ip-10-0-133-144: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:57:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T03:56:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-224-to-network-check-target-ip-10-0-138-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-224.ec2.internal
      uid: 105dc9f5-963b-45d4-9a4b-724b32bb9863
    resourceVersion: "24461"
    uid: be6c82e0-d3a4-44a3-a761-7912fc5be7ad
  spec:
    sourcePod: network-check-source-7bc5b6bf85-hcwqn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T04:03:19Z"
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 840.291µs
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:03:19Z"
    - latency: 820.588µs
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:02:19Z"
    - latency: 1.541458ms
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:01:19Z"
    - latency: 2.335125ms
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:00:19Z"
    - latency: 1.464713ms
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:59:19Z"
    - latency: 802.594µs
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:58:19Z"
    - latency: 1.655311ms
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:57:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T03:56:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-224-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-224.ec2.internal
      uid: 105dc9f5-963b-45d4-9a4b-724b32bb9863
    resourceVersion: "23020"
    uid: f01cc280-3d57-4dcc-be3b-b2332c2eb111
  spec:
    sourcePod: network-check-source-7bc5b6bf85-hcwqn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T04:02:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 962.159µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:02:19Z"
    - latency: 1.771005ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T04:02:19Z"
    - latency: 836.507µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:01:19Z"
    - latency: 2.138222ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T04:01:19Z"
    - latency: 2.310472ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T04:00:19Z"
    - latency: 2.271209ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T04:00:19Z"
    - latency: 881.704µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:59:19Z"
    - latency: 1.433903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:59:19Z"
    - latency: 759.495µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T03:58:19Z"
    - latency: 1.844869ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T03:58:19Z"
kind: List
metadata:
  resourceVersion: ""