apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-150-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-150.ec2.internal
      uid: 29a036fc-dfe2-4210-8871-2f0a45492fa6
    resourceVersion: "14001"
    uid: bd268c57-d343-4bc5-820f-dba3c4d6112f
  spec:
    sourcePod: network-check-source-869dcfcdcd-fg6lf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:02:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 801.776µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:18Z"
    - latency: 1.030367ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:18Z"
    - latency: 846.48µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:18Z"
    - latency: 956.473µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:59:18Z"
    - latency: 983.574µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:58:18Z"
    - latency: 1.221851ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:57:18Z"
    - latency: 895.815µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:56:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-150-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-150.ec2.internal
      uid: 29a036fc-dfe2-4210-8871-2f0a45492fa6
    resourceVersion: "13638"
    uid: 8c668cde-1bce-4660-a804-8cf154f4ef23
  spec:
    sourcePod: network-check-source-869dcfcdcd-fg6lf
    targetEndpoint: a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:01:18Z"
      message: 'load-balancer-api-external: tcp connection to a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.478709ms
      message: 'load-balancer-api-external: tcp connection to a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:18Z"
    - latency: 11.991743ms
      message: 'load-balancer-api-external: resolved host name a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:01:18Z"
    - latency: 4.67416ms
      message: 'load-balancer-api-external: tcp connection to a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:18Z"
    - latency: 6.87044ms
      message: 'load-balancer-api-external: resolved host name a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:00:18Z"
    - latency: 6.04718ms
      message: 'load-balancer-api-external: tcp connection to a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:59:18Z"
    - latency: 9.287643ms
      message: 'load-balancer-api-external: resolved host name a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:59:18Z"
    - latency: 5.211957ms
      message: 'load-balancer-api-external: tcp connection to a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:58:18Z"
    - latency: 6.962641ms
      message: 'load-balancer-api-external: resolved host name a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:58:18Z"
    - latency: 5.513022ms
      message: 'load-balancer-api-external: tcp connection to a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:57:18Z"
    - latency: 13.549209ms
      message: 'load-balancer-api-external: resolved host name a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:57:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-150-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-150.ec2.internal
      uid: 29a036fc-dfe2-4210-8871-2f0a45492fa6
    resourceVersion: "13637"
    uid: 41d52b59-83f8-47e3-8e6a-ab040e881836
  spec:
    sourcePod: network-check-source-869dcfcdcd-fg6lf
    targetEndpoint: a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:01:18Z"
      message: 'load-balancer-api-internal: tcp connection to a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.517663ms
      message: 'load-balancer-api-internal: tcp connection to a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:18Z"
    - latency: 11.953569ms
      message: 'load-balancer-api-internal: resolved host name a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:01:18Z"
    - latency: 4.662698ms
      message: 'load-balancer-api-internal: tcp connection to a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:18Z"
    - latency: 6.898193ms
      message: 'load-balancer-api-internal: resolved host name a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:00:18Z"
    - latency: 5.094641ms
      message: 'load-balancer-api-internal: tcp connection to a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:59:18Z"
    - latency: 9.257106ms
      message: 'load-balancer-api-internal: resolved host name a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:59:18Z"
    - latency: 4.497616ms
      message: 'load-balancer-api-internal: tcp connection to a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:58:18Z"
    - latency: 6.998861ms
      message: 'load-balancer-api-internal: resolved host name a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:58:18Z"
    - latency: 5.467495ms
      message: 'load-balancer-api-internal: tcp connection to a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:57:18Z"
    - latency: 13.502616ms
      message: 'load-balancer-api-internal: resolved host name a28668d668f6248bc80dce14a5e1073d-5e5921e6b127d13c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:57:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-150-to-network-check-target-ip-10-0-131-249
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-150.ec2.internal
      uid: 29a036fc-dfe2-4210-8871-2f0a45492fa6
    resourceVersion: "13999"
    uid: 5e9a309a-bb9d-4d88-b71b-ca1249be76b1
  spec:
    sourcePod: network-check-source-869dcfcdcd-fg6lf
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:02:18Z"
      message: 'network-check-target-ip-10-0-131-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.193697ms
      message: 'network-check-target-ip-10-0-131-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:18Z"
    - latency: 2.022798ms
      message: 'network-check-target-ip-10-0-131-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:18Z"
    - latency: 2.316227ms
      message: 'network-check-target-ip-10-0-131-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:18Z"
    - latency: 2.161686ms
      message: 'network-check-target-ip-10-0-131-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:59:18Z"
    - latency: 2.057842ms
      message: 'network-check-target-ip-10-0-131-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:58:18Z"
    - latency: 2.34319ms
      message: 'network-check-target-ip-10-0-131-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:57:18Z"
    - latency: 2.170117ms
      message: 'network-check-target-ip-10-0-131-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:56:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-150-to-network-check-target-ip-10-0-132-50
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-150.ec2.internal
      uid: 29a036fc-dfe2-4210-8871-2f0a45492fa6
    resourceVersion: "14000"
    uid: 388fe5e5-fd5d-4f83-a361-12aa864865d0
  spec:
    sourcePod: network-check-source-869dcfcdcd-fg6lf
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:02:18Z"
      message: 'network-check-target-ip-10-0-132-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.278646ms
      message: 'network-check-target-ip-10-0-132-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:18Z"
    - latency: 2.329969ms
      message: 'network-check-target-ip-10-0-132-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:18Z"
    - latency: 2.371645ms
      message: 'network-check-target-ip-10-0-132-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:18Z"
    - latency: 2.017625ms
      message: 'network-check-target-ip-10-0-132-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:59:18Z"
    - latency: 2.269726ms
      message: 'network-check-target-ip-10-0-132-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:58:18Z"
    - latency: 2.314408ms
      message: 'network-check-target-ip-10-0-132-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:57:18Z"
    - latency: 2.267237ms
      message: 'network-check-target-ip-10-0-132-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:56:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-150-to-network-check-target-ip-10-0-138-150
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-150.ec2.internal
      uid: 29a036fc-dfe2-4210-8871-2f0a45492fa6
    resourceVersion: "13998"
    uid: 1d40b20c-0c1e-4f9d-905f-8ce4ef622be2
  spec:
    sourcePod: network-check-source-869dcfcdcd-fg6lf
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:02:18Z"
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 944.131µs
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:18Z"
    - latency: 1.035169ms
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:18Z"
    - latency: 1.070565ms
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:18Z"
    - latency: 1.346418ms
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:59:18Z"
    - latency: 1.105592ms
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:58:18Z"
    - latency: 1.343453ms
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:57:18Z"
    - latency: 1.74994ms
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:56:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-150-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-150.ec2.internal
      uid: 29a036fc-dfe2-4210-8871-2f0a45492fa6
    resourceVersion: "13636"
    uid: fddfc3ec-967f-4ec3-8bc9-616f8a924a5b
  spec:
    sourcePod: network-check-source-869dcfcdcd-fg6lf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:01:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 766.713µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:18Z"
    - latency: 1.803848ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:01:18Z"
    - latency: 908.544µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:18Z"
    - latency: 1.955892ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:00:18Z"
    - latency: 833.412µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:59:18Z"
    - latency: 1.913398ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:59:18Z"
    - latency: 1.206502ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:58:18Z"
    - latency: 1.732329ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:58:18Z"
    - latency: 1.045707ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:57:18Z"
    - latency: 2.028107ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:57:18Z"
kind: List
metadata:
  resourceVersion: ""