apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T01:48:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-122-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-122.ec2.internal
      uid: 22cc6b51-8352-4a1f-a050-69cd352b7040
    resourceVersion: "15788"
    uid: 1ec15eab-02d1-45f8-aeb5-69bf3b453e3d
  spec:
    sourcePod: network-check-source-dbd9cf844-t2gdg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T01:55:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 922.365µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:55:23Z"
    - latency: 956.369µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:54:23Z"
    - latency: 979.29µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:53:23Z"
    - latency: 1.009959ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:52:23Z"
    - latency: 709.869µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:51:23Z"
    - latency: 1.514735ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:50:23Z"
    - latency: 910.384µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:49:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T01:48:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-122-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-122.ec2.internal
      uid: 22cc6b51-8352-4a1f-a050-69cd352b7040
    resourceVersion: "15460"
    uid: f11fe854-1ad2-4fc6-8104-dc0209160750
  spec:
    sourcePod: network-check-source-dbd9cf844-t2gdg
    targetEndpoint: a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T01:54:23Z"
      message: 'load-balancer-api-external: tcp connection to a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.525822ms
      message: 'load-balancer-api-external: tcp connection to a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:54:23Z"
    - latency: 7.577684ms
      message: 'load-balancer-api-external: resolved host name a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T01:54:23Z"
    - latency: 5.517192ms
      message: 'load-balancer-api-external: tcp connection to a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:53:23Z"
    - latency: 9.478481ms
      message: 'load-balancer-api-external: resolved host name a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T01:53:23Z"
    - latency: 4.764695ms
      message: 'load-balancer-api-external: tcp connection to a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:52:23Z"
    - latency: 8.909998ms
      message: 'load-balancer-api-external: resolved host name a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T01:52:23Z"
    - latency: 4.290058ms
      message: 'load-balancer-api-external: tcp connection to a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:51:23Z"
    - latency: 7.81885ms
      message: 'load-balancer-api-external: resolved host name a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T01:51:23Z"
    - latency: 5.39204ms
      message: 'load-balancer-api-external: tcp connection to a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:50:23Z"
    - latency: 7.789176ms
      message: 'load-balancer-api-external: resolved host name a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T01:50:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T01:48:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-122-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-122.ec2.internal
      uid: 22cc6b51-8352-4a1f-a050-69cd352b7040
    resourceVersion: "15459"
    uid: 1a069b83-964f-49c8-9d2a-de501891404d
  spec:
    sourcePod: network-check-source-dbd9cf844-t2gdg
    targetEndpoint: a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T01:54:23Z"
      message: 'load-balancer-api-internal: tcp connection to a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.697887ms
      message: 'load-balancer-api-internal: tcp connection to a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:54:23Z"
    - latency: 7.647039ms
      message: 'load-balancer-api-internal: resolved host name a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T01:54:23Z"
    - latency: 5.514239ms
      message: 'load-balancer-api-internal: tcp connection to a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:53:23Z"
    - latency: 9.426564ms
      message: 'load-balancer-api-internal: resolved host name a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T01:53:23Z"
    - latency: 4.653857ms
      message: 'load-balancer-api-internal: tcp connection to a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:52:23Z"
    - latency: 9.018669ms
      message: 'load-balancer-api-internal: resolved host name a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T01:52:23Z"
    - latency: 4.626815ms
      message: 'load-balancer-api-internal: tcp connection to a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:51:23Z"
    - latency: 7.942715ms
      message: 'load-balancer-api-internal: resolved host name a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T01:51:23Z"
    - latency: 5.044849ms
      message: 'load-balancer-api-internal: tcp connection to a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:50:23Z"
    - latency: 7.845139ms
      message: 'load-balancer-api-internal: resolved host name a7c11fe8be05340e89c31d33e5cca846-c7bb3173791095fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T01:50:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T01:48:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-122-to-network-check-target-ip-10-0-131-122
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-122.ec2.internal
      uid: 22cc6b51-8352-4a1f-a050-69cd352b7040
    resourceVersion: "15785"
    uid: 2c6de158-6800-44b4-9faf-648de989db3b
  spec:
    sourcePod: network-check-source-dbd9cf844-t2gdg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T01:55:23Z"
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 835.8µs
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:55:23Z"
    - latency: 1.169691ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:54:23Z"
    - latency: 1.231953ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:53:23Z"
    - latency: 767.211µs
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:52:23Z"
    - latency: 935.839µs
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:51:23Z"
    - latency: 743.008µs
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:50:23Z"
    - latency: 1.07308ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:49:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T01:48:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-122-to-network-check-target-ip-10-0-138-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-122.ec2.internal
      uid: 22cc6b51-8352-4a1f-a050-69cd352b7040
    resourceVersion: "15787"
    uid: a363c7b4-8505-4778-b91f-01a1a834af5a
  spec:
    sourcePod: network-check-source-dbd9cf844-t2gdg
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T01:55:23Z"
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.174792ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:55:23Z"
    - latency: 2.29313ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:54:23Z"
    - latency: 2.083131ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:53:23Z"
    - latency: 2.084083ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:52:23Z"
    - latency: 1.831408ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:51:23Z"
    - latency: 2.084052ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:50:23Z"
    - latency: 2.246546ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:49:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T01:48:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-122-to-network-check-target-ip-10-0-142-29
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-122.ec2.internal
      uid: 22cc6b51-8352-4a1f-a050-69cd352b7040
    resourceVersion: "15786"
    uid: 0d6b9aee-be8b-4c97-be6c-ac9346b02131
  spec:
    sourcePod: network-check-source-dbd9cf844-t2gdg
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T01:55:23Z"
      message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.014432ms
      message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:55:23Z"
    - latency: 1.961091ms
      message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:54:23Z"
    - latency: 1.90469ms
      message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:53:23Z"
    - latency: 1.931169ms
      message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:52:23Z"
    - latency: 1.601795ms
      message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:51:23Z"
    - latency: 1.946048ms
      message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:50:23Z"
    - latency: 2.107702ms
      message: 'network-check-target-ip-10-0-142-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:49:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T01:48:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-122-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-122.ec2.internal
      uid: 22cc6b51-8352-4a1f-a050-69cd352b7040
    resourceVersion: "15458"
    uid: 3f9de3bf-5b41-4453-8290-b6307ca82f86
  spec:
    sourcePod: network-check-source-dbd9cf844-t2gdg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T01:54:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 777.264µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:54:23Z"
    - latency: 1.812842ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T01:54:23Z"
    - latency: 1.048244ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:53:23Z"
    - latency: 1.683296ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T01:53:23Z"
    - latency: 713.577µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:52:23Z"
    - latency: 1.620395ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T01:52:23Z"
    - latency: 876.36µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:51:23Z"
    - latency: 1.582105ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T01:51:23Z"
    - latency: 938.255µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T01:50:23Z"
    - latency: 1.874588ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T01:50:23Z"
kind: List
metadata:
  resourceVersion: ""