apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:52:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-205-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-205.ec2.internal uid: 6453ce49-e0df-46ea-b0e6-c4ecaf05a6d2 resourceVersion: "21965" uid: 102f5fbb-673b-4397-83bb-f490a6f3695a spec: sourcePod: network-check-source-869dcfcdcd-rzhqt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-13T18:59:41Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 794.772µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:13:41Z" - latency: 913.165µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:12:41Z" - latency: 1.187026ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:11:41Z" - latency: 1.181419ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:10:41Z" - latency: 911.169µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:09:41Z" - latency: 829.319µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:08:41Z" - latency: 1.270647ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:07:41Z" - latency: 1.022819ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:06:41Z" - latency: 1.060829ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:05:41Z" - latency: 883.647µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:52:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-205-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-205.ec2.internal uid: 6453ce49-e0df-46ea-b0e6-c4ecaf05a6d2 resourceVersion: "20341" uid: 35b650c6-c8a3-4dc7-9642-f1438e25be3d spec: sourcePod: network-check-source-869dcfcdcd-rzhqt targetEndpoint: a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T18:58:41Z" message: 'load-balancer-api-external: tcp connection to a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.414367ms message: 'load-balancer-api-external: tcp connection to a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:10:41Z" - latency: 10.821765ms message: 'load-balancer-api-external: resolved host name a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:10:41Z" - latency: 5.175975ms message: 'load-balancer-api-external: tcp connection to a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:09:41Z" - latency: 7.807413ms message: 'load-balancer-api-external: resolved host name a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:09:41Z" - latency: 5.618366ms message: 'load-balancer-api-external: tcp connection to a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:08:41Z" - latency: 7.84599ms message: 'load-balancer-api-external: resolved host name a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:08:41Z" - latency: 4.998939ms message: 'load-balancer-api-external: tcp connection to a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:07:41Z" - latency: 8.784741ms message: 'load-balancer-api-external: resolved host name a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:07:41Z" - latency: 5.559685ms message: 'load-balancer-api-external: tcp connection to a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:06:41Z" - latency: 14.288052ms message: 'load-balancer-api-external: resolved host name a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:06:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:52:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-205-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-205.ec2.internal uid: 6453ce49-e0df-46ea-b0e6-c4ecaf05a6d2 resourceVersion: "20343" uid: 292fc9a1-5367-4312-84d3-f16719222ec4 spec: sourcePod: network-check-source-869dcfcdcd-rzhqt targetEndpoint: a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T18:58:41Z" message: 'load-balancer-api-internal: tcp connection to a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.816325ms message: 'load-balancer-api-internal: tcp connection to a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:10:41Z" - latency: 10.893285ms message: 'load-balancer-api-internal: resolved host name a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:10:41Z" - latency: 5.12569ms message: 'load-balancer-api-internal: tcp connection to a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:09:41Z" - latency: 7.841175ms message: 'load-balancer-api-internal: resolved host name a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:09:41Z" - latency: 5.579614ms message: 'load-balancer-api-internal: tcp connection to a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:08:41Z" - latency: 7.883665ms message: 'load-balancer-api-internal: resolved host name a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:08:41Z" - latency: 4.951702ms message: 'load-balancer-api-internal: tcp connection to a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:07:41Z" - latency: 8.815849ms message: 'load-balancer-api-internal: resolved host name a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:07:41Z" - latency: 5.583623ms message: 'load-balancer-api-internal: tcp connection to a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:06:41Z" - latency: 14.352382ms message: 'load-balancer-api-internal: resolved host name a85f6116b7a7d47bb8254ac93ee721ff-bbe4eedbb22bd9a0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T19:06:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:52:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-205-to-network-check-target-ip-10-0-130-96 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-205.ec2.internal uid: 6453ce49-e0df-46ea-b0e6-c4ecaf05a6d2 resourceVersion: "21963" uid: de1c6c4a-f4e4-4bb8-b236-fb5f54901b07 spec: sourcePod: network-check-source-869dcfcdcd-rzhqt targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-13T18:59:41Z" message: 'network-check-target-ip-10-0-130-96: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.737232ms message: 'network-check-target-ip-10-0-130-96: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:13:41Z" - latency: 1.828285ms message: 'network-check-target-ip-10-0-130-96: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:12:41Z" - latency: 1.91867ms message: 'network-check-target-ip-10-0-130-96: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:11:41Z" - latency: 1.90832ms message: 'network-check-target-ip-10-0-130-96: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:10:41Z" - latency: 1.886531ms message: 'network-check-target-ip-10-0-130-96: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:09:41Z" - latency: 1.912611ms message: 'network-check-target-ip-10-0-130-96: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:08:41Z" - latency: 1.813214ms message: 'network-check-target-ip-10-0-130-96: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:07:41Z" - latency: 2.068213ms message: 'network-check-target-ip-10-0-130-96: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:06:41Z" - latency: 1.902413ms message: 'network-check-target-ip-10-0-130-96: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:05:41Z" - latency: 1.900464ms message: 'network-check-target-ip-10-0-130-96: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:52:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-205-to-network-check-target-ip-10-0-131-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-205.ec2.internal uid: 6453ce49-e0df-46ea-b0e6-c4ecaf05a6d2 resourceVersion: "21964" uid: f40fa484-852b-4790-a26a-f93ea3bef0f9 spec: sourcePod: network-check-source-869dcfcdcd-rzhqt targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T18:59:41Z" message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.02053ms message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:13:41Z" - latency: 2.136616ms message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:12:41Z" - latency: 2.401693ms message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:11:41Z" - latency: 2.054882ms message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:10:41Z" - latency: 2.197298ms message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:09:41Z" - latency: 2.273652ms message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:08:41Z" - latency: 2.277006ms message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:07:41Z" - latency: 2.475275ms message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:06:41Z" - latency: 2.079221ms message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:05:41Z" - latency: 1.923397ms message: 'network-check-target-ip-10-0-131-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:52:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-205-to-network-check-target-ip-10-0-132-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-205.ec2.internal uid: 6453ce49-e0df-46ea-b0e6-c4ecaf05a6d2 resourceVersion: "21962" uid: 16c2e44d-6277-40f2-84da-3a3083115847 spec: sourcePod: network-check-source-869dcfcdcd-rzhqt targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T18:59:41Z" message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 675.766µs message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:13:41Z" - latency: 1.257461ms message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:12:41Z" - latency: 894.767µs message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:11:41Z" - latency: 1.148369ms message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:10:41Z" - latency: 1.066546ms message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:09:41Z" - latency: 790.823µs message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:08:41Z" - latency: 772.788µs message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:07:41Z" - latency: 1.058281ms message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:06:41Z" - latency: 833.775µs message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:05:41Z" - latency: 1.043063ms message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:52:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-205-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-205.ec2.internal uid: 6453ce49-e0df-46ea-b0e6-c4ecaf05a6d2 resourceVersion: "20340" uid: b5e99c93-280e-4e07-8c69-647d2cb2ac35 spec: sourcePod: network-check-source-869dcfcdcd-rzhqt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-13T18:58:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 910.478µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:10:41Z" - latency: 2.337339ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T19:10:41Z" - latency: 944.495µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:09:41Z" - latency: 1.744443ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T19:09:41Z" - latency: 779.714µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:08:41Z" - latency: 1.650261ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T19:08:41Z" - latency: 733.7µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:07:41Z" - latency: 1.74591ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T19:07:41Z" - latency: 933.496µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T19:06:41Z" - latency: 1.816127ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T19:06:41Z" kind: List metadata: resourceVersion: ""