apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:54:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-251-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-251.ec2.internal
      uid: d2944662-9936-4bf2-891c-c41017ad4450
    resourceVersion: "14904"
    uid: ac6b16df-a109-4ccd-91b7-609c22305bab
  spec:
    sourcePod: network-check-source-685456655f-97kw4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T09:01:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.309283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:01:17Z"
    - latency: 942.817µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:00:17Z"
    - latency: 837.576µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:59:17Z"
    - latency: 1.137963ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:58:17Z"
    - latency: 1.008643ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:57:17Z"
    - latency: 1.053581ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:56:17Z"
    - latency: 1.702131ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:55:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:54:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-251-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-251.ec2.internal
      uid: d2944662-9936-4bf2-891c-c41017ad4450
    resourceVersion: "14441"
    uid: 2e228a9d-57e2-4e28-91a6-44fd8da31d62
  spec:
    sourcePod: network-check-source-685456655f-97kw4
    targetEndpoint: a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T09:00:17Z"
      message: 'load-balancer-api-external: tcp connection to a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.556936ms
      message: 'load-balancer-api-external: tcp connection to a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:00:17Z"
    - latency: 6.457024ms
      message: 'load-balancer-api-external: resolved host name a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T09:00:17Z"
    - latency: 4.096962ms
      message: 'load-balancer-api-external: tcp connection to a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:59:17Z"
    - latency: 6.454951ms
      message: 'load-balancer-api-external: resolved host name a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:59:17Z"
    - latency: 5.80678ms
      message: 'load-balancer-api-external: tcp connection to a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:58:17Z"
    - latency: 6.06163ms
      message: 'load-balancer-api-external: resolved host name a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:58:17Z"
    - latency: 4.774025ms
      message: 'load-balancer-api-external: tcp connection to a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:57:17Z"
    - latency: 6.734397ms
      message: 'load-balancer-api-external: resolved host name a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:57:17Z"
    - latency: 4.274159ms
      message: 'load-balancer-api-external: tcp connection to a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:56:17Z"
    - latency: 6.089623ms
      message: 'load-balancer-api-external: resolved host name a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:56:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:54:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-251-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-251.ec2.internal
      uid: d2944662-9936-4bf2-891c-c41017ad4450
    resourceVersion: "14442"
    uid: 2f25644b-0e23-442c-a5e4-fb9bb19ad3de
  spec:
    sourcePod: network-check-source-685456655f-97kw4
    targetEndpoint: a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T09:00:17Z"
      message: 'load-balancer-api-internal: tcp connection to a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.369865ms
      message: 'load-balancer-api-internal: tcp connection to a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:00:17Z"
    - latency: 6.475053ms
      message: 'load-balancer-api-internal: resolved host name a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T09:00:17Z"
    - latency: 4.369256ms
      message: 'load-balancer-api-internal: tcp connection to a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:59:17Z"
    - latency: 6.433665ms
      message: 'load-balancer-api-internal: resolved host name a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:59:17Z"
    - latency: 5.762548ms
      message: 'load-balancer-api-internal: tcp connection to a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:58:17Z"
    - latency: 6.026481ms
      message: 'load-balancer-api-internal: resolved host name a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:58:17Z"
    - latency: 4.796689ms
      message: 'load-balancer-api-internal: tcp connection to a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:57:17Z"
    - latency: 6.680098ms
      message: 'load-balancer-api-internal: resolved host name a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:57:17Z"
    - latency: 4.294859ms
      message: 'load-balancer-api-internal: tcp connection to a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:56:17Z"
    - latency: 6.032932ms
      message: 'load-balancer-api-internal: resolved host name a14b25b7113d142e696295ee4d4612d7-7bd454d887aa8f4d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:56:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:54:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-251-to-network-check-target-ip-10-0-134-251
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-251.ec2.internal
      uid: d2944662-9936-4bf2-891c-c41017ad4450
    resourceVersion: "14900"
    uid: 339acb85-843e-4e19-ae91-bec843bb835e
  spec:
    sourcePod: network-check-source-685456655f-97kw4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T09:01:17Z"
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.63735ms
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:01:17Z"
    - latency: 917.743µs
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:00:17Z"
    - latency: 1.569679ms
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:59:17Z"
    - latency: 924.667µs
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:58:17Z"
    - latency: 858.536µs
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:57:17Z"
    - latency: 994.722µs
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:56:17Z"
    - latency: 1.628739ms
      message: 'network-check-target-ip-10-0-134-251: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:55:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:54:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-251-to-network-check-target-ip-10-0-140-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-251.ec2.internal
      uid: d2944662-9936-4bf2-891c-c41017ad4450
    resourceVersion: "14902"
    uid: e067516c-858e-4324-ba90-62390596a20e
  spec:
    sourcePod: network-check-source-685456655f-97kw4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T09:01:17Z"
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.505769ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:01:17Z"
    - latency: 2.514246ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:00:17Z"
    - latency: 2.225415ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:59:17Z"
    - latency: 2.099669ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:58:17Z"
    - latency: 2.212914ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:57:17Z"
    - latency: 2.386659ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:56:17Z"
    - latency: 2.721169ms
      message: 'network-check-target-ip-10-0-140-180: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:55:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:54:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-251-to-network-check-target-ip-10-0-142-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-251.ec2.internal
      uid: d2944662-9936-4bf2-891c-c41017ad4450
    resourceVersion: "14901"
    uid: 749ff94b-f130-4342-baa9-2e161bf87356
  spec:
    sourcePod: network-check-source-685456655f-97kw4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T09:01:17Z"
      message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.801358ms
      message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:01:17Z"
    - latency: 2.072509ms
      message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:00:17Z"
    - latency: 2.213379ms
      message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:59:17Z"
    - latency: 2.124574ms
      message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:58:17Z"
    - latency: 1.804184ms
      message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:57:17Z"
    - latency: 1.843352ms
      message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:56:17Z"
    - latency: 2.723605ms
      message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:55:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:54:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-251-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-251.ec2.internal
      uid: d2944662-9936-4bf2-891c-c41017ad4450
    resourceVersion: "14439"
    uid: bb62b2cd-6971-4a32-affd-8928e2a43f9b
  spec:
    sourcePod: network-check-source-685456655f-97kw4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T09:00:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 912.281µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:00:17Z"
    - latency: 1.716597ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T09:00:17Z"
    - latency: 793.358µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:59:17Z"
    - latency: 1.741606ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:59:17Z"
    - latency: 1.052412ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:58:17Z"
    - latency: 1.728372ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:58:17Z"
    - latency: 943.382µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:57:17Z"
    - latency: 1.73228ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:57:17Z"
    - latency: 864.751µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:56:17Z"
    - latency: 1.659461ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:56:17Z"
kind: List
metadata:
  resourceVersion: ""