apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T13:41:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-248-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-248.ec2.internal uid: 21dd3aaf-a26a-481e-a23e-3e0412d245d5 resourceVersion: "29476" uid: 6195e638-ed5b-4dba-8ec8-0bb941bd4a64 spec: sourcePod: network-check-source-6f78d59f99-24vmh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T13:48:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.181299ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:44:06Z" - latency: 1.182778ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:43:06Z" - latency: 1.423206ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:42:06Z" - latency: 1.422918ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:41:06Z" - latency: 853.929µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:40:06Z" - latency: 1.101683ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:39:06Z" - latency: 1.026989ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:38:06Z" - latency: 1.091316ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:37:06Z" - latency: 1.231433ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:36:06Z" - latency: 1.14379ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:35:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T13:41:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-248-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-248.ec2.internal uid: 21dd3aaf-a26a-481e-a23e-3e0412d245d5 resourceVersion: "30368" uid: 1bd077da-acbd-448b-ab51-bcb42b68c5c9 spec: sourcePod: network-check-source-6f78d59f99-24vmh targetEndpoint: a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T13:47:06Z" message: 'load-balancer-api-external: tcp connection to a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 15.282834ms message: 'load-balancer-api-external: tcp connection to a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:47:06Z" - latency: 8.236215ms message: 'load-balancer-api-external: resolved host name a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:47:06Z" - latency: 15.765591ms message: 'load-balancer-api-external: tcp connection to a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:46:06Z" - latency: 6.872278ms message: 'load-balancer-api-external: resolved host name a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:46:06Z" - latency: 16.868198ms message: 'load-balancer-api-external: tcp connection to a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:45:06Z" - latency: 9.148598ms message: 'load-balancer-api-external: resolved host name a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:45:06Z" - latency: 17.855187ms message: 'load-balancer-api-external: tcp connection to a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:44:06Z" - latency: 8.8695ms message: 'load-balancer-api-external: resolved host name a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:44:06Z" - latency: 17.383641ms message: 'load-balancer-api-external: tcp connection to a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:43:06Z" - latency: 9.085109ms message: 'load-balancer-api-external: resolved host name a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:43:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T13:41:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-248-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-248.ec2.internal uid: 21dd3aaf-a26a-481e-a23e-3e0412d245d5 resourceVersion: "30369" uid: 8189a2a1-b234-4a61-adff-d4a5a7c4d573 spec: sourcePod: network-check-source-6f78d59f99-24vmh targetEndpoint: a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T13:47:06Z" message: 'load-balancer-api-internal: tcp connection to a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 14.432726ms message: 'load-balancer-api-internal: tcp connection to a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:47:06Z" - latency: 8.176998ms message: 'load-balancer-api-internal: resolved host name a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:47:06Z" - latency: 17.502216ms message: 'load-balancer-api-internal: tcp connection to a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:46:06Z" - latency: 6.911386ms message: 'load-balancer-api-internal: resolved host name a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:46:06Z" - latency: 18.080879ms message: 'load-balancer-api-internal: tcp connection to a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:45:06Z" - latency: 9.096383ms message: 'load-balancer-api-internal: resolved host name a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:45:06Z" - latency: 17.480467ms message: 'load-balancer-api-internal: tcp connection to a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:44:06Z" - latency: 8.817724ms message: 'load-balancer-api-internal: resolved host name a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:44:06Z" - latency: 16.414243ms message: 'load-balancer-api-internal: tcp connection to a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:43:06Z" - latency: 9.045494ms message: 'load-balancer-api-internal: resolved host name a8441adc32f374102892c7ee7d01b8a7-d071e663d2213b72.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:43:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T13:41:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-248-to-network-check-target-ip-10-0-129-20 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-248.ec2.internal uid: 21dd3aaf-a26a-481e-a23e-3e0412d245d5 resourceVersion: "29474" uid: 3a047b15-677e-4123-af0b-28a858fafbb1 spec: sourcePod: network-check-source-6f78d59f99-24vmh targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T13:48:06Z" message: 'network-check-target-ip-10-0-129-20: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.430968ms message: 'network-check-target-ip-10-0-129-20: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:44:06Z" - latency: 2.726823ms message: 'network-check-target-ip-10-0-129-20: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:43:06Z" - latency: 2.444104ms message: 'network-check-target-ip-10-0-129-20: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:42:06Z" - latency: 2.279719ms message: 'network-check-target-ip-10-0-129-20: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:41:06Z" - latency: 2.320446ms message: 'network-check-target-ip-10-0-129-20: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:40:06Z" - latency: 2.459758ms message: 'network-check-target-ip-10-0-129-20: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:39:06Z" - latency: 2.329964ms message: 'network-check-target-ip-10-0-129-20: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:38:06Z" - latency: 2.556526ms message: 'network-check-target-ip-10-0-129-20: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:37:06Z" - latency: 2.593346ms message: 'network-check-target-ip-10-0-129-20: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:36:06Z" - latency: 2.342764ms message: 'network-check-target-ip-10-0-129-20: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:35:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T13:41:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-248-to-network-check-target-ip-10-0-132-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-248.ec2.internal uid: 21dd3aaf-a26a-481e-a23e-3e0412d245d5 resourceVersion: "29475" uid: d1c202cb-90a8-4875-856e-6027afc74646 spec: sourcePod: network-check-source-6f78d59f99-24vmh targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T13:48:06Z" message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.107684ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:44:06Z" - latency: 2.679159ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:43:06Z" - latency: 2.659832ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:42:06Z" - latency: 2.119822ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:41:06Z" - latency: 2.702406ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:40:06Z" - latency: 2.75491ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:39:06Z" - latency: 2.616254ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:38:06Z" - latency: 2.789926ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:37:06Z" - latency: 2.626ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:36:06Z" - latency: 2.47331ms message: 'network-check-target-ip-10-0-132-161: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:35:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T13:41:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-248-to-network-check-target-ip-10-0-132-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-248.ec2.internal uid: 21dd3aaf-a26a-481e-a23e-3e0412d245d5 resourceVersion: "29473" uid: e745a79c-58a8-403c-945e-b4f1fedbd85f spec: sourcePod: network-check-source-6f78d59f99-24vmh targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T13:48:06Z" message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.019037ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:44:06Z" - latency: 1.474309ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:43:06Z" - latency: 1.25224ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:42:06Z" - latency: 984.63µs message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:41:06Z" - latency: 2.124395ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:40:06Z" - latency: 1.113647ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:39:06Z" - latency: 988.701µs message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:38:06Z" - latency: 988.185µs message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:37:06Z" - latency: 1.613265ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:36:06Z" - latency: 1.551187ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:35:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T13:41:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-248-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-248.ec2.internal uid: 21dd3aaf-a26a-481e-a23e-3e0412d245d5 resourceVersion: "30367" uid: 72ab56ec-20d9-4ea7-94dd-c62bd1e68639 spec: sourcePod: network-check-source-6f78d59f99-24vmh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T13:47:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.023924ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:47:06Z" - latency: 1.826033ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T14:47:06Z" - latency: 1.605706ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:46:06Z" - latency: 1.844261ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T14:46:06Z" - latency: 1.065121ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:45:06Z" - latency: 2.492891ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T14:45:06Z" - latency: 801.412µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:44:06Z" - latency: 2.197667ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T14:44:06Z" - latency: 986.603µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:43:06Z" - latency: 1.809607ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T14:43:06Z" kind: List metadata: resourceVersion: ""