apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T20:57:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-77-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-77.ec2.internal uid: eafc4b0e-23a3-4ce4-8f11-0cf235124b5c resourceVersion: "43906" uid: 23f3e249-08d2-43d5-b634-97f19e7ea633 spec: sourcePod: network-check-source-7f44b6dd87-zm2vd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T21:04:41Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 845.787µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:25:41Z" - latency: 915.46µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:24:41Z" - latency: 1.173979ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:23:41Z" - latency: 1.078652ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:22:41Z" - latency: 1.032799ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:21:41Z" - latency: 1.003051ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:20:41Z" - latency: 1.069984ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:19:41Z" - latency: 839.126µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:18:41Z" - latency: 1.061245ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:17:41Z" - latency: 985.622µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:16:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T20:57:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-77-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-77.ec2.internal uid: eafc4b0e-23a3-4ce4-8f11-0cf235124b5c resourceVersion: "45934" uid: 57f7a298-02c9-473c-8386-8d4768302219 spec: sourcePod: network-check-source-7f44b6dd87-zm2vd targetEndpoint: a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T21:03:41Z" message: 'load-balancer-api-external: tcp connection to a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.048882ms message: 'load-balancer-api-external: tcp connection to a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:27:41Z" - latency: 8.772691ms message: 'load-balancer-api-external: resolved host name a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T21:27:41Z" - latency: 3.624312ms message: 'load-balancer-api-external: tcp connection to a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:26:41Z" - latency: 7.975681ms message: 'load-balancer-api-external: resolved host name a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T21:26:41Z" - latency: 3.727634ms message: 'load-balancer-api-external: tcp connection to a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:25:41Z" - latency: 7.530515ms message: 'load-balancer-api-external: resolved host name a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T21:25:41Z" - latency: 6.194267ms message: 'load-balancer-api-external: tcp connection to a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:24:41Z" - latency: 7.812481ms message: 'load-balancer-api-external: resolved host name a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T21:24:41Z" - latency: 4.391516ms message: 'load-balancer-api-external: tcp connection to a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:23:41Z" - latency: 7.472694ms message: 'load-balancer-api-external: resolved host name a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T21:23:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T20:57:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-77-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-77.ec2.internal uid: eafc4b0e-23a3-4ce4-8f11-0cf235124b5c resourceVersion: "45935" uid: 531495d8-6e29-4dfb-922b-b9231fb084f7 spec: sourcePod: network-check-source-7f44b6dd87-zm2vd targetEndpoint: a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T21:03:41Z" message: 'load-balancer-api-internal: tcp connection to a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.052017ms message: 'load-balancer-api-internal: tcp connection to a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:27:41Z" - latency: 8.7421ms message: 'load-balancer-api-internal: resolved host name a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T21:27:41Z" - latency: 4.181046ms message: 'load-balancer-api-internal: tcp connection to a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:26:41Z" - latency: 8.00673ms message: 'load-balancer-api-internal: resolved host name a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T21:26:41Z" - latency: 3.81971ms message: 'load-balancer-api-internal: tcp connection to a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:25:41Z" - latency: 7.443181ms message: 'load-balancer-api-internal: resolved host name a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T21:25:41Z" - latency: 6.184945ms message: 'load-balancer-api-internal: tcp connection to a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:24:41Z" - latency: 7.743649ms message: 'load-balancer-api-internal: resolved host name a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T21:24:41Z" - latency: 3.991048ms message: 'load-balancer-api-internal: tcp connection to a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:23:41Z" - latency: 7.450083ms message: 'load-balancer-api-internal: resolved host name a90c4e9e6194440d1a1b6223923176a8-87b2b7739a773048.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T21:23:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T20:57:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-77-to-network-check-target-ip-10-0-133-41 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-77.ec2.internal uid: eafc4b0e-23a3-4ce4-8f11-0cf235124b5c resourceVersion: "43905" uid: cb7605b0-6c5f-4000-a5c3-98f5cae46ea8 spec: sourcePod: network-check-source-7f44b6dd87-zm2vd targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T21:04:41Z" message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.041508ms message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:25:41Z" - latency: 2.006168ms message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:24:41Z" - latency: 2.306448ms message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:23:41Z" - latency: 2.154028ms message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:22:41Z" - latency: 1.893046ms message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:21:41Z" - latency: 1.732518ms message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:20:41Z" - latency: 2.102181ms message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:19:41Z" - latency: 2.032209ms message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:18:41Z" - latency: 1.787562ms message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:17:41Z" - latency: 1.742976ms message: 'network-check-target-ip-10-0-133-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:16:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T20:57:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-77-to-network-check-target-ip-10-0-136-77 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-77.ec2.internal uid: eafc4b0e-23a3-4ce4-8f11-0cf235124b5c resourceVersion: "43903" uid: 89baaf07-f422-47ce-9dcf-efbe694fe7d8 spec: sourcePod: network-check-source-7f44b6dd87-zm2vd targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T21:04:41Z" message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 885.384µs message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:25:41Z" - latency: 962.945µs message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:24:41Z" - latency: 1.176662ms message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:23:41Z" - latency: 859.71µs message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:22:41Z" - latency: 1.464769ms message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:21:41Z" - latency: 1.44322ms message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:20:41Z" - latency: 1.270063ms message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:19:41Z" - latency: 691.097µs message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:18:41Z" - latency: 728.95µs message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:17:41Z" - latency: 1.464842ms message: 'network-check-target-ip-10-0-136-77: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:16:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T20:57:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-77-to-network-check-target-ip-10-0-140-94 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-77.ec2.internal uid: eafc4b0e-23a3-4ce4-8f11-0cf235124b5c resourceVersion: "43904" uid: deed244a-0b1d-4cc2-945c-027cf6b36004 spec: sourcePod: network-check-source-7f44b6dd87-zm2vd targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T21:04:41Z" message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.782253ms message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:25:41Z" - latency: 1.818765ms message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:24:41Z" - latency: 2.141784ms message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:23:41Z" - latency: 2.238902ms message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:22:41Z" - latency: 1.744025ms message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:21:41Z" - latency: 2.055629ms message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:20:41Z" - latency: 2.017074ms message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:19:41Z" - latency: 1.731276ms message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:18:41Z" - latency: 1.959411ms message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:17:41Z" - latency: 2.144662ms message: 'network-check-target-ip-10-0-140-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:16:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T20:57:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-77-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-77.ec2.internal uid: eafc4b0e-23a3-4ce4-8f11-0cf235124b5c resourceVersion: "45933" uid: d79400f0-fda4-48dc-bcbe-a8473853c0af spec: sourcePod: network-check-source-7f44b6dd87-zm2vd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T21:03:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 748.963µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:27:41Z" - latency: 2.653574ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T21:27:41Z" - latency: 772.438µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:26:41Z" - latency: 1.812643ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T21:26:41Z" - latency: 838.657µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:25:41Z" - latency: 1.857691ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T21:25:41Z" - latency: 1.036535ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:24:41Z" - latency: 1.578684ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T21:24:41Z" - latency: 827.383µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T21:23:41Z" - latency: 1.857608ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T21:23:41Z" kind: List metadata: resourceVersion: ""