apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:32:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-48-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-48.ec2.internal uid: 9eea0a85-b122-4ef7-8f3a-4515f3510b09 resourceVersion: "32563" uid: 480348c0-c1e4-4d96-8a8b-59b4aa33913d spec: sourcePod: network-check-source-8894fc9bd-7jkld targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T21:39:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 883.189µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:14:51Z" - latency: 829.692µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:51Z" - latency: 927.447µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:51Z" - latency: 827.059µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:51Z" - latency: 1.169268ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:51Z" - latency: 1.061683ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:51Z" - latency: 896.971µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:51Z" - latency: 1.050511ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:07:51Z" - latency: 995.329µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:51Z" - latency: 981.255µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:32:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-48-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-48.ec2.internal uid: 9eea0a85-b122-4ef7-8f3a-4515f3510b09 resourceVersion: "32565" uid: c0fb0592-418e-4625-9053-8edb0ad512c6 spec: sourcePod: network-check-source-8894fc9bd-7jkld targetEndpoint: a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:38:51Z" message: 'load-balancer-api-external: tcp connection to a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.049735ms message: 'load-balancer-api-external: tcp connection to a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:14:51Z" - latency: 14.495547ms message: 'load-balancer-api-external: resolved host name a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:14:51Z" - latency: 5.250926ms message: 'load-balancer-api-external: tcp connection to a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:51Z" - latency: 8.383395ms message: 'load-balancer-api-external: resolved host name a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:13:51Z" - latency: 8.156282ms message: 'load-balancer-api-external: tcp connection to a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:51Z" - latency: 8.08733ms message: 'load-balancer-api-external: resolved host name a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:12:51Z" - latency: 5.310105ms message: 'load-balancer-api-external: tcp connection to a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:51Z" - latency: 8.126737ms message: 'load-balancer-api-external: resolved host name a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:11:51Z" - latency: 5.140707ms message: 'load-balancer-api-external: tcp connection to a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:51Z" - latency: 7.710256ms message: 'load-balancer-api-external: resolved host name a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:10:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:32:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-48-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-48.ec2.internal uid: 9eea0a85-b122-4ef7-8f3a-4515f3510b09 resourceVersion: "32564" uid: 62827154-6e3e-45c6-83e9-5ce7908dc0c8 spec: sourcePod: network-check-source-8894fc9bd-7jkld targetEndpoint: a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:38:51Z" message: 'load-balancer-api-internal: tcp connection to a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.43002ms message: 'load-balancer-api-internal: tcp connection to a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:14:51Z" - latency: 14.509501ms message: 'load-balancer-api-internal: resolved host name a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:14:51Z" - latency: 5.262484ms message: 'load-balancer-api-internal: tcp connection to a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:51Z" - latency: 8.334705ms message: 'load-balancer-api-internal: resolved host name a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:13:51Z" - latency: 14.267079ms message: 'load-balancer-api-internal: tcp connection to a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:51Z" - latency: 8.018997ms message: 'load-balancer-api-internal: resolved host name a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:12:51Z" - latency: 5.350886ms message: 'load-balancer-api-internal: tcp connection to a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:51Z" - latency: 8.1087ms message: 'load-balancer-api-internal: resolved host name a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:11:51Z" - latency: 5.11977ms message: 'load-balancer-api-internal: tcp connection to a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:51Z" - latency: 7.762592ms message: 'load-balancer-api-internal: resolved host name a1a9170875bca43c5ae4071bd058bbe7-1f34f369d4bddbbd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:10:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:32:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-48-to-network-check-target-ip-10-0-133-209 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-48.ec2.internal uid: 9eea0a85-b122-4ef7-8f3a-4515f3510b09 resourceVersion: "32560" uid: 670a85d4-a323-4d3f-a8a0-a5cbdffdf139 spec: sourcePod: network-check-source-8894fc9bd-7jkld targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:39:51Z" message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.109806ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:14:51Z" - latency: 2.26588ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:51Z" - latency: 2.245163ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:51Z" - latency: 2.022382ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:51Z" - latency: 2.249094ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:51Z" - latency: 2.167931ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:51Z" - latency: 2.080395ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:51Z" - latency: 2.159538ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:07:51Z" - latency: 2.115162ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:51Z" - latency: 2.096307ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:32:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-48-to-network-check-target-ip-10-0-133-48 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-48.ec2.internal uid: 9eea0a85-b122-4ef7-8f3a-4515f3510b09 resourceVersion: "32558" uid: 644c94e1-a594-4ff0-a25c-e6c9e04c91de spec: sourcePod: network-check-source-8894fc9bd-7jkld targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:39:51Z" message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.194859ms message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:14:51Z" - latency: 997.094µs message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:51Z" - latency: 900.74µs message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:51Z" - latency: 877.424µs message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:51Z" - latency: 1.532487ms message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:51Z" - latency: 834.282µs message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:51Z" - latency: 801.475µs message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:51Z" - latency: 826.187µs message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:07:51Z" - latency: 840.038µs message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:51Z" - latency: 713.417µs message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:32:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-48-to-network-check-target-ip-10-0-136-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-48.ec2.internal uid: 9eea0a85-b122-4ef7-8f3a-4515f3510b09 resourceVersion: "32561" uid: 299e59c2-cb0b-4f25-b993-45c60d8555bf spec: sourcePod: network-check-source-8894fc9bd-7jkld targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:39:51Z" message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.514016ms message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:14:51Z" - latency: 1.926053ms message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:51Z" - latency: 2.264427ms message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:51Z" - latency: 2.247213ms message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:51Z" - latency: 2.313974ms message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:51Z" - latency: 2.234173ms message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:09:51Z" - latency: 2.226657ms message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:08:51Z" - latency: 2.515069ms message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:07:51Z" - latency: 2.206974ms message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:06:51Z" - latency: 2.042348ms message: 'network-check-target-ip-10-0-136-201: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:05:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:32:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-48-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-48.ec2.internal uid: 9eea0a85-b122-4ef7-8f3a-4515f3510b09 resourceVersion: "32562" uid: f46235e5-a9a5-4e82-b2dd-3681ea1fb30c spec: sourcePod: network-check-source-8894fc9bd-7jkld targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T21:38:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 865.275µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:14:51Z" - latency: 1.989658ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:14:51Z" - latency: 804.416µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:13:51Z" - latency: 1.642395ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:13:51Z" - latency: 848.815µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:12:51Z" - latency: 1.554865ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:12:51Z" - latency: 804.49µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:11:51Z" - latency: 1.550436ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:11:51Z" - latency: 781.244µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:10:51Z" - latency: 2.017462ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:10:51Z" kind: List metadata: resourceVersion: ""