apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:38:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-92-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-92.ec2.internal uid: 661a4925-08c7-40d8-a7e2-c79512b5a376 resourceVersion: "21867" uid: 80478ac9-2532-4aed-9870-a5ccce8888e6 spec: sourcePod: network-check-source-989f8b8dc-ktm7j targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T20:45:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.045523ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:59:19Z" - latency: 957.083µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:58:19Z" - latency: 1.015258ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:57:19Z" - latency: 830.663µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:56:19Z" - latency: 905.13µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:55:19Z" - latency: 866.741µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:54:19Z" - latency: 886.261µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:53:19Z" - latency: 953.826µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:52:19Z" - latency: 797.443µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:51:19Z" - latency: 1.45835ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:50:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:38:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-92-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-92.ec2.internal uid: 661a4925-08c7-40d8-a7e2-c79512b5a376 resourceVersion: "20306" uid: 88006303-f7be-4d4b-a8a8-949ad74f2860 spec: sourcePod: network-check-source-989f8b8dc-ktm7j targetEndpoint: a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T20:44:19Z" message: 'load-balancer-api-external: tcp connection to a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.841838ms message: 'load-balancer-api-external: tcp connection to a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:56:19Z" - latency: 7.571179ms message: 'load-balancer-api-external: resolved host name a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:56:19Z" - latency: 5.162189ms message: 'load-balancer-api-external: tcp connection to a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:55:19Z" - latency: 9.13997ms message: 'load-balancer-api-external: resolved host name a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:55:19Z" - latency: 4.679837ms message: 'load-balancer-api-external: tcp connection to a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:54:19Z" - latency: 8.23102ms message: 'load-balancer-api-external: resolved host name a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:54:19Z" - latency: 5.653325ms message: 'load-balancer-api-external: tcp connection to a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:53:19Z" - latency: 8.121217ms message: 'load-balancer-api-external: resolved host name a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:53:19Z" - latency: 7.841783ms message: 'load-balancer-api-external: tcp connection to a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:52:19Z" - latency: 8.109683ms message: 'load-balancer-api-external: resolved host name a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:52:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:38:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-92-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-92.ec2.internal uid: 661a4925-08c7-40d8-a7e2-c79512b5a376 resourceVersion: "20305" uid: bc209359-bdf4-4fc1-9086-ae835106f913 spec: sourcePod: network-check-source-989f8b8dc-ktm7j targetEndpoint: a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T20:44:19Z" message: 'load-balancer-api-internal: tcp connection to a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.783946ms message: 'load-balancer-api-internal: tcp connection to a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:56:19Z" - latency: 7.513338ms message: 'load-balancer-api-internal: resolved host name a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:56:19Z" - latency: 5.206655ms message: 'load-balancer-api-internal: tcp connection to a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:55:19Z" - latency: 9.111587ms message: 'load-balancer-api-internal: resolved host name a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:55:19Z" - latency: 4.679324ms message: 'load-balancer-api-internal: tcp connection to a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:54:19Z" - latency: 8.108881ms message: 'load-balancer-api-internal: resolved host name a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:54:19Z" - latency: 5.645401ms message: 'load-balancer-api-internal: tcp connection to a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:53:19Z" - latency: 8.147829ms message: 'load-balancer-api-internal: resolved host name a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:53:19Z" - latency: 3.743042ms message: 'load-balancer-api-internal: tcp connection to a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:52:19Z" - latency: 8.028178ms message: 'load-balancer-api-internal: resolved host name a1d7c40f0817c4a4cb90045cee978384-ab0a3ee8c9ebcf0a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:52:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:38:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-92-to-network-check-target-ip-10-0-129-46 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-92.ec2.internal uid: 661a4925-08c7-40d8-a7e2-c79512b5a376 resourceVersion: "21866" uid: fba1ee0a-570b-4dfb-8b58-0bfa4bf78a30 spec: sourcePod: network-check-source-989f8b8dc-ktm7j targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:45:19Z" message: 'network-check-target-ip-10-0-129-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.34731ms message: 'network-check-target-ip-10-0-129-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:59:19Z" - latency: 2.309687ms message: 'network-check-target-ip-10-0-129-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:58:19Z" - latency: 2.510434ms message: 'network-check-target-ip-10-0-129-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:57:19Z" - latency: 2.035952ms message: 'network-check-target-ip-10-0-129-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:56:19Z" - latency: 2.320812ms message: 'network-check-target-ip-10-0-129-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:55:19Z" - latency: 2.389882ms message: 'network-check-target-ip-10-0-129-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:54:19Z" - latency: 2.597692ms message: 'network-check-target-ip-10-0-129-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:53:19Z" - latency: 2.353587ms message: 'network-check-target-ip-10-0-129-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:52:19Z" - latency: 2.029252ms message: 'network-check-target-ip-10-0-129-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:51:19Z" - latency: 2.330545ms message: 'network-check-target-ip-10-0-129-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:50:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:38:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-92-to-network-check-target-ip-10-0-130-92 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-92.ec2.internal uid: 661a4925-08c7-40d8-a7e2-c79512b5a376 resourceVersion: "21864" uid: fa3d8f7a-f4ce-4ad4-86f5-9f516ef11e22 spec: sourcePod: network-check-source-989f8b8dc-ktm7j targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:45:19Z" message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 849.116µs message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:59:19Z" - latency: 846.479µs message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:58:19Z" - latency: 902.105µs message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:57:19Z" - latency: 882.088µs message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:56:19Z" - latency: 872.91µs message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:55:19Z" - latency: 1.2255ms message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:54:19Z" - latency: 1.171703ms message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:53:19Z" - latency: 712.433µs message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:52:19Z" - latency: 923.093µs message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:51:19Z" - latency: 913.67µs message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:50:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:38:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-92-to-network-check-target-ip-10-0-139-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-92.ec2.internal uid: 661a4925-08c7-40d8-a7e2-c79512b5a376 resourceVersion: "21865" uid: e2b2458f-530d-494c-ac57-adbb08c4a6a2 spec: sourcePod: network-check-source-989f8b8dc-ktm7j targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T20:45:19Z" message: 'network-check-target-ip-10-0-139-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.241448ms message: 'network-check-target-ip-10-0-139-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:59:19Z" - latency: 2.306697ms message: 'network-check-target-ip-10-0-139-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:58:19Z" - latency: 2.270214ms message: 'network-check-target-ip-10-0-139-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:57:19Z" - latency: 2.211174ms message: 'network-check-target-ip-10-0-139-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:56:19Z" - latency: 2.407188ms message: 'network-check-target-ip-10-0-139-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:55:19Z" - latency: 2.26696ms message: 'network-check-target-ip-10-0-139-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:54:19Z" - latency: 2.07817ms message: 'network-check-target-ip-10-0-139-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:53:19Z" - latency: 2.305876ms message: 'network-check-target-ip-10-0-139-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:52:19Z" - latency: 1.819481ms message: 'network-check-target-ip-10-0-139-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:51:19Z" - latency: 2.281207ms message: 'network-check-target-ip-10-0-139-250: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:50:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T20:38:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-92-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-92.ec2.internal uid: 661a4925-08c7-40d8-a7e2-c79512b5a376 resourceVersion: "20304" uid: 46404c27-5fa6-46b8-85bb-bb7f51ba3978 spec: sourcePod: network-check-source-989f8b8dc-ktm7j targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T20:44:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 898.556µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:56:19Z" - latency: 1.683155ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:56:19Z" - latency: 1.043ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:55:19Z" - latency: 1.658242ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:55:19Z" - latency: 812.9µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:54:19Z" - latency: 1.6006ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:54:19Z" - latency: 790.142µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:53:19Z" - latency: 1.911424ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:53:19Z" - latency: 762.647µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:52:19Z" - latency: 1.685835ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:52:19Z" kind: List metadata: resourceVersion: ""