apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T09:12:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-16-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-16.ec2.internal uid: eabc227d-8792-4ff5-8091-3fa801d53058 resourceVersion: "56727" uid: 5fac1889-8c45-4d02-901c-79bbe420ee91 spec: sourcePod: network-check-source-869dcfcdcd-z95sx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T09:20: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.220701ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:48:00Z" - latency: 1.258927ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:47:00Z" - latency: 1.318339ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:46:00Z" - latency: 1.023053ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:45:00Z" - latency: 905.138µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:44:00Z" - latency: 1.022284ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:43:00Z" - latency: 1.477988ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:42:00Z" - latency: 947.795µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:41:00Z" - latency: 1.193085ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:40:00Z" - latency: 1.117621ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:39:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T09:12:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-16-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-16.ec2.internal uid: eabc227d-8792-4ff5-8091-3fa801d53058 resourceVersion: "57736" uid: 45de15e4-8c22-4b23-916a-549a8bbf473a spec: sourcePod: network-check-source-869dcfcdcd-z95sx targetEndpoint: a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T09:19:00Z" message: 'load-balancer-api-external: tcp connection to a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.269687ms message: 'load-balancer-api-external: tcp connection to a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:49:00Z" - latency: 10.395298ms message: 'load-balancer-api-external: resolved host name a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:49:00Z" - latency: 4.400778ms message: 'load-balancer-api-external: tcp connection to a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:48:00Z" - latency: 9.983417ms message: 'load-balancer-api-external: resolved host name a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:48:00Z" - latency: 5.109399ms message: 'load-balancer-api-external: tcp connection to a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:47:00Z" - latency: 9.177799ms message: 'load-balancer-api-external: resolved host name a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:47:00Z" - latency: 5.541049ms message: 'load-balancer-api-external: tcp connection to a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:46:00Z" - latency: 9.270177ms message: 'load-balancer-api-external: resolved host name a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:46:00Z" - latency: 4.982772ms message: 'load-balancer-api-external: tcp connection to a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:45:00Z" - latency: 8.377662ms message: 'load-balancer-api-external: resolved host name a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:45:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T09:12:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-16-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-16.ec2.internal uid: eabc227d-8792-4ff5-8091-3fa801d53058 resourceVersion: "57737" uid: 00c2e4ae-e1fa-44d4-a78e-01af92f5584f spec: sourcePod: network-check-source-869dcfcdcd-z95sx targetEndpoint: a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T09:19:00Z" message: 'load-balancer-api-internal: tcp connection to a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.639397ms message: 'load-balancer-api-internal: tcp connection to a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:49:00Z" - latency: 10.357993ms message: 'load-balancer-api-internal: resolved host name a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:49:00Z" - latency: 24.730291ms message: 'load-balancer-api-internal: tcp connection to a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:48:00Z" - latency: 10.012056ms message: 'load-balancer-api-internal: resolved host name a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:48:00Z" - latency: 4.59347ms message: 'load-balancer-api-internal: tcp connection to a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:47:00Z" - latency: 9.10363ms message: 'load-balancer-api-internal: resolved host name a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:47:00Z" - latency: 5.553614ms message: 'load-balancer-api-internal: tcp connection to a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:46:00Z" - latency: 9.221373ms message: 'load-balancer-api-internal: resolved host name a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:46:00Z" - latency: 6.028653ms message: 'load-balancer-api-internal: tcp connection to a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:45:00Z" - latency: 8.319844ms message: 'load-balancer-api-internal: resolved host name a5b688bd150204e739aad5856cf83187-8c053c53195d13cb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T09:45:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T09:12:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-16-to-network-check-target-ip-10-0-130-231 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-16.ec2.internal uid: eabc227d-8792-4ff5-8091-3fa801d53058 resourceVersion: "56724" uid: f3a710ba-9912-4bd3-bdf6-e96587194626 spec: sourcePod: network-check-source-869dcfcdcd-z95sx targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T09:20:00Z" message: 'network-check-target-ip-10-0-130-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.182205ms message: 'network-check-target-ip-10-0-130-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:48:00Z" - latency: 2.860355ms message: 'network-check-target-ip-10-0-130-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:47:00Z" - latency: 2.394639ms message: 'network-check-target-ip-10-0-130-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:46:00Z" - latency: 2.248759ms message: 'network-check-target-ip-10-0-130-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:45:00Z" - latency: 2.572562ms message: 'network-check-target-ip-10-0-130-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:44:00Z" - latency: 2.5566ms message: 'network-check-target-ip-10-0-130-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:43:00Z" - latency: 2.70379ms message: 'network-check-target-ip-10-0-130-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:42:00Z" - latency: 2.325706ms message: 'network-check-target-ip-10-0-130-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:41:00Z" - latency: 2.291655ms message: 'network-check-target-ip-10-0-130-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:40:00Z" - latency: 2.292371ms message: 'network-check-target-ip-10-0-130-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:39:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T09:12:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-16-to-network-check-target-ip-10-0-134-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-16.ec2.internal uid: eabc227d-8792-4ff5-8091-3fa801d53058 resourceVersion: "56725" uid: 0b898cf9-f3e8-4891-ab4b-9e8185271538 spec: sourcePod: network-check-source-869dcfcdcd-z95sx targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T09:20:00Z" message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.57677ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:48:00Z" - latency: 1.465054ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:47:00Z" - latency: 1.548167ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:46:00Z" - latency: 1.027239ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:45:00Z" - latency: 1.063618ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:44:00Z" - latency: 957.92µs message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:43:00Z" - latency: 1.979707ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:42:00Z" - latency: 1.441253ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:41:00Z" - latency: 1.238071ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:40:00Z" - latency: 1.460739ms message: 'network-check-target-ip-10-0-134-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:39:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T09:12:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-16-to-network-check-target-ip-10-0-137-79 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-16.ec2.internal uid: eabc227d-8792-4ff5-8091-3fa801d53058 resourceVersion: "56726" uid: 1206d801-7f76-490b-b48c-7a1c7addc745 spec: sourcePod: network-check-source-869dcfcdcd-z95sx targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T09:20:00Z" message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.52177ms message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:48:00Z" - latency: 2.374837ms message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:47:00Z" - latency: 2.259578ms message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:46:00Z" - latency: 2.279325ms message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:45:00Z" - latency: 2.189217ms message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:44:00Z" - latency: 1.909878ms message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:43:00Z" - latency: 2.680863ms message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:42:00Z" - latency: 2.378792ms message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:41:00Z" - latency: 2.490278ms message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:40:00Z" - latency: 2.58229ms message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:39:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T09:12:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-16-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-16.ec2.internal uid: eabc227d-8792-4ff5-8091-3fa801d53058 resourceVersion: "57735" uid: 4b769296-e2f7-4ff7-8b8d-fae58a749d01 spec: sourcePod: network-check-source-869dcfcdcd-z95sx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T09:19:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.343714ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:49:00Z" - latency: 1.95567ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T09:49:00Z" - latency: 1.5466ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:48:00Z" - latency: 1.940636ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T09:48:00Z" - latency: 994.845µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:47:00Z" - latency: 2.006554ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T09:47:00Z" - latency: 1.314082ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:46:00Z" - latency: 1.673264ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T09:46:00Z" - latency: 1.135976ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T09:45:00Z" - latency: 1.766313ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T09:45:00Z" kind: List metadata: resourceVersion: ""