apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:28:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-177-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-177.us-east-2.compute.internal uid: a6366ad2-a28d-46c5-a9dd-80ca9f2e8055 resourceVersion: "20621" uid: 0f38b16b-4fb2-4331-977d-5d41bd0a3f13 spec: sourcePod: network-check-source-6f78d59f99-lvbl2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T19:35:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.133345ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:42:51Z" - latency: 784.147µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:41:51Z" - latency: 1.386574ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:40:51Z" - latency: 1.129209ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:39:51Z" - latency: 1.24881ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:38:51Z" - latency: 1.108203ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:37:51Z" - latency: 1.147885ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:36:51Z" - latency: 886.05µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:35:51Z" - latency: 1.195786ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:34:51Z" - latency: 1.710327ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:33:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:28:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-177-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-177.us-east-2.compute.internal uid: a6366ad2-a28d-46c5-a9dd-80ca9f2e8055 resourceVersion: "23205" uid: 099b8fec-809e-48f9-a353-df44168eda76 spec: sourcePod: network-check-source-6f78d59f99-lvbl2 targetEndpoint: adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T19:34:51Z" message: 'load-balancer-api-external: tcp connection to adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.229443ms message: 'load-balancer-api-external: tcp connection to adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:46:51Z" - latency: 6.797621ms message: 'load-balancer-api-external: resolved host name adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:46:51Z" - latency: 4.269848ms message: 'load-balancer-api-external: tcp connection to adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:45:51Z" - latency: 6.846879ms message: 'load-balancer-api-external: resolved host name adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:45:51Z" - latency: 4.238796ms message: 'load-balancer-api-external: tcp connection to adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:44:51Z" - latency: 7.709403ms message: 'load-balancer-api-external: resolved host name adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:44:51Z" - latency: 6.626303ms message: 'load-balancer-api-external: tcp connection to adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:43:51Z" - latency: 6.181816ms message: 'load-balancer-api-external: resolved host name adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:43:51Z" - latency: 6.728542ms message: 'load-balancer-api-external: tcp connection to adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:42:51Z" - latency: 10.10361ms message: 'load-balancer-api-external: resolved host name adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:42:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:28:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-177-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-177.us-east-2.compute.internal uid: a6366ad2-a28d-46c5-a9dd-80ca9f2e8055 resourceVersion: "23204" uid: 2ff99e4b-8ba6-4e2b-96b6-b12f5888ee3e spec: sourcePod: network-check-source-6f78d59f99-lvbl2 targetEndpoint: adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T19:34:51Z" message: 'load-balancer-api-internal: tcp connection to adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.522381ms message: 'load-balancer-api-internal: tcp connection to adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:46:51Z" - latency: 6.770997ms message: 'load-balancer-api-internal: resolved host name adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:46:51Z" - latency: 4.213049ms message: 'load-balancer-api-internal: tcp connection to adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:45:51Z" - latency: 6.802269ms message: 'load-balancer-api-internal: resolved host name adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:45:51Z" - latency: 3.720337ms message: 'load-balancer-api-internal: tcp connection to adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:44:51Z" - latency: 7.682727ms message: 'load-balancer-api-internal: resolved host name adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:44:51Z" - latency: 6.633033ms message: 'load-balancer-api-internal: tcp connection to adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:43:51Z" - latency: 6.149923ms message: 'load-balancer-api-internal: resolved host name adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:43:51Z" - latency: 7.090767ms message: 'load-balancer-api-internal: tcp connection to adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:42:51Z" - latency: 10.047695ms message: 'load-balancer-api-internal: resolved host name adace1519588c450aa3304455caee28e-db04ab781b4c3a0e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:42:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:28:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-177-to-network-check-target-ip-10-0-130-177 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-177.us-east-2.compute.internal uid: a6366ad2-a28d-46c5-a9dd-80ca9f2e8055 resourceVersion: "20618" uid: 61d95589-29b6-42dc-a8d9-c0ddefd7f101 spec: sourcePod: network-check-source-6f78d59f99-lvbl2 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T19:35:51Z" message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.226065ms message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:42:51Z" - latency: 904.431µs message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:41:51Z" - latency: 982.066µs message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:40:51Z" - latency: 1.790096ms message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:39:51Z" - latency: 658.892µs message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:38:51Z" - latency: 1.313146ms message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:37:51Z" - latency: 778.555µs message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:36:51Z" - latency: 840.365µs message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:35:51Z" - latency: 806.827µs message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:34:51Z" - latency: 791.523µs message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:33:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:28:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-177-to-network-check-target-ip-10-0-133-127 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-177.us-east-2.compute.internal uid: a6366ad2-a28d-46c5-a9dd-80ca9f2e8055 resourceVersion: "20619" uid: bf809922-86ca-4d8a-a0cc-14dc9cbd65a9 spec: sourcePod: network-check-source-6f78d59f99-lvbl2 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T19:35:51Z" message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.985992ms message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:42:51Z" - latency: 1.939166ms message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:41:51Z" - latency: 1.74635ms message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:40:51Z" - latency: 2.02045ms message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:39:51Z" - latency: 1.91227ms message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:38:51Z" - latency: 1.823041ms message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:37:51Z" - latency: 1.756512ms message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:36:51Z" - latency: 1.825775ms message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:35:51Z" - latency: 1.888595ms message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:34:51Z" - latency: 2.002267ms message: 'network-check-target-ip-10-0-133-127: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:33:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:28:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-177-to-network-check-target-ip-10-0-141-132 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-177.us-east-2.compute.internal uid: a6366ad2-a28d-46c5-a9dd-80ca9f2e8055 resourceVersion: "20620" uid: 5060ad2b-a870-4384-af87-9ae4e7cc801c spec: sourcePod: network-check-source-6f78d59f99-lvbl2 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T19:35:51Z" message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.233285ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:42:51Z" - latency: 2.138467ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:41:51Z" - latency: 2.228216ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:40:51Z" - latency: 2.110523ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:39:51Z" - latency: 1.998471ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:38:51Z" - latency: 2.220849ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:37:51Z" - latency: 2.286248ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:36:51Z" - latency: 2.06695ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:35:51Z" - latency: 2.007486ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:34:51Z" - latency: 2.33631ms message: 'network-check-target-ip-10-0-141-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:33:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:28:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-177-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-177.us-east-2.compute.internal uid: a6366ad2-a28d-46c5-a9dd-80ca9f2e8055 resourceVersion: "23203" uid: 3e058f8f-bac1-46f3-8872-a206753e58f2 spec: sourcePod: network-check-source-6f78d59f99-lvbl2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T19:34:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 906.334µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:46:51Z" - latency: 1.832724ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T19:46:51Z" - latency: 746.852µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:45:51Z" - latency: 2.114327ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T19:45:51Z" - latency: 1.027206ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:44:51Z" - latency: 1.904723ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T19:44:51Z" - latency: 1.214954ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:43:51Z" - latency: 1.694487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T19:43:51Z" - latency: 1.375496ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:42:51Z" - latency: 1.787214ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T19:42:51Z" kind: List metadata: resourceVersion: ""