apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:32:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-26-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-26.ec2.internal
      uid: 7d6acd14-f454-41c2-aa45-60eb2aea0cc0
    resourceVersion: "15207"
    uid: ecf048b0-a211-49c9-b3ed-7bb9fc61bb6c
  spec:
    sourcePod: network-check-source-869dcfcdcd-gdz6r
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:39:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.198092ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:39:28Z"
    - latency: 975.169µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:38:28Z"
    - latency: 1.230748ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:37:28Z"
    - latency: 1.104565ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:36:28Z"
    - latency: 933.948µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:35:28Z"
    - latency: 1.017424ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:34:28Z"
    - latency: 1.14565ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:33:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:32:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-26-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-26.ec2.internal
      uid: 7d6acd14-f454-41c2-aa45-60eb2aea0cc0
    resourceVersion: "14842"
    uid: 3b66639c-cac9-4be9-a924-e8e5c7e3c81a
  spec:
    sourcePod: network-check-source-869dcfcdcd-gdz6r
    targetEndpoint: abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:38:28Z"
      message: 'load-balancer-api-external: tcp connection to abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.741618ms
      message: 'load-balancer-api-external: tcp connection to abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:38:28Z"
    - latency: 8.202131ms
      message: 'load-balancer-api-external: resolved host name abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:38:28Z"
    - latency: 5.104397ms
      message: 'load-balancer-api-external: tcp connection to abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:37:28Z"
    - latency: 9.380439ms
      message: 'load-balancer-api-external: resolved host name abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:37:28Z"
    - latency: 5.155019ms
      message: 'load-balancer-api-external: tcp connection to abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:36:28Z"
    - latency: 6.531232ms
      message: 'load-balancer-api-external: resolved host name abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:36:28Z"
    - latency: 5.883799ms
      message: 'load-balancer-api-external: tcp connection to abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:35:28Z"
    - latency: 11.297286ms
      message: 'load-balancer-api-external: resolved host name abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:35:28Z"
    - latency: 4.89499ms
      message: 'load-balancer-api-external: tcp connection to abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:34:28Z"
    - latency: 7.824142ms
      message: 'load-balancer-api-external: resolved host name abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:34:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:32:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-26-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-26.ec2.internal
      uid: 7d6acd14-f454-41c2-aa45-60eb2aea0cc0
    resourceVersion: "14841"
    uid: b7659115-bbdc-4837-91cd-e1e0304c4446
  spec:
    sourcePod: network-check-source-869dcfcdcd-gdz6r
    targetEndpoint: abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:38:28Z"
      message: 'load-balancer-api-internal: tcp connection to abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.632837ms
      message: 'load-balancer-api-internal: tcp connection to abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:38:28Z"
    - latency: 8.312618ms
      message: 'load-balancer-api-internal: resolved host name abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:38:28Z"
    - latency: 4.539403ms
      message: 'load-balancer-api-internal: tcp connection to abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:37:28Z"
    - latency: 9.245071ms
      message: 'load-balancer-api-internal: resolved host name abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:37:28Z"
    - latency: 5.116039ms
      message: 'load-balancer-api-internal: tcp connection to abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:36:28Z"
    - latency: 6.631741ms
      message: 'load-balancer-api-internal: resolved host name abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:36:28Z"
    - latency: 3.694095ms
      message: 'load-balancer-api-internal: tcp connection to abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:35:28Z"
    - latency: 11.242522ms
      message: 'load-balancer-api-internal: resolved host name abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:35:28Z"
    - latency: 5.052657ms
      message: 'load-balancer-api-internal: tcp connection to abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:34:28Z"
    - latency: 7.884284ms
      message: 'load-balancer-api-internal: resolved host name abebe3b4a81c94018a780181af4685a8-3d38e9911cd68ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:34:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:32:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-26-to-network-check-target-ip-10-0-128-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-26.ec2.internal
      uid: 7d6acd14-f454-41c2-aa45-60eb2aea0cc0
    resourceVersion: "15204"
    uid: 35432e43-346a-4cf1-917d-61fbc12a684a
  spec:
    sourcePod: network-check-source-869dcfcdcd-gdz6r
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:39:28Z"
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.416589ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:39:28Z"
    - latency: 952.183µs
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:38:28Z"
    - latency: 848.787µs
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:37:28Z"
    - latency: 906.194µs
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:36:28Z"
    - latency: 885.586µs
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:35:28Z"
    - latency: 766.765µs
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:34:28Z"
    - latency: 2.135139ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:33:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:32:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-26-to-network-check-target-ip-10-0-136-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-26.ec2.internal
      uid: 7d6acd14-f454-41c2-aa45-60eb2aea0cc0
    resourceVersion: "15205"
    uid: 7bd906f6-92d2-4928-8e7e-2e5c6471e5ba
  spec:
    sourcePod: network-check-source-869dcfcdcd-gdz6r
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:39:28Z"
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.322492ms
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:39:28Z"
    - latency: 2.410447ms
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:38:28Z"
    - latency: 2.334932ms
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:37:28Z"
    - latency: 2.41904ms
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:36:28Z"
    - latency: 2.410736ms
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:35:28Z"
    - latency: 2.012729ms
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:34:28Z"
    - latency: 2.454355ms
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:33:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:32:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-26-to-network-check-target-ip-10-0-137-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-26.ec2.internal
      uid: 7d6acd14-f454-41c2-aa45-60eb2aea0cc0
    resourceVersion: "15206"
    uid: e6ffa0c1-a3c2-4f96-b232-e4cc46ac432e
  spec:
    sourcePod: network-check-source-869dcfcdcd-gdz6r
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:39:28Z"
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.729337ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:39:28Z"
    - latency: 2.317394ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:38:28Z"
    - latency: 2.323963ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:37:28Z"
    - latency: 2.366457ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:36:28Z"
    - latency: 2.756417ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:35:28Z"
    - latency: 2.270392ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:34:28Z"
    - latency: 2.112252ms
      message: 'network-check-target-ip-10-0-137-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:33:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:32:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-26-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-26.ec2.internal
      uid: 7d6acd14-f454-41c2-aa45-60eb2aea0cc0
    resourceVersion: "14840"
    uid: bceed5b7-cf75-4f4e-a00f-035b239b654c
  spec:
    sourcePod: network-check-source-869dcfcdcd-gdz6r
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:38:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 979.594µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:38:28Z"
    - latency: 2.271728ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:38:28Z"
    - latency: 854.955µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:37:28Z"
    - latency: 1.624234ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:37:28Z"
    - latency: 915.839µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:36:28Z"
    - latency: 1.718329ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:36:28Z"
    - latency: 1.016299ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:35:28Z"
    - latency: 2.098774ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:35:28Z"
    - latency: 841.473µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:34:28Z"
    - latency: 1.637092ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:34:28Z"
kind: List
metadata:
  resourceVersion: ""