apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:26:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-195-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-195.ec2.internal
      uid: a8d71553-304f-4970-b57c-4a1292c0b5d3
    resourceVersion: "15157"
    uid: 5281517b-bcbe-45a6-9814-cddc1f57fed4
  spec:
    sourcePod: network-check-source-6f8b768455-7btmh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:33:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.792187ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:33:45Z"
    - latency: 1.028464ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:32:45Z"
    - latency: 829.448µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:31:45Z"
    - latency: 970.319µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:30:45Z"
    - latency: 1.165889ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:29:45Z"
    - latency: 862.689µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:28:45Z"
    - latency: 870.348µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:27:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:26:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-195-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-195.ec2.internal
      uid: a8d71553-304f-4970-b57c-4a1292c0b5d3
    resourceVersion: "14691"
    uid: 5ab6ec13-1d87-4ed0-ade6-447db345f062
  spec:
    sourcePod: network-check-source-6f8b768455-7btmh
    targetEndpoint: acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:32:45Z"
      message: 'load-balancer-api-external: tcp connection to acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.817915ms
      message: 'load-balancer-api-external: tcp connection to acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:32:45Z"
    - latency: 8.301697ms
      message: 'load-balancer-api-external: resolved host name acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:32:45Z"
    - latency: 4.755939ms
      message: 'load-balancer-api-external: tcp connection to acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:31:45Z"
    - latency: 10.171955ms
      message: 'load-balancer-api-external: resolved host name acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:31:45Z"
    - latency: 5.629839ms
      message: 'load-balancer-api-external: tcp connection to acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:30:45Z"
    - latency: 8.739657ms
      message: 'load-balancer-api-external: resolved host name acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:30:45Z"
    - latency: 4.466935ms
      message: 'load-balancer-api-external: tcp connection to acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:29:45Z"
    - latency: 8.098718ms
      message: 'load-balancer-api-external: resolved host name acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:29:45Z"
    - latency: 5.204935ms
      message: 'load-balancer-api-external: tcp connection to acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:28:45Z"
    - latency: 7.06244ms
      message: 'load-balancer-api-external: resolved host name acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:28:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:26:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-195-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-195.ec2.internal
      uid: a8d71553-304f-4970-b57c-4a1292c0b5d3
    resourceVersion: "14690"
    uid: b86f29b2-8dd3-49ba-89a9-8294915e0f69
  spec:
    sourcePod: network-check-source-6f8b768455-7btmh
    targetEndpoint: acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:32:45Z"
      message: 'load-balancer-api-internal: tcp connection to acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.489023ms
      message: 'load-balancer-api-internal: tcp connection to acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:32:45Z"
    - latency: 8.380771ms
      message: 'load-balancer-api-internal: resolved host name acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:32:45Z"
    - latency: 4.747644ms
      message: 'load-balancer-api-internal: tcp connection to acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:31:45Z"
    - latency: 10.256447ms
      message: 'load-balancer-api-internal: resolved host name acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:31:45Z"
    - latency: 5.052615ms
      message: 'load-balancer-api-internal: tcp connection to acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:30:45Z"
    - latency: 8.828648ms
      message: 'load-balancer-api-internal: resolved host name acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:30:45Z"
    - latency: 4.605445ms
      message: 'load-balancer-api-internal: tcp connection to acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:29:45Z"
    - latency: 8.010704ms
      message: 'load-balancer-api-internal: resolved host name acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:29:45Z"
    - latency: 5.214411ms
      message: 'load-balancer-api-internal: tcp connection to acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:28:45Z"
    - latency: 7.09578ms
      message: 'load-balancer-api-internal: resolved host name acdc0ee6b58ec4185967aca33f984b19-8e6fcb33cbbce9cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:28:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:26:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-195-to-network-check-target-ip-10-0-134-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-195.ec2.internal
      uid: a8d71553-304f-4970-b57c-4a1292c0b5d3
    resourceVersion: "15155"
    uid: eb077136-2d00-4087-9fbf-e4258ded7e12
  spec:
    sourcePod: network-check-source-6f8b768455-7btmh
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:33:45Z"
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.002557ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:33:45Z"
    - latency: 1.885245ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:32:45Z"
    - latency: 1.974265ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:31:45Z"
    - latency: 1.850273ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:30:45Z"
    - latency: 1.834564ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:29:45Z"
    - latency: 1.948666ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:28:45Z"
    - latency: 2.626255ms
      message: 'network-check-target-ip-10-0-134-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:27:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:26:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-195-to-network-check-target-ip-10-0-134-195
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-195.ec2.internal
      uid: a8d71553-304f-4970-b57c-4a1292c0b5d3
    resourceVersion: "15154"
    uid: 39e7f4f7-990b-4420-8221-666b28dcb311
  spec:
    sourcePod: network-check-source-6f8b768455-7btmh
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:33:45Z"
      message: 'network-check-target-ip-10-0-134-195: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.842µs
      message: 'network-check-target-ip-10-0-134-195: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:33:45Z"
    - latency: 1.404292ms
      message: 'network-check-target-ip-10-0-134-195: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:32:45Z"
    - latency: 720.361µs
      message: 'network-check-target-ip-10-0-134-195: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:31:45Z"
    - latency: 794.922µs
      message: 'network-check-target-ip-10-0-134-195: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:30:45Z"
    - latency: 800.522µs
      message: 'network-check-target-ip-10-0-134-195: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:29:45Z"
    - latency: 843.316µs
      message: 'network-check-target-ip-10-0-134-195: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:28:45Z"
    - latency: 1.486911ms
      message: 'network-check-target-ip-10-0-134-195: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:27:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:26:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-195-to-network-check-target-ip-10-0-140-27
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-195.ec2.internal
      uid: a8d71553-304f-4970-b57c-4a1292c0b5d3
    resourceVersion: "15156"
    uid: a68be3f8-e54e-4975-b333-6ac2124960b7
  spec:
    sourcePod: network-check-source-6f8b768455-7btmh
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:33:45Z"
      message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.515887ms
      message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:33:45Z"
    - latency: 2.179101ms
      message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:32:45Z"
    - latency: 2.193858ms
      message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:31:45Z"
    - latency: 2.259044ms
      message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:30:45Z"
    - latency: 2.163763ms
      message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:29:45Z"
    - latency: 2.067497ms
      message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:28:45Z"
    - latency: 2.953404ms
      message: 'network-check-target-ip-10-0-140-27: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:27:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T08:26:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-195-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-195.ec2.internal
      uid: a8d71553-304f-4970-b57c-4a1292c0b5d3
    resourceVersion: "14689"
    uid: 216d4602-401d-4734-b30a-cf085df2c34b
  spec:
    sourcePod: network-check-source-6f8b768455-7btmh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T08:32:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.292277ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:32:45Z"
    - latency: 1.743266ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:32:45Z"
    - latency: 1.022146ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:31:45Z"
    - latency: 1.518369ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:31:45Z"
    - latency: 927.646µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:30:45Z"
    - latency: 2.042192ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:30:45Z"
    - latency: 1.274353ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:29:45Z"
    - latency: 1.653349ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:29:45Z"
    - latency: 946.994µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T08:28:45Z"
    - latency: 1.558953ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T08:28:45Z"
kind: List
metadata:
  resourceVersion: ""