apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T21:00:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-226-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-226.ec2.internal uid: 38b508f0-3178-41d5-a5bb-039ac72374b5 resourceVersion: "50027" uid: 34b75285-9db4-4eaa-acc2-1d96c5aa8a60 spec: sourcePod: network-check-source-869dcfcdcd-dpxtc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T21:07:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 958.811µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:35:58Z" - latency: 973.659µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:34:58Z" - latency: 1.114101ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:33:58Z" - latency: 954.205µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:32:58Z" - latency: 1.054202ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:31:58Z" - latency: 972.343µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:30:58Z" - latency: 1.229651ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:29:58Z" - latency: 1.335549ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:28:58Z" - latency: 1.518574ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:27:58Z" - latency: 1.151364ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:26:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T21:00:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-226-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-226.ec2.internal uid: 38b508f0-3178-41d5-a5bb-039ac72374b5 resourceVersion: "50629" uid: 0c142b6e-0474-45ae-ac6f-c9bf3e80237c spec: sourcePod: network-check-source-869dcfcdcd-dpxtc targetEndpoint: a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T21:06:58Z" message: 'load-balancer-api-external: tcp connection to a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.14917ms message: 'load-balancer-api-external: tcp connection to a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:36:58Z" - latency: 8.507267ms message: 'load-balancer-api-external: resolved host name a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:36:58Z" - latency: 5.97402ms message: 'load-balancer-api-external: tcp connection to a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:35:58Z" - latency: 8.624121ms message: 'load-balancer-api-external: resolved host name a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:35:58Z" - latency: 3.799252ms message: 'load-balancer-api-external: tcp connection to a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:34:58Z" - latency: 15.704745ms message: 'load-balancer-api-external: resolved host name a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:34:58Z" - latency: 4.991771ms message: 'load-balancer-api-external: tcp connection to a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:33:58Z" - latency: 8.415841ms message: 'load-balancer-api-external: resolved host name a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:33:58Z" - latency: 5.955576ms message: 'load-balancer-api-external: tcp connection to a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:32:58Z" - latency: 8.426776ms message: 'load-balancer-api-external: resolved host name a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:32:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T21:00:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-226-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-226.ec2.internal uid: 38b508f0-3178-41d5-a5bb-039ac72374b5 resourceVersion: "50630" uid: 031d5132-734e-49a4-97d7-71afec71350e spec: sourcePod: network-check-source-869dcfcdcd-dpxtc targetEndpoint: a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T21:06:58Z" message: 'load-balancer-api-internal: tcp connection to a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.160173ms message: 'load-balancer-api-internal: tcp connection to a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:36:58Z" - latency: 8.455018ms message: 'load-balancer-api-internal: resolved host name a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:36:58Z" - latency: 5.102437ms message: 'load-balancer-api-internal: tcp connection to a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:35:58Z" - latency: 8.57493ms message: 'load-balancer-api-internal: resolved host name a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:35:58Z" - latency: 3.729987ms message: 'load-balancer-api-internal: tcp connection to a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:34:58Z" - latency: 15.655301ms message: 'load-balancer-api-internal: resolved host name a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:34:58Z" - latency: 5.019652ms message: 'load-balancer-api-internal: tcp connection to a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:33:58Z" - latency: 8.328285ms message: 'load-balancer-api-internal: resolved host name a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:33:58Z" - latency: 5.184087ms message: 'load-balancer-api-internal: tcp connection to a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:32:58Z" - latency: 8.355209ms message: 'load-balancer-api-internal: resolved host name a74992c5a613f4e82adfcbc55f8da4ec-80a30782df3a53ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T21:32:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T21:00:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-226-to-network-check-target-ip-10-0-131-227 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-226.ec2.internal uid: 38b508f0-3178-41d5-a5bb-039ac72374b5 resourceVersion: "50025" uid: b1472a81-d055-478c-9565-e68b010759de spec: sourcePod: network-check-source-869dcfcdcd-dpxtc targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T21:07:58Z" message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.298624ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:35:58Z" - latency: 2.291254ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:34:58Z" - latency: 2.217418ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:33:58Z" - latency: 1.970029ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:32:58Z" - latency: 2.3558ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:31:58Z" - latency: 2.373799ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:30:58Z" - latency: 2.279455ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:29:58Z" - latency: 2.637805ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:28:58Z" - latency: 2.715038ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:27:58Z" - latency: 2.592819ms message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:26:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T21:00:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-226-to-network-check-target-ip-10-0-137-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-226.ec2.internal uid: 38b508f0-3178-41d5-a5bb-039ac72374b5 resourceVersion: "50026" uid: ba1cfd8c-7915-40a0-8a6a-18f95a7d2bd7 spec: sourcePod: network-check-source-869dcfcdcd-dpxtc targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T21:07:58Z" message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.33447ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:35:58Z" - latency: 2.340957ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:34:58Z" - latency: 2.58672ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:33:58Z" - latency: 2.193325ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:32:58Z" - latency: 2.435337ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:31:58Z" - latency: 2.405446ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:30:58Z" - latency: 2.462243ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:29:58Z" - latency: 2.103007ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:28:58Z" - latency: 2.123146ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:27:58Z" - latency: 2.414415ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:26:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T21:00:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-226-to-network-check-target-ip-10-0-140-226 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-226.ec2.internal uid: 38b508f0-3178-41d5-a5bb-039ac72374b5 resourceVersion: "50024" uid: be8305cc-9e62-4fe8-aa28-0e6d74d5ac5b spec: sourcePod: network-check-source-869dcfcdcd-dpxtc targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T21:07:58Z" message: 'network-check-target-ip-10-0-140-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.31122ms message: 'network-check-target-ip-10-0-140-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:35:58Z" - latency: 1.180687ms message: 'network-check-target-ip-10-0-140-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:34:58Z" - latency: 1.307281ms message: 'network-check-target-ip-10-0-140-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:33:58Z" - latency: 932.498µs message: 'network-check-target-ip-10-0-140-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:32:58Z" - latency: 862.815µs message: 'network-check-target-ip-10-0-140-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:31:58Z" - latency: 870.327µs message: 'network-check-target-ip-10-0-140-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:30:58Z" - latency: 1.438737ms message: 'network-check-target-ip-10-0-140-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:29:58Z" - latency: 955.76µs message: 'network-check-target-ip-10-0-140-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:28:58Z" - latency: 1.3862ms message: 'network-check-target-ip-10-0-140-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:27:58Z" - latency: 1.340217ms message: 'network-check-target-ip-10-0-140-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:26:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T21:00:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-226-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-226.ec2.internal uid: 38b508f0-3178-41d5-a5bb-039ac72374b5 resourceVersion: "50628" uid: 1ef917da-f193-4e8a-9021-d8e142d7da73 spec: sourcePod: network-check-source-869dcfcdcd-dpxtc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T21:06:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 861.446µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:36:58Z" - latency: 1.766356ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:36:58Z" - latency: 788.644µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:35:58Z" - latency: 1.663929ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:35:58Z" - latency: 846.226µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:34:58Z" - latency: 2.268634ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:34:58Z" - latency: 751.562µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:33:58Z" - latency: 2.286715ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:33:58Z" - latency: 965.502µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T21:32:58Z" - latency: 1.688016ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T21:32:58Z" kind: List metadata: resourceVersion: ""