apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T00:16:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-192-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-192.ec2.internal uid: 6774484a-9578-4f4b-ad30-f0cd599b5782 resourceVersion: "70054" uid: d50f3a71-5422-4e83-ae63-3142626ae7ba spec: sourcePod: network-check-source-6f8b768455-b6g2z targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T00:23:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.137474ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:51:17Z" - latency: 909.02µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:50:17Z" - latency: 1.838244ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:49:17Z" - latency: 1.267741ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:48:17Z" - latency: 1.068528ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:47:17Z" - latency: 930.564µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:46:17Z" - latency: 1.500522ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:45:17Z" - latency: 1.106225ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:44:17Z" - latency: 1.245631ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:43:17Z" - latency: 1.078907ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:42:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T00:16:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-192-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-192.ec2.internal uid: 6774484a-9578-4f4b-ad30-f0cd599b5782 resourceVersion: "71040" uid: df37ee80-41e9-40cb-88df-ac1222c078da spec: sourcePod: network-check-source-6f8b768455-b6g2z targetEndpoint: a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T00:22:17Z" message: 'load-balancer-api-external: tcp connection to a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.207436ms message: 'load-balancer-api-external: tcp connection to a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:52:17Z" - latency: 6.147988ms message: 'load-balancer-api-external: resolved host name a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T00:52:17Z" - latency: 5.113858ms message: 'load-balancer-api-external: tcp connection to a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:51:17Z" - latency: 6.964498ms message: 'load-balancer-api-external: resolved host name a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T00:51:17Z" - latency: 5.407235ms message: 'load-balancer-api-external: tcp connection to a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:50:17Z" - latency: 7.174886ms message: 'load-balancer-api-external: resolved host name a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T00:50:17Z" - latency: 5.029552ms message: 'load-balancer-api-external: tcp connection to a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:49:17Z" - latency: 8.22803ms message: 'load-balancer-api-external: resolved host name a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T00:49:17Z" - latency: 2.899668ms message: 'load-balancer-api-external: tcp connection to a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:48:17Z" - latency: 6.75798ms message: 'load-balancer-api-external: resolved host name a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T00:48:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T00:16:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-192-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-192.ec2.internal uid: 6774484a-9578-4f4b-ad30-f0cd599b5782 resourceVersion: "71041" uid: 91973b05-6f24-4d50-96c3-10f02717c2c6 spec: sourcePod: network-check-source-6f8b768455-b6g2z targetEndpoint: a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T00:22:17Z" message: 'load-balancer-api-internal: tcp connection to a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.87275ms message: 'load-balancer-api-internal: tcp connection to a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:52:17Z" - latency: 6.1272ms message: 'load-balancer-api-internal: resolved host name a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T00:52:17Z" - latency: 5.348317ms message: 'load-balancer-api-internal: tcp connection to a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:51:17Z" - latency: 6.91579ms message: 'load-balancer-api-internal: resolved host name a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T00:51:17Z" - latency: 5.070145ms message: 'load-balancer-api-internal: tcp connection to a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:50:17Z" - latency: 7.259324ms message: 'load-balancer-api-internal: resolved host name a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T00:50:17Z" - latency: 5.068364ms message: 'load-balancer-api-internal: tcp connection to a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:49:17Z" - latency: 8.399599ms message: 'load-balancer-api-internal: resolved host name a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T00:49:17Z" - latency: 4.660563ms message: 'load-balancer-api-internal: tcp connection to a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:48:17Z" - latency: 6.706088ms message: 'load-balancer-api-internal: resolved host name a40b851e263de4b1380ec6fe8a601e31-cff530c1d4a2d4c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T00:48:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T00:16:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-192-to-network-check-target-ip-10-0-135-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-192.ec2.internal uid: 6774484a-9578-4f4b-ad30-f0cd599b5782 resourceVersion: "70051" uid: 586c8f9f-d14b-4ad2-a296-175128d93fde spec: sourcePod: network-check-source-6f8b768455-b6g2z targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T00:23:17Z" message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 858.825µs message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:51:17Z" - latency: 901.173µs message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:50:17Z" - latency: 1.082983ms message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:49:17Z" - latency: 1.2667ms message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:48:17Z" - latency: 1.499715ms message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:47:17Z" - latency: 1.104218ms message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:46:17Z" - latency: 1.191791ms message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:45:17Z" - latency: 977.562µs message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:44:17Z" - latency: 903.437µs message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:43:17Z" - latency: 1.012268ms message: 'network-check-target-ip-10-0-135-192: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:42:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T00:16:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-192-to-network-check-target-ip-10-0-138-211 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-192.ec2.internal uid: 6774484a-9578-4f4b-ad30-f0cd599b5782 resourceVersion: "70053" uid: 65647a63-61fa-4a8c-89fa-21d0a75321c7 spec: sourcePod: network-check-source-6f8b768455-b6g2z targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T00:23:17Z" message: 'network-check-target-ip-10-0-138-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.786079ms message: 'network-check-target-ip-10-0-138-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:51:17Z" - latency: 2.148537ms message: 'network-check-target-ip-10-0-138-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:50:17Z" - latency: 3.003349ms message: 'network-check-target-ip-10-0-138-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:49:17Z" - latency: 2.209357ms message: 'network-check-target-ip-10-0-138-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:48:17Z" - latency: 2.150585ms message: 'network-check-target-ip-10-0-138-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:47:17Z" - latency: 2.410778ms message: 'network-check-target-ip-10-0-138-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:46:17Z" - latency: 2.56023ms message: 'network-check-target-ip-10-0-138-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:45:17Z" - latency: 2.843692ms message: 'network-check-target-ip-10-0-138-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:44:17Z" - latency: 2.503083ms message: 'network-check-target-ip-10-0-138-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:43:17Z" - latency: 2.681172ms message: 'network-check-target-ip-10-0-138-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:42:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T00:16:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-192-to-network-check-target-ip-10-0-139-27 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-192.ec2.internal uid: 6774484a-9578-4f4b-ad30-f0cd599b5782 resourceVersion: "70052" uid: fd77174f-0430-43ef-aec7-4036e4dfee94 spec: sourcePod: network-check-source-6f8b768455-b6g2z targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T00:23:17Z" message: 'network-check-target-ip-10-0-139-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.377756ms message: 'network-check-target-ip-10-0-139-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:51:17Z" - latency: 2.067904ms message: 'network-check-target-ip-10-0-139-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:50:17Z" - latency: 2.577213ms message: 'network-check-target-ip-10-0-139-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:49:17Z" - latency: 2.395306ms message: 'network-check-target-ip-10-0-139-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:48:17Z" - latency: 2.694429ms message: 'network-check-target-ip-10-0-139-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:47:17Z" - latency: 2.27861ms message: 'network-check-target-ip-10-0-139-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:46:17Z" - latency: 2.537772ms message: 'network-check-target-ip-10-0-139-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:45:17Z" - latency: 2.474638ms message: 'network-check-target-ip-10-0-139-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:44:17Z" - latency: 2.273782ms message: 'network-check-target-ip-10-0-139-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:43:17Z" - latency: 2.411003ms message: 'network-check-target-ip-10-0-139-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:42:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T00:16:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-192-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-192.ec2.internal uid: 6774484a-9578-4f4b-ad30-f0cd599b5782 resourceVersion: "71039" uid: c356b456-9a85-45d3-84c5-13a8a4f249fe spec: sourcePod: network-check-source-6f8b768455-b6g2z targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T00:22:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 861.469µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:52:17Z" - latency: 1.866565ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T00:52:17Z" - latency: 1.122678ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:51:17Z" - latency: 2.026554ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T00:51:17Z" - latency: 1.044599ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:50:17Z" - latency: 1.865702ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T00:50:17Z" - latency: 1.278833ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:49:17Z" - latency: 2.352175ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T00:49:17Z" - latency: 955.722µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T00:48:17Z" - latency: 1.947971ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T00:48:17Z" kind: List metadata: resourceVersion: ""