apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:24:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-110-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-110.ec2.internal
      uid: 8916d1bc-d424-481f-9c04-b59f0939ccd4
    resourceVersion: "23273"
    uid: f51d30c7-8366-408a-ade9-0367b1116f03
  spec:
    sourcePod: network-check-source-685456655f-rz5zs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:32:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 852.652µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:32:00Z"
    - latency: 1.477585ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:31:00Z"
    - latency: 1.517589ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:30:00Z"
    - latency: 1.073758ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:29:00Z"
    - latency: 2.549327ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:28:00Z"
    - latency: 1.700726ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:27:00Z"
    - latency: 1.0386ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:26:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:24:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-110-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-110.ec2.internal
      uid: 8916d1bc-d424-481f-9c04-b59f0939ccd4
    resourceVersion: "22591"
    uid: 4edf35c5-058b-48dc-911b-4dc6483eb001
  spec:
    sourcePod: network-check-source-685456655f-rz5zs
    targetEndpoint: a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:31:00Z"
      message: 'load-balancer-api-external: tcp connection to a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.61374ms
      message: 'load-balancer-api-external: tcp connection to a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:31:00Z"
    - latency: 9.527907ms
      message: 'load-balancer-api-external: resolved host name a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:31:00Z"
    - latency: 4.309453ms
      message: 'load-balancer-api-external: tcp connection to a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:30:00Z"
    - latency: 12.015911ms
      message: 'load-balancer-api-external: resolved host name a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:30:00Z"
    - latency: 4.972962ms
      message: 'load-balancer-api-external: tcp connection to a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:29:00Z"
    - latency: 7.078422ms
      message: 'load-balancer-api-external: resolved host name a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:29:00Z"
    - latency: 6.293533ms
      message: 'load-balancer-api-external: tcp connection to a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:28:00Z"
    - latency: 33.46268ms
      message: 'load-balancer-api-external: resolved host name a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:28:00Z"
    - latency: 4.865902ms
      message: 'load-balancer-api-external: tcp connection to a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:27:00Z"
    - latency: 12.395827ms
      message: 'load-balancer-api-external: resolved host name a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:27:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:24:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-110-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-110.ec2.internal
      uid: 8916d1bc-d424-481f-9c04-b59f0939ccd4
    resourceVersion: "22590"
    uid: 52a88f60-d05b-404d-83bc-8ec376f0fdd1
  spec:
    sourcePod: network-check-source-685456655f-rz5zs
    targetEndpoint: a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:31:00Z"
      message: 'load-balancer-api-internal: tcp connection to a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.327238ms
      message: 'load-balancer-api-internal: tcp connection to a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:31:00Z"
    - latency: 9.451691ms
      message: 'load-balancer-api-internal: resolved host name a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:31:00Z"
    - latency: 4.982392ms
      message: 'load-balancer-api-internal: tcp connection to a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:30:00Z"
    - latency: 11.888007ms
      message: 'load-balancer-api-internal: resolved host name a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:30:00Z"
    - latency: 3.99319ms
      message: 'load-balancer-api-internal: tcp connection to a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:29:00Z"
    - latency: 7.057669ms
      message: 'load-balancer-api-internal: resolved host name a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:29:00Z"
    - latency: 5.750796ms
      message: 'load-balancer-api-internal: tcp connection to a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:28:00Z"
    - latency: 33.408516ms
      message: 'load-balancer-api-internal: resolved host name a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:28:00Z"
    - latency: 4.823219ms
      message: 'load-balancer-api-internal: tcp connection to a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:27:00Z"
    - latency: 12.266801ms
      message: 'load-balancer-api-internal: resolved host name a265963c4f20a47a0b673d8908b1bf3d-fdb7ae36278be4c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:27:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:24:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-110-to-network-check-target-ip-10-0-130-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-110.ec2.internal
      uid: 8916d1bc-d424-481f-9c04-b59f0939ccd4
    resourceVersion: "23271"
    uid: 8fe8ca7b-dd00-4e98-8f28-fc4834806fe7
  spec:
    sourcePod: network-check-source-685456655f-rz5zs
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:32:00Z"
      message: 'network-check-target-ip-10-0-130-44: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.552437ms
      message: 'network-check-target-ip-10-0-130-44: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:32:00Z"
    - latency: 3.118356ms
      message: 'network-check-target-ip-10-0-130-44: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:31:00Z"
    - latency: 2.250658ms
      message: 'network-check-target-ip-10-0-130-44: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:30:00Z"
    - latency: 2.720838ms
      message: 'network-check-target-ip-10-0-130-44: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:29:00Z"
    - latency: 14.432446ms
      message: 'network-check-target-ip-10-0-130-44: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:28:00Z"
    - latency: 3.098785ms
      message: 'network-check-target-ip-10-0-130-44: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:27:00Z"
    - latency: 4.471543ms
      message: 'network-check-target-ip-10-0-130-44: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:26:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:24:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-110-to-network-check-target-ip-10-0-141-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-110.ec2.internal
      uid: 8916d1bc-d424-481f-9c04-b59f0939ccd4
    resourceVersion: "23270"
    uid: 5b7f97b7-c74a-4c5c-86c9-2bd5e48de674
  spec:
    sourcePod: network-check-source-685456655f-rz5zs
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:32:00Z"
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.269564ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:32:00Z"
    - latency: 2.195151ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:31:00Z"
    - latency: 1.846653ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:30:00Z"
    - latency: 2.148225ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:29:00Z"
    - latency: 2.883324ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:28:00Z"
    - latency: 2.189579ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:27:00Z"
    - latency: 2.372655ms
      message: 'network-check-target-ip-10-0-141-33: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:26:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:24:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-110-to-network-check-target-ip-10-0-142-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-110.ec2.internal
      uid: 8916d1bc-d424-481f-9c04-b59f0939ccd4
    resourceVersion: "23269"
    uid: f510d820-73a7-4390-8e4f-f15481555240
  spec:
    sourcePod: network-check-source-685456655f-rz5zs
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:32:00Z"
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.196433ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:32:00Z"
    - latency: 2.613771ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:31:00Z"
    - latency: 1.035ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:30:00Z"
    - latency: 1.575345ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:29:00Z"
    - latency: 2.080088ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:28:00Z"
    - latency: 2.172412ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:27:00Z"
    - latency: 1.588308ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:26:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:24:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-110-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-110.ec2.internal
      uid: 8916d1bc-d424-481f-9c04-b59f0939ccd4
    resourceVersion: "22589"
    uid: 967511e1-b4b4-4418-97fb-656c449612e3
  spec:
    sourcePod: network-check-source-685456655f-rz5zs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:31:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.014603ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:31:00Z"
    - latency: 3.470078ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:31:00Z"
    - latency: 998.271µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:30:00Z"
    - latency: 2.250483ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:30:00Z"
    - latency: 1.310939ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:29:00Z"
    - latency: 2.057741ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:29:00Z"
    - latency: 4.067628ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:28:00Z"
    - latency: 14.269968ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:28:00Z"
    - latency: 1.353893ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:27:00Z"
    - latency: 2.642359ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:27:00Z"
kind: List
metadata:
  resourceVersion: ""