apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:38:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-195-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-195.ec2.internal uid: 3fa59af7-05e7-4cc1-be2e-03fb79c9a9c2 resourceVersion: "69704" uid: 929d1cf3-38ea-41c3-84b9-314267b216a2 spec: sourcePod: network-check-source-7d88cb55d8-dj2d7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T17:45:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.264169ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:27:39Z" - latency: 1.252584ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:26:39Z" - latency: 1.749796ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:25:39Z" - latency: 1.026714ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:24:39Z" - latency: 1.157678ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:23:39Z" - latency: 1.035114ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:22:39Z" - latency: 1.170233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:21:39Z" - latency: 1.262305ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:20:39Z" - latency: 1.01548ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:19:39Z" - latency: 1.15251ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:18:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:38:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-195-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-195.ec2.internal uid: 3fa59af7-05e7-4cc1-be2e-03fb79c9a9c2 resourceVersion: "79045" uid: f40c8d3b-7c63-4f79-95a4-f42ce8015266 spec: sourcePod: network-check-source-7d88cb55d8-dj2d7 targetEndpoint: a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:44:39Z" message: 'load-balancer-api-external: tcp connection to a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.979431ms message: 'load-balancer-api-external: tcp connection to a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:32:39Z" - latency: 7.61723ms message: 'load-balancer-api-external: resolved host name a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:32:39Z" - latency: 6.13105ms message: 'load-balancer-api-external: tcp connection to a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:31:39Z" - latency: 7.153961ms message: 'load-balancer-api-external: resolved host name a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:31:39Z" - latency: 5.616803ms message: 'load-balancer-api-external: tcp connection to a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:30:39Z" - latency: 7.165791ms message: 'load-balancer-api-external: resolved host name a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:30:39Z" - latency: 5.146471ms message: 'load-balancer-api-external: tcp connection to a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:29:39Z" - latency: 7.119176ms message: 'load-balancer-api-external: resolved host name a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:29:39Z" - latency: 5.938736ms message: 'load-balancer-api-external: tcp connection to a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:28:39Z" - latency: 6.734728ms message: 'load-balancer-api-external: resolved host name a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:28:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:38:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-195-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-195.ec2.internal uid: 3fa59af7-05e7-4cc1-be2e-03fb79c9a9c2 resourceVersion: "79046" uid: b3dcaf83-1ef5-4c9f-8d3e-a97d7881dec0 spec: sourcePod: network-check-source-7d88cb55d8-dj2d7 targetEndpoint: a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:44:39Z" message: 'load-balancer-api-internal: tcp connection to a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.985682ms message: 'load-balancer-api-internal: tcp connection to a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:32:39Z" - latency: 7.661418ms message: 'load-balancer-api-internal: resolved host name a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:32:39Z" - latency: 6.814527ms message: 'load-balancer-api-internal: tcp connection to a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:31:39Z" - latency: 7.119042ms message: 'load-balancer-api-internal: resolved host name a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:31:39Z" - latency: 4.246126ms message: 'load-balancer-api-internal: tcp connection to a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:30:39Z" - latency: 7.3437ms message: 'load-balancer-api-internal: resolved host name a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:30:39Z" - latency: 5.024125ms message: 'load-balancer-api-internal: tcp connection to a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:29:39Z" - latency: 7.104414ms message: 'load-balancer-api-internal: resolved host name a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:29:39Z" - latency: 5.919681ms message: 'load-balancer-api-internal: tcp connection to a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:28:39Z" - latency: 6.862677ms message: 'load-balancer-api-internal: resolved host name a71de326cd6d64cc9bcbd8c97474b3f6-4f0a782ad580bc2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:28:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:38:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-195-to-network-check-target-ip-10-0-136-126 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-195.ec2.internal uid: 3fa59af7-05e7-4cc1-be2e-03fb79c9a9c2 resourceVersion: "69702" uid: 66215925-6c2f-4d76-964a-60afe675e827 spec: sourcePod: network-check-source-7d88cb55d8-dj2d7 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:45:39Z" message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.25406ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:27:39Z" - latency: 2.418457ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:26:39Z" - latency: 2.323523ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:25:39Z" - latency: 2.234662ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:24:39Z" - latency: 1.958259ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:23:39Z" - latency: 2.431376ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:22:39Z" - latency: 2.275486ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:21:39Z" - latency: 2.297748ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:20:39Z" - latency: 1.771307ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:19:39Z" - latency: 2.528441ms message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:18:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:38:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-195-to-network-check-target-ip-10-0-139-157 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-195.ec2.internal uid: 3fa59af7-05e7-4cc1-be2e-03fb79c9a9c2 resourceVersion: "69703" uid: 74c6b1a3-abfc-4a3b-a435-ae1b2e4af70e spec: sourcePod: network-check-source-7d88cb55d8-dj2d7 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:45:39Z" message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.376017ms message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:27:39Z" - latency: 2.392977ms message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:26:39Z" - latency: 2.014139ms message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:25:39Z" - latency: 2.272756ms message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:24:39Z" - latency: 1.945274ms message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:23:39Z" - latency: 2.349588ms message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:22:39Z" - latency: 2.413041ms message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:21:39Z" - latency: 2.29274ms message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:20:39Z" - latency: 2.499403ms message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:19:39Z" - latency: 2.342105ms message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:18:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:38:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-195-to-network-check-target-ip-10-0-142-195 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-195.ec2.internal uid: 3fa59af7-05e7-4cc1-be2e-03fb79c9a9c2 resourceVersion: "69701" uid: b71f3fa8-0906-465b-81fb-e1b2ded7f456 spec: sourcePod: network-check-source-7d88cb55d8-dj2d7 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:45:39Z" message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 940.726µs message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:27:39Z" - latency: 1.123147ms message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:26:39Z" - latency: 927.768µs message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:25:39Z" - latency: 978.624µs message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:24:39Z" - latency: 1.27174ms message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:23:39Z" - latency: 1.308653ms message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:22:39Z" - latency: 937.502µs message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:21:39Z" - latency: 1.483525ms message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:20:39Z" - latency: 1.005099ms message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:19:39Z" - latency: 1.171016ms message: 'network-check-target-ip-10-0-142-195: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:18:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:38:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-195-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-195.ec2.internal uid: 3fa59af7-05e7-4cc1-be2e-03fb79c9a9c2 resourceVersion: "79044" uid: 7626ca99-a0e1-48e8-9b26-b8fcec281475 spec: sourcePod: network-check-source-7d88cb55d8-dj2d7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T17:44:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 907.619µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:32:39Z" - latency: 1.988519ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:32:39Z" - latency: 1.257004ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:31:39Z" - latency: 1.810025ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:31:39Z" - latency: 1.108194ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:30:39Z" - latency: 1.921812ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:30:39Z" - latency: 1.054789ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:29:39Z" - latency: 1.771441ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:29:39Z" - latency: 919.259µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:28:39Z" - latency: 2.028086ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:28:39Z" kind: List metadata: resourceVersion: ""