apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T08:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-31-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-31.ec2.internal
      uid: ee525ce7-99c3-4d14-b878-96acf9ac47e5
    resourceVersion: "14597"
    uid: 22e21134-12fb-4ab1-8754-6f22e73c8097
  spec:
    sourcePod: network-check-source-8894fc9bd-mbsts
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T09:02:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 732.33µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:02:13Z"
    - latency: 1.254438ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:01:13Z"
    - latency: 1.583323ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:00:13Z"
    - latency: 1.129764ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:59:13Z"
    - latency: 789.706µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:58:13Z"
    - latency: 1.225049ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:57:13Z"
    - latency: 947.451µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:56:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T08:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-31-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-31.ec2.internal
      uid: ee525ce7-99c3-4d14-b878-96acf9ac47e5
    resourceVersion: "14088"
    uid: 281f204f-2b63-46e0-9545-333ceb0ccb75
  spec:
    sourcePod: network-check-source-8894fc9bd-mbsts
    targetEndpoint: a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T09:01:13Z"
      message: 'load-balancer-api-external: tcp connection to a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.408624ms
      message: 'load-balancer-api-external: tcp connection to a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:01:13Z"
    - latency: 8.214945ms
      message: 'load-balancer-api-external: resolved host name a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:01:13Z"
    - latency: 6.055855ms
      message: 'load-balancer-api-external: tcp connection to a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:00:13Z"
    - latency: 8.861406ms
      message: 'load-balancer-api-external: resolved host name a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:00:13Z"
    - latency: 4.886711ms
      message: 'load-balancer-api-external: tcp connection to a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:59:13Z"
    - latency: 11.928872ms
      message: 'load-balancer-api-external: resolved host name a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T08:59:13Z"
    - latency: 3.816084ms
      message: 'load-balancer-api-external: tcp connection to a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:58:13Z"
    - latency: 8.233903ms
      message: 'load-balancer-api-external: resolved host name a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T08:58:13Z"
    - latency: 5.740772ms
      message: 'load-balancer-api-external: tcp connection to a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:57:13Z"
    - latency: 7.985799ms
      message: 'load-balancer-api-external: resolved host name a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T08:57:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T08:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-31-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-31.ec2.internal
      uid: ee525ce7-99c3-4d14-b878-96acf9ac47e5
    resourceVersion: "14089"
    uid: d44b9acf-6ec5-4226-bed8-746400d134a9
  spec:
    sourcePod: network-check-source-8894fc9bd-mbsts
    targetEndpoint: a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T09:01:13Z"
      message: 'load-balancer-api-internal: tcp connection to a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.332902ms
      message: 'load-balancer-api-internal: tcp connection to a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:01:13Z"
    - latency: 8.250391ms
      message: 'load-balancer-api-internal: resolved host name a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:01:13Z"
    - latency: 5.948502ms
      message: 'load-balancer-api-internal: tcp connection to a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:00:13Z"
    - latency: 8.789496ms
      message: 'load-balancer-api-internal: resolved host name a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:00:13Z"
    - latency: 4.457159ms
      message: 'load-balancer-api-internal: tcp connection to a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:59:13Z"
    - latency: 12.036447ms
      message: 'load-balancer-api-internal: resolved host name a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T08:59:13Z"
    - latency: 3.605602ms
      message: 'load-balancer-api-internal: tcp connection to a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:58:13Z"
    - latency: 8.217806ms
      message: 'load-balancer-api-internal: resolved host name a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T08:58:13Z"
    - latency: 4.831278ms
      message: 'load-balancer-api-internal: tcp connection to a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:57:13Z"
    - latency: 8.008689ms
      message: 'load-balancer-api-internal: resolved host name a163cbf338b594cb394b5bd5c29279dc-35b54a50c396cf02.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T08:57:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T08:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-31-to-network-check-target-ip-10-0-136-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-31.ec2.internal
      uid: ee525ce7-99c3-4d14-b878-96acf9ac47e5
    resourceVersion: "14595"
    uid: e657c19e-c24d-4947-b326-c717a145776e
  spec:
    sourcePod: network-check-source-8894fc9bd-mbsts
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T09:02:13Z"
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.232456ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:02:13Z"
    - latency: 2.536629ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:01:13Z"
    - latency: 2.822467ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:00:13Z"
    - latency: 2.104002ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:59:13Z"
    - latency: 2.125255ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:58:13Z"
    - latency: 2.164788ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:57:13Z"
    - latency: 2.41756ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:56:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T08:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-31-to-network-check-target-ip-10-0-137-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-31.ec2.internal
      uid: ee525ce7-99c3-4d14-b878-96acf9ac47e5
    resourceVersion: "14594"
    uid: 768b369c-3158-450e-8b43-a9b6eed45026
  spec:
    sourcePod: network-check-source-8894fc9bd-mbsts
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T09:02:13Z"
      message: 'network-check-target-ip-10-0-137-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 977.341µs
      message: 'network-check-target-ip-10-0-137-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:02:13Z"
    - latency: 724.121µs
      message: 'network-check-target-ip-10-0-137-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:01:13Z"
    - latency: 930.7µs
      message: 'network-check-target-ip-10-0-137-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:00:13Z"
    - latency: 1.034199ms
      message: 'network-check-target-ip-10-0-137-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:59:13Z"
    - latency: 1.144193ms
      message: 'network-check-target-ip-10-0-137-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:58:13Z"
    - latency: 989.057µs
      message: 'network-check-target-ip-10-0-137-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:57:13Z"
    - latency: 1.169646ms
      message: 'network-check-target-ip-10-0-137-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:56:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T08:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-31-to-network-check-target-ip-10-0-141-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-31.ec2.internal
      uid: ee525ce7-99c3-4d14-b878-96acf9ac47e5
    resourceVersion: "14596"
    uid: 4e77f949-d600-448a-9a9a-55c2aac664eb
  spec:
    sourcePod: network-check-source-8894fc9bd-mbsts
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T09:02:13Z"
      message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.186475ms
      message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:02:13Z"
    - latency: 2.288883ms
      message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:01:13Z"
    - latency: 2.463002ms
      message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:00:13Z"
    - latency: 2.235318ms
      message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:59:13Z"
    - latency: 2.301231ms
      message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:58:13Z"
    - latency: 2.661034ms
      message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:57:13Z"
    - latency: 2.357472ms
      message: 'network-check-target-ip-10-0-141-250: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:56:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T08:55:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-31-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-31.ec2.internal
      uid: ee525ce7-99c3-4d14-b878-96acf9ac47e5
    resourceVersion: "14087"
    uid: abac8aaa-2270-4cc0-8e99-f5c9cc5db4fd
  spec:
    sourcePod: network-check-source-8894fc9bd-mbsts
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T09:01:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 904.611µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:01:13Z"
    - latency: 1.705324ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:01:13Z"
    - latency: 910.558µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T09:00:13Z"
    - latency: 1.791364ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T09:00:13Z"
    - latency: 1.079713ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:59:13Z"
    - latency: 2.461911ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T08:59:13Z"
    - latency: 935.015µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:58:13Z"
    - latency: 1.568332ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T08:58:13Z"
    - latency: 872.376µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T08:57:13Z"
    - latency: 1.656915ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T08:57:13Z"
kind: List
metadata:
  resourceVersion: ""