apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T11:06:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-204-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-204.us-east-2.compute.internal
      uid: 3bdc29a7-291d-443e-b9dc-263dc9aa6e82
    resourceVersion: "20385"
    uid: 24a499ca-a4bd-4e07-b7ad-c99e3ecdc0f6
  spec:
    sourcePod: network-check-source-6f78d59f99-llgfh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T11:13:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.155884ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:13:06Z"
    - latency: 1.53614ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:12:06Z"
    - latency: 1.764764ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:11:06Z"
    - latency: 1.109545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:10:06Z"
    - latency: 954.271µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:09:06Z"
    - latency: 1.083929ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:08:06Z"
    - latency: 1.328568ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:07:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T11:06:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-204-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-204.us-east-2.compute.internal
      uid: 3bdc29a7-291d-443e-b9dc-263dc9aa6e82
    resourceVersion: "23341"
    uid: 6ee10189-c7a6-4c8a-82a5-9af76348a212
  spec:
    sourcePod: network-check-source-6f78d59f99-llgfh
    targetEndpoint: aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T11:12:06Z"
      message: 'load-balancer-api-external: tcp connection to aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.180651ms
      message: 'load-balancer-api-external: tcp connection to aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:18:06Z"
    - latency: 8.6854ms
      message: 'load-balancer-api-external: resolved host name aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T11:18:06Z"
    - latency: 4.701711ms
      message: 'load-balancer-api-external: tcp connection to aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:17:06Z"
    - latency: 7.686108ms
      message: 'load-balancer-api-external: resolved host name aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T11:17:06Z"
    - latency: 5.335172ms
      message: 'load-balancer-api-external: tcp connection to aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:16:06Z"
    - latency: 8.335731ms
      message: 'load-balancer-api-external: resolved host name aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T11:16:06Z"
    - latency: 5.614995ms
      message: 'load-balancer-api-external: tcp connection to aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:15:06Z"
    - latency: 7.426042ms
      message: 'load-balancer-api-external: resolved host name aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T11:15:06Z"
    - latency: 14.104953ms
      message: 'load-balancer-api-external: tcp connection to aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:14:06Z"
    - latency: 6.871889ms
      message: 'load-balancer-api-external: resolved host name aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T11:14:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T11:06:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-204-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-204.us-east-2.compute.internal
      uid: 3bdc29a7-291d-443e-b9dc-263dc9aa6e82
    resourceVersion: "23342"
    uid: 4e2d7823-d361-45ae-8f71-466eefce85b0
  spec:
    sourcePod: network-check-source-6f78d59f99-llgfh
    targetEndpoint: aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T11:12:06Z"
      message: 'load-balancer-api-internal: tcp connection to aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.171472ms
      message: 'load-balancer-api-internal: tcp connection to aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:18:06Z"
    - latency: 8.74992ms
      message: 'load-balancer-api-internal: resolved host name aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T11:18:06Z"
    - latency: 4.718189ms
      message: 'load-balancer-api-internal: tcp connection to aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:17:06Z"
    - latency: 7.777098ms
      message: 'load-balancer-api-internal: resolved host name aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T11:17:06Z"
    - latency: 5.351551ms
      message: 'load-balancer-api-internal: tcp connection to aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:16:06Z"
    - latency: 8.410909ms
      message: 'load-balancer-api-internal: resolved host name aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T11:16:06Z"
    - latency: 6.505756ms
      message: 'load-balancer-api-internal: tcp connection to aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:15:06Z"
    - latency: 7.539ms
      message: 'load-balancer-api-internal: resolved host name aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T11:15:06Z"
    - latency: 5.338679ms
      message: 'load-balancer-api-internal: tcp connection to aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:14:06Z"
    - latency: 6.929723ms
      message: 'load-balancer-api-internal: resolved host name aeff7bc5420bc488b8bf15a71c041cbf-128ee949b55b4e0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T11:14:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T11:06:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-204-to-network-check-target-ip-10-0-129-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-204.us-east-2.compute.internal
      uid: 3bdc29a7-291d-443e-b9dc-263dc9aa6e82
    resourceVersion: "20382"
    uid: bd867c93-25f6-40ac-8522-4b0e259dedb9
  spec:
    sourcePod: network-check-source-6f78d59f99-llgfh
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T11:13:06Z"
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.017466ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:13:06Z"
    - latency: 871.932µs
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:12:06Z"
    - latency: 1.822643ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:11:06Z"
    - latency: 1.746403ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:10:06Z"
    - latency: 1.12461ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:09:06Z"
    - latency: 964.895µs
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:08:06Z"
    - latency: 2.188388ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:07:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T11:06:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-204-to-network-check-target-ip-10-0-134-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-204.us-east-2.compute.internal
      uid: 3bdc29a7-291d-443e-b9dc-263dc9aa6e82
    resourceVersion: "20384"
    uid: 637ac3d7-9d86-47a0-800a-0b859755e746
  spec:
    sourcePod: network-check-source-6f78d59f99-llgfh
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T11:13:06Z"
      message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.938658ms
      message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:13:06Z"
    - latency: 2.188552ms
      message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:12:06Z"
    - latency: 2.666065ms
      message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:11:06Z"
    - latency: 2.150962ms
      message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:10:06Z"
    - latency: 2.423252ms
      message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:09:06Z"
    - latency: 2.231775ms
      message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:08:06Z"
    - latency: 2.120588ms
      message: 'network-check-target-ip-10-0-134-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:07:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T11:06:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-204-to-network-check-target-ip-10-0-138-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-204.us-east-2.compute.internal
      uid: 3bdc29a7-291d-443e-b9dc-263dc9aa6e82
    resourceVersion: "20383"
    uid: 049006ba-47e0-4ba2-8da7-aeffe3da4894
  spec:
    sourcePod: network-check-source-6f78d59f99-llgfh
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T11:13:06Z"
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.505408ms
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:13:06Z"
    - latency: 2.549972ms
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:12:06Z"
    - latency: 3.505401ms
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:11:06Z"
    - latency: 2.235758ms
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:10:06Z"
    - latency: 2.424939ms
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:09:06Z"
    - latency: 2.130265ms
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:08:06Z"
    - latency: 2.575273ms
      message: 'network-check-target-ip-10-0-138-114: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:07:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T11:06:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-204-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-204.us-east-2.compute.internal
      uid: 3bdc29a7-291d-443e-b9dc-263dc9aa6e82
    resourceVersion: "23340"
    uid: 0180122a-5406-40bc-88ab-8ff9ba6917f0
  spec:
    sourcePod: network-check-source-6f78d59f99-llgfh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T11:12:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.095371ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:18:06Z"
    - latency: 2.623082ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T11:18:06Z"
    - latency: 741.139µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:17:06Z"
    - latency: 2.172574ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T11:17:06Z"
    - latency: 859.119µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:16:06Z"
    - latency: 2.021489ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T11:16:06Z"
    - latency: 1.328689ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:15:06Z"
    - latency: 1.672046ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T11:15:06Z"
    - latency: 956.681µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T11:14:06Z"
    - latency: 2.482928ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T11:14:06Z"
kind: List
metadata:
  resourceVersion: ""