apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:07:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-159-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-159.ec2.internal
      uid: 68302193-b9a1-46cd-b89a-8b36c313b8b4
    resourceVersion: "22791"
    uid: b54a2d3e-893a-4b45-8922-16593c506ff0
  spec:
    sourcePod: network-check-source-8894fc9bd-q6svq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T20:14:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.115268ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:14:46Z"
    - latency: 1.109871ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:13:46Z"
    - latency: 1.674481ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:12:46Z"
    - latency: 890.844µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:11:46Z"
    - latency: 790.702µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:10:46Z"
    - latency: 1.072658ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:09:46Z"
    - latency: 1.290384ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:08:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:07:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-159-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-159.ec2.internal
      uid: 68302193-b9a1-46cd-b89a-8b36c313b8b4
    resourceVersion: "27235"
    uid: 0822630b-2aed-4a2a-8133-44af399ec271
  spec:
    sourcePod: network-check-source-8894fc9bd-q6svq
    targetEndpoint: a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T20:13:46Z"
      message: 'load-balancer-api-external: tcp connection to a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.425368ms
      message: 'load-balancer-api-external: tcp connection to a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:19:46Z"
    - latency: 8.478544ms
      message: 'load-balancer-api-external: resolved host name a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:19:46Z"
    - latency: 4.846817ms
      message: 'load-balancer-api-external: tcp connection to a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:18:46Z"
    - latency: 6.735062ms
      message: 'load-balancer-api-external: resolved host name a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:18:46Z"
    - latency: 4.953529ms
      message: 'load-balancer-api-external: tcp connection to a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:17:46Z"
    - latency: 7.403648ms
      message: 'load-balancer-api-external: resolved host name a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:17:46Z"
    - latency: 5.181649ms
      message: 'load-balancer-api-external: tcp connection to a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:16:46Z"
    - latency: 7.520464ms
      message: 'load-balancer-api-external: resolved host name a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:16:46Z"
    - latency: 4.458237ms
      message: 'load-balancer-api-external: tcp connection to a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:15:46Z"
    - latency: 6.623753ms
      message: 'load-balancer-api-external: resolved host name a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:15:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:07:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-159-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-159.ec2.internal
      uid: 68302193-b9a1-46cd-b89a-8b36c313b8b4
    resourceVersion: "27234"
    uid: 452fc3a3-7f17-4c5a-b77b-c09c0c05b89e
  spec:
    sourcePod: network-check-source-8894fc9bd-q6svq
    targetEndpoint: a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T20:13:46Z"
      message: 'load-balancer-api-internal: tcp connection to a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.332452ms
      message: 'load-balancer-api-internal: tcp connection to a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:19:46Z"
    - latency: 8.921366ms
      message: 'load-balancer-api-internal: resolved host name a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:19:46Z"
    - latency: 4.946738ms
      message: 'load-balancer-api-internal: tcp connection to a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:18:46Z"
    - latency: 6.681937ms
      message: 'load-balancer-api-internal: resolved host name a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:18:46Z"
    - latency: 5.175083ms
      message: 'load-balancer-api-internal: tcp connection to a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:17:46Z"
    - latency: 7.453143ms
      message: 'load-balancer-api-internal: resolved host name a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:17:46Z"
    - latency: 5.160481ms
      message: 'load-balancer-api-internal: tcp connection to a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:16:46Z"
    - latency: 7.487158ms
      message: 'load-balancer-api-internal: resolved host name a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:16:46Z"
    - latency: 3.951914ms
      message: 'load-balancer-api-internal: tcp connection to a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:15:46Z"
    - latency: 6.661273ms
      message: 'load-balancer-api-internal: resolved host name a7a7b1331a9e54e16820867d945cf8fb-ddf299bbcd2829e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:15:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:07:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-159-to-network-check-target-ip-10-0-130-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-159.ec2.internal
      uid: 68302193-b9a1-46cd-b89a-8b36c313b8b4
    resourceVersion: "22788"
    uid: a39608a4-8e9e-42a3-ac6a-a103e2aea0d0
  spec:
    sourcePod: network-check-source-8894fc9bd-q6svq
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T20:14:46Z"
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 861.903µs
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:14:46Z"
    - latency: 1.269567ms
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:13:46Z"
    - latency: 1.11905ms
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:12:46Z"
    - latency: 948.213µs
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:11:46Z"
    - latency: 766.103µs
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:10:46Z"
    - latency: 849.073µs
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:09:46Z"
    - latency: 1.847938ms
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:08:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:07:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-159-to-network-check-target-ip-10-0-131-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-159.ec2.internal
      uid: 68302193-b9a1-46cd-b89a-8b36c313b8b4
    resourceVersion: "22789"
    uid: 461132ad-3627-484f-a70d-dd86dd5140f1
  spec:
    sourcePod: network-check-source-8894fc9bd-q6svq
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T20:14:46Z"
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.187967ms
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:14:46Z"
    - latency: 2.033059ms
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:13:46Z"
    - latency: 2.158577ms
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:12:46Z"
    - latency: 2.073751ms
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:11:46Z"
    - latency: 2.024805ms
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:10:46Z"
    - latency: 1.988145ms
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:09:46Z"
    - latency: 1.971745ms
      message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:08:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:07:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-159-to-network-check-target-ip-10-0-134-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-159.ec2.internal
      uid: 68302193-b9a1-46cd-b89a-8b36c313b8b4
    resourceVersion: "22790"
    uid: d54510d7-82ae-4ebc-a963-b8bf1fa280c9
  spec:
    sourcePod: network-check-source-8894fc9bd-q6svq
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T20:14:46Z"
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.5496ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:14:46Z"
    - latency: 2.256021ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:13:46Z"
    - latency: 2.101448ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:12:46Z"
    - latency: 2.094887ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:11:46Z"
    - latency: 2.069972ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:10:46Z"
    - latency: 2.043393ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:09:46Z"
    - latency: 2.293215ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:08:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:07:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-159-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-159.ec2.internal
      uid: 68302193-b9a1-46cd-b89a-8b36c313b8b4
    resourceVersion: "27232"
    uid: 23b518cb-7f29-41d7-8f5b-46879530987e
  spec:
    sourcePod: network-check-source-8894fc9bd-q6svq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T20:13:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.159524ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:19:46Z"
    - latency: 3.138862ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:19:46Z"
    - latency: 887.521µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:18:46Z"
    - latency: 1.629924ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:18:46Z"
    - latency: 1.138959ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:17:46Z"
    - latency: 1.859941ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:17:46Z"
    - latency: 1.046244ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:16:46Z"
    - latency: 1.816303ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:16:46Z"
    - latency: 918.281µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:15:46Z"
    - latency: 1.686557ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:15:46Z"
kind: List
metadata:
  resourceVersion: ""