apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T00:00:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-106-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-106.ec2.internal
      uid: 67989016-487e-42f7-9fa0-1669b7e00d8b
    resourceVersion: "15707"
    uid: 9fc5d850-1906-49e3-a1a9-d0d4cf553c31
  spec:
    sourcePod: network-check-source-dbd9cf844-s4xxl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T00:07:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.13633ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:07:48Z"
    - latency: 1.057489ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:06:48Z"
    - latency: 933.554µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:05:48Z"
    - latency: 1.217497ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:04:48Z"
    - latency: 1.011991ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:03:48Z"
    - latency: 1.299155ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:02:48Z"
    - latency: 816.815µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:01:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T00:00:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-106-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-106.ec2.internal
      uid: 67989016-487e-42f7-9fa0-1669b7e00d8b
    resourceVersion: "15378"
    uid: 8788432e-ec8d-4cd9-b2ca-46a33d7cbfb8
  spec:
    sourcePod: network-check-source-dbd9cf844-s4xxl
    targetEndpoint: a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T00:06:48Z"
      message: 'load-balancer-api-external: tcp connection to a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.052697ms
      message: 'load-balancer-api-external: tcp connection to a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:06:48Z"
    - latency: 6.355837ms
      message: 'load-balancer-api-external: resolved host name a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:06:48Z"
    - latency: 5.611128ms
      message: 'load-balancer-api-external: tcp connection to a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:05:48Z"
    - latency: 7.874722ms
      message: 'load-balancer-api-external: resolved host name a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:05:48Z"
    - latency: 4.5137ms
      message: 'load-balancer-api-external: tcp connection to a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:04:48Z"
    - latency: 6.246162ms
      message: 'load-balancer-api-external: resolved host name a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:04:48Z"
    - latency: 4.537028ms
      message: 'load-balancer-api-external: tcp connection to a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:03:48Z"
    - latency: 9.326005ms
      message: 'load-balancer-api-external: resolved host name a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:03:48Z"
    - latency: 4.254045ms
      message: 'load-balancer-api-external: tcp connection to a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:02:48Z"
    - latency: 6.023717ms
      message: 'load-balancer-api-external: resolved host name a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:02:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T00:00:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-106-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-106.ec2.internal
      uid: 67989016-487e-42f7-9fa0-1669b7e00d8b
    resourceVersion: "15377"
    uid: 2e011fc5-5017-4b8a-820a-959af8bc76f1
  spec:
    sourcePod: network-check-source-dbd9cf844-s4xxl
    targetEndpoint: a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T00:06:48Z"
      message: 'load-balancer-api-internal: tcp connection to a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.079902ms
      message: 'load-balancer-api-internal: tcp connection to a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:06:48Z"
    - latency: 6.227332ms
      message: 'load-balancer-api-internal: resolved host name a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:06:48Z"
    - latency: 5.371446ms
      message: 'load-balancer-api-internal: tcp connection to a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:05:48Z"
    - latency: 7.709755ms
      message: 'load-balancer-api-internal: resolved host name a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:05:48Z"
    - latency: 4.525727ms
      message: 'load-balancer-api-internal: tcp connection to a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:04:48Z"
    - latency: 6.320559ms
      message: 'load-balancer-api-internal: resolved host name a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:04:48Z"
    - latency: 4.475768ms
      message: 'load-balancer-api-internal: tcp connection to a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:03:48Z"
    - latency: 9.386169ms
      message: 'load-balancer-api-internal: resolved host name a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:03:48Z"
    - latency: 4.272176ms
      message: 'load-balancer-api-internal: tcp connection to a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:02:48Z"
    - latency: 5.904396ms
      message: 'load-balancer-api-internal: resolved host name a6a25f32dbdb9473495911699f98c52f-440bf4511dbb5b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:02:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T00:00:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-106-to-network-check-target-ip-10-0-128-106
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-106.ec2.internal
      uid: 67989016-487e-42f7-9fa0-1669b7e00d8b
    resourceVersion: "15702"
    uid: a5dd3e28-57a7-4af6-9e60-c54f4532e695
  spec:
    sourcePod: network-check-source-dbd9cf844-s4xxl
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T00:07:48Z"
      message: 'network-check-target-ip-10-0-128-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.676688ms
      message: 'network-check-target-ip-10-0-128-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:07:48Z"
    - latency: 1.372082ms
      message: 'network-check-target-ip-10-0-128-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:06:48Z"
    - latency: 932.792µs
      message: 'network-check-target-ip-10-0-128-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:05:48Z"
    - latency: 957.607µs
      message: 'network-check-target-ip-10-0-128-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:04:48Z"
    - latency: 902.136µs
      message: 'network-check-target-ip-10-0-128-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:03:48Z"
    - latency: 1.254903ms
      message: 'network-check-target-ip-10-0-128-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:02:48Z"
    - latency: 1.092849ms
      message: 'network-check-target-ip-10-0-128-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:01:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T00:00:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-106-to-network-check-target-ip-10-0-130-131
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-106.ec2.internal
      uid: 67989016-487e-42f7-9fa0-1669b7e00d8b
    resourceVersion: "15704"
    uid: 12418116-1ea9-4eec-817b-8eb934d5bc43
  spec:
    sourcePod: network-check-source-dbd9cf844-s4xxl
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T00:07:48Z"
      message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.831519ms
      message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:07:48Z"
    - latency: 2.360211ms
      message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:06:48Z"
    - latency: 2.350524ms
      message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:05:48Z"
    - latency: 2.330131ms
      message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:04:48Z"
    - latency: 2.127176ms
      message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:03:48Z"
    - latency: 2.253265ms
      message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:02:48Z"
    - latency: 2.098502ms
      message: 'network-check-target-ip-10-0-130-131: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:01:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T00:00:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-106-to-network-check-target-ip-10-0-140-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-106.ec2.internal
      uid: 67989016-487e-42f7-9fa0-1669b7e00d8b
    resourceVersion: "15703"
    uid: 8424041f-2112-4e9c-935c-fa4b6021d643
  spec:
    sourcePod: network-check-source-dbd9cf844-s4xxl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T00:07:48Z"
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.173838ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:07:48Z"
    - latency: 2.276972ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:06:48Z"
    - latency: 2.030228ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:05:48Z"
    - latency: 2.300931ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:04:48Z"
    - latency: 2.363422ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:03:48Z"
    - latency: 2.182597ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:02:48Z"
    - latency: 2.070709ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:01:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T00:00:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-106-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-106.ec2.internal
      uid: 67989016-487e-42f7-9fa0-1669b7e00d8b
    resourceVersion: "15375"
    uid: c6ef79d7-22e9-4a7c-9d46-785471ca3b76
  spec:
    sourcePod: network-check-source-dbd9cf844-s4xxl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T00:06:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 922.249µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:06:48Z"
    - latency: 1.861566ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:06:48Z"
    - latency: 941.91µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:05:48Z"
    - latency: 2.079342ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:05:48Z"
    - latency: 1.265719ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:04:48Z"
    - latency: 1.769215ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:04:48Z"
    - latency: 719.446µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:03:48Z"
    - latency: 1.812522ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:03:48Z"
    - latency: 998.645µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T00:02:48Z"
    - latency: 1.585406ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T00:02:48Z"
kind: List
metadata:
  resourceVersion: ""