apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T00:44:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-137-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-137.ec2.internal uid: 193ceb6d-df19-441b-b673-4b5bf41c3f35 resourceVersion: "62182" uid: 1af864cf-21ff-4bda-86d6-0b4a1e158582 spec: sourcePod: network-check-source-7bc5b6bf85-lsf2j targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-21T00:51:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 815.599µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:26:25Z" - latency: 1.166825ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:25:25Z" - latency: 1.525243ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:24:25Z" - latency: 1.797438ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:23:25Z" - latency: 932.319µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:22:25Z" - latency: 996.437µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:21:25Z" - latency: 1.169358ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:20:25Z" - latency: 1.153883ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:19:25Z" - latency: 1.075325ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:18:25Z" - latency: 1.167637ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:17:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T00:44:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-137-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-137.ec2.internal uid: 193ceb6d-df19-441b-b673-4b5bf41c3f35 resourceVersion: "62183" uid: ab44cd4f-2ad4-47b7-b61e-4262263a7821 spec: sourcePod: network-check-source-7bc5b6bf85-lsf2j targetEndpoint: a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T00:50:25Z" message: 'load-balancer-api-external: tcp connection to a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.313449ms message: 'load-balancer-api-external: tcp connection to a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:26:25Z" - latency: 8.091319ms message: 'load-balancer-api-external: resolved host name a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T01:26:25Z" - latency: 7.549835ms message: 'load-balancer-api-external: tcp connection to a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:25:25Z" - latency: 6.609391ms message: 'load-balancer-api-external: resolved host name a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T01:25:25Z" - latency: 5.361979ms message: 'load-balancer-api-external: tcp connection to a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:24:25Z" - latency: 7.945256ms message: 'load-balancer-api-external: resolved host name a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T01:24:25Z" - latency: 4.606305ms message: 'load-balancer-api-external: tcp connection to a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:23:25Z" - latency: 8.5143ms message: 'load-balancer-api-external: resolved host name a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T01:23:25Z" - latency: 4.881557ms message: 'load-balancer-api-external: tcp connection to a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:22:25Z" - latency: 7.111256ms message: 'load-balancer-api-external: resolved host name a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T01:22:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T00:44:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-137-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-137.ec2.internal uid: 193ceb6d-df19-441b-b673-4b5bf41c3f35 resourceVersion: "62184" uid: 87f82b79-eb33-420d-98f0-746efca4fce8 spec: sourcePod: network-check-source-7bc5b6bf85-lsf2j targetEndpoint: a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T00:50:25Z" message: 'load-balancer-api-internal: tcp connection to a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.089115ms message: 'load-balancer-api-internal: tcp connection to a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:26:25Z" - latency: 8.010821ms message: 'load-balancer-api-internal: resolved host name a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T01:26:25Z" - latency: 5.869549ms message: 'load-balancer-api-internal: tcp connection to a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:25:25Z" - latency: 6.638455ms message: 'load-balancer-api-internal: resolved host name a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T01:25:25Z" - latency: 5.504235ms message: 'load-balancer-api-internal: tcp connection to a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:24:25Z" - latency: 7.926652ms message: 'load-balancer-api-internal: resolved host name a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T01:24:25Z" - latency: 5.067646ms message: 'load-balancer-api-internal: tcp connection to a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:23:25Z" - latency: 8.550687ms message: 'load-balancer-api-internal: resolved host name a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T01:23:25Z" - latency: 4.908593ms message: 'load-balancer-api-internal: tcp connection to a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:22:25Z" - latency: 7.071191ms message: 'load-balancer-api-internal: resolved host name a5b220e3076994070b3499b8accfb60b-a161de2c6b259f4e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T01:22:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T00:44:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-137-to-network-check-target-ip-10-0-129-137 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-137.ec2.internal uid: 193ceb6d-df19-441b-b673-4b5bf41c3f35 resourceVersion: "62178" uid: 599e320b-1c65-42a8-8d9d-3acd9d8250c4 spec: sourcePod: network-check-source-7bc5b6bf85-lsf2j targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T00:51:25Z" message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 764.522µs message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:26:25Z" - latency: 1.240924ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:25:25Z" - latency: 1.412545ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:24:25Z" - latency: 1.221862ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:23:25Z" - latency: 816.921µs message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:22:25Z" - latency: 1.022634ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:21:25Z" - latency: 891.693µs message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:20:25Z" - latency: 1.450358ms message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:19:25Z" - latency: 940.171µs message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:18:25Z" - latency: 947.901µs message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:17:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T00:44:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-137-to-network-check-target-ip-10-0-133-75 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-137.ec2.internal uid: 193ceb6d-df19-441b-b673-4b5bf41c3f35 resourceVersion: "62179" uid: 021c3a5c-81e4-47a1-82b4-43a9145e58d7 spec: sourcePod: network-check-source-7bc5b6bf85-lsf2j targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T00:51:25Z" message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.916424ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:26:25Z" - latency: 2.466812ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:25:25Z" - latency: 2.312396ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:24:25Z" - latency: 3.078753ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:23:25Z" - latency: 2.171986ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:22:25Z" - latency: 2.139929ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:21:25Z" - latency: 2.609386ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:20:25Z" - latency: 2.478898ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:19:25Z" - latency: 2.482973ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:18:25Z" - latency: 2.200396ms message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:17:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T00:44:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-137-to-network-check-target-ip-10-0-138-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-137.ec2.internal uid: 193ceb6d-df19-441b-b673-4b5bf41c3f35 resourceVersion: "62180" uid: aa0819d9-fc6c-42d8-9d09-cb8f9c579d4a spec: sourcePod: network-check-source-7bc5b6bf85-lsf2j targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-21T00:51:25Z" message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.972775ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:26:25Z" - latency: 2.310617ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:25:25Z" - latency: 2.687867ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:24:25Z" - latency: 2.485484ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:23:25Z" - latency: 2.255645ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:22:25Z" - latency: 2.266922ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:21:25Z" - latency: 2.302867ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:20:25Z" - latency: 2.390557ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:19:25Z" - latency: 2.313497ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:18:25Z" - latency: 2.358211ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:17:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T00:44:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-137-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-137.ec2.internal uid: 193ceb6d-df19-441b-b673-4b5bf41c3f35 resourceVersion: "62181" uid: c2d3b917-6344-411e-ad58-235ffd9a13a9 spec: sourcePod: network-check-source-7bc5b6bf85-lsf2j targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-21T00:50:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 932.788µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:26:25Z" - latency: 2.206886ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T01:26:25Z" - latency: 891.254µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:25:25Z" - latency: 1.821154ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T01:25:25Z" - latency: 948.285µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:24:25Z" - latency: 2.232188ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T01:24:25Z" - latency: 973.179µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:23:25Z" - latency: 2.485122ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T01:23:25Z" - latency: 1.092899ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T01:22:25Z" - latency: 1.895843ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T01:22:25Z" kind: List metadata: resourceVersion: ""