apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:35:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-231-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-231.ec2.internal
      uid: e9bbbb3c-1817-4caa-b0d6-c04bb94d5d03
    resourceVersion: "22558"
    uid: 65a6034a-ce82-4c8f-965f-3c22225ea49e
  spec:
    sourcePod: network-check-source-56499946bc-ww94b
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:42:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.013204ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:42:42Z"
    - latency: 1.270305ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:41:42Z"
    - latency: 928.894µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:40:42Z"
    - latency: 811.396µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:39:42Z"
    - latency: 1.347225ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:38:42Z"
    - latency: 1.052566ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:37:42Z"
    - latency: 1.63401ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:36:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:35:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-231-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-231.ec2.internal
      uid: e9bbbb3c-1817-4caa-b0d6-c04bb94d5d03
    resourceVersion: "21578"
    uid: 868b7275-9c14-4e07-ac42-5c63d7c92858
  spec:
    sourcePod: network-check-source-56499946bc-ww94b
    targetEndpoint: a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:41:42Z"
      message: 'load-balancer-api-external: tcp connection to a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.872636ms
      message: 'load-balancer-api-external: tcp connection to a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:41:42Z"
    - latency: 8.661736ms
      message: 'load-balancer-api-external: resolved host name a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:41:42Z"
    - latency: 5.155401ms
      message: 'load-balancer-api-external: tcp connection to a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:40:42Z"
    - latency: 7.821762ms
      message: 'load-balancer-api-external: resolved host name a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:40:42Z"
    - latency: 6.115148ms
      message: 'load-balancer-api-external: tcp connection to a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:39:42Z"
    - latency: 10.590508ms
      message: 'load-balancer-api-external: resolved host name a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:39:42Z"
    - latency: 4.700582ms
      message: 'load-balancer-api-external: tcp connection to a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:38:42Z"
    - latency: 8.606489ms
      message: 'load-balancer-api-external: resolved host name a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:38:42Z"
    - latency: 6.3848ms
      message: 'load-balancer-api-external: tcp connection to a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:37:42Z"
    - latency: 7.126357ms
      message: 'load-balancer-api-external: resolved host name a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:37:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:35:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-231-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-231.ec2.internal
      uid: e9bbbb3c-1817-4caa-b0d6-c04bb94d5d03
    resourceVersion: "21579"
    uid: 5f344c51-3ce7-4aa4-849e-9ca582f0b056
  spec:
    sourcePod: network-check-source-56499946bc-ww94b
    targetEndpoint: a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:41:42Z"
      message: 'load-balancer-api-internal: tcp connection to a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.871963ms
      message: 'load-balancer-api-internal: tcp connection to a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:41:42Z"
    - latency: 8.704659ms
      message: 'load-balancer-api-internal: resolved host name a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:41:42Z"
    - latency: 5.043431ms
      message: 'load-balancer-api-internal: tcp connection to a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:40:42Z"
    - latency: 7.960747ms
      message: 'load-balancer-api-internal: resolved host name a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:40:42Z"
    - latency: 6.070934ms
      message: 'load-balancer-api-internal: tcp connection to a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:39:42Z"
    - latency: 10.56988ms
      message: 'load-balancer-api-internal: resolved host name a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:39:42Z"
    - latency: 4.990643ms
      message: 'load-balancer-api-internal: tcp connection to a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:38:42Z"
    - latency: 8.577614ms
      message: 'load-balancer-api-internal: resolved host name a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:38:42Z"
    - latency: 5.415194ms
      message: 'load-balancer-api-internal: tcp connection to a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:37:42Z"
    - latency: 7.182428ms
      message: 'load-balancer-api-internal: resolved host name a85e5d73d60a4433880ca92753d11836-9dd659391e2123a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:37:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:35:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-231-to-network-check-target-ip-10-0-132-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-231.ec2.internal
      uid: e9bbbb3c-1817-4caa-b0d6-c04bb94d5d03
    resourceVersion: "22556"
    uid: 00e34f9a-b5e7-4ab9-b0c5-74ad8ee04506
  spec:
    sourcePod: network-check-source-56499946bc-ww94b
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:42:42Z"
      message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.310652ms
      message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:42:42Z"
    - latency: 2.528453ms
      message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:41:42Z"
    - latency: 2.109451ms
      message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:40:42Z"
    - latency: 2.007727ms
      message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:39:42Z"
    - latency: 2.171516ms
      message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:38:42Z"
    - latency: 2.206435ms
      message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:37:42Z"
    - latency: 2.45951ms
      message: 'network-check-target-ip-10-0-132-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:36:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:35:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-231-to-network-check-target-ip-10-0-138-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-231.ec2.internal
      uid: e9bbbb3c-1817-4caa-b0d6-c04bb94d5d03
    resourceVersion: "22555"
    uid: 1e87f7c0-45c6-4f76-be81-69353781acbe
  spec:
    sourcePod: network-check-source-56499946bc-ww94b
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:42:42Z"
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.146885ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:42:42Z"
    - latency: 961.161µs
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:41:42Z"
    - latency: 1.267358ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:40:42Z"
    - latency: 757.769µs
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:39:42Z"
    - latency: 876.409µs
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:38:42Z"
    - latency: 1.245563ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:37:42Z"
    - latency: 1.263601ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:36:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:35:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-231-to-network-check-target-ip-10-0-141-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-231.ec2.internal
      uid: e9bbbb3c-1817-4caa-b0d6-c04bb94d5d03
    resourceVersion: "22557"
    uid: dc469aca-0b83-4395-ad90-f1e9e0ef5a0f
  spec:
    sourcePod: network-check-source-56499946bc-ww94b
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:42:42Z"
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.412827ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:42:42Z"
    - latency: 1.900924ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:41:42Z"
    - latency: 2.427948ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:40:42Z"
    - latency: 2.074382ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:39:42Z"
    - latency: 2.270541ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:38:42Z"
    - latency: 2.480937ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:37:42Z"
    - latency: 3.196189ms
      message: 'network-check-target-ip-10-0-141-190: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:36:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T22:35:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-231-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-231.ec2.internal
      uid: e9bbbb3c-1817-4caa-b0d6-c04bb94d5d03
    resourceVersion: "21577"
    uid: 4e363591-3b85-4e41-8f28-eb4f99bdc60d
  spec:
    sourcePod: network-check-source-56499946bc-ww94b
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T22:41:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.128667ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:41:42Z"
    - latency: 2.692682ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:41:42Z"
    - latency: 923.764µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:40:42Z"
    - latency: 1.796414ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:40:42Z"
    - latency: 861.412µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:39:42Z"
    - latency: 2.189572ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:39:42Z"
    - latency: 1.000679ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:38:42Z"
    - latency: 2.145979ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:38:42Z"
    - latency: 838.044µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T22:37:42Z"
    - latency: 1.850039ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T22:37:42Z"
kind: List
metadata:
  resourceVersion: ""