apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T21:42:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-151-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-151.ec2.internal
      uid: ecc5dfea-196b-4247-a9b5-fd643ea8395d
    resourceVersion: "15074"
    uid: 6e569736-7d83-46a8-963d-e90492fca2db
  spec:
    sourcePod: network-check-source-869dcfcdcd-sfr9m
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T21:49:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.222414ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:49:49Z"
    - latency: 1.291614ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:48:49Z"
    - latency: 930.585µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:47:49Z"
    - latency: 1.233662ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:46:49Z"
    - latency: 1.155004ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:45:49Z"
    - latency: 874.819µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:44:49Z"
    - latency: 1.120609ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:43:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T21:42:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-151-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-151.ec2.internal
      uid: ecc5dfea-196b-4247-a9b5-fd643ea8395d
    resourceVersion: "14536"
    uid: 123d9726-b5cb-4905-9a8e-3cb61f1ce458
  spec:
    sourcePod: network-check-source-869dcfcdcd-sfr9m
    targetEndpoint: ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T21:48:49Z"
      message: 'load-balancer-api-external: tcp connection to ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.323925ms
      message: 'load-balancer-api-external: tcp connection to ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:48:49Z"
    - latency: 7.687092ms
      message: 'load-balancer-api-external: resolved host name ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:48:49Z"
    - latency: 5.203014ms
      message: 'load-balancer-api-external: tcp connection to ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:47:49Z"
    - latency: 9.123683ms
      message: 'load-balancer-api-external: resolved host name ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:47:49Z"
    - latency: 5.173012ms
      message: 'load-balancer-api-external: tcp connection to ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:46:49Z"
    - latency: 8.542273ms
      message: 'load-balancer-api-external: resolved host name ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:46:49Z"
    - latency: 4.76152ms
      message: 'load-balancer-api-external: tcp connection to ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:45:49Z"
    - latency: 8.874004ms
      message: 'load-balancer-api-external: resolved host name ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:45:49Z"
    - latency: 4.082714ms
      message: 'load-balancer-api-external: tcp connection to ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:44:49Z"
    - latency: 8.120576ms
      message: 'load-balancer-api-external: resolved host name ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:44:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T21:42:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-151-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-151.ec2.internal
      uid: ecc5dfea-196b-4247-a9b5-fd643ea8395d
    resourceVersion: "14537"
    uid: e8049206-c43a-44c4-8ff2-12ba10211ae6
  spec:
    sourcePod: network-check-source-869dcfcdcd-sfr9m
    targetEndpoint: ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T21:48:49Z"
      message: 'load-balancer-api-internal: tcp connection to ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.313943ms
      message: 'load-balancer-api-internal: tcp connection to ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:48:49Z"
    - latency: 7.783108ms
      message: 'load-balancer-api-internal: resolved host name ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:48:49Z"
    - latency: 5.145231ms
      message: 'load-balancer-api-internal: tcp connection to ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:47:49Z"
    - latency: 9.050021ms
      message: 'load-balancer-api-internal: resolved host name ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:47:49Z"
    - latency: 5.353146ms
      message: 'load-balancer-api-internal: tcp connection to ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:46:49Z"
    - latency: 8.524066ms
      message: 'load-balancer-api-internal: resolved host name ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:46:49Z"
    - latency: 4.756808ms
      message: 'load-balancer-api-internal: tcp connection to ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:45:49Z"
    - latency: 8.793481ms
      message: 'load-balancer-api-internal: resolved host name ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:45:49Z"
    - latency: 4.06139ms
      message: 'load-balancer-api-internal: tcp connection to ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:44:49Z"
    - latency: 8.18027ms
      message: 'load-balancer-api-internal: resolved host name ab32951f74bdb4a6786e08d87a20e0b2-4c440e0662165a20.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:44:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T21:42:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-151-to-network-check-target-ip-10-0-134-81
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-151.ec2.internal
      uid: ecc5dfea-196b-4247-a9b5-fd643ea8395d
    resourceVersion: "15073"
    uid: 80dfdaa4-e634-450d-9479-7888b4ef0545
  spec:
    sourcePod: network-check-source-869dcfcdcd-sfr9m
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T21:49:49Z"
      message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.630452ms
      message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:49:49Z"
    - latency: 2.460227ms
      message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:48:49Z"
    - latency: 1.805813ms
      message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:47:49Z"
    - latency: 2.348082ms
      message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:46:49Z"
    - latency: 2.19018ms
      message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:45:49Z"
    - latency: 2.143501ms
      message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:44:49Z"
    - latency: 2.325905ms
      message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:43:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T21:42:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-151-to-network-check-target-ip-10-0-139-151
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-151.ec2.internal
      uid: ecc5dfea-196b-4247-a9b5-fd643ea8395d
    resourceVersion: "15071"
    uid: 9e1a53d8-7538-4ec7-ba83-3305e88184d2
  spec:
    sourcePod: network-check-source-869dcfcdcd-sfr9m
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T21:49:49Z"
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.223648ms
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:49:49Z"
    - latency: 1.530958ms
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:48:49Z"
    - latency: 734.383µs
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:47:49Z"
    - latency: 944.213µs
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:46:49Z"
    - latency: 1.288561ms
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:45:49Z"
    - latency: 903.479µs
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:44:49Z"
    - latency: 1.740184ms
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:43:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T21:42:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-151-to-network-check-target-ip-10-0-142-38
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-151.ec2.internal
      uid: ecc5dfea-196b-4247-a9b5-fd643ea8395d
    resourceVersion: "15072"
    uid: 08a8b568-0e42-4508-97b8-eaaa120bb965
  spec:
    sourcePod: network-check-source-869dcfcdcd-sfr9m
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T21:49:49Z"
      message: 'network-check-target-ip-10-0-142-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.071699ms
      message: 'network-check-target-ip-10-0-142-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:49:49Z"
    - latency: 2.193667ms
      message: 'network-check-target-ip-10-0-142-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:48:49Z"
    - latency: 2.141623ms
      message: 'network-check-target-ip-10-0-142-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:47:49Z"
    - latency: 2.06101ms
      message: 'network-check-target-ip-10-0-142-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:46:49Z"
    - latency: 1.772557ms
      message: 'network-check-target-ip-10-0-142-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:45:49Z"
    - latency: 1.843727ms
      message: 'network-check-target-ip-10-0-142-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:44:49Z"
    - latency: 2.261405ms
      message: 'network-check-target-ip-10-0-142-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:43:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T21:42:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-151-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-151.ec2.internal
      uid: ecc5dfea-196b-4247-a9b5-fd643ea8395d
    resourceVersion: "14535"
    uid: c08994b6-fdaf-4500-a194-ee30c0b4ded7
  spec:
    sourcePod: network-check-source-869dcfcdcd-sfr9m
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T21:48:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 848.586µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:48:49Z"
    - latency: 1.70051ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:48:49Z"
    - latency: 891.957µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:47:49Z"
    - latency: 2.035237ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:47:49Z"
    - latency: 1.333561ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:46:49Z"
    - latency: 1.779732ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:46:49Z"
    - latency: 999.94µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:45:49Z"
    - latency: 1.839177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:45:49Z"
    - latency: 882.798µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T21:44:49Z"
    - latency: 1.830535ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T21:44:49Z"
kind: List
metadata:
  resourceVersion: ""