apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T03:08:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-122-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-122.us-west-1.compute.internal uid: 1b1aaa24-fbda-40d3-97ee-421a6dad1466 resourceVersion: "117374" uid: 482df288-f331-4ed4-93ea-027724cba67d spec: sourcePod: network-check-source-6f78d59f99-fsr8j targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-01T03:15:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 949.007µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:11:54Z" - latency: 835.237µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:10:54Z" - latency: 4.118733ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:09:54Z" - latency: 1.238478ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:08:54Z" - latency: 1.408255ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:07:54Z" - latency: 2.48909ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:06:54Z" - latency: 1.06527ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:05:54Z" - latency: 1.223499ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:04:54Z" - latency: 968.993µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:03:54Z" - latency: 1.354957ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:02:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T03:08:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-122-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-122.us-west-1.compute.internal uid: 1b1aaa24-fbda-40d3-97ee-421a6dad1466 resourceVersion: "120932" uid: 8dbdb0f4-6351-46eb-a70a-98c22bd0bb23 spec: sourcePod: network-check-source-6f78d59f99-fsr8j targetEndpoint: a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T03:14:54Z" message: 'load-balancer-api-external: tcp connection to a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.246324ms message: 'load-balancer-api-external: tcp connection to a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:14:54Z" - latency: 6.799706ms message: 'load-balancer-api-external: resolved host name a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:14:54Z" - latency: 54.12937ms message: 'load-balancer-api-external: tcp connection to a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:13:54Z" - latency: 7.620019ms message: 'load-balancer-api-external: resolved host name a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:13:54Z" - latency: 54.396501ms message: 'load-balancer-api-external: tcp connection to a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:12:54Z" - latency: 6.774343ms message: 'load-balancer-api-external: resolved host name a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:12:54Z" - latency: 55.353044ms message: 'load-balancer-api-external: tcp connection to a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:11:54Z" - latency: 7.024821ms message: 'load-balancer-api-external: resolved host name a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:11:54Z" - latency: 53.78113ms message: 'load-balancer-api-external: tcp connection to a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:10:54Z" - latency: 7.066776ms message: 'load-balancer-api-external: resolved host name a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:10:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T03:08:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-122-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-122.us-west-1.compute.internal uid: 1b1aaa24-fbda-40d3-97ee-421a6dad1466 resourceVersion: "120934" uid: 639de5b7-2922-4e1b-b89a-a1dcda6c0681 spec: sourcePod: network-check-source-6f78d59f99-fsr8j targetEndpoint: a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T03:14:54Z" message: 'load-balancer-api-internal: tcp connection to a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.605568ms message: 'load-balancer-api-internal: tcp connection to a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:14:54Z" - latency: 6.828643ms message: 'load-balancer-api-internal: resolved host name a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:14:54Z" - latency: 54.100467ms message: 'load-balancer-api-internal: tcp connection to a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:13:54Z" - latency: 7.660057ms message: 'load-balancer-api-internal: resolved host name a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:13:54Z" - latency: 54.424147ms message: 'load-balancer-api-internal: tcp connection to a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:12:54Z" - latency: 6.801335ms message: 'load-balancer-api-internal: resolved host name a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:12:54Z" - latency: 55.72968ms message: 'load-balancer-api-internal: tcp connection to a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:11:54Z" - latency: 7.033124ms message: 'load-balancer-api-internal: resolved host name a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:11:54Z" - latency: 54.593406ms message: 'load-balancer-api-internal: tcp connection to a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:10:54Z" - latency: 7.048018ms message: 'load-balancer-api-internal: resolved host name a28e94d7245cf43b9a1c835832cbb3a3-03ecbaf5388fcb74.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:10:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T03:08:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-122-to-network-check-target-ip-10-0-133-54 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-122.us-west-1.compute.internal uid: 1b1aaa24-fbda-40d3-97ee-421a6dad1466 resourceVersion: "117372" uid: 59c8d741-d748-498c-85f4-76dc5f38bfe8 spec: sourcePod: network-check-source-6f78d59f99-fsr8j targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-01T03:15:54Z" message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.139731ms message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:11:54Z" - latency: 2.123228ms message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:10:54Z" - latency: 3.390814ms message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:09:54Z" - latency: 2.417501ms message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:08:54Z" - latency: 2.554409ms message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:07:54Z" - latency: 2.989594ms message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:06:54Z" - latency: 2.246998ms message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:05:54Z" - latency: 2.939088ms message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:04:54Z" - latency: 2.334028ms message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:03:54Z" - latency: 2.570064ms message: 'network-check-target-ip-10-0-133-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:02:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T03:08:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-122-to-network-check-target-ip-10-0-134-33 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-122.us-west-1.compute.internal uid: 1b1aaa24-fbda-40d3-97ee-421a6dad1466 resourceVersion: "117373" uid: 292ccae5-c2ec-409e-90ac-56509acdffe3 spec: sourcePod: network-check-source-6f78d59f99-fsr8j targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-01T03:15:54Z" message: 'network-check-target-ip-10-0-134-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.138837ms message: 'network-check-target-ip-10-0-134-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:11:54Z" - latency: 1.96789ms message: 'network-check-target-ip-10-0-134-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:10:54Z" - latency: 3.191676ms message: 'network-check-target-ip-10-0-134-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:09:54Z" - latency: 1.956892ms message: 'network-check-target-ip-10-0-134-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:08:54Z" - latency: 2.433479ms message: 'network-check-target-ip-10-0-134-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:07:54Z" - latency: 2.746407ms message: 'network-check-target-ip-10-0-134-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:06:54Z" - latency: 2.105728ms message: 'network-check-target-ip-10-0-134-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:05:54Z" - latency: 2.078281ms message: 'network-check-target-ip-10-0-134-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:04:54Z" - latency: 1.95859ms message: 'network-check-target-ip-10-0-134-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:03:54Z" - latency: 2.560634ms message: 'network-check-target-ip-10-0-134-33: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:02:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T03:08:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-122-to-network-check-target-ip-10-0-141-122 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-122.us-west-1.compute.internal uid: 1b1aaa24-fbda-40d3-97ee-421a6dad1466 resourceVersion: "117371" uid: 7ab1fe77-0857-4478-8c42-cde7955ef828 spec: sourcePod: network-check-source-6f78d59f99-fsr8j targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-01T03:15:54Z" message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 937.926µs message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:11:54Z" - latency: 1.163641ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:10:54Z" - latency: 5.127474ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:09:54Z" - latency: 1.441509ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:08:54Z" - latency: 1.443939ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:07:54Z" - latency: 2.073774ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:06:54Z" - latency: 1.219312ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:05:54Z" - latency: 1.97348ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:04:54Z" - latency: 2.5922ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:03:54Z" - latency: 1.17012ms message: 'network-check-target-ip-10-0-141-122: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:02:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T03:08:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-122-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-122.us-west-1.compute.internal uid: 1b1aaa24-fbda-40d3-97ee-421a6dad1466 resourceVersion: "120931" uid: 0bfa385c-1e5f-4c5a-b33c-54c86ffc35fb spec: sourcePod: network-check-source-6f78d59f99-fsr8j targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-01T03:14:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.05512ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:14:54Z" - latency: 2.134111ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T04:14:54Z" - latency: 1.046626ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:13:54Z" - latency: 2.135387ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T04:13:54Z" - latency: 1.021439ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:12:54Z" - latency: 2.433922ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T04:12:54Z" - latency: 889.059µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:11:54Z" - latency: 2.434693ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T04:11:54Z" - latency: 1.081504ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:10:54Z" - latency: 1.928487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T04:10:54Z" kind: List metadata: resourceVersion: ""