apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:33:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-52-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-52.ec2.internal
      uid: 5fb6274d-2d22-4118-a7af-b6930f196867
    resourceVersion: "14744"
    uid: fd5f4f0e-a8e3-4366-bcb5-e10ffee69761
  spec:
    sourcePod: network-check-source-869dcfcdcd-54vpp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:40:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 948.887µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:40:48Z"
    - latency: 939.459µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:39:48Z"
    - latency: 1.062009ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:38:48Z"
    - latency: 1.041431ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:37:48Z"
    - latency: 1.10982ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:36:48Z"
    - latency: 1.100444ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:35:48Z"
    - latency: 1.184838ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:34:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:33:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-52-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-52.ec2.internal
      uid: 5fb6274d-2d22-4118-a7af-b6930f196867
    resourceVersion: "14314"
    uid: 592c038e-8a25-43c9-a7a1-5f9241b014c7
  spec:
    sourcePod: network-check-source-869dcfcdcd-54vpp
    targetEndpoint: a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:39:48Z"
      message: 'load-balancer-api-external: tcp connection to a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.575279ms
      message: 'load-balancer-api-external: tcp connection to a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:39:48Z"
    - latency: 8.518319ms
      message: 'load-balancer-api-external: resolved host name a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:39:48Z"
    - latency: 4.554859ms
      message: 'load-balancer-api-external: tcp connection to a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:38:48Z"
    - latency: 8.320634ms
      message: 'load-balancer-api-external: resolved host name a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:38:48Z"
    - latency: 5.232434ms
      message: 'load-balancer-api-external: tcp connection to a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:37:48Z"
    - latency: 7.457767ms
      message: 'load-balancer-api-external: resolved host name a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:37:48Z"
    - latency: 5.334557ms
      message: 'load-balancer-api-external: tcp connection to a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:36:48Z"
    - latency: 10.307598ms
      message: 'load-balancer-api-external: resolved host name a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:36:48Z"
    - latency: 4.4696ms
      message: 'load-balancer-api-external: tcp connection to a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:35:48Z"
    - latency: 8.029211ms
      message: 'load-balancer-api-external: resolved host name a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:35:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:33:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-52-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-52.ec2.internal
      uid: 5fb6274d-2d22-4118-a7af-b6930f196867
    resourceVersion: "14313"
    uid: f522fb66-f02f-491e-b496-869b0bbe2a68
  spec:
    sourcePod: network-check-source-869dcfcdcd-54vpp
    targetEndpoint: a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:39:48Z"
      message: 'load-balancer-api-internal: tcp connection to a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.565474ms
      message: 'load-balancer-api-internal: tcp connection to a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:39:48Z"
    - latency: 8.480503ms
      message: 'load-balancer-api-internal: resolved host name a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:39:48Z"
    - latency: 9.046116ms
      message: 'load-balancer-api-internal: tcp connection to a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:38:48Z"
    - latency: 8.281768ms
      message: 'load-balancer-api-internal: resolved host name a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:38:48Z"
    - latency: 5.468827ms
      message: 'load-balancer-api-internal: tcp connection to a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:37:48Z"
    - latency: 7.500697ms
      message: 'load-balancer-api-internal: resolved host name a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:37:48Z"
    - latency: 4.822667ms
      message: 'load-balancer-api-internal: tcp connection to a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:36:48Z"
    - latency: 10.331238ms
      message: 'load-balancer-api-internal: resolved host name a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:36:48Z"
    - latency: 3.675897ms
      message: 'load-balancer-api-internal: tcp connection to a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:35:48Z"
    - latency: 7.96951ms
      message: 'load-balancer-api-internal: resolved host name a7e66a272220b4612bcc599c508d8158-e7786f322ab7f408.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:35:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:33:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-52-to-network-check-target-ip-10-0-133-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-52.ec2.internal
      uid: 5fb6274d-2d22-4118-a7af-b6930f196867
    resourceVersion: "14742"
    uid: cd2207aa-0163-4c75-b4ef-eabc35ace61f
  spec:
    sourcePod: network-check-source-869dcfcdcd-54vpp
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:40:48Z"
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.182714ms
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:40:48Z"
    - latency: 2.122889ms
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:39:48Z"
    - latency: 2.085579ms
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:38:48Z"
    - latency: 1.975106ms
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:37:48Z"
    - latency: 2.148905ms
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:36:48Z"
    - latency: 2.150347ms
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:35:48Z"
    - latency: 2.356066ms
      message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:34:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:33:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-52-to-network-check-target-ip-10-0-137-251
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-52.ec2.internal
      uid: 5fb6274d-2d22-4118-a7af-b6930f196867
    resourceVersion: "14743"
    uid: d18e1b40-8472-45c5-b216-a93767368e3f
  spec:
    sourcePod: network-check-source-869dcfcdcd-54vpp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:40:48Z"
      message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.082917ms
      message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:40:48Z"
    - latency: 2.099259ms
      message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:39:48Z"
    - latency: 1.947869ms
      message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:38:48Z"
    - latency: 1.808062ms
      message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:37:48Z"
    - latency: 1.769637ms
      message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:36:48Z"
    - latency: 1.910246ms
      message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:35:48Z"
    - latency: 2.320227ms
      message: 'network-check-target-ip-10-0-137-251: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:34:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:33:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-52-to-network-check-target-ip-10-0-142-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-52.ec2.internal
      uid: 5fb6274d-2d22-4118-a7af-b6930f196867
    resourceVersion: "14741"
    uid: 4bc7c716-72e8-4c9e-8058-4959a3e5be5c
  spec:
    sourcePod: network-check-source-869dcfcdcd-54vpp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:40:48Z"
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.030629ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:40:48Z"
    - latency: 1.108755ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:39:48Z"
    - latency: 815.793µs
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:38:48Z"
    - latency: 1.053573ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:37:48Z"
    - latency: 728.734µs
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:36:48Z"
    - latency: 916.86µs
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:35:48Z"
    - latency: 1.430573ms
      message: 'network-check-target-ip-10-0-142-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:34:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:33:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-52-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-52.ec2.internal
      uid: 5fb6274d-2d22-4118-a7af-b6930f196867
    resourceVersion: "14312"
    uid: 964d248e-d854-49d9-adf6-f6f25121e10a
  spec:
    sourcePod: network-check-source-869dcfcdcd-54vpp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:39:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 837.341µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:39:48Z"
    - latency: 1.800707ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:39:48Z"
    - latency: 866.905µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:38:48Z"
    - latency: 2.022729ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:38:48Z"
    - latency: 1.068629ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:37:48Z"
    - latency: 1.713202ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:37:48Z"
    - latency: 1.109717ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:36:48Z"
    - latency: 1.805987ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:36:48Z"
    - latency: 866.383µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:35:48Z"
    - latency: 1.806391ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:35:48Z"
kind: List
metadata:
  resourceVersion: ""