apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:47:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-19-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-19.us-west-2.compute.internal
      uid: 62867322-534f-4235-bdc4-6a04e2f2c6ea
    resourceVersion: "11786"
    uid: 8cba67c5-02a0-4e63-8f31-8bb3b912cf97
  spec:
    sourcePod: network-check-source-6f78d59f99-4bp94
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:54:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.586µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:54:39Z"
    - latency: 1.037067ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:53:39Z"
    - latency: 1.44243ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:52:39Z"
    - latency: 1.298377ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:51:39Z"
    - latency: 1.032328ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:50:39Z"
    - latency: 1.238763ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:49:39Z"
    - latency: 1.160443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:48:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:47:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-19-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-19.us-west-2.compute.internal
      uid: 62867322-534f-4235-bdc4-6a04e2f2c6ea
    resourceVersion: "11632"
    uid: 28e518f8-db81-4b3b-b015-96568bb02a9f
  spec:
    sourcePod: network-check-source-6f78d59f99-4bp94
    targetEndpoint: ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:53:39Z"
      message: 'load-balancer-api-external: tcp connection to ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 52.666074ms
      message: 'load-balancer-api-external: tcp connection to ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:53:39Z"
    - latency: 7.196552ms
      message: 'load-balancer-api-external: resolved host name ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:53:39Z"
    - latency: 55.312063ms
      message: 'load-balancer-api-external: tcp connection to ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:52:39Z"
    - latency: 6.449488ms
      message: 'load-balancer-api-external: resolved host name ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:52:39Z"
    - latency: 57.106461ms
      message: 'load-balancer-api-external: tcp connection to ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:51:39Z"
    - latency: 6.583451ms
      message: 'load-balancer-api-external: resolved host name ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:51:39Z"
    - latency: 52.564397ms
      message: 'load-balancer-api-external: tcp connection to ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:50:39Z"
    - latency: 6.352181ms
      message: 'load-balancer-api-external: resolved host name ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:50:39Z"
    - latency: 62.336808ms
      message: 'load-balancer-api-external: tcp connection to ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:49:39Z"
    - latency: 8.750606ms
      message: 'load-balancer-api-external: resolved host name ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:49:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:47:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-19-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-19.us-west-2.compute.internal
      uid: 62867322-534f-4235-bdc4-6a04e2f2c6ea
    resourceVersion: "11633"
    uid: 2b6617f6-b190-4526-bd14-f7bead03ffb3
  spec:
    sourcePod: network-check-source-6f78d59f99-4bp94
    targetEndpoint: ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:53:39Z"
      message: 'load-balancer-api-internal: tcp connection to ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.886517ms
      message: 'load-balancer-api-internal: tcp connection to ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:53:39Z"
    - latency: 7.155102ms
      message: 'load-balancer-api-internal: resolved host name ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:53:39Z"
    - latency: 53.891044ms
      message: 'load-balancer-api-internal: tcp connection to ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:52:39Z"
    - latency: 6.426276ms
      message: 'load-balancer-api-internal: resolved host name ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:52:39Z"
    - latency: 52.570392ms
      message: 'load-balancer-api-internal: tcp connection to ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:51:39Z"
    - latency: 6.59426ms
      message: 'load-balancer-api-internal: resolved host name ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:51:39Z"
    - latency: 52.531899ms
      message: 'load-balancer-api-internal: tcp connection to ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:50:39Z"
    - latency: 6.39765ms
      message: 'load-balancer-api-internal: resolved host name ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:50:39Z"
    - latency: 60.525949ms
      message: 'load-balancer-api-internal: tcp connection to ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:49:39Z"
    - latency: 9.329069ms
      message: 'load-balancer-api-internal: resolved host name ae8ec3e99e19a4db4a68844a5b4adf86-369e2fd48d205356.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:49:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:47:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-19-to-network-check-target-ip-10-0-130-19
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-19.us-west-2.compute.internal
      uid: 62867322-534f-4235-bdc4-6a04e2f2c6ea
    resourceVersion: "11783"
    uid: 76514187-437d-4878-b6a2-fbd164ed90f6
  spec:
    sourcePod: network-check-source-6f78d59f99-4bp94
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:54:39Z"
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 974.684µs
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:54:39Z"
    - latency: 852.948µs
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:53:39Z"
    - latency: 1.583239ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:52:39Z"
    - latency: 1.53568ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:51:39Z"
    - latency: 790.3µs
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:50:39Z"
    - latency: 3.049055ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:49:39Z"
    - latency: 1.097061ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:48:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:47:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-19-to-network-check-target-ip-10-0-131-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-19.us-west-2.compute.internal
      uid: 62867322-534f-4235-bdc4-6a04e2f2c6ea
    resourceVersion: "11785"
    uid: 4940a792-6aee-4390-8949-c747fcc9a98c
  spec:
    sourcePod: network-check-source-6f78d59f99-4bp94
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:54:39Z"
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.763798ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:54:39Z"
    - latency: 2.331901ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:53:39Z"
    - latency: 2.070389ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:52:39Z"
    - latency: 1.93717ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:51:39Z"
    - latency: 1.907313ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:50:39Z"
    - latency: 2.215595ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:49:39Z"
    - latency: 2.181561ms
      message: 'network-check-target-ip-10-0-131-250: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:48:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:47:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-19-to-network-check-target-ip-10-0-134-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-19.us-west-2.compute.internal
      uid: 62867322-534f-4235-bdc4-6a04e2f2c6ea
    resourceVersion: "11784"
    uid: 0b31978e-c1bb-4890-a476-1490804b05c9
  spec:
    sourcePod: network-check-source-6f78d59f99-4bp94
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:54:39Z"
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.267083ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:54:39Z"
    - latency: 2.123563ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:53:39Z"
    - latency: 2.315692ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:52:39Z"
    - latency: 2.23589ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:51:39Z"
    - latency: 1.86921ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:50:39Z"
    - latency: 2.495187ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:49:39Z"
    - latency: 2.20059ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:48:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:47:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-19-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-19.us-west-2.compute.internal
      uid: 62867322-534f-4235-bdc4-6a04e2f2c6ea
    resourceVersion: "11631"
    uid: 5261c061-282e-4894-9fbe-85c7b56653b4
  spec:
    sourcePod: network-check-source-6f78d59f99-4bp94
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:53:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 916.888µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:53:39Z"
    - latency: 1.999689ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:53:39Z"
    - latency: 876.649µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:52:39Z"
    - latency: 1.847825ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:52:39Z"
    - latency: 1.176359ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:51:39Z"
    - latency: 1.834515ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:51:39Z"
    - latency: 962.248µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:50:39Z"
    - latency: 2.386024ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:50:39Z"
    - latency: 996.207µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:49:39Z"
    - latency: 3.576174ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:49:39Z"
kind: List
metadata:
  resourceVersion: ""