apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T19:05:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-177-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-177.ec2.internal uid: 4c04b0b1-2219-4700-aac3-fd1576ba0cf8 resourceVersion: "28416" uid: 350b2da6-505f-4698-9465-e5e1dd928419 spec: sourcePod: network-check-source-56d84b9f44-qbblk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T19:12:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.149937ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:19:45Z" - latency: 928.498µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:18:45Z" - latency: 1.423516ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:17:45Z" - latency: 1.468444ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:16:45Z" - latency: 934.209µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:15:45Z" - latency: 957.299µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:14:45Z" - latency: 1.2753ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:13:45Z" - latency: 889.617µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:12:45Z" - latency: 816.064µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:11:45Z" - latency: 1.034891ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:10:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T19:05:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-177-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-177.ec2.internal uid: 4c04b0b1-2219-4700-aac3-fd1576ba0cf8 resourceVersion: "27169" uid: 1444d8ee-36f6-4404-8d8b-9d788195e2b8 spec: sourcePod: network-check-source-56d84b9f44-qbblk targetEndpoint: a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T19:11:45Z" message: 'load-balancer-api-external: tcp connection to a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.161878ms message: 'load-balancer-api-external: tcp connection to a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:17:45Z" - latency: 7.227076ms message: 'load-balancer-api-external: resolved host name a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T19:17:45Z" - latency: 5.074723ms message: 'load-balancer-api-external: tcp connection to a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:16:45Z" - latency: 6.712147ms message: 'load-balancer-api-external: resolved host name a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T19:16:45Z" - latency: 4.644279ms message: 'load-balancer-api-external: tcp connection to a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:15:45Z" - latency: 7.684542ms message: 'load-balancer-api-external: resolved host name a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T19:15:45Z" - latency: 6.435578ms message: 'load-balancer-api-external: tcp connection to a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:14:45Z" - latency: 6.806014ms message: 'load-balancer-api-external: resolved host name a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T19:14:45Z" - latency: 5.15456ms message: 'load-balancer-api-external: tcp connection to a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:13:45Z" - latency: 7.455452ms message: 'load-balancer-api-external: resolved host name a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T19:13:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T19:05:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-177-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-177.ec2.internal uid: 4c04b0b1-2219-4700-aac3-fd1576ba0cf8 resourceVersion: "27168" uid: 27899c1b-17be-46ad-8bb7-10caffee2ecc spec: sourcePod: network-check-source-56d84b9f44-qbblk targetEndpoint: a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T19:11:45Z" message: 'load-balancer-api-internal: tcp connection to a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.710333ms message: 'load-balancer-api-internal: tcp connection to a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:17:45Z" - latency: 7.189445ms message: 'load-balancer-api-internal: resolved host name a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T19:17:45Z" - latency: 4.938337ms message: 'load-balancer-api-internal: tcp connection to a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:16:45Z" - latency: 6.643788ms message: 'load-balancer-api-internal: resolved host name a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T19:16:45Z" - latency: 4.671891ms message: 'load-balancer-api-internal: tcp connection to a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:15:45Z" - latency: 7.670867ms message: 'load-balancer-api-internal: resolved host name a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T19:15:45Z" - latency: 6.441619ms message: 'load-balancer-api-internal: tcp connection to a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:14:45Z" - latency: 6.752368ms message: 'load-balancer-api-internal: resolved host name a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T19:14:45Z" - latency: 7.287944ms message: 'load-balancer-api-internal: tcp connection to a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:13:45Z" - latency: 7.41244ms message: 'load-balancer-api-internal: resolved host name a8de85e5750784fafa4ea70f0e2063f3-3637b5ecf0201650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T19:13:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T19:06:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-177-to-network-check-target-ip-10-0-137-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-177.ec2.internal uid: 4c04b0b1-2219-4700-aac3-fd1576ba0cf8 resourceVersion: "28783" uid: 4b112bae-bb7b-4441-b3db-21fb6156ef12 spec: sourcePod: network-check-source-56d84b9f44-qbblk targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T19:13:18Z" message: 'network-check-target-ip-10-0-137-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.14527ms message: 'network-check-target-ip-10-0-137-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:20:18Z" - latency: 2.332615ms message: 'network-check-target-ip-10-0-137-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:19:18Z" - latency: 1.920247ms message: 'network-check-target-ip-10-0-137-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:18:18Z" - latency: 1.938239ms message: 'network-check-target-ip-10-0-137-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:17:18Z" - latency: 1.955146ms message: 'network-check-target-ip-10-0-137-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:16:18Z" - latency: 2.270102ms message: 'network-check-target-ip-10-0-137-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:15:18Z" - latency: 2.000694ms message: 'network-check-target-ip-10-0-137-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:14:18Z" - latency: 1.954323ms message: 'network-check-target-ip-10-0-137-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:13:18Z" - latency: 1.976506ms message: 'network-check-target-ip-10-0-137-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:12:18Z" - latency: 2.131388ms message: 'network-check-target-ip-10-0-137-24: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:11:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T19:05:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-177-to-network-check-target-ip-10-0-138-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-177.ec2.internal uid: 4c04b0b1-2219-4700-aac3-fd1576ba0cf8 resourceVersion: "28414" uid: 9949a507-578e-4e5b-85b0-059bdb891c84 spec: sourcePod: network-check-source-56d84b9f44-qbblk targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T19:12:45Z" message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.542455ms message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:19:45Z" - latency: 1.9192ms message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:18:45Z" - latency: 2.125552ms message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:17:45Z" - latency: 2.096321ms message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:16:45Z" - latency: 1.922211ms message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:15:45Z" - latency: 1.924069ms message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:14:45Z" - latency: 2.179545ms message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:13:45Z" - latency: 2.040582ms message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:12:45Z" - latency: 2.266722ms message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:11:45Z" - latency: 2.423781ms message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:10:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T19:05:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-177-to-network-check-target-ip-10-0-141-177 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-177.ec2.internal uid: 4c04b0b1-2219-4700-aac3-fd1576ba0cf8 resourceVersion: "28415" uid: dd7e1de8-5561-474c-82e7-8e413944668a spec: sourcePod: network-check-source-56d84b9f44-qbblk targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T19:12:45Z" message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.490419ms message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:19:45Z" - latency: 955.107µs message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:18:45Z" - latency: 1.561081ms message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:17:45Z" - latency: 693.825µs message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:16:45Z" - latency: 905.144µs message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:15:45Z" - latency: 786.715µs message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:14:45Z" - latency: 1.002976ms message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:13:45Z" - latency: 926.633µs message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:12:45Z" - latency: 1.766449ms message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:11:45Z" - latency: 819.639µs message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:10:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T19:05:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-177-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-177.ec2.internal uid: 4c04b0b1-2219-4700-aac3-fd1576ba0cf8 resourceVersion: "27167" uid: a3d610a2-5f3f-445a-b718-16856d101ba1 spec: sourcePod: network-check-source-56d84b9f44-qbblk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T19:11:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.117894ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:17:45Z" - latency: 1.897399ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T19:17:45Z" - latency: 1.95269ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:16:45Z" - latency: 1.742743ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T19:16:45Z" - latency: 876.102µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:15:45Z" - latency: 1.878342ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T19:15:45Z" - latency: 2.098282ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:14:45Z" - latency: 1.683026ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T19:14:45Z" - latency: 996.981µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T19:13:45Z" - latency: 2.16274ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T19:13:45Z" kind: List metadata: resourceVersion: ""