apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:33:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-235-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-235.ec2.internal
      uid: 4cb6ad5d-05c0-4179-9722-dd4c5bc54a79
    resourceVersion: "15557"
    uid: 30749d1f-bc96-469c-b685-c8231dc11745
  spec:
    sourcePod: network-check-source-dbd9cf844-jj49x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T13:40:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 820.467µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:40:08Z"
    - latency: 889.251µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:39:08Z"
    - latency: 936.306µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:38:08Z"
    - latency: 905.002µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:37:08Z"
    - latency: 841.708µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:36:08Z"
    - latency: 1.437667ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:35:08Z"
    - latency: 933.93µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:34:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:33:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-235-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-235.ec2.internal
      uid: 4cb6ad5d-05c0-4179-9722-dd4c5bc54a79
    resourceVersion: "17794"
    uid: 2cac27fa-0803-4346-b756-70a13ff78855
  spec:
    sourcePod: network-check-source-dbd9cf844-jj49x
    targetEndpoint: a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T13:39:08Z"
      message: 'load-balancer-api-external: tcp connection to a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.615366ms
      message: 'load-balancer-api-external: tcp connection to a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:45:08Z"
    - latency: 8.636975ms
      message: 'load-balancer-api-external: resolved host name a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:45:08Z"
    - latency: 5.601528ms
      message: 'load-balancer-api-external: tcp connection to a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:44:08Z"
    - latency: 11.609295ms
      message: 'load-balancer-api-external: resolved host name a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:44:08Z"
    - latency: 4.240101ms
      message: 'load-balancer-api-external: tcp connection to a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:43:08Z"
    - latency: 14.627617ms
      message: 'load-balancer-api-external: resolved host name a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:43:08Z"
    - latency: 4.375661ms
      message: 'load-balancer-api-external: tcp connection to a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:42:08Z"
    - latency: 6.601266ms
      message: 'load-balancer-api-external: resolved host name a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:42:08Z"
    - latency: 4.539893ms
      message: 'load-balancer-api-external: tcp connection to a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:41:08Z"
    - latency: 7.792826ms
      message: 'load-balancer-api-external: resolved host name a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:41:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:33:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-235-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-235.ec2.internal
      uid: 4cb6ad5d-05c0-4179-9722-dd4c5bc54a79
    resourceVersion: "17793"
    uid: 7bcf9f56-a180-4205-bb99-b177473e8909
  spec:
    sourcePod: network-check-source-dbd9cf844-jj49x
    targetEndpoint: a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T13:39:08Z"
      message: 'load-balancer-api-internal: tcp connection to a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.562621ms
      message: 'load-balancer-api-internal: tcp connection to a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:45:08Z"
    - latency: 7.940589ms
      message: 'load-balancer-api-internal: resolved host name a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:45:08Z"
    - latency: 4.149934ms
      message: 'load-balancer-api-internal: tcp connection to a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:44:08Z"
    - latency: 11.670775ms
      message: 'load-balancer-api-internal: resolved host name a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:44:08Z"
    - latency: 4.19152ms
      message: 'load-balancer-api-internal: tcp connection to a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:43:08Z"
    - latency: 14.503746ms
      message: 'load-balancer-api-internal: resolved host name a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:43:08Z"
    - latency: 4.434079ms
      message: 'load-balancer-api-internal: tcp connection to a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:42:08Z"
    - latency: 6.505353ms
      message: 'load-balancer-api-internal: resolved host name a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:42:08Z"
    - latency: 4.58437ms
      message: 'load-balancer-api-internal: tcp connection to a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:41:08Z"
    - latency: 7.670105ms
      message: 'load-balancer-api-internal: resolved host name a1f4f5e88391a4b1b9748cd23e9a3d0c-3fea3daf21a72eb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:41:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:33:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-235-to-network-check-target-ip-10-0-135-125
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-235.ec2.internal
      uid: 4cb6ad5d-05c0-4179-9722-dd4c5bc54a79
    resourceVersion: "15556"
    uid: 01132775-b098-48e6-9c62-197b39bd3142
  spec:
    sourcePod: network-check-source-dbd9cf844-jj49x
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T13:40:08Z"
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.098212ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:40:08Z"
    - latency: 2.192937ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:39:08Z"
    - latency: 1.943841ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:38:08Z"
    - latency: 1.851918ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:37:08Z"
    - latency: 1.855395ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:36:08Z"
    - latency: 2.191598ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:35:08Z"
    - latency: 2.198156ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:34:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:33:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-235-to-network-check-target-ip-10-0-139-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-235.ec2.internal
      uid: 4cb6ad5d-05c0-4179-9722-dd4c5bc54a79
    resourceVersion: "15554"
    uid: 3f747bdb-4dc0-46ba-8fab-8ee152e05197
  spec:
    sourcePod: network-check-source-dbd9cf844-jj49x
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T13:40:08Z"
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 979.17µs
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:40:08Z"
    - latency: 744.08µs
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:39:08Z"
    - latency: 854.975µs
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:38:08Z"
    - latency: 711.298µs
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:37:08Z"
    - latency: 994.27µs
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:36:08Z"
    - latency: 835.677µs
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:35:08Z"
    - latency: 1.28709ms
      message: 'network-check-target-ip-10-0-139-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:34:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:33:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-235-to-network-check-target-ip-10-0-142-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-235.ec2.internal
      uid: 4cb6ad5d-05c0-4179-9722-dd4c5bc54a79
    resourceVersion: "15555"
    uid: d86a2774-0baf-44d8-bcbf-f353afc4ab82
  spec:
    sourcePod: network-check-source-dbd9cf844-jj49x
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T13:40:08Z"
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.949869ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:40:08Z"
    - latency: 1.839565ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:39:08Z"
    - latency: 2.082746ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:38:08Z"
    - latency: 1.781603ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:37:08Z"
    - latency: 1.786548ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:36:08Z"
    - latency: 2.117829ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:35:08Z"
    - latency: 2.219458ms
      message: 'network-check-target-ip-10-0-142-95: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:34:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T13:33:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-235-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-235.ec2.internal
      uid: 4cb6ad5d-05c0-4179-9722-dd4c5bc54a79
    resourceVersion: "17792"
    uid: ca5ff2b9-a5c7-4975-a220-c477b6dd187d
  spec:
    sourcePod: network-check-source-dbd9cf844-jj49x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T13:39:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.162696ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:45:08Z"
    - latency: 2.934419ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:45:08Z"
    - latency: 888.164µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:44:08Z"
    - latency: 2.211565ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:44:08Z"
    - latency: 1.438243ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:43:08Z"
    - latency: 2.591915ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:43:08Z"
    - latency: 940.585µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:42:08Z"
    - latency: 1.780109ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:42:08Z"
    - latency: 1.211345ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T13:41:08Z"
    - latency: 1.591672ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T13:41:08Z"
kind: List
metadata:
  resourceVersion: ""