apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:31:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-231-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-231.ec2.internal
      uid: eb751082-3d49-4163-ad19-c8426c5b591b
    resourceVersion: "14404"
    uid: 8def4e7d-1b7e-4467-99e5-7764ec9baeb6
  spec:
    sourcePod: network-check-source-56d84b9f44-tthjd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T09:38:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.759938ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:38:02Z"
    - latency: 1.070513ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:37:02Z"
    - latency: 932.639µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:36:02Z"
    - latency: 866.039µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:35:02Z"
    - latency: 1.38008ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:34:02Z"
    - latency: 977.925µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:33:02Z"
    - latency: 992.532µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:32:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:31:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-231-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-231.ec2.internal
      uid: eb751082-3d49-4163-ad19-c8426c5b591b
    resourceVersion: "14067"
    uid: 273820e7-2f6f-4c11-8ed2-4ef7947c0699
  spec:
    sourcePod: network-check-source-56d84b9f44-tthjd
    targetEndpoint: ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T09:37:02Z"
      message: 'load-balancer-api-external: tcp connection to ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.207834ms
      message: 'load-balancer-api-external: tcp connection to ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:37:02Z"
    - latency: 8.479937ms
      message: 'load-balancer-api-external: resolved host name ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:37:02Z"
    - latency: 5.03296ms
      message: 'load-balancer-api-external: tcp connection to ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:36:02Z"
    - latency: 7.978254ms
      message: 'load-balancer-api-external: resolved host name ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:36:02Z"
    - latency: 5.006201ms
      message: 'load-balancer-api-external: tcp connection to ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:35:02Z"
    - latency: 10.009145ms
      message: 'load-balancer-api-external: resolved host name ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:35:02Z"
    - latency: 4.232151ms
      message: 'load-balancer-api-external: tcp connection to ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:34:02Z"
    - latency: 8.041699ms
      message: 'load-balancer-api-external: resolved host name ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:34:02Z"
    - latency: 5.313449ms
      message: 'load-balancer-api-external: tcp connection to ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:33:02Z"
    - latency: 9.202656ms
      message: 'load-balancer-api-external: resolved host name ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:33:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:31:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-231-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-231.ec2.internal
      uid: eb751082-3d49-4163-ad19-c8426c5b591b
    resourceVersion: "14066"
    uid: a207147a-2a92-4ce6-ac56-b12126015879
  spec:
    sourcePod: network-check-source-56d84b9f44-tthjd
    targetEndpoint: ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T09:37:02Z"
      message: 'load-balancer-api-internal: tcp connection to ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.12109ms
      message: 'load-balancer-api-internal: tcp connection to ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:37:02Z"
    - latency: 8.532223ms
      message: 'load-balancer-api-internal: resolved host name ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:37:02Z"
    - latency: 4.51323ms
      message: 'load-balancer-api-internal: tcp connection to ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:36:02Z"
    - latency: 8.083944ms
      message: 'load-balancer-api-internal: resolved host name ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:36:02Z"
    - latency: 5.019381ms
      message: 'load-balancer-api-internal: tcp connection to ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:35:02Z"
    - latency: 10.091332ms
      message: 'load-balancer-api-internal: resolved host name ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:35:02Z"
    - latency: 3.673207ms
      message: 'load-balancer-api-internal: tcp connection to ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:34:02Z"
    - latency: 8.110658ms
      message: 'load-balancer-api-internal: resolved host name ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:34:02Z"
    - latency: 5.383068ms
      message: 'load-balancer-api-internal: tcp connection to ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:33:02Z"
    - latency: 9.294067ms
      message: 'load-balancer-api-internal: resolved host name ab60b137990cd43d091da21e702d4330-d69797171ef94fcf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:33:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:31:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-231-to-network-check-target-ip-10-0-130-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-231.ec2.internal
      uid: eb751082-3d49-4163-ad19-c8426c5b591b
    resourceVersion: "14403"
    uid: beea4c32-a79e-4caf-8701-2e49ca39833e
  spec:
    sourcePod: network-check-source-56d84b9f44-tthjd
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T09:38:02Z"
      message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.268428ms
      message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:38:02Z"
    - latency: 1.969532ms
      message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:37:02Z"
    - latency: 2.133571ms
      message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:36:02Z"
    - latency: 2.415902ms
      message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:35:02Z"
    - latency: 2.60443ms
      message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:34:02Z"
    - latency: 2.619509ms
      message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:33:02Z"
    - latency: 2.42052ms
      message: 'network-check-target-ip-10-0-130-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:32:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:31:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-231-to-network-check-target-ip-10-0-132-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-231.ec2.internal
      uid: eb751082-3d49-4163-ad19-c8426c5b591b
    resourceVersion: "14401"
    uid: 1eb21728-178f-4962-b36e-6c59c9fecc7d
  spec:
    sourcePod: network-check-source-56d84b9f44-tthjd
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T09:38:02Z"
      message: 'network-check-target-ip-10-0-132-231: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 937.031µs
      message: 'network-check-target-ip-10-0-132-231: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:38:02Z"
    - latency: 1.215372ms
      message: 'network-check-target-ip-10-0-132-231: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:37:02Z"
    - latency: 925.591µs
      message: 'network-check-target-ip-10-0-132-231: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:36:02Z"
    - latency: 981.342µs
      message: 'network-check-target-ip-10-0-132-231: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:35:02Z"
    - latency: 1.035504ms
      message: 'network-check-target-ip-10-0-132-231: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:34:02Z"
    - latency: 1.461606ms
      message: 'network-check-target-ip-10-0-132-231: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:33:02Z"
    - latency: 1.268819ms
      message: 'network-check-target-ip-10-0-132-231: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:32:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:31:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-231-to-network-check-target-ip-10-0-137-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-231.ec2.internal
      uid: eb751082-3d49-4163-ad19-c8426c5b591b
    resourceVersion: "14402"
    uid: d1bffef5-61e9-4ad5-8201-abbdb5595420
  spec:
    sourcePod: network-check-source-56d84b9f44-tthjd
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T09:38:02Z"
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.701987ms
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:38:02Z"
    - latency: 2.143095ms
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:37:02Z"
    - latency: 2.580267ms
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:36:02Z"
    - latency: 2.501959ms
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:35:02Z"
    - latency: 2.641081ms
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:34:02Z"
    - latency: 2.807287ms
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:33:02Z"
    - latency: 2.377739ms
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:32:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T09:31:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-231-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-231.ec2.internal
      uid: eb751082-3d49-4163-ad19-c8426c5b591b
    resourceVersion: "14065"
    uid: 9b27e2eb-60c8-4eb8-8ed3-0977a3b09402
  spec:
    sourcePod: network-check-source-56d84b9f44-tthjd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T09:37:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.028989ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:37:02Z"
    - latency: 2.125729ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:37:02Z"
    - latency: 1.078687ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:36:02Z"
    - latency: 1.975384ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:36:02Z"
    - latency: 865.843µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:35:02Z"
    - latency: 1.802168ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:35:02Z"
    - latency: 990.126µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:34:02Z"
    - latency: 1.80407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:34:02Z"
    - latency: 924.798µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T09:33:02Z"
    - latency: 2.152265ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T09:33:02Z"
kind: List
metadata:
  resourceVersion: ""