apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T20:00:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-155-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-155.ec2.internal uid: 1f414cec-0cbb-41a1-9a6c-f246c1d50e02 resourceVersion: "46568" uid: c140d620-e4cf-4761-a920-ec0f5b129b54 spec: sourcePod: network-check-source-6947749cfc-qbb86 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T20:07:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.671433ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:28:32Z" - latency: 904.128µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:27:32Z" - latency: 910.571µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:26:32Z" - latency: 1.101854ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:25:32Z" - latency: 818.25µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:24:32Z" - latency: 816.808µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:23:32Z" - latency: 848.969µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:22:32Z" - latency: 713.073µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:21:32Z" - latency: 827.47µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:20:32Z" - latency: 984.669µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:19:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T20:00:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-155-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-155.ec2.internal uid: 1f414cec-0cbb-41a1-9a6c-f246c1d50e02 resourceVersion: "48650" uid: a23b32d3-0b42-4e67-94ac-71ae5f550193 spec: sourcePod: network-check-source-6947749cfc-qbb86 targetEndpoint: a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T20:06:32Z" message: 'load-balancer-api-external: tcp connection to a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.52308ms message: 'load-balancer-api-external: tcp connection to a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:30:32Z" - latency: 6.774566ms message: 'load-balancer-api-external: resolved host name a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:30:32Z" - latency: 4.470231ms message: 'load-balancer-api-external: tcp connection to a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:29:32Z" - latency: 6.848875ms message: 'load-balancer-api-external: resolved host name a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:29:32Z" - latency: 5.417832ms message: 'load-balancer-api-external: tcp connection to a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:28:32Z" - latency: 7.546828ms message: 'load-balancer-api-external: resolved host name a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:28:32Z" - latency: 4.925077ms message: 'load-balancer-api-external: tcp connection to a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:27:32Z" - latency: 12.428859ms message: 'load-balancer-api-external: resolved host name a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:27:32Z" - latency: 5.635574ms message: 'load-balancer-api-external: tcp connection to a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:26:32Z" - latency: 6.726407ms message: 'load-balancer-api-external: resolved host name a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:26:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T20:00:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-155-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-155.ec2.internal uid: 1f414cec-0cbb-41a1-9a6c-f246c1d50e02 resourceVersion: "48649" uid: 3ae04d7f-af25-4da2-a430-039e4340d6cb spec: sourcePod: network-check-source-6947749cfc-qbb86 targetEndpoint: a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T20:06:32Z" message: 'load-balancer-api-internal: tcp connection to a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.835026ms message: 'load-balancer-api-internal: tcp connection to a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:30:32Z" - latency: 6.791268ms message: 'load-balancer-api-internal: resolved host name a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:30:32Z" - latency: 5.342921ms message: 'load-balancer-api-internal: tcp connection to a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:29:32Z" - latency: 7.01025ms message: 'load-balancer-api-internal: resolved host name a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:29:32Z" - latency: 5.436815ms message: 'load-balancer-api-internal: tcp connection to a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:28:32Z" - latency: 7.517591ms message: 'load-balancer-api-internal: resolved host name a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:28:32Z" - latency: 4.472628ms message: 'load-balancer-api-internal: tcp connection to a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:27:32Z" - latency: 12.394497ms message: 'load-balancer-api-internal: resolved host name a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:27:32Z" - latency: 5.615646ms message: 'load-balancer-api-internal: tcp connection to a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:26:32Z" - latency: 6.69025ms message: 'load-balancer-api-internal: resolved host name a178d9d50fe6d45baad793648231dc54-18c50627db42d7b0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T20:26:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T20:00:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-155-to-network-check-target-ip-10-0-128-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-155.ec2.internal uid: 1f414cec-0cbb-41a1-9a6c-f246c1d50e02 resourceVersion: "46567" uid: 14bc9805-b5af-47a2-9d5e-0a882c9ff5be spec: sourcePod: network-check-source-6947749cfc-qbb86 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T20:07:32Z" message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.133042ms message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:28:32Z" - latency: 2.18904ms message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:27:32Z" - latency: 2.637971ms message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:26:32Z" - latency: 2.264465ms message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:25:32Z" - latency: 1.931124ms message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:24:32Z" - latency: 2.329264ms message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:23:32Z" - latency: 2.567244ms message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:22:32Z" - latency: 2.269599ms message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:21:32Z" - latency: 2.462405ms message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:20:32Z" - latency: 2.41562ms message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:19:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T20:00:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-155-to-network-check-target-ip-10-0-137-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-155.ec2.internal uid: 1f414cec-0cbb-41a1-9a6c-f246c1d50e02 resourceVersion: "46565" uid: 7e7e7da2-4ae4-4f78-a6f2-f531f74804dc spec: sourcePod: network-check-source-6947749cfc-qbb86 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T20:07:32Z" message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 940.318µs message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:28:32Z" - latency: 1.197313ms message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:27:32Z" - latency: 1.240748ms message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:26:32Z" - latency: 1.246724ms message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:25:32Z" - latency: 867.489µs message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:24:32Z" - latency: 1.054622ms message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:23:32Z" - latency: 963.457µs message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:22:32Z" - latency: 804.282µs message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:21:32Z" - latency: 996.112µs message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:20:32Z" - latency: 1.096007ms message: 'network-check-target-ip-10-0-137-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:19:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T20:00:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-155-to-network-check-target-ip-10-0-142-46 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-155.ec2.internal uid: 1f414cec-0cbb-41a1-9a6c-f246c1d50e02 resourceVersion: "46566" uid: 8feb55b1-0685-4421-94da-5b7f63161153 spec: sourcePod: network-check-source-6947749cfc-qbb86 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T20:07:32Z" message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.996441ms message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:28:32Z" - latency: 2.317004ms message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:27:32Z" - latency: 2.142319ms message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:26:32Z" - latency: 1.71067ms message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:25:32Z" - latency: 1.817867ms message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:24:32Z" - latency: 2.519212ms message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:23:32Z" - latency: 2.131005ms message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:22:32Z" - latency: 2.073837ms message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:21:32Z" - latency: 2.028341ms message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:20:32Z" - latency: 2.13068ms message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:19:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T20:00:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-155-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-155.ec2.internal uid: 1f414cec-0cbb-41a1-9a6c-f246c1d50e02 resourceVersion: "48648" uid: 79b76297-1806-4180-8744-17eaf9853be0 spec: sourcePod: network-check-source-6947749cfc-qbb86 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T20:06:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 813.086µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:30:32Z" - latency: 1.658234ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T20:30:32Z" - latency: 1.017856ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:29:32Z" - latency: 1.526469ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T20:29:32Z" - latency: 1.087939ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:28:32Z" - latency: 1.958289ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T20:28:32Z" - latency: 877.493µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:27:32Z" - latency: 1.654583ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T20:27:32Z" - latency: 1.047994ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T20:26:32Z" - latency: 1.608626ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T20:26:32Z" kind: List metadata: resourceVersion: ""