apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T13:34:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-26-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-26.ec2.internal
      uid: 2f21dd57-1435-452a-94bf-97531c6b3924
    resourceVersion: "16474"
    uid: f3a732ff-52fe-40a2-9659-bad62ac81391
  spec:
    sourcePod: network-check-source-dbd9cf844-ftjj8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T13:41:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.67333ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:41:52Z"
    - latency: 1.518681ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:40:52Z"
    - latency: 1.276814ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:39:52Z"
    - latency: 1.255918ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:38:52Z"
    - latency: 862.907µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:37:52Z"
    - latency: 1.473757ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:36:52Z"
    - latency: 1.097958ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:35:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T13:34:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-26-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-26.ec2.internal
      uid: 2f21dd57-1435-452a-94bf-97531c6b3924
    resourceVersion: "16069"
    uid: a67c237d-b6a0-4118-9537-ef4d3b15bccb
  spec:
    sourcePod: network-check-source-dbd9cf844-ftjj8
    targetEndpoint: ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T13:40:52Z"
      message: 'load-balancer-api-external: tcp connection to ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.67691ms
      message: 'load-balancer-api-external: tcp connection to ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:40:52Z"
    - latency: 8.441587ms
      message: 'load-balancer-api-external: resolved host name ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T13:40:52Z"
    - latency: 4.824767ms
      message: 'load-balancer-api-external: tcp connection to ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:39:52Z"
    - latency: 9.331455ms
      message: 'load-balancer-api-external: resolved host name ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T13:39:52Z"
    - latency: 4.60706ms
      message: 'load-balancer-api-external: tcp connection to ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:38:52Z"
    - latency: 7.9703ms
      message: 'load-balancer-api-external: resolved host name ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T13:38:52Z"
    - latency: 4.299725ms
      message: 'load-balancer-api-external: tcp connection to ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:37:52Z"
    - latency: 8.242054ms
      message: 'load-balancer-api-external: resolved host name ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T13:37:52Z"
    - latency: 4.086067ms
      message: 'load-balancer-api-external: tcp connection to ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:36:52Z"
    - latency: 9.126633ms
      message: 'load-balancer-api-external: resolved host name ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T13:36:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T13:34:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-26-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-26.ec2.internal
      uid: 2f21dd57-1435-452a-94bf-97531c6b3924
    resourceVersion: "16068"
    uid: 0e2f6662-ef35-4dbb-b5b8-f2eb24a2b860
  spec:
    sourcePod: network-check-source-dbd9cf844-ftjj8
    targetEndpoint: ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T13:40:52Z"
      message: 'load-balancer-api-internal: tcp connection to ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.654336ms
      message: 'load-balancer-api-internal: tcp connection to ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:40:52Z"
    - latency: 8.448851ms
      message: 'load-balancer-api-internal: resolved host name ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T13:40:52Z"
    - latency: 6.120946ms
      message: 'load-balancer-api-internal: tcp connection to ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:39:52Z"
    - latency: 9.357624ms
      message: 'load-balancer-api-internal: resolved host name ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T13:39:52Z"
    - latency: 3.777835ms
      message: 'load-balancer-api-internal: tcp connection to ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:38:52Z"
    - latency: 7.910022ms
      message: 'load-balancer-api-internal: resolved host name ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T13:38:52Z"
    - latency: 4.285118ms
      message: 'load-balancer-api-internal: tcp connection to ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:37:52Z"
    - latency: 8.21709ms
      message: 'load-balancer-api-internal: resolved host name ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T13:37:52Z"
    - latency: 3.695439ms
      message: 'load-balancer-api-internal: tcp connection to ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:36:52Z"
    - latency: 9.238231ms
      message: 'load-balancer-api-internal: resolved host name ae117538df24d475f8dd479a75f8f845-08807d13500171ba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T13:36:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T13:34:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-26-to-network-check-target-ip-10-0-132-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-26.ec2.internal
      uid: 2f21dd57-1435-452a-94bf-97531c6b3924
    resourceVersion: "16472"
    uid: 727af61b-71b4-4afe-8ae2-42c0f4dc17db
  spec:
    sourcePod: network-check-source-dbd9cf844-ftjj8
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T13:41:52Z"
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.195569ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:41:52Z"
    - latency: 2.212418ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:40:52Z"
    - latency: 2.125965ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:39:52Z"
    - latency: 2.316846ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:38:52Z"
    - latency: 2.066149ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:37:52Z"
    - latency: 1.942299ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:36:52Z"
    - latency: 2.400555ms
      message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:35:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T13:34:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-26-to-network-check-target-ip-10-0-138-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-26.ec2.internal
      uid: 2f21dd57-1435-452a-94bf-97531c6b3924
    resourceVersion: "16471"
    uid: db7b35b9-7919-4a59-a225-05c3a22a3752
  spec:
    sourcePod: network-check-source-dbd9cf844-ftjj8
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T13:41:52Z"
      message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 849.76µs
      message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:41:52Z"
    - latency: 892.89µs
      message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:40:52Z"
    - latency: 1.25109ms
      message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:39:52Z"
    - latency: 885.89µs
      message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:38:52Z"
    - latency: 940.144µs
      message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:37:52Z"
    - latency: 867.428µs
      message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:36:52Z"
    - latency: 1.546893ms
      message: 'network-check-target-ip-10-0-138-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:35:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T13:34:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-26-to-network-check-target-ip-10-0-140-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-26.ec2.internal
      uid: 2f21dd57-1435-452a-94bf-97531c6b3924
    resourceVersion: "16473"
    uid: 8e627d2b-a0d0-4d57-b25c-1971339786c6
  spec:
    sourcePod: network-check-source-dbd9cf844-ftjj8
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T13:41:52Z"
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.949874ms
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:41:52Z"
    - latency: 2.208025ms
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:40:52Z"
    - latency: 2.046962ms
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:39:52Z"
    - latency: 2.02431ms
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:38:52Z"
    - latency: 1.855746ms
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:37:52Z"
    - latency: 1.77562ms
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:36:52Z"
    - latency: 2.065591ms
      message: 'network-check-target-ip-10-0-140-186: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:35:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T13:34:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-26-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-26.ec2.internal
      uid: 2f21dd57-1435-452a-94bf-97531c6b3924
    resourceVersion: "16067"
    uid: 6ee19e52-147e-4984-bb4d-033b3e5b8b50
  spec:
    sourcePod: network-check-source-dbd9cf844-ftjj8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T13:40:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 940.07µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:40:52Z"
    - latency: 1.929151ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T13:40:52Z"
    - latency: 698.437µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:39:52Z"
    - latency: 1.875597ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T13:39:52Z"
    - latency: 910.337µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:38:52Z"
    - latency: 1.832156ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T13:38:52Z"
    - latency: 992.524µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:37:52Z"
    - latency: 1.766039ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T13:37:52Z"
    - latency: 920.754µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T13:36:52Z"
    - latency: 1.739458ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T13:36:52Z"
kind: List
metadata:
  resourceVersion: ""