apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T03:50:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-9-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-9.us-east-2.compute.internal
      uid: 84b2ab30-de69-44c1-9468-230d578a9679
    resourceVersion: "20884"
    uid: ca94e525-ed7a-4107-abe1-1b70565745e1
  spec:
    sourcePod: network-check-source-6f78d59f99-5xh74
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T03:57:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.123297ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:57:44Z"
    - latency: 1.174176ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:56:44Z"
    - latency: 1.403236ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:55:44Z"
    - latency: 1.084233ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:54:44Z"
    - latency: 1.137055ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:53:44Z"
    - latency: 1.351882ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:52:44Z"
    - latency: 850.359µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:51:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T03:50:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-9-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-9.us-east-2.compute.internal
      uid: 84b2ab30-de69-44c1-9468-230d578a9679
    resourceVersion: "39048"
    uid: 9f945dfc-d0bd-4a32-95d1-dff72b7c9176
  spec:
    sourcePod: network-check-source-6f78d59f99-5xh74
    targetEndpoint: ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T03:56:44Z"
      message: 'load-balancer-api-external: tcp connection to ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.162973ms
      message: 'load-balancer-api-external: tcp connection to ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T04:02:44Z"
    - latency: 6.808237ms
      message: 'load-balancer-api-external: resolved host name ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T04:02:44Z"
    - latency: 11.43817ms
      message: 'load-balancer-api-external: tcp connection to ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T04:01:44Z"
    - latency: 72.328746ms
      message: 'load-balancer-api-external: resolved host name ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T04:01:44Z"
    - latency: 5.188789ms
      message: 'load-balancer-api-external: tcp connection to ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T04:00:44Z"
    - latency: 7.25102ms
      message: 'load-balancer-api-external: resolved host name ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T04:00:44Z"
    - latency: 11.382008ms
      message: 'load-balancer-api-external: tcp connection to ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:59:44Z"
    - latency: 8.170563ms
      message: 'load-balancer-api-external: resolved host name ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T03:59:44Z"
    - latency: 6.771745ms
      message: 'load-balancer-api-external: tcp connection to ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:58:44Z"
    - latency: 7.129432ms
      message: 'load-balancer-api-external: resolved host name ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T03:58:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T03:50:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-9-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-9.us-east-2.compute.internal
      uid: 84b2ab30-de69-44c1-9468-230d578a9679
    resourceVersion: "39049"
    uid: 2e8638cf-4ee9-4c14-9f3b-0dc4213e7b94
  spec:
    sourcePod: network-check-source-6f78d59f99-5xh74
    targetEndpoint: ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T03:56:44Z"
      message: 'load-balancer-api-internal: tcp connection to ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.192224ms
      message: 'load-balancer-api-internal: tcp connection to ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T04:02:44Z"
    - latency: 6.833614ms
      message: 'load-balancer-api-internal: resolved host name ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T04:02:44Z"
    - latency: 14.860504ms
      message: 'load-balancer-api-internal: tcp connection to ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T04:01:44Z"
    - latency: 71.736384ms
      message: 'load-balancer-api-internal: resolved host name ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T04:01:44Z"
    - latency: 5.177526ms
      message: 'load-balancer-api-internal: tcp connection to ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T04:00:44Z"
    - latency: 7.181058ms
      message: 'load-balancer-api-internal: resolved host name ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T04:00:44Z"
    - latency: 6.625021ms
      message: 'load-balancer-api-internal: tcp connection to ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:59:44Z"
    - latency: 8.079471ms
      message: 'load-balancer-api-internal: resolved host name ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T03:59:44Z"
    - latency: 6.839686ms
      message: 'load-balancer-api-internal: tcp connection to ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:58:44Z"
    - latency: 7.210925ms
      message: 'load-balancer-api-internal: resolved host name ac90e24ce094c470db5409297b84b1e2-ce4588b5848107ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T03:58:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T03:50:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-9-to-network-check-target-ip-10-0-129-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-9.us-east-2.compute.internal
      uid: 84b2ab30-de69-44c1-9468-230d578a9679
    resourceVersion: "20881"
    uid: 75faafd4-fa2f-422f-b2fc-080c313a9945
  spec:
    sourcePod: network-check-source-6f78d59f99-5xh74
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T03:57:44Z"
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 13.481519ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:57:44Z"
    - latency: 2.253442ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:56:44Z"
    - latency: 2.690458ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:55:44Z"
    - latency: 2.266555ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:54:44Z"
    - latency: 2.42619ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:53:44Z"
    - latency: 2.431192ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:52:44Z"
    - latency: 2.00607ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:51:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T03:50:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-9-to-network-check-target-ip-10-0-129-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-9.us-east-2.compute.internal
      uid: 84b2ab30-de69-44c1-9468-230d578a9679
    resourceVersion: "20883"
    uid: a625b0d0-8337-4740-aae3-aee5a349e3ef
  spec:
    sourcePod: network-check-source-6f78d59f99-5xh74
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T03:57:44Z"
      message: 'network-check-target-ip-10-0-129-253: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 14.445764ms
      message: 'network-check-target-ip-10-0-129-253: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:57:44Z"
    - latency: 2.116897ms
      message: 'network-check-target-ip-10-0-129-253: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:56:44Z"
    - latency: 2.601649ms
      message: 'network-check-target-ip-10-0-129-253: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:55:44Z"
    - latency: 2.47587ms
      message: 'network-check-target-ip-10-0-129-253: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:54:44Z"
    - latency: 6.632824ms
      message: 'network-check-target-ip-10-0-129-253: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:53:44Z"
    - latency: 2.415226ms
      message: 'network-check-target-ip-10-0-129-253: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:52:44Z"
    - latency: 2.16657ms
      message: 'network-check-target-ip-10-0-129-253: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:51:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T03:50:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-9-to-network-check-target-ip-10-0-138-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-9.us-east-2.compute.internal
      uid: 84b2ab30-de69-44c1-9468-230d578a9679
    resourceVersion: "20882"
    uid: e42ca76e-97ee-43f8-8d39-47d5cd88569c
  spec:
    sourcePod: network-check-source-6f78d59f99-5xh74
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T03:57:44Z"
      message: 'network-check-target-ip-10-0-138-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.960142ms
      message: 'network-check-target-ip-10-0-138-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:57:44Z"
    - latency: 936.634µs
      message: 'network-check-target-ip-10-0-138-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:56:44Z"
    - latency: 1.274998ms
      message: 'network-check-target-ip-10-0-138-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:55:44Z"
    - latency: 1.302802ms
      message: 'network-check-target-ip-10-0-138-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:54:44Z"
    - latency: 866.914µs
      message: 'network-check-target-ip-10-0-138-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:53:44Z"
    - latency: 995.475µs
      message: 'network-check-target-ip-10-0-138-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:52:44Z"
    - latency: 1.625263ms
      message: 'network-check-target-ip-10-0-138-9: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:51:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T03:50:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-9-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-9.us-east-2.compute.internal
      uid: 84b2ab30-de69-44c1-9468-230d578a9679
    resourceVersion: "39047"
    uid: 87882f33-b9ae-4e67-bc68-dbc3b92c5b36
  spec:
    sourcePod: network-check-source-6f78d59f99-5xh74
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T03:56:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.055383ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T04:02:44Z"
    - latency: 1.776227ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T04:02:44Z"
    - latency: 2.481969ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T04:01:44Z"
    - latency: 54.219899ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T04:01:44Z"
    - latency: 1.264863ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T04:00:44Z"
    - latency: 1.838052ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T04:00:44Z"
    - latency: 919.095µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:59:44Z"
    - latency: 2.914359ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T03:59:44Z"
    - latency: 1.363461ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T03:58:44Z"
    - latency: 2.117619ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T03:58:44Z"
kind: List
metadata:
  resourceVersion: ""