apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:00:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-172-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-172.ec2.internal
      uid: 1b85024f-c7ea-422d-90fe-063a83a03a8e
    resourceVersion: "15224"
    uid: 4b645d0a-3c86-4b73-95d3-bef11d1dc27f
  spec:
    sourcePod: network-check-source-7f44b6dd87-bksb8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:08:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 857.452µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:08:00Z"
    - latency: 1.033538ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:07:00Z"
    - latency: 930.707µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:06:00Z"
    - latency: 1.123259ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:05:00Z"
    - latency: 1.29735ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:04:00Z"
    - latency: 993.993µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:03:00Z"
    - latency: 922.197µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:02:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:00:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-172-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-172.ec2.internal
      uid: 1b85024f-c7ea-422d-90fe-063a83a03a8e
    resourceVersion: "14890"
    uid: 2d3721f8-ae98-4f43-ad5d-0557e6d798b6
  spec:
    sourcePod: network-check-source-7f44b6dd87-bksb8
    targetEndpoint: a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:07:00Z"
      message: 'load-balancer-api-external: tcp connection to a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.215147ms
      message: 'load-balancer-api-external: tcp connection to a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:07:00Z"
    - latency: 7.481287ms
      message: 'load-balancer-api-external: resolved host name a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:07:00Z"
    - latency: 5.777152ms
      message: 'load-balancer-api-external: tcp connection to a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:06:00Z"
    - latency: 9.193882ms
      message: 'load-balancer-api-external: resolved host name a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:06:00Z"
    - latency: 4.453429ms
      message: 'load-balancer-api-external: tcp connection to a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:05:00Z"
    - latency: 7.362874ms
      message: 'load-balancer-api-external: resolved host name a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:05:00Z"
    - latency: 4.098688ms
      message: 'load-balancer-api-external: tcp connection to a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:04:00Z"
    - latency: 9.410958ms
      message: 'load-balancer-api-external: resolved host name a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:04:00Z"
    - latency: 4.757787ms
      message: 'load-balancer-api-external: tcp connection to a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:03:00Z"
    - latency: 7.320625ms
      message: 'load-balancer-api-external: resolved host name a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:03:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:00:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-172-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-172.ec2.internal
      uid: 1b85024f-c7ea-422d-90fe-063a83a03a8e
    resourceVersion: "14889"
    uid: 69032471-750f-404f-8ff8-4ddff98c8a4a
  spec:
    sourcePod: network-check-source-7f44b6dd87-bksb8
    targetEndpoint: a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:07:00Z"
      message: 'load-balancer-api-internal: tcp connection to a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.810788ms
      message: 'load-balancer-api-internal: tcp connection to a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:07:00Z"
    - latency: 7.565531ms
      message: 'load-balancer-api-internal: resolved host name a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:07:00Z"
    - latency: 4.737071ms
      message: 'load-balancer-api-internal: tcp connection to a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:06:00Z"
    - latency: 9.125126ms
      message: 'load-balancer-api-internal: resolved host name a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:06:00Z"
    - latency: 4.477514ms
      message: 'load-balancer-api-internal: tcp connection to a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:05:00Z"
    - latency: 7.314064ms
      message: 'load-balancer-api-internal: resolved host name a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:05:00Z"
    - latency: 4.01764ms
      message: 'load-balancer-api-internal: tcp connection to a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:04:00Z"
    - latency: 9.419598ms
      message: 'load-balancer-api-internal: resolved host name a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:04:00Z"
    - latency: 4.773203ms
      message: 'load-balancer-api-internal: tcp connection to a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:03:00Z"
    - latency: 7.28402ms
      message: 'load-balancer-api-internal: resolved host name a8e5f34d16bdc4476acc6299e7572bda-a20273b2ff6a0b70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:03:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:00:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-172-to-network-check-target-ip-10-0-128-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-172.ec2.internal
      uid: 1b85024f-c7ea-422d-90fe-063a83a03a8e
    resourceVersion: "15221"
    uid: 2536b77e-82c6-4852-9b22-e84ea7c48b3e
  spec:
    sourcePod: network-check-source-7f44b6dd87-bksb8
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:08:00Z"
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 857.075µs
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:08:00Z"
    - latency: 744.158µs
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:07:00Z"
    - latency: 1.488762ms
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:06:00Z"
    - latency: 1.574051ms
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:05:00Z"
    - latency: 781.673µs
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:04:00Z"
    - latency: 853.731µs
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:03:00Z"
    - latency: 1.068922ms
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:02:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:00:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-172-to-network-check-target-ip-10-0-132-140
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-172.ec2.internal
      uid: 1b85024f-c7ea-422d-90fe-063a83a03a8e
    resourceVersion: "15223"
    uid: 73a3abdf-7225-40b6-84a5-dede42027b59
  spec:
    sourcePod: network-check-source-7f44b6dd87-bksb8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:08:00Z"
      message: 'network-check-target-ip-10-0-132-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.35111ms
      message: 'network-check-target-ip-10-0-132-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:08:00Z"
    - latency: 2.119057ms
      message: 'network-check-target-ip-10-0-132-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:07:00Z"
    - latency: 2.134026ms
      message: 'network-check-target-ip-10-0-132-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:06:00Z"
    - latency: 2.249226ms
      message: 'network-check-target-ip-10-0-132-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:05:00Z"
    - latency: 2.273586ms
      message: 'network-check-target-ip-10-0-132-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:04:00Z"
    - latency: 2.197171ms
      message: 'network-check-target-ip-10-0-132-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:03:00Z"
    - latency: 2.389962ms
      message: 'network-check-target-ip-10-0-132-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:02:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:00:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-172-to-network-check-target-ip-10-0-142-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-172.ec2.internal
      uid: 1b85024f-c7ea-422d-90fe-063a83a03a8e
    resourceVersion: "15222"
    uid: 9b052e12-0a5e-4cd1-afaa-7d3cdff37879
  spec:
    sourcePod: network-check-source-7f44b6dd87-bksb8
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:08:00Z"
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.175196ms
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:08:00Z"
    - latency: 1.932637ms
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:07:00Z"
    - latency: 2.251349ms
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:06:00Z"
    - latency: 2.2495ms
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:05:00Z"
    - latency: 2.166211ms
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:04:00Z"
    - latency: 2.241148ms
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:03:00Z"
    - latency: 2.390781ms
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:02:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:00:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-172-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-172.ec2.internal
      uid: 1b85024f-c7ea-422d-90fe-063a83a03a8e
    resourceVersion: "14888"
    uid: 786d38be-0470-43fd-84df-04ccbc3bb09b
  spec:
    sourcePod: network-check-source-7f44b6dd87-bksb8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:07:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.253511ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:07:00Z"
    - latency: 1.576745ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:07:00Z"
    - latency: 698.513µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:06:00Z"
    - latency: 2.333023ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:06:00Z"
    - latency: 743.053µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:05:00Z"
    - latency: 1.5959ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:05:00Z"
    - latency: 910.303µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:04:00Z"
    - latency: 1.584705ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:04:00Z"
    - latency: 773.721µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:03:00Z"
    - latency: 1.528369ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:03:00Z"
kind: List
metadata:
  resourceVersion: ""