apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:01:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-160-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-160.ec2.internal uid: 3c26dbde-acf3-4a0c-9f5b-6b3b67c58d91 resourceVersion: "79221" uid: afb1b687-a91c-4c13-bc95-0bcf2020b369 spec: sourcePod: network-check-source-7bc5b6bf85-gvfp6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-20T10:08:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 906.614µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:25:27Z" - latency: 1.340115ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:24:27Z" - latency: 838.838µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:23:27Z" - latency: 900.064µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:22:27Z" - latency: 1.444514ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:21:27Z" - latency: 878.075µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:20:27Z" - latency: 1.01287ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:19:27Z" - latency: 1.22299ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:18:27Z" - latency: 926.304µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:17:27Z" - latency: 977.545µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:16:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:01:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-160-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-160.ec2.internal uid: 3c26dbde-acf3-4a0c-9f5b-6b3b67c58d91 resourceVersion: "79222" uid: 7e310f4a-852b-42d5-babc-8096ae3903d0 spec: sourcePod: network-check-source-7bc5b6bf85-gvfp6 targetEndpoint: a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T10:07:27Z" message: 'load-balancer-api-external: tcp connection to a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.151766ms message: 'load-balancer-api-external: tcp connection to a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:25:27Z" - latency: 7.042813ms message: 'load-balancer-api-external: resolved host name a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:25:27Z" - latency: 4.676028ms message: 'load-balancer-api-external: tcp connection to a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:24:27Z" - latency: 7.469057ms message: 'load-balancer-api-external: resolved host name a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:24:27Z" - latency: 4.419606ms message: 'load-balancer-api-external: tcp connection to a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:23:27Z" - latency: 6.960396ms message: 'load-balancer-api-external: resolved host name a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:23:27Z" - latency: 4.118605ms message: 'load-balancer-api-external: tcp connection to a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:22:27Z" - latency: 7.713716ms message: 'load-balancer-api-external: resolved host name a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:22:27Z" - latency: 4.188254ms message: 'load-balancer-api-external: tcp connection to a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:21:27Z" - latency: 8.846716ms message: 'load-balancer-api-external: resolved host name a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:21:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:01:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-160-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-160.ec2.internal uid: 3c26dbde-acf3-4a0c-9f5b-6b3b67c58d91 resourceVersion: "79223" uid: cecd9558-c2fd-4702-ac61-0f430faef1a5 spec: sourcePod: network-check-source-7bc5b6bf85-gvfp6 targetEndpoint: a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T10:07:27Z" message: 'load-balancer-api-internal: tcp connection to a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.211303ms message: 'load-balancer-api-internal: tcp connection to a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:25:27Z" - latency: 7.118423ms message: 'load-balancer-api-internal: resolved host name a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:25:27Z" - latency: 4.708334ms message: 'load-balancer-api-internal: tcp connection to a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:24:27Z" - latency: 7.442051ms message: 'load-balancer-api-internal: resolved host name a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:24:27Z" - latency: 4.408242ms message: 'load-balancer-api-internal: tcp connection to a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:23:27Z" - latency: 6.99278ms message: 'load-balancer-api-internal: resolved host name a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:23:27Z" - latency: 4.152982ms message: 'load-balancer-api-internal: tcp connection to a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:22:27Z" - latency: 7.792773ms message: 'load-balancer-api-internal: resolved host name a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:22:27Z" - latency: 4.196204ms message: 'load-balancer-api-internal: tcp connection to a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:21:27Z" - latency: 8.893088ms message: 'load-balancer-api-internal: resolved host name a058b0e053a364039a705a4c8606d4df-530244ab7b089203.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T11:21:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:01:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-160-to-network-check-target-ip-10-0-133-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-160.ec2.internal uid: 3c26dbde-acf3-4a0c-9f5b-6b3b67c58d91 resourceVersion: "79217" uid: 728efb20-a0f8-4d1e-8e06-3724de71620c spec: sourcePod: network-check-source-7bc5b6bf85-gvfp6 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T10:08:27Z" message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 887.775µs message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:25:27Z" - latency: 875.087µs message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:24:27Z" - latency: 1.262009ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:23:27Z" - latency: 872.066µs message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:22:27Z" - latency: 1.019369ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:21:27Z" - latency: 887.179µs message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:20:27Z" - latency: 860.189µs message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:19:27Z" - latency: 859.228µs message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:18:27Z" - latency: 1.088723ms message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:17:27Z" - latency: 947.2µs message: 'network-check-target-ip-10-0-133-160: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:16:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:01:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-160-to-network-check-target-ip-10-0-137-140 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-160.ec2.internal uid: 3c26dbde-acf3-4a0c-9f5b-6b3b67c58d91 resourceVersion: "79218" uid: e5f31e3a-1909-459c-83fb-16eabe8697ac spec: sourcePod: network-check-source-7bc5b6bf85-gvfp6 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T10:08:27Z" message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.437024ms message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:25:27Z" - latency: 2.673805ms message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:24:27Z" - latency: 2.113834ms message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:23:27Z" - latency: 2.262023ms message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:22:27Z" - latency: 2.305872ms message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:21:27Z" - latency: 2.410317ms message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:20:27Z" - latency: 2.284597ms message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:19:27Z" - latency: 2.372819ms message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:18:27Z" - latency: 2.560574ms message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:17:27Z" - latency: 2.276073ms message: 'network-check-target-ip-10-0-137-140: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:16:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:01:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-160-to-network-check-target-ip-10-0-138-196 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-160.ec2.internal uid: 3c26dbde-acf3-4a0c-9f5b-6b3b67c58d91 resourceVersion: "79220" uid: e89d7e47-95df-4c27-978b-fc7733b04d37 spec: sourcePod: network-check-source-7bc5b6bf85-gvfp6 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-20T10:08:27Z" message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.603277ms message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:25:27Z" - latency: 2.373373ms message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:24:27Z" - latency: 2.251555ms message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:23:27Z" - latency: 2.367152ms message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:22:27Z" - latency: 2.57213ms message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:21:27Z" - latency: 2.405061ms message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:20:27Z" - latency: 2.267303ms message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:19:27Z" - latency: 2.741054ms message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:18:27Z" - latency: 2.468558ms message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:17:27Z" - latency: 2.827724ms message: 'network-check-target-ip-10-0-138-196: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:16:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T10:01:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-160-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-160.ec2.internal uid: 3c26dbde-acf3-4a0c-9f5b-6b3b67c58d91 resourceVersion: "79219" uid: ec8accbb-5299-415c-b774-3b294381f3de spec: sourcePod: network-check-source-7bc5b6bf85-gvfp6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T10:07:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 891.319µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:25:27Z" - latency: 1.888801ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T11:25:27Z" - latency: 939.209µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:24:27Z" - latency: 1.720963ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T11:24:27Z" - latency: 1.118223ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:23:27Z" - latency: 1.85026ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T11:23:27Z" - latency: 847.933µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:22:27Z" - latency: 1.663788ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T11:22:27Z" - latency: 1.178729ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T11:21:27Z" - latency: 1.791355ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T11:21:27Z" kind: List metadata: resourceVersion: ""