apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T12:31:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-96-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-96.ec2.internal uid: 70bb47bf-d6d5-46b4-8293-be1d1e435457 resourceVersion: "78893" uid: dd0ec7e9-4e08-4298-b0f6-bf816acdeb4d spec: sourcePod: network-check-source-65bdbbff45-xzs9g targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T12:38:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 835.778µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:27:38Z" - latency: 1.33829ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:26:38Z" - latency: 1.03376ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:25:38Z" - latency: 1.383416ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:24:38Z" - latency: 1.496756ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:23:38Z" - latency: 1.13035ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:22:38Z" - latency: 1.313196ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:21:38Z" - latency: 1.121932ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:20:38Z" - latency: 1.035917ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:19:38Z" - latency: 1.206097ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:18:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T12:31:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-96-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-96.ec2.internal uid: 70bb47bf-d6d5-46b4-8293-be1d1e435457 resourceVersion: "76938" uid: 24d10734-b2f0-4595-abe7-bcd3501b0dae spec: sourcePod: network-check-source-65bdbbff45-xzs9g targetEndpoint: a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T12:37:38Z" message: 'load-balancer-api-external: tcp connection to a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.936407ms message: 'load-balancer-api-external: tcp connection to a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:25:38Z" - latency: 7.439956ms message: 'load-balancer-api-external: resolved host name a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T13:25:38Z" - latency: 4.665863ms message: 'load-balancer-api-external: tcp connection to a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:24:38Z" - latency: 9.402591ms message: 'load-balancer-api-external: resolved host name a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T13:24:38Z" - latency: 4.638286ms message: 'load-balancer-api-external: tcp connection to a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:23:38Z" - latency: 7.839282ms message: 'load-balancer-api-external: resolved host name a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T13:23:38Z" - latency: 5.236452ms message: 'load-balancer-api-external: tcp connection to a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:22:38Z" - latency: 7.807877ms message: 'load-balancer-api-external: resolved host name a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T13:22:38Z" - latency: 5.386108ms message: 'load-balancer-api-external: tcp connection to a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:21:38Z" - latency: 10.649937ms message: 'load-balancer-api-external: resolved host name a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T13:21:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T12:31:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-96-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-96.ec2.internal uid: 70bb47bf-d6d5-46b4-8293-be1d1e435457 resourceVersion: "76939" uid: 285f92c1-01a3-4db8-8453-4745d622fef4 spec: sourcePod: network-check-source-65bdbbff45-xzs9g targetEndpoint: a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T12:37:38Z" message: 'load-balancer-api-internal: tcp connection to a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.91146ms message: 'load-balancer-api-internal: tcp connection to a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:25:38Z" - latency: 7.373718ms message: 'load-balancer-api-internal: resolved host name a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T13:25:38Z" - latency: 4.912794ms message: 'load-balancer-api-internal: tcp connection to a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:24:38Z" - latency: 9.456621ms message: 'load-balancer-api-internal: resolved host name a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T13:24:38Z" - latency: 4.508183ms message: 'load-balancer-api-internal: tcp connection to a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:23:38Z" - latency: 7.808968ms message: 'load-balancer-api-internal: resolved host name a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T13:23:38Z" - latency: 5.280298ms message: 'load-balancer-api-internal: tcp connection to a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:22:38Z" - latency: 7.77698ms message: 'load-balancer-api-internal: resolved host name a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T13:22:38Z" - latency: 5.359804ms message: 'load-balancer-api-internal: tcp connection to a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:21:38Z" - latency: 10.823753ms message: 'load-balancer-api-internal: resolved host name a788eb0c9f29c4c8680f682965398b75-683ef0471382d98c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T13:21:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T12:31:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-96-to-network-check-target-ip-10-0-132-243 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-96.ec2.internal uid: 70bb47bf-d6d5-46b4-8293-be1d1e435457 resourceVersion: "78892" uid: 339af983-f3ff-4ae5-bb1e-8adc34f11c0d spec: sourcePod: network-check-source-65bdbbff45-xzs9g targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-04T12:38:38Z" message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.138907ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:27:38Z" - latency: 2.459796ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:26:38Z" - latency: 2.427289ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:25:38Z" - latency: 2.356956ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:24:38Z" - latency: 2.338446ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:23:38Z" - latency: 2.237335ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:22:38Z" - latency: 2.134836ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:21:38Z" - latency: 2.137711ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:20:38Z" - latency: 2.350918ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:19:38Z" - latency: 2.666468ms message: 'network-check-target-ip-10-0-132-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:18:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T12:31:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-96-to-network-check-target-ip-10-0-132-96 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-96.ec2.internal uid: 70bb47bf-d6d5-46b4-8293-be1d1e435457 resourceVersion: "78890" uid: 77d12f57-8ed3-4431-9792-6b41cc91a420 spec: sourcePod: network-check-source-65bdbbff45-xzs9g targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-04T12:38:38Z" message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.02075ms message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:27:38Z" - latency: 1.730155ms message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:26:38Z" - latency: 1.1421ms message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:25:38Z" - latency: 1.680396ms message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:24:38Z" - latency: 1.246358ms message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:23:38Z" - latency: 968.729µs message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:22:38Z" - latency: 988.153µs message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:21:38Z" - latency: 771.617µs message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:20:38Z" - latency: 906.952µs message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:19:38Z" - latency: 1.079284ms message: 'network-check-target-ip-10-0-132-96: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:18:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T12:31:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-96-to-network-check-target-ip-10-0-136-46 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-96.ec2.internal uid: 70bb47bf-d6d5-46b4-8293-be1d1e435457 resourceVersion: "78891" uid: f291c563-ea5a-4ca4-9952-1d50c5cc6ae3 spec: sourcePod: network-check-source-65bdbbff45-xzs9g targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T12:38:38Z" message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.826891ms message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:27:38Z" - latency: 2.12532ms message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:26:38Z" - latency: 2.127646ms message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:25:38Z" - latency: 2.062474ms message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:24:38Z" - latency: 2.179642ms message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:23:38Z" - latency: 2.085336ms message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:22:38Z" - latency: 2.347769ms message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:21:38Z" - latency: 2.089287ms message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:20:38Z" - latency: 2.397663ms message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:19:38Z" - latency: 2.172142ms message: 'network-check-target-ip-10-0-136-46: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:18:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T12:31:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-96-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-96.ec2.internal uid: 70bb47bf-d6d5-46b4-8293-be1d1e435457 resourceVersion: "76937" uid: 44d8bb97-43cc-4ded-a3a7-0e5344eb9646 spec: sourcePod: network-check-source-65bdbbff45-xzs9g targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T12:37:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 966.584µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:25:38Z" - latency: 2.049738ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T13:25:38Z" - latency: 1.153389ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:24:38Z" - latency: 1.774903ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T13:24:38Z" - latency: 1.184906ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:23:38Z" - latency: 2.133616ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T13:23:38Z" - latency: 1.013748ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:22:38Z" - latency: 2.144865ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T13:22:38Z" - latency: 938.224µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T13:21:38Z" - latency: 1.889912ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T13:21:38Z" kind: List metadata: resourceVersion: ""