apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T18:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-244-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-244.ec2.internal uid: 99d26cff-2198-404e-bb56-bec2fb711b6b resourceVersion: "68453" uid: 306bb0f7-1d2c-4495-b638-6314eb331eb8 spec: sourcePod: network-check-source-7d88cb55d8-68kn5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T18:08:34Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.168393ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:34Z" - latency: 1.188811ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:34Z" - latency: 1.156587ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:48:34Z" - latency: 1.169314ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:47:34Z" - latency: 1.21197ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:46:34Z" - latency: 1.453157ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:45:34Z" - latency: 1.276198ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:44:34Z" - latency: 1.408082ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:43:34Z" - latency: 1.206025ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:42:34Z" - latency: 1.521713ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:41:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T18:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-244-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-244.ec2.internal uid: 99d26cff-2198-404e-bb56-bec2fb711b6b resourceVersion: "73651" uid: f0a1ba40-cfcd-4d86-84c2-83c09a2b8647 spec: sourcePod: network-check-source-7d88cb55d8-68kn5 targetEndpoint: aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T18:07:34Z" message: 'load-balancer-api-external: tcp connection to aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.768418ms message: 'load-balancer-api-external: tcp connection to aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:55:34Z" - latency: 12.371984ms message: 'load-balancer-api-external: resolved host name aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:55:34Z" - latency: 5.358664ms message: 'load-balancer-api-external: tcp connection to aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:54:34Z" - latency: 7.375424ms message: 'load-balancer-api-external: resolved host name aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:54:34Z" - latency: 5.14578ms message: 'load-balancer-api-external: tcp connection to aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:53:34Z" - latency: 7.218238ms message: 'load-balancer-api-external: resolved host name aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:53:34Z" - latency: 5.312713ms message: 'load-balancer-api-external: tcp connection to aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:52:34Z" - latency: 7.291087ms message: 'load-balancer-api-external: resolved host name aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:52:34Z" - latency: 5.386718ms message: 'load-balancer-api-external: tcp connection to aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:51:34Z" - latency: 6.702053ms message: 'load-balancer-api-external: resolved host name aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:51:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T18:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-244-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-244.ec2.internal uid: 99d26cff-2198-404e-bb56-bec2fb711b6b resourceVersion: "73650" uid: 68994b45-d53c-463b-b2c3-f635cae523b3 spec: sourcePod: network-check-source-7d88cb55d8-68kn5 targetEndpoint: aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T18:07:34Z" message: 'load-balancer-api-internal: tcp connection to aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.681381ms message: 'load-balancer-api-internal: tcp connection to aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:55:34Z" - latency: 12.420702ms message: 'load-balancer-api-internal: resolved host name aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:55:34Z" - latency: 5.337546ms message: 'load-balancer-api-internal: tcp connection to aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:54:34Z" - latency: 7.475806ms message: 'load-balancer-api-internal: resolved host name aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:54:34Z" - latency: 5.157494ms message: 'load-balancer-api-internal: tcp connection to aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:53:34Z" - latency: 7.327798ms message: 'load-balancer-api-internal: resolved host name aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:53:34Z" - latency: 5.3467ms message: 'load-balancer-api-internal: tcp connection to aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:52:34Z" - latency: 7.327682ms message: 'load-balancer-api-internal: resolved host name aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:52:34Z" - latency: 5.444688ms message: 'load-balancer-api-internal: tcp connection to aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:51:34Z" - latency: 6.652369ms message: 'load-balancer-api-internal: resolved host name aa1c912c1b6a947329fbfe5b483116ca-9c3454bd08671ec6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:51:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T18:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-244-to-network-check-target-ip-10-0-132-23 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-244.ec2.internal uid: 99d26cff-2198-404e-bb56-bec2fb711b6b resourceVersion: "68451" uid: bd90350c-883c-4b46-9260-8e48ef926d8f spec: sourcePod: network-check-source-7d88cb55d8-68kn5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T18:08:34Z" message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.35154ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:34Z" - latency: 2.859796ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:34Z" - latency: 2.420521ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:48:34Z" - latency: 2.596293ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:47:34Z" - latency: 2.777164ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:46:34Z" - latency: 2.977854ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:45:34Z" - latency: 2.65975ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:44:34Z" - latency: 2.376108ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:43:34Z" - latency: 2.680816ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:42:34Z" - latency: 2.533763ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:41:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T18:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-244-to-network-check-target-ip-10-0-133-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-244.ec2.internal uid: 99d26cff-2198-404e-bb56-bec2fb711b6b resourceVersion: "68450" uid: b333721f-337c-4967-9c5f-0af6fd91b9e7 spec: sourcePod: network-check-source-7d88cb55d8-68kn5 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T18:08:34Z" message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.054629ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:34Z" - latency: 1.703018ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:34Z" - latency: 1.535703ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:48:34Z" - latency: 1.143434ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:47:34Z" - latency: 1.445492ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:46:34Z" - latency: 1.128699ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:45:34Z" - latency: 1.355515ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:44:34Z" - latency: 1.158061ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:43:34Z" - latency: 1.070383ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:42:34Z" - latency: 1.70952ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:41:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T18:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-244-to-network-check-target-ip-10-0-135-147 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-244.ec2.internal uid: 99d26cff-2198-404e-bb56-bec2fb711b6b resourceVersion: "68452" uid: 0cd31ef9-1d20-4a44-a226-039ab57bb498 spec: sourcePod: network-check-source-7d88cb55d8-68kn5 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T18:08:34Z" message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.505161ms message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:34Z" - latency: 2.79211ms message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:34Z" - latency: 2.324753ms message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:48:34Z" - latency: 2.517684ms message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:47:34Z" - latency: 2.540083ms message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:46:34Z" - latency: 2.500566ms message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:45:34Z" - latency: 2.702185ms message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:44:34Z" - latency: 2.54564ms message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:43:34Z" - latency: 2.606279ms message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:42:34Z" - latency: 2.592082ms message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:41:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T18:01:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-244-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-244.ec2.internal uid: 99d26cff-2198-404e-bb56-bec2fb711b6b resourceVersion: "73649" uid: 9bf0afe4-676b-425b-adeb-293c586f90a4 spec: sourcePod: network-check-source-7d88cb55d8-68kn5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T18:07:34Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.07703ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:55:34Z" - latency: 2.138201ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:55:34Z" - latency: 912.719µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:54:34Z" - latency: 2.005753ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:54:34Z" - latency: 1.244671ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:53:34Z" - latency: 2.015584ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:53:34Z" - latency: 1.426572ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:52:34Z" - latency: 2.09428ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:52:34Z" - latency: 1.0171ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:51:34Z" - latency: 1.998399ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:51:34Z" kind: List metadata: resourceVersion: ""