apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T11:44:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-113-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-113.ec2.internal
      uid: 8b2cdbac-5f56-4bb1-be39-12d3e01a8fa7
    resourceVersion: "16270"
    uid: a075bf69-0372-4506-9ab7-d2f274e8d3e8
  spec:
    sourcePod: network-check-source-dbd9cf844-wr87x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:51:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 954.588µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:51:41Z"
    - latency: 767.559µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:50:41Z"
    - latency: 10.57578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:49:41Z"
    - latency: 978.513µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:48:41Z"
    - latency: 1.052687ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:47:41Z"
    - latency: 841.016µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:46:41Z"
    - latency: 1.154128ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:45:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T11:44:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-113-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-113.ec2.internal
      uid: 8b2cdbac-5f56-4bb1-be39-12d3e01a8fa7
    resourceVersion: "15851"
    uid: fca675a9-5eef-4f00-982f-e3dc20a6e010
  spec:
    sourcePod: network-check-source-dbd9cf844-wr87x
    targetEndpoint: ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:50:41Z"
      message: 'load-balancer-api-external: tcp connection to ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.526433ms
      message: 'load-balancer-api-external: tcp connection to ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:50:41Z"
    - latency: 7.290508ms
      message: 'load-balancer-api-external: resolved host name ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:50:41Z"
    - latency: 6.288922ms
      message: 'load-balancer-api-external: tcp connection to ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:49:41Z"
    - latency: 33.482821ms
      message: 'load-balancer-api-external: resolved host name ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:49:41Z"
    - latency: 4.395498ms
      message: 'load-balancer-api-external: tcp connection to ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:48:41Z"
    - latency: 7.372236ms
      message: 'load-balancer-api-external: resolved host name ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:48:41Z"
    - latency: 4.801386ms
      message: 'load-balancer-api-external: tcp connection to ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:47:41Z"
    - latency: 7.144259ms
      message: 'load-balancer-api-external: resolved host name ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:47:41Z"
    - latency: 5.543235ms
      message: 'load-balancer-api-external: tcp connection to ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:46:41Z"
    - latency: 6.457795ms
      message: 'load-balancer-api-external: resolved host name ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:46:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T11:44:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-113-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-113.ec2.internal
      uid: 8b2cdbac-5f56-4bb1-be39-12d3e01a8fa7
    resourceVersion: "15850"
    uid: fdcff7f3-1f96-4865-b657-eaebb3c5926e
  spec:
    sourcePod: network-check-source-dbd9cf844-wr87x
    targetEndpoint: ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:50:41Z"
      message: 'load-balancer-api-internal: tcp connection to ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.06292ms
      message: 'load-balancer-api-internal: tcp connection to ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:50:41Z"
    - latency: 7.172842ms
      message: 'load-balancer-api-internal: resolved host name ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:50:41Z"
    - latency: 6.600862ms
      message: 'load-balancer-api-internal: tcp connection to ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:49:41Z"
    - latency: 32.637104ms
      message: 'load-balancer-api-internal: resolved host name ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:49:41Z"
    - latency: 4.40058ms
      message: 'load-balancer-api-internal: tcp connection to ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:48:41Z"
    - latency: 7.305798ms
      message: 'load-balancer-api-internal: resolved host name ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:48:41Z"
    - latency: 4.820773ms
      message: 'load-balancer-api-internal: tcp connection to ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:47:41Z"
    - latency: 7.117873ms
      message: 'load-balancer-api-internal: resolved host name ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:47:41Z"
    - latency: 4.389368ms
      message: 'load-balancer-api-internal: tcp connection to ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:46:41Z"
    - latency: 6.259054ms
      message: 'load-balancer-api-internal: resolved host name ac92d62d6867444a4932fc67cafae2dd-d9ac50f92d8d0c8c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:46:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T11:44:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-113-to-network-check-target-ip-10-0-129-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-113.ec2.internal
      uid: 8b2cdbac-5f56-4bb1-be39-12d3e01a8fa7
    resourceVersion: "16269"
    uid: b60d74c7-ae32-4da0-9e97-0e278abd8281
  spec:
    sourcePod: network-check-source-dbd9cf844-wr87x
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:51:41Z"
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.305095ms
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:51:41Z"
    - latency: 2.114432ms
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:50:41Z"
    - latency: 9.073937ms
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:49:41Z"
    - latency: 2.358621ms
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:48:41Z"
    - latency: 2.829301ms
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:47:41Z"
    - latency: 2.345369ms
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:46:41Z"
    - latency: 2.708807ms
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:45:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T11:44:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-113-to-network-check-target-ip-10-0-135-216
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-113.ec2.internal
      uid: 8b2cdbac-5f56-4bb1-be39-12d3e01a8fa7
    resourceVersion: "16268"
    uid: 9b4998f2-992c-439a-b79d-4555a0e397ce
  spec:
    sourcePod: network-check-source-dbd9cf844-wr87x
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:51:41Z"
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.223847ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:51:41Z"
    - latency: 1.925519ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:50:41Z"
    - latency: 9.41621ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:49:41Z"
    - latency: 2.202992ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:48:41Z"
    - latency: 2.332183ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:47:41Z"
    - latency: 2.103308ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:46:41Z"
    - latency: 2.595781ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:45:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T11:44:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-113-to-network-check-target-ip-10-0-140-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-113.ec2.internal
      uid: 8b2cdbac-5f56-4bb1-be39-12d3e01a8fa7
    resourceVersion: "16267"
    uid: 2f045dd6-9086-4e43-9c1b-a0a1df045776
  spec:
    sourcePod: network-check-source-dbd9cf844-wr87x
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:51:41Z"
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.231721ms
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:51:41Z"
    - latency: 824.789µs
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:50:41Z"
    - latency: 10.74773ms
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:49:41Z"
    - latency: 933.439µs
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:48:41Z"
    - latency: 1.459192ms
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:47:41Z"
    - latency: 1.029915ms
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:46:41Z"
    - latency: 1.528554ms
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:45:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T11:44:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-113-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-113.ec2.internal
      uid: 8b2cdbac-5f56-4bb1-be39-12d3e01a8fa7
    resourceVersion: "15849"
    uid: b31f14bc-4c04-4c40-9830-9fa631df3154
  spec:
    sourcePod: network-check-source-dbd9cf844-wr87x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:50:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 781.232µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:50:41Z"
    - latency: 1.81704ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:50:41Z"
    - latency: 1.129372ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:49:41Z"
    - latency: 12.035504ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:49:41Z"
    - latency: 1.282832ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:48:41Z"
    - latency: 1.711422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:48:41Z"
    - latency: 1.471807ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:47:41Z"
    - latency: 1.944018ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:47:41Z"
    - latency: 1.273222ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:46:41Z"
    - latency: 1.810858ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:46:41Z"
kind: List
metadata:
  resourceVersion: ""