apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:40:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-4-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-4.ec2.internal
      uid: c843a4cf-f99a-43e5-b56a-9bab9a0de7bc
    resourceVersion: "14800"
    uid: 8cb6d5cc-7d84-4357-91ad-25380289b2f9
  spec:
    sourcePod: network-check-source-685456655f-62d7m
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:47:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 870.174µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:47:51Z"
    - latency: 870.167µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:46:51Z"
    - latency: 976.979µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:45:51Z"
    - latency: 1.058203ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:44:51Z"
    - latency: 1.001715ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:43:51Z"
    - latency: 846.989µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:42:51Z"
    - latency: 861.421µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:41:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:40:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-4-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-4.ec2.internal
      uid: c843a4cf-f99a-43e5-b56a-9bab9a0de7bc
    resourceVersion: "14469"
    uid: f89ae1d1-fa1d-4a41-ba9c-f2efeb41536b
  spec:
    sourcePod: network-check-source-685456655f-62d7m
    targetEndpoint: a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:46:51Z"
      message: 'load-balancer-api-external: tcp connection to a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.275499ms
      message: 'load-balancer-api-external: tcp connection to a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:46:51Z"
    - latency: 8.966158ms
      message: 'load-balancer-api-external: resolved host name a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:46:51Z"
    - latency: 5.282026ms
      message: 'load-balancer-api-external: tcp connection to a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:45:51Z"
    - latency: 8.05445ms
      message: 'load-balancer-api-external: resolved host name a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:45:51Z"
    - latency: 4.857105ms
      message: 'load-balancer-api-external: tcp connection to a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:44:51Z"
    - latency: 7.818694ms
      message: 'load-balancer-api-external: resolved host name a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:44:51Z"
    - latency: 5.962329ms
      message: 'load-balancer-api-external: tcp connection to a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:43:51Z"
    - latency: 8.468818ms
      message: 'load-balancer-api-external: resolved host name a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:43:51Z"
    - latency: 5.143465ms
      message: 'load-balancer-api-external: tcp connection to a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:42:51Z"
    - latency: 8.347622ms
      message: 'load-balancer-api-external: resolved host name a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:42:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:40:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-4-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-4.ec2.internal
      uid: c843a4cf-f99a-43e5-b56a-9bab9a0de7bc
    resourceVersion: "14470"
    uid: 879980eb-3d29-4155-a7f3-fa1b397c16da
  spec:
    sourcePod: network-check-source-685456655f-62d7m
    targetEndpoint: a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:46:51Z"
      message: 'load-balancer-api-internal: tcp connection to a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.375876ms
      message: 'load-balancer-api-internal: tcp connection to a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:46:51Z"
    - latency: 8.930004ms
      message: 'load-balancer-api-internal: resolved host name a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:46:51Z"
    - latency: 5.317035ms
      message: 'load-balancer-api-internal: tcp connection to a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:45:51Z"
    - latency: 8.092095ms
      message: 'load-balancer-api-internal: resolved host name a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:45:51Z"
    - latency: 4.843941ms
      message: 'load-balancer-api-internal: tcp connection to a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:44:51Z"
    - latency: 7.838865ms
      message: 'load-balancer-api-internal: resolved host name a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:44:51Z"
    - latency: 5.506298ms
      message: 'load-balancer-api-internal: tcp connection to a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:43:51Z"
    - latency: 8.488163ms
      message: 'load-balancer-api-internal: resolved host name a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:43:51Z"
    - latency: 5.126381ms
      message: 'load-balancer-api-internal: tcp connection to a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:42:51Z"
    - latency: 8.278649ms
      message: 'load-balancer-api-internal: resolved host name a0edc8eb7d0884581a8589f7b8a9fd35-4aa4339f78e9d57d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:42:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:40:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-4-to-network-check-target-ip-10-0-132-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-4.ec2.internal
      uid: c843a4cf-f99a-43e5-b56a-9bab9a0de7bc
    resourceVersion: "14798"
    uid: f2b58e9c-4267-4e35-859d-6b41e13356d4
  spec:
    sourcePod: network-check-source-685456655f-62d7m
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:47:51Z"
      message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.96628ms
      message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:47:51Z"
    - latency: 2.195251ms
      message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:46:51Z"
    - latency: 2.14021ms
      message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:45:51Z"
    - latency: 2.196916ms
      message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:44:51Z"
    - latency: 2.234502ms
      message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:43:51Z"
    - latency: 2.282154ms
      message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:42:51Z"
    - latency: 2.184388ms
      message: 'network-check-target-ip-10-0-132-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:41:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:40:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-4-to-network-check-target-ip-10-0-136-88
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-4.ec2.internal
      uid: c843a4cf-f99a-43e5-b56a-9bab9a0de7bc
    resourceVersion: "14799"
    uid: 20dd8a08-26e5-4ae9-a4c9-71f4cebf9daf
  spec:
    sourcePod: network-check-source-685456655f-62d7m
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:47:51Z"
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.378965ms
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:47:51Z"
    - latency: 2.2279ms
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:46:51Z"
    - latency: 2.324437ms
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:45:51Z"
    - latency: 2.126645ms
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:44:51Z"
    - latency: 1.938981ms
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:43:51Z"
    - latency: 2.265818ms
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:42:51Z"
    - latency: 2.448992ms
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:41:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:40:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-4-to-network-check-target-ip-10-0-140-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-4.ec2.internal
      uid: c843a4cf-f99a-43e5-b56a-9bab9a0de7bc
    resourceVersion: "14797"
    uid: bb7721dd-926c-4b96-8c9e-38a967ce1d25
  spec:
    sourcePod: network-check-source-685456655f-62d7m
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:47:51Z"
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.18344ms
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:47:51Z"
    - latency: 829.993µs
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:46:51Z"
    - latency: 944.577µs
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:45:51Z"
    - latency: 843.247µs
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:44:51Z"
    - latency: 949.382µs
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:43:51Z"
    - latency: 863.308µs
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:42:51Z"
    - latency: 1.531824ms
      message: 'network-check-target-ip-10-0-140-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:41:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T02:40:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-4-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-4.ec2.internal
      uid: c843a4cf-f99a-43e5-b56a-9bab9a0de7bc
    resourceVersion: "14468"
    uid: 8f99abf0-b9dd-4ddd-a6c3-7b415a04024a
  spec:
    sourcePod: network-check-source-685456655f-62d7m
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T02:46:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 986.427µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:46:51Z"
    - latency: 1.830426ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:46:51Z"
    - latency: 917.842µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:45:51Z"
    - latency: 1.921238ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:45:51Z"
    - latency: 1.097977ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:44:51Z"
    - latency: 1.733599ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:44:51Z"
    - latency: 1.130419ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:43:51Z"
    - latency: 1.764642ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:43:51Z"
    - latency: 831.277µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T02:42:51Z"
    - latency: 1.609067ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T02:42:51Z"
kind: List
metadata:
  resourceVersion: ""