apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:09:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-219-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-219.ec2.internal uid: 19686ae8-d1c4-4d8b-8e02-c091537af231 resourceVersion: "53235" uid: ce85e825-0f59-4371-8a57-efd588961268 spec: sourcePod: network-check-source-7d88cb55d8-vlktg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T21:16:20Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 878.579µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:33:20Z" - latency: 844.812µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:32:20Z" - latency: 1.035523ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:31:20Z" - latency: 950.741µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:30:20Z" - latency: 1.006238ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:29:20Z" - latency: 1.068464ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:28:20Z" - latency: 970.429µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:27:20Z" - latency: 963.928µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:26:20Z" - latency: 912.007µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:25:20Z" - latency: 1.324884ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:24:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:09:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-219-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-219.ec2.internal uid: 19686ae8-d1c4-4d8b-8e02-c091537af231 resourceVersion: "53236" uid: 96552899-6af9-4671-8d43-007a3735694b spec: sourcePod: network-check-source-7d88cb55d8-vlktg targetEndpoint: ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T21:15:20Z" message: 'load-balancer-api-external: tcp connection to ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.415531ms message: 'load-balancer-api-external: tcp connection to ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:33:20Z" - latency: 9.785787ms message: 'load-balancer-api-external: resolved host name ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:33:20Z" - latency: 5.18597ms message: 'load-balancer-api-external: tcp connection to ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:32:20Z" - latency: 8.370385ms message: 'load-balancer-api-external: resolved host name ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:32:20Z" - latency: 5.272187ms message: 'load-balancer-api-external: tcp connection to ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:31:20Z" - latency: 8.082433ms message: 'load-balancer-api-external: resolved host name ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:31:20Z" - latency: 4.653134ms message: 'load-balancer-api-external: tcp connection to ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:30:20Z" - latency: 8.295008ms message: 'load-balancer-api-external: resolved host name ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:30:20Z" - latency: 4.383025ms message: 'load-balancer-api-external: tcp connection to ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:29:20Z" - latency: 6.688043ms message: 'load-balancer-api-external: resolved host name ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:29:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:09:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-219-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-219.ec2.internal uid: 19686ae8-d1c4-4d8b-8e02-c091537af231 resourceVersion: "53238" uid: c397b52c-72cc-4b68-9870-2526605d0044 spec: sourcePod: network-check-source-7d88cb55d8-vlktg targetEndpoint: ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T21:15:20Z" message: 'load-balancer-api-internal: tcp connection to ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.531189ms message: 'load-balancer-api-internal: tcp connection to ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:33:20Z" - latency: 9.860738ms message: 'load-balancer-api-internal: resolved host name ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:33:20Z" - latency: 5.154895ms message: 'load-balancer-api-internal: tcp connection to ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:32:20Z" - latency: 8.520719ms message: 'load-balancer-api-internal: resolved host name ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:32:20Z" - latency: 5.470297ms message: 'load-balancer-api-internal: tcp connection to ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:31:20Z" - latency: 8.178766ms message: 'load-balancer-api-internal: resolved host name ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:31:20Z" - latency: 4.405103ms message: 'load-balancer-api-internal: tcp connection to ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:30:20Z" - latency: 8.333403ms message: 'load-balancer-api-internal: resolved host name ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:30:20Z" - latency: 4.448351ms message: 'load-balancer-api-internal: tcp connection to ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:29:20Z" - latency: 6.730363ms message: 'load-balancer-api-internal: resolved host name ae1c247b4234d4fce8ea89d5104529ea-d7343bd6b876e38c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T22:29:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:09:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-219-to-network-check-target-ip-10-0-131-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-219.ec2.internal uid: 19686ae8-d1c4-4d8b-8e02-c091537af231 resourceVersion: "53234" uid: 921cdcc3-ff73-4809-9870-cab10401a664 spec: sourcePod: network-check-source-7d88cb55d8-vlktg targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T21:16:20Z" message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.223203ms message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:33:20Z" - latency: 2.195584ms message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:32:20Z" - latency: 2.329323ms message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:31:20Z" - latency: 2.433961ms message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:30:20Z" - latency: 2.382248ms message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:29:20Z" - latency: 2.213334ms message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:28:20Z" - latency: 2.098613ms message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:27:20Z" - latency: 2.504819ms message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:26:20Z" - latency: 2.321559ms message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:25:20Z" - latency: 2.29989ms message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:24:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:09:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-219-to-network-check-target-ip-10-0-142-219 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-219.ec2.internal uid: 19686ae8-d1c4-4d8b-8e02-c091537af231 resourceVersion: "53231" uid: cb945ce1-6953-4971-ae89-d462285bf02f spec: sourcePod: network-check-source-7d88cb55d8-vlktg targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T21:16:20Z" message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 955.641µs message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:33:20Z" - latency: 898.241µs message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:32:20Z" - latency: 1.050894ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:31:20Z" - latency: 1.194946ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:30:20Z" - latency: 942.742µs message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:29:20Z" - latency: 799.616µs message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:28:20Z" - latency: 874.405µs message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:27:20Z" - latency: 938.52µs message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:26:20Z" - latency: 692.567µs message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:25:20Z" - latency: 1.24359ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:24:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:09:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-219-to-network-check-target-ip-10-0-142-251 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-219.ec2.internal uid: 19686ae8-d1c4-4d8b-8e02-c091537af231 resourceVersion: "53232" uid: 18f95bc9-0bab-468a-8190-e17e3af341f9 spec: sourcePod: network-check-source-7d88cb55d8-vlktg targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T21:16:20Z" message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.125507ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:33:20Z" - latency: 2.21123ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:32:20Z" - latency: 2.166409ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:31:20Z" - latency: 2.124716ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:30:20Z" - latency: 1.972956ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:29:20Z" - latency: 1.899371ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:28:20Z" - latency: 1.945347ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:27:20Z" - latency: 2.450171ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:26:20Z" - latency: 2.310865ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:25:20Z" - latency: 1.963464ms message: 'network-check-target-ip-10-0-142-251: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:24:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T21:09:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-219-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-219.ec2.internal uid: 19686ae8-d1c4-4d8b-8e02-c091537af231 resourceVersion: "53233" uid: ac841bea-c29b-46a1-b731-40bb0e26610e spec: sourcePod: network-check-source-7d88cb55d8-vlktg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T21:15:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 711.896µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:33:20Z" - latency: 1.725857ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:33:20Z" - latency: 1.3177ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:32:20Z" - latency: 1.738548ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:32:20Z" - latency: 794.905µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:31:20Z" - latency: 1.676165ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:31:20Z" - latency: 1.025352ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:30:20Z" - latency: 1.868887ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:30:20Z" - latency: 742.988µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T22:29:20Z" - latency: 1.699707ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T22:29:20Z" kind: List metadata: resourceVersion: ""