apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:56:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-57-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-57.ec2.internal
      uid: 94e21299-b4b4-4a7a-93fc-a8968b717cbd
    resourceVersion: "15217"
    uid: 3ac5a8be-bf3c-4506-b179-6622ad68fc76
  spec:
    sourcePod: network-check-source-7cbc45fddc-qkbr6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:03:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.364412ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:03:39Z"
    - latency: 915.704µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:02:39Z"
    - latency: 913.63µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:01:39Z"
    - latency: 966.909µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:00:39Z"
    - latency: 892.218µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:59:39Z"
    - latency: 1.190761ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:58:39Z"
    - latency: 1.066411ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:57:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:56:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-57-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-57.ec2.internal
      uid: 94e21299-b4b4-4a7a-93fc-a8968b717cbd
    resourceVersion: "18155"
    uid: 9aba7f93-4b69-4c5c-9cad-12d37a44aee4
  spec:
    sourcePod: network-check-source-7cbc45fddc-qkbr6
    targetEndpoint: ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:02:39Z"
      message: 'load-balancer-api-external: tcp connection to ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.945742ms
      message: 'load-balancer-api-external: tcp connection to ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:08:39Z"
    - latency: 8.510598ms
      message: 'load-balancer-api-external: resolved host name ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:08:39Z"
    - latency: 5.483493ms
      message: 'load-balancer-api-external: tcp connection to ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:07:39Z"
    - latency: 13.264762ms
      message: 'load-balancer-api-external: resolved host name ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:07:39Z"
    - latency: 4.5115ms
      message: 'load-balancer-api-external: tcp connection to ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:06:39Z"
    - latency: 8.719102ms
      message: 'load-balancer-api-external: resolved host name ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:06:39Z"
    - latency: 4.848435ms
      message: 'load-balancer-api-external: tcp connection to ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:05:39Z"
    - latency: 9.519942ms
      message: 'load-balancer-api-external: resolved host name ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:05:39Z"
    - latency: 3.868954ms
      message: 'load-balancer-api-external: tcp connection to ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:04:39Z"
    - latency: 10.224718ms
      message: 'load-balancer-api-external: resolved host name ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:04:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:56:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-57-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-57.ec2.internal
      uid: 94e21299-b4b4-4a7a-93fc-a8968b717cbd
    resourceVersion: "18156"
    uid: 4253d4f3-3c11-4f37-b931-f295e8c7220c
  spec:
    sourcePod: network-check-source-7cbc45fddc-qkbr6
    targetEndpoint: ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:02:39Z"
      message: 'load-balancer-api-internal: tcp connection to ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.683226ms
      message: 'load-balancer-api-internal: tcp connection to ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:08:39Z"
    - latency: 8.423353ms
      message: 'load-balancer-api-internal: resolved host name ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:08:39Z"
    - latency: 5.452533ms
      message: 'load-balancer-api-internal: tcp connection to ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:07:39Z"
    - latency: 13.37055ms
      message: 'load-balancer-api-internal: resolved host name ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:07:39Z"
    - latency: 4.494785ms
      message: 'load-balancer-api-internal: tcp connection to ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:06:39Z"
    - latency: 8.627998ms
      message: 'load-balancer-api-internal: resolved host name ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:06:39Z"
    - latency: 4.904868ms
      message: 'load-balancer-api-internal: tcp connection to ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:05:39Z"
    - latency: 9.461593ms
      message: 'load-balancer-api-internal: resolved host name ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:05:39Z"
    - latency: 4.397759ms
      message: 'load-balancer-api-internal: tcp connection to ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:04:39Z"
    - latency: 10.261261ms
      message: 'load-balancer-api-internal: resolved host name ad04c5f991a5d4bf7a02741850821aa5-f7da1d18a70d1ff4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:04:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:56:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-57-to-network-check-target-ip-10-0-134-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-57.ec2.internal
      uid: 94e21299-b4b4-4a7a-93fc-a8968b717cbd
    resourceVersion: "15216"
    uid: 32064da1-fd9c-4b7f-9317-5f4fe8dbda6e
  spec:
    sourcePod: network-check-source-7cbc45fddc-qkbr6
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:03:39Z"
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.498826ms
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:03:39Z"
    - latency: 2.118321ms
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:02:39Z"
    - latency: 1.935066ms
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:01:39Z"
    - latency: 2.163171ms
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:00:39Z"
    - latency: 2.049308ms
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:59:39Z"
    - latency: 2.230092ms
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:58:39Z"
    - latency: 2.557565ms
      message: 'network-check-target-ip-10-0-134-159: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:57:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:56:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-57-to-network-check-target-ip-10-0-134-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-57.ec2.internal
      uid: 94e21299-b4b4-4a7a-93fc-a8968b717cbd
    resourceVersion: "15214"
    uid: f5f952ce-2bd3-4cd7-8beb-53d2ce1788e9
  spec:
    sourcePod: network-check-source-7cbc45fddc-qkbr6
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:03:39Z"
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.275136ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:03:39Z"
    - latency: 1.284878ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:02:39Z"
    - latency: 1.092812ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:01:39Z"
    - latency: 1.289486ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:00:39Z"
    - latency: 761.79µs
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:59:39Z"
    - latency: 911.923µs
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:58:39Z"
    - latency: 1.268815ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:57:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:56:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-57-to-network-check-target-ip-10-0-137-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-57.ec2.internal
      uid: 94e21299-b4b4-4a7a-93fc-a8968b717cbd
    resourceVersion: "15215"
    uid: 3a9f552e-653f-45c6-9b26-f29413541cdb
  spec:
    sourcePod: network-check-source-7cbc45fddc-qkbr6
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:03:39Z"
      message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.203778ms
      message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:03:39Z"
    - latency: 1.873749ms
      message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:02:39Z"
    - latency: 1.851504ms
      message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:01:39Z"
    - latency: 2.050146ms
      message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:00:39Z"
    - latency: 1.873461ms
      message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:59:39Z"
    - latency: 1.912679ms
      message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:58:39Z"
    - latency: 1.950961ms
      message: 'network-check-target-ip-10-0-137-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T08:57:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T08:56:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-57-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-57.ec2.internal
      uid: 94e21299-b4b4-4a7a-93fc-a8968b717cbd
    resourceVersion: "18154"
    uid: 3bb1daf6-5ccb-4fef-b3ad-039809c2b1eb
  spec:
    sourcePod: network-check-source-7cbc45fddc-qkbr6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T09:02:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 879.395µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:08:39Z"
    - latency: 1.845713ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:08:39Z"
    - latency: 1.325094ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:07:39Z"
    - latency: 1.92486ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:07:39Z"
    - latency: 965.178µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:06:39Z"
    - latency: 1.69053ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:06:39Z"
    - latency: 1.033471ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:05:39Z"
    - latency: 1.762583ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:05:39Z"
    - latency: 986.967µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T09:04:39Z"
    - latency: 1.737166ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T09:04:39Z"
kind: List
metadata:
  resourceVersion: ""