apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-254-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-254.us-west-1.compute.internal
      uid: 0090655a-3992-4f9a-9060-e42da40ebac3
    resourceVersion: "11672"
    uid: efa62117-3ccb-4f9a-a731-ce8e19172bfc
  spec:
    sourcePod: network-check-source-6f78d59f99-tm8pr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:01:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.221441ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:01:01Z"
    - latency: 1.122613ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:00:01Z"
    - latency: 918.373µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:59:01Z"
    - latency: 1.201329ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:58:01Z"
    - latency: 1.193419ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:57:01Z"
    - latency: 806.497µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:56:01Z"
    - latency: 944.389µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:55:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-254-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-254.us-west-1.compute.internal
      uid: 0090655a-3992-4f9a-9060-e42da40ebac3
    resourceVersion: "11365"
    uid: a4db0a26-b670-4474-87a1-93ff451eae56
  spec:
    sourcePod: network-check-source-6f78d59f99-tm8pr
    targetEndpoint: a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:00:01Z"
      message: 'load-balancer-api-external: tcp connection to a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.563384ms
      message: 'load-balancer-api-external: tcp connection to a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:00:01Z"
    - latency: 6.635095ms
      message: 'load-balancer-api-external: resolved host name a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:00:01Z"
    - latency: 56.317391ms
      message: 'load-balancer-api-external: tcp connection to a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:59:01Z"
    - latency: 6.273232ms
      message: 'load-balancer-api-external: resolved host name a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:59:01Z"
    - latency: 54.619782ms
      message: 'load-balancer-api-external: tcp connection to a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:58:01Z"
    - latency: 7.625853ms
      message: 'load-balancer-api-external: resolved host name a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:58:01Z"
    - latency: 53.381525ms
      message: 'load-balancer-api-external: tcp connection to a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:57:01Z"
    - latency: 8.603489ms
      message: 'load-balancer-api-external: resolved host name a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:57:01Z"
    - latency: 53.2161ms
      message: 'load-balancer-api-external: tcp connection to a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:56:01Z"
    - latency: 6.073784ms
      message: 'load-balancer-api-external: resolved host name a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:56:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-254-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-254.us-west-1.compute.internal
      uid: 0090655a-3992-4f9a-9060-e42da40ebac3
    resourceVersion: "11364"
    uid: 3908d551-ebe7-45f9-87fa-2913cd202c13
  spec:
    sourcePod: network-check-source-6f78d59f99-tm8pr
    targetEndpoint: a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:00:01Z"
      message: 'load-balancer-api-internal: tcp connection to a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.537141ms
      message: 'load-balancer-api-internal: tcp connection to a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:00:01Z"
    - latency: 6.592767ms
      message: 'load-balancer-api-internal: resolved host name a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:00:01Z"
    - latency: 57.767111ms
      message: 'load-balancer-api-internal: tcp connection to a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:59:01Z"
    - latency: 6.426418ms
      message: 'load-balancer-api-internal: resolved host name a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:59:01Z"
    - latency: 53.843382ms
      message: 'load-balancer-api-internal: tcp connection to a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:58:01Z"
    - latency: 7.672458ms
      message: 'load-balancer-api-internal: resolved host name a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:58:01Z"
    - latency: 53.421047ms
      message: 'load-balancer-api-internal: tcp connection to a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:57:01Z"
    - latency: 8.566696ms
      message: 'load-balancer-api-internal: resolved host name a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:57:01Z"
    - latency: 53.205219ms
      message: 'load-balancer-api-internal: tcp connection to a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:56:01Z"
    - latency: 6.103156ms
      message: 'load-balancer-api-internal: resolved host name a56d5f2650dee468f85cac5580a852e2-bbdeb2d3d4ced318.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:56:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-254-to-network-check-target-ip-10-0-130-254
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-254.us-west-1.compute.internal
      uid: 0090655a-3992-4f9a-9060-e42da40ebac3
    resourceVersion: "11669"
    uid: af114a81-b720-422e-8c3f-3fd0c32cd642
  spec:
    sourcePod: network-check-source-6f78d59f99-tm8pr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:01:01Z"
      message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 943.703µs
      message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:01:01Z"
    - latency: 859.819µs
      message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:00:01Z"
    - latency: 848.204µs
      message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:59:01Z"
    - latency: 744.411µs
      message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:58:01Z"
    - latency: 1.345069ms
      message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:57:01Z"
    - latency: 955.204µs
      message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:56:01Z"
    - latency: 1.516726ms
      message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:55:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-254-to-network-check-target-ip-10-0-133-103
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-254.us-west-1.compute.internal
      uid: 0090655a-3992-4f9a-9060-e42da40ebac3
    resourceVersion: "11671"
    uid: 311ecaf7-942d-43f1-955e-c018c867b376
  spec:
    sourcePod: network-check-source-6f78d59f99-tm8pr
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:01:01Z"
      message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.125205ms
      message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:01:01Z"
    - latency: 1.873873ms
      message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:00:01Z"
    - latency: 1.901497ms
      message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:59:01Z"
    - latency: 1.944034ms
      message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:58:01Z"
    - latency: 1.90571ms
      message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:57:01Z"
    - latency: 2.038151ms
      message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:56:01Z"
    - latency: 1.908167ms
      message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:55:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-254-to-network-check-target-ip-10-0-143-16
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-254.us-west-1.compute.internal
      uid: 0090655a-3992-4f9a-9060-e42da40ebac3
    resourceVersion: "11670"
    uid: e9058712-a469-490a-9709-fc62ac746d7e
  spec:
    sourcePod: network-check-source-6f78d59f99-tm8pr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:01:01Z"
      message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.791199ms
      message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:01:01Z"
    - latency: 2.006242ms
      message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:00:01Z"
    - latency: 1.772205ms
      message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:59:01Z"
    - latency: 2.055971ms
      message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:58:01Z"
    - latency: 1.825553ms
      message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:57:01Z"
    - latency: 1.796957ms
      message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:56:01Z"
    - latency: 2.028351ms
      message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:55:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-254-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-254.us-west-1.compute.internal
      uid: 0090655a-3992-4f9a-9060-e42da40ebac3
    resourceVersion: "11363"
    uid: 82271a14-a21e-4531-8562-dea991b67916
  spec:
    sourcePod: network-check-source-6f78d59f99-tm8pr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T18:00:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 825.172µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:00:01Z"
    - latency: 1.781676ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T18:00:01Z"
    - latency: 781.54µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:59:01Z"
    - latency: 1.660132ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:59:01Z"
    - latency: 833.244µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:58:01Z"
    - latency: 1.694758ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:58:01Z"
    - latency: 803.082µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:57:01Z"
    - latency: 2.10177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:57:01Z"
    - latency: 848.847µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:56:01Z"
    - latency: 1.813306ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:56:01Z"
kind: List
metadata:
  resourceVersion: ""