apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:20:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-188-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-188.ec2.internal uid: 25bccf89-a1bd-4a79-ab66-df0ab896b83c resourceVersion: "95065" uid: be5d42ac-005e-4160-a28d-abe5c78c56db spec: sourcePod: network-check-source-7d88cb55d8-mh7dr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T17:27:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.080795ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:51:22Z" - latency: 941.323µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:22Z" - latency: 923.39µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:22Z" - latency: 899.638µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:48:22Z" - latency: 1.27108ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:47:22Z" - latency: 826.663µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:46:22Z" - latency: 1.107335ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:45:22Z" - latency: 1.021671ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:44:22Z" - latency: 908.071µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:43:22Z" - latency: 1.39884ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:42:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:20:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-188-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-188.ec2.internal uid: 25bccf89-a1bd-4a79-ab66-df0ab896b83c resourceVersion: "94110" uid: 79f6e47b-37a1-420d-be0b-d5c5d3539224 spec: sourcePod: network-check-source-7d88cb55d8-mh7dr targetEndpoint: afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:26:22Z" message: 'load-balancer-api-external: tcp connection to afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.276156ms message: 'load-balancer-api-external: tcp connection to afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:22Z" - latency: 8.870157ms message: 'load-balancer-api-external: resolved host name afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:50:22Z" - latency: 4.907343ms message: 'load-balancer-api-external: tcp connection to afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:22Z" - latency: 10.640872ms message: 'load-balancer-api-external: resolved host name afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:49:22Z" - latency: 4.885329ms message: 'load-balancer-api-external: tcp connection to afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:48:22Z" - latency: 8.307869ms message: 'load-balancer-api-external: resolved host name afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:48:22Z" - latency: 4.451296ms message: 'load-balancer-api-external: tcp connection to afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:47:22Z" - latency: 9.227586ms message: 'load-balancer-api-external: resolved host name afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:47:22Z" - latency: 4.784886ms message: 'load-balancer-api-external: tcp connection to afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:46:22Z" - latency: 8.164089ms message: 'load-balancer-api-external: resolved host name afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:46:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:20:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-188-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-188.ec2.internal uid: 25bccf89-a1bd-4a79-ab66-df0ab896b83c resourceVersion: "94111" uid: 41fdbfcd-8559-43b1-b22d-ab5b3dc7c24b spec: sourcePod: network-check-source-7d88cb55d8-mh7dr targetEndpoint: afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:26:22Z" message: 'load-balancer-api-internal: tcp connection to afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.265632ms message: 'load-balancer-api-internal: tcp connection to afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:22Z" - latency: 8.90117ms message: 'load-balancer-api-internal: resolved host name afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:50:22Z" - latency: 4.916652ms message: 'load-balancer-api-internal: tcp connection to afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:22Z" - latency: 10.581023ms message: 'load-balancer-api-internal: resolved host name afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:49:22Z" - latency: 3.671901ms message: 'load-balancer-api-internal: tcp connection to afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:48:22Z" - latency: 8.247525ms message: 'load-balancer-api-internal: resolved host name afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:48:22Z" - latency: 5.78472ms message: 'load-balancer-api-internal: tcp connection to afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:47:22Z" - latency: 9.10205ms message: 'load-balancer-api-internal: resolved host name afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:47:22Z" - latency: 4.81368ms message: 'load-balancer-api-internal: tcp connection to afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:46:22Z" - latency: 8.076574ms message: 'load-balancer-api-internal: resolved host name afd3bdff287004064be9628906775d0c-001fd88cd0fa6e57.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:46:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:20:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-188-to-network-check-target-ip-10-0-135-188 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-188.ec2.internal uid: 25bccf89-a1bd-4a79-ab66-df0ab896b83c resourceVersion: "95062" uid: e62e13de-e0cf-4a98-98da-1b1bb675ec09 spec: sourcePod: network-check-source-7d88cb55d8-mh7dr targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:27:22Z" message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 792.36µs message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:51:22Z" - latency: 934.163µs message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:22Z" - latency: 1.14234ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:22Z" - latency: 950.284µs message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:48:22Z" - latency: 1.07057ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:47:22Z" - latency: 938.801µs message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:46:22Z" - latency: 1.056468ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:45:22Z" - latency: 985.756µs message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:44:22Z" - latency: 980.869µs message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:43:22Z" - latency: 899.619µs message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:42:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:20:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-188-to-network-check-target-ip-10-0-135-20 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-188.ec2.internal uid: 25bccf89-a1bd-4a79-ab66-df0ab896b83c resourceVersion: "95064" uid: 4f490f27-50ac-4ec0-9a87-e440d22f5120 spec: sourcePod: network-check-source-7d88cb55d8-mh7dr targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:27:22Z" message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.083683ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:51:22Z" - latency: 2.29565ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:22Z" - latency: 2.28274ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:22Z" - latency: 2.275585ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:48:22Z" - latency: 2.339786ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:47:22Z" - latency: 2.260052ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:46:22Z" - latency: 2.520871ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:45:22Z" - latency: 2.357606ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:44:22Z" - latency: 2.569595ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:43:22Z" - latency: 1.998788ms message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:42:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:20:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-188-to-network-check-target-ip-10-0-140-52 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-188.ec2.internal uid: 25bccf89-a1bd-4a79-ab66-df0ab896b83c resourceVersion: "95063" uid: adf15e57-0a82-48db-b880-fbb387bb2c30 spec: sourcePod: network-check-source-7d88cb55d8-mh7dr targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:27:22Z" message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.587808ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:51:22Z" - latency: 2.38818ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:22Z" - latency: 2.804641ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:22Z" - latency: 2.43779ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:48:22Z" - latency: 2.568702ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:47:22Z" - latency: 2.263203ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:46:22Z" - latency: 2.491804ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:45:22Z" - latency: 2.483432ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:44:22Z" - latency: 2.428727ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:43:22Z" - latency: 2.386367ms message: 'network-check-target-ip-10-0-140-52: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:42:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:20:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-188-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-188.ec2.internal uid: 25bccf89-a1bd-4a79-ab66-df0ab896b83c resourceVersion: "94109" uid: 344072b0-c7b7-49db-a925-bbd125568448 spec: sourcePod: network-check-source-7d88cb55d8-mh7dr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T17:26:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 877.533µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:50:22Z" - latency: 1.873287ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:50:22Z" - latency: 937.547µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:49:22Z" - latency: 1.904628ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:49:22Z" - latency: 885.99µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:48:22Z" - latency: 1.599222ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:48:22Z" - latency: 1.522983ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:47:22Z" - latency: 1.975767ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:47:22Z" - latency: 1.106167ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:46:22Z" - latency: 1.691944ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:46:22Z" kind: List metadata: resourceVersion: ""