apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:30:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-105-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-105.ec2.internal uid: 66f74a6c-ca32-4081-b71e-829610f48899 resourceVersion: "18968" uid: 4570f867-34e4-40b3-9304-4718c372877d spec: sourcePod: network-check-source-8894fc9bd-6kv77 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T17:37:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 996.824µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:44:40Z" - latency: 1.146276ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:43:40Z" - latency: 996.062µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:42:40Z" - latency: 1.013816ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:41:40Z" - latency: 1.114056ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:40:40Z" - latency: 998.469µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:39:40Z" - latency: 961.15µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:38:40Z" - latency: 1.386306ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:37:40Z" - latency: 968.022µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:36:40Z" - latency: 817.62µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:35:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:30:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-105-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-105.ec2.internal uid: 66f74a6c-ca32-4081-b71e-829610f48899 resourceVersion: "21034" uid: dafbf62b-7f61-4058-94b6-618e2e4c89db spec: sourcePod: network-check-source-8894fc9bd-6kv77 targetEndpoint: a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T17:36:40Z" message: 'load-balancer-api-external: tcp connection to a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.448405ms message: 'load-balancer-api-external: tcp connection to a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:48:40Z" - latency: 8.017512ms message: 'load-balancer-api-external: resolved host name a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:48:40Z" - latency: 4.324219ms message: 'load-balancer-api-external: tcp connection to a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:47:40Z" - latency: 7.83287ms message: 'load-balancer-api-external: resolved host name a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:47:40Z" - latency: 4.07123ms message: 'load-balancer-api-external: tcp connection to a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:46:40Z" - latency: 7.761329ms message: 'load-balancer-api-external: resolved host name a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:46:40Z" - latency: 5.045059ms message: 'load-balancer-api-external: tcp connection to a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:45:40Z" - latency: 8.335574ms message: 'load-balancer-api-external: resolved host name a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:45:40Z" - latency: 4.509756ms message: 'load-balancer-api-external: tcp connection to a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:44:40Z" - latency: 7.996196ms message: 'load-balancer-api-external: resolved host name a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:44:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:30:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-105-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-105.ec2.internal uid: 66f74a6c-ca32-4081-b71e-829610f48899 resourceVersion: "21035" uid: c5c20bd0-3133-4d7f-bd1a-8d0348b1a101 spec: sourcePod: network-check-source-8894fc9bd-6kv77 targetEndpoint: a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T17:36:40Z" message: 'load-balancer-api-internal: tcp connection to a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.326307ms message: 'load-balancer-api-internal: tcp connection to a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:48:40Z" - latency: 8.006498ms message: 'load-balancer-api-internal: resolved host name a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:48:40Z" - latency: 3.891283ms message: 'load-balancer-api-internal: tcp connection to a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:47:40Z" - latency: 7.891019ms message: 'load-balancer-api-internal: resolved host name a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:47:40Z" - latency: 4.074344ms message: 'load-balancer-api-internal: tcp connection to a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:46:40Z" - latency: 7.728533ms message: 'load-balancer-api-internal: resolved host name a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:46:40Z" - latency: 5.348846ms message: 'load-balancer-api-internal: tcp connection to a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:45:40Z" - latency: 8.442293ms message: 'load-balancer-api-internal: resolved host name a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:45:40Z" - latency: 4.474542ms message: 'load-balancer-api-internal: tcp connection to a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:44:40Z" - latency: 8.022311ms message: 'load-balancer-api-internal: resolved host name a69c88afb31ed463daa3a1b81da1af16-6839b47111a0284b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T17:44:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:30:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-105-to-network-check-target-ip-10-0-135-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-105.ec2.internal uid: 66f74a6c-ca32-4081-b71e-829610f48899 resourceVersion: "18965" uid: 78874a87-30e6-42e6-8019-bd8e2fe457a3 spec: sourcePod: network-check-source-8894fc9bd-6kv77 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:37:40Z" message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.185346ms message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:44:40Z" - latency: 819.04µs message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:43:40Z" - latency: 759.468µs message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:42:40Z" - latency: 820.183µs message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:41:40Z" - latency: 1.337439ms message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:40:40Z" - latency: 866.616µs message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:39:40Z" - latency: 747.413µs message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:38:40Z" - latency: 885.745µs message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:37:40Z" - latency: 803.653µs message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:36:40Z" - latency: 1.026968ms message: 'network-check-target-ip-10-0-135-105: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:35:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:30:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-105-to-network-check-target-ip-10-0-135-127 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-105.ec2.internal uid: 66f74a6c-ca32-4081-b71e-829610f48899 resourceVersion: "18967" uid: 8a64c224-19d6-4c5b-a7df-51ca92b0f154 spec: sourcePod: network-check-source-8894fc9bd-6kv77 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:37:40Z" message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.260565ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:44:40Z" - latency: 2.362639ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:43:40Z" - latency: 2.123649ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:42:40Z" - latency: 2.035101ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:41:40Z" - latency: 2.072088ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:40:40Z" - latency: 1.924571ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:39:40Z" - latency: 1.966559ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:38:40Z" - latency: 2.596668ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:37:40Z" - latency: 1.948505ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:36:40Z" - latency: 1.944475ms message: 'network-check-target-ip-10-0-135-127: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:35:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:30:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-105-to-network-check-target-ip-10-0-137-46 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-105.ec2.internal uid: 66f74a6c-ca32-4081-b71e-829610f48899 resourceVersion: "18966" uid: 61d0bbdb-b18d-4644-b1af-a34022187792 spec: sourcePod: network-check-source-8894fc9bd-6kv77 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T17:37:40Z" message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.176131ms message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:44:40Z" - latency: 2.343516ms message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:43:40Z" - latency: 2.130426ms message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:42:40Z" - latency: 2.17944ms message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:41:40Z" - latency: 2.578008ms message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:40:40Z" - latency: 2.604152ms message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:39:40Z" - latency: 2.114276ms message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:38:40Z" - latency: 2.308984ms message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:37:40Z" - latency: 2.246308ms message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:36:40Z" - latency: 2.14894ms message: 'network-check-target-ip-10-0-137-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:35:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T17:30:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-105-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-105.ec2.internal uid: 66f74a6c-ca32-4081-b71e-829610f48899 resourceVersion: "21033" uid: ad74261a-79e9-492c-baa7-590d7c9ae4f1 spec: sourcePod: network-check-source-8894fc9bd-6kv77 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T17:36:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 794.029µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:48:40Z" - latency: 1.719115ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:48:40Z" - latency: 791.467µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:47:40Z" - latency: 1.67214ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:47:40Z" - latency: 921.594µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:46:40Z" - latency: 1.803254ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:46:40Z" - latency: 837.917µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:45:40Z" - latency: 1.655903ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:45:40Z" - latency: 871.584µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T17:44:40Z" - latency: 1.627227ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T17:44:40Z" kind: List metadata: resourceVersion: ""