apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:56:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-47-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-47.ec2.internal uid: dc49f853-0433-4d44-9f06-925872ef27df resourceVersion: "24315" uid: 004df40d-ca95-4063-b9bd-f35bd104912b spec: sourcePod: network-check-source-8894fc9bd-4tw8h targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T17:04:00Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.186941ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:04:00Z" - latency: 1.225001ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:03:00Z" - latency: 1.190642ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:02:00Z" - latency: 1.438006ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:01:00Z" - latency: 931.896µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:00:00Z" - latency: 1.188145ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:59:00Z" - latency: 1.169584ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:58:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:56:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-47-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-47.ec2.internal uid: dc49f853-0433-4d44-9f06-925872ef27df resourceVersion: "22998" uid: fbef1040-bd06-43a7-8a5b-b0df6566ac42 spec: sourcePod: network-check-source-8894fc9bd-4tw8h targetEndpoint: a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T17:03:00Z" message: 'load-balancer-api-external: tcp connection to a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.485963ms message: 'load-balancer-api-external: tcp connection to a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:03:00Z" - latency: 8.018479ms message: 'load-balancer-api-external: resolved host name a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:03:00Z" - latency: 2.937196ms message: 'load-balancer-api-external: tcp connection to a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:02:00Z" - latency: 6.516221ms message: 'load-balancer-api-external: resolved host name a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:02:00Z" - latency: 4.661502ms message: 'load-balancer-api-external: tcp connection to a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:01:00Z" - latency: 6.573612ms message: 'load-balancer-api-external: resolved host name a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:01:00Z" - latency: 5.659952ms message: 'load-balancer-api-external: tcp connection to a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:00:00Z" - latency: 6.5347ms message: 'load-balancer-api-external: resolved host name a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:00:00Z" - latency: 3.461516ms message: 'load-balancer-api-external: tcp connection to a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:59:00Z" - latency: 6.62432ms message: 'load-balancer-api-external: resolved host name a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:59:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:56:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-47-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-47.ec2.internal uid: dc49f853-0433-4d44-9f06-925872ef27df resourceVersion: "22999" uid: debb441c-7a74-47b9-903a-297c6dc3086b spec: sourcePod: network-check-source-8894fc9bd-4tw8h targetEndpoint: a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T17:03:00Z" message: 'load-balancer-api-internal: tcp connection to a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.51934ms message: 'load-balancer-api-internal: tcp connection to a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:03:00Z" - latency: 7.954879ms message: 'load-balancer-api-internal: resolved host name a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:03:00Z" - latency: 3.293147ms message: 'load-balancer-api-internal: tcp connection to a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:02:00Z" - latency: 6.550713ms message: 'load-balancer-api-internal: resolved host name a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:02:00Z" - latency: 4.64762ms message: 'load-balancer-api-internal: tcp connection to a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:01:00Z" - latency: 6.638387ms message: 'load-balancer-api-internal: resolved host name a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:01:00Z" - latency: 5.237831ms message: 'load-balancer-api-internal: tcp connection to a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:00:00Z" - latency: 6.565129ms message: 'load-balancer-api-internal: resolved host name a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:00:00Z" - latency: 3.44373ms message: 'load-balancer-api-internal: tcp connection to a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:59:00Z" - latency: 6.600145ms message: 'load-balancer-api-internal: resolved host name a2832a68c14bc410f9ce7ac2ab66b1cb-070d4943019f8e31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:59:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:56:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-47-to-network-check-target-ip-10-0-132-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-47.ec2.internal uid: dc49f853-0433-4d44-9f06-925872ef27df resourceVersion: "24314" uid: 26f0e5fa-2d28-4f3e-ae74-fdf2585366cf spec: sourcePod: network-check-source-8894fc9bd-4tw8h targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:04:00Z" message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.529106ms message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:04:00Z" - latency: 1.934035ms message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:03:00Z" - latency: 1.990385ms message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:02:00Z" - latency: 2.264626ms message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:01:00Z" - latency: 1.739226ms message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:00:00Z" - latency: 1.99791ms message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:59:00Z" - latency: 2.011679ms message: 'network-check-target-ip-10-0-132-199: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:58:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:56:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-47-to-network-check-target-ip-10-0-134-88 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-47.ec2.internal uid: dc49f853-0433-4d44-9f06-925872ef27df resourceVersion: "24313" uid: e07a70a3-6c0c-4b45-958a-f16c47192817 spec: sourcePod: network-check-source-8894fc9bd-4tw8h targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:04:00Z" message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.786444ms message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:04:00Z" - latency: 1.946539ms message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:03:00Z" - latency: 1.677748ms message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:02:00Z" - latency: 2.113144ms message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:01:00Z" - latency: 1.846883ms message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:00:00Z" - latency: 2.05139ms message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:59:00Z" - latency: 2.206886ms message: 'network-check-target-ip-10-0-134-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:58:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:56:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-47-to-network-check-target-ip-10-0-138-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-47.ec2.internal uid: dc49f853-0433-4d44-9f06-925872ef27df resourceVersion: "24312" uid: e807bf51-b973-448d-9a69-13bc299baaec spec: sourcePod: network-check-source-8894fc9bd-4tw8h targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:04:00Z" message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.32473ms message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:04:00Z" - latency: 1.843164ms message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:03:00Z" - latency: 880.74µs message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:02:00Z" - latency: 986.885µs message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:01:00Z" - latency: 721.65µs message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:00:00Z" - latency: 984.199µs message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:59:00Z" - latency: 1.208236ms message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:58:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:56:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-47-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-47.ec2.internal uid: dc49f853-0433-4d44-9f06-925872ef27df resourceVersion: "22997" uid: 5d737f2a-f39a-43a3-9508-ba20c9dc164d spec: sourcePod: network-check-source-8894fc9bd-4tw8h targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T17:03:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 894.239µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:03:00Z" - latency: 1.960818ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:03:00Z" - latency: 844.032µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:02:00Z" - latency: 1.826441ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:02:00Z" - latency: 875.461µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:01:00Z" - latency: 1.921994ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:01:00Z" - latency: 737.242µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:00:00Z" - latency: 1.604473ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:00:00Z" - latency: 783.123µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:59:00Z" - latency: 2.05077ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T16:59:00Z" kind: List metadata: resourceVersion: ""