apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:21:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-56-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-56.ec2.internal
      uid: 3e957867-019c-4dd3-9102-3ec394d36fc5
    resourceVersion: "24800"
    uid: 234d7976-a454-4c28-afec-112633bc830f
  spec:
    sourcePod: network-check-source-685456655f-rqj45
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:28:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 943.281µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:28:10Z"
    - latency: 1.021539ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:27:10Z"
    - latency: 1.110386ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:26:10Z"
    - latency: 813.455µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:25:10Z"
    - latency: 910.803µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:24:10Z"
    - latency: 916.043µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:23:10Z"
    - latency: 1.025991ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:22:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:21:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-56-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-56.ec2.internal
      uid: 3e957867-019c-4dd3-9102-3ec394d36fc5
    resourceVersion: "23561"
    uid: dea40764-8549-4be7-8728-e93025b629b6
  spec:
    sourcePod: network-check-source-685456655f-rqj45
    targetEndpoint: aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:27:10Z"
      message: 'load-balancer-api-external: tcp connection to aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.991494ms
      message: 'load-balancer-api-external: tcp connection to aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:27:10Z"
    - latency: 6.250628ms
      message: 'load-balancer-api-external: resolved host name aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:27:10Z"
    - latency: 4.140661ms
      message: 'load-balancer-api-external: tcp connection to aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:26:10Z"
    - latency: 6.724515ms
      message: 'load-balancer-api-external: resolved host name aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:26:10Z"
    - latency: 5.333426ms
      message: 'load-balancer-api-external: tcp connection to aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:25:10Z"
    - latency: 6.539569ms
      message: 'load-balancer-api-external: resolved host name aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:25:10Z"
    - latency: 3.916222ms
      message: 'load-balancer-api-external: tcp connection to aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:24:10Z"
    - latency: 6.86964ms
      message: 'load-balancer-api-external: resolved host name aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:24:10Z"
    - latency: 3.497961ms
      message: 'load-balancer-api-external: tcp connection to aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:23:10Z"
    - latency: 5.971437ms
      message: 'load-balancer-api-external: resolved host name aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:23:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:21:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-56-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-56.ec2.internal
      uid: 3e957867-019c-4dd3-9102-3ec394d36fc5
    resourceVersion: "23560"
    uid: 962adc7f-2114-4f72-a195-cafadcb6bf95
  spec:
    sourcePod: network-check-source-685456655f-rqj45
    targetEndpoint: aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:27:10Z"
      message: 'load-balancer-api-internal: tcp connection to aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.984272ms
      message: 'load-balancer-api-internal: tcp connection to aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:27:10Z"
    - latency: 6.11047ms
      message: 'load-balancer-api-internal: resolved host name aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:27:10Z"
    - latency: 7.744582ms
      message: 'load-balancer-api-internal: tcp connection to aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:26:10Z"
    - latency: 6.737456ms
      message: 'load-balancer-api-internal: resolved host name aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:26:10Z"
    - latency: 5.363322ms
      message: 'load-balancer-api-internal: tcp connection to aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:25:10Z"
    - latency: 6.482398ms
      message: 'load-balancer-api-internal: resolved host name aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:25:10Z"
    - latency: 3.905934ms
      message: 'load-balancer-api-internal: tcp connection to aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:24:10Z"
    - latency: 6.931373ms
      message: 'load-balancer-api-internal: resolved host name aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:24:10Z"
    - latency: 3.532961ms
      message: 'load-balancer-api-internal: tcp connection to aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:23:10Z"
    - latency: 5.918116ms
      message: 'load-balancer-api-internal: resolved host name aa8b60400973b40538009c77bbc62bbb-586e11de25fda232.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:23:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:21:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-56-to-network-check-target-ip-10-0-132-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-56.ec2.internal
      uid: 3e957867-019c-4dd3-9102-3ec394d36fc5
    resourceVersion: "24797"
    uid: 30b1957e-e92a-491e-9baa-17af910ee8fa
  spec:
    sourcePod: network-check-source-685456655f-rqj45
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:28:10Z"
      message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.177045ms
      message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:28:10Z"
    - latency: 1.240612ms
      message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:27:10Z"
    - latency: 1.379921ms
      message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:26:10Z"
    - latency: 1.107169ms
      message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:25:10Z"
    - latency: 1.385038ms
      message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:24:10Z"
    - latency: 923.266µs
      message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:23:10Z"
    - latency: 1.784047ms
      message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:22:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:21:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-56-to-network-check-target-ip-10-0-133-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-56.ec2.internal
      uid: 3e957867-019c-4dd3-9102-3ec394d36fc5
    resourceVersion: "24799"
    uid: 7ccd360a-1e15-489b-9351-812e22cb4c95
  spec:
    sourcePod: network-check-source-685456655f-rqj45
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:28:10Z"
      message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.303498ms
      message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:28:10Z"
    - latency: 2.129416ms
      message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:27:10Z"
    - latency: 2.193768ms
      message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:26:10Z"
    - latency: 1.889692ms
      message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:25:10Z"
    - latency: 2.208088ms
      message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:24:10Z"
    - latency: 2.130315ms
      message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:23:10Z"
    - latency: 2.34185ms
      message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:22:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:21:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-56-to-network-check-target-ip-10-0-141-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-56.ec2.internal
      uid: 3e957867-019c-4dd3-9102-3ec394d36fc5
    resourceVersion: "24798"
    uid: bd1b0452-bced-45f8-96a0-ddfbcfd7dea8
  spec:
    sourcePod: network-check-source-685456655f-rqj45
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:28:10Z"
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.309184ms
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:28:10Z"
    - latency: 2.299841ms
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:27:10Z"
    - latency: 2.585101ms
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:26:10Z"
    - latency: 1.832504ms
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:25:10Z"
    - latency: 2.043319ms
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:24:10Z"
    - latency: 2.436426ms
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:23:10Z"
    - latency: 2.07334ms
      message: 'network-check-target-ip-10-0-141-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:22:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:21:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-56-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-56.ec2.internal
      uid: 3e957867-019c-4dd3-9102-3ec394d36fc5
    resourceVersion: "23559"
    uid: b10f5d3c-1de2-4516-8383-ba2d71bcaaed
  spec:
    sourcePod: network-check-source-685456655f-rqj45
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:27:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 864.583µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:27:10Z"
    - latency: 1.81153ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:27:10Z"
    - latency: 1.066784ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:26:10Z"
    - latency: 1.685646ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:26:10Z"
    - latency: 878.29µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:25:10Z"
    - latency: 1.89338ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:25:10Z"
    - latency: 1.054339ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:24:10Z"
    - latency: 1.766325ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:24:10Z"
    - latency: 834.91µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:23:10Z"
    - latency: 1.845763ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:23:10Z"
kind: List
metadata:
  resourceVersion: ""