apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T02:29:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-253-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-253.ec2.internal uid: d36abaa1-b807-4737-8e04-e118f50ecf4a resourceVersion: "42994" uid: 3a827f2f-fd64-4cd4-b990-1c527f96c380 spec: sourcePod: network-check-source-7f44b6dd87-8457p targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-25T02:36:48Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 819.322µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:57:48Z" - latency: 1.243102ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:56:48Z" - latency: 1.090531ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:55:48Z" - latency: 1.193904ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:54:48Z" - latency: 1.144604ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:53:48Z" - latency: 930.394µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:52:48Z" - latency: 1.093873ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:51:48Z" - latency: 896.142µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:50:48Z" - latency: 1.171602ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:49:48Z" - latency: 1.160807ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:48:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T02:29:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-253-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-253.ec2.internal uid: d36abaa1-b807-4737-8e04-e118f50ecf4a resourceVersion: "45169" uid: 03dd0751-c133-4468-8900-0a2f19341423 spec: sourcePod: network-check-source-7f44b6dd87-8457p targetEndpoint: adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T02:35:48Z" message: 'load-balancer-api-external: tcp connection to adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.878148ms message: 'load-balancer-api-external: tcp connection to adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:59:48Z" - latency: 9.03626ms message: 'load-balancer-api-external: resolved host name adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T02:59:48Z" - latency: 3.912386ms message: 'load-balancer-api-external: tcp connection to adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:58:48Z" - latency: 9.011337ms message: 'load-balancer-api-external: resolved host name adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T02:58:48Z" - latency: 5.844929ms message: 'load-balancer-api-external: tcp connection to adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:57:48Z" - latency: 6.572676ms message: 'load-balancer-api-external: resolved host name adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T02:57:48Z" - latency: 5.716559ms message: 'load-balancer-api-external: tcp connection to adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:56:48Z" - latency: 7.347915ms message: 'load-balancer-api-external: resolved host name adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T02:56:48Z" - latency: 4.457676ms message: 'load-balancer-api-external: tcp connection to adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:55:48Z" - latency: 7.061783ms message: 'load-balancer-api-external: resolved host name adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T02:55:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T02:29:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-253-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-253.ec2.internal uid: d36abaa1-b807-4737-8e04-e118f50ecf4a resourceVersion: "45170" uid: 22fd5bc7-256a-4c64-a3ae-ba2a25eace34 spec: sourcePod: network-check-source-7f44b6dd87-8457p targetEndpoint: adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T02:35:48Z" message: 'load-balancer-api-internal: tcp connection to adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.323903ms message: 'load-balancer-api-internal: tcp connection to adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:59:48Z" - latency: 8.99367ms message: 'load-balancer-api-internal: resolved host name adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T02:59:48Z" - latency: 4.870006ms message: 'load-balancer-api-internal: tcp connection to adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:58:48Z" - latency: 9.062084ms message: 'load-balancer-api-internal: resolved host name adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T02:58:48Z" - latency: 5.908605ms message: 'load-balancer-api-internal: tcp connection to adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:57:48Z" - latency: 6.498819ms message: 'load-balancer-api-internal: resolved host name adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T02:57:48Z" - latency: 5.708365ms message: 'load-balancer-api-internal: tcp connection to adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:56:48Z" - latency: 7.315793ms message: 'load-balancer-api-internal: resolved host name adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T02:56:48Z" - latency: 4.448792ms message: 'load-balancer-api-internal: tcp connection to adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:55:48Z" - latency: 7.007516ms message: 'load-balancer-api-internal: resolved host name adcf94811bd42416fb43c95021097457-b38183b7f32ef80e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T02:55:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T02:29:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-253-to-network-check-target-ip-10-0-128-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-253.ec2.internal uid: d36abaa1-b807-4737-8e04-e118f50ecf4a resourceVersion: "42992" uid: 4483c01d-b745-4ae8-8f78-87dc39b0f926 spec: sourcePod: network-check-source-7f44b6dd87-8457p targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T02:36:48Z" message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.222519ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:57:48Z" - latency: 1.89351ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:56:48Z" - latency: 1.921142ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:55:48Z" - latency: 2.10642ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:54:48Z" - latency: 1.827047ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:53:48Z" - latency: 1.855676ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:52:48Z" - latency: 2.072378ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:51:48Z" - latency: 1.787849ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:50:48Z" - latency: 1.922444ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:49:48Z" - latency: 1.812399ms message: 'network-check-target-ip-10-0-128-55: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:48:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T02:29:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-253-to-network-check-target-ip-10-0-133-46 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-253.ec2.internal uid: d36abaa1-b807-4737-8e04-e118f50ecf4a resourceVersion: "42993" uid: 4d825e3b-1222-4af9-a751-385a6c95daf1 spec: sourcePod: network-check-source-7f44b6dd87-8457p targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-25T02:36:48Z" message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.232832ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:57:48Z" - latency: 2.08535ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:56:48Z" - latency: 2.560296ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:55:48Z" - latency: 2.130478ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:54:48Z" - latency: 2.174563ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:53:48Z" - latency: 2.146368ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:52:48Z" - latency: 2.6594ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:51:48Z" - latency: 1.927861ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:50:48Z" - latency: 2.141487ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:49:48Z" - latency: 1.95417ms message: 'network-check-target-ip-10-0-133-46: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:48:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T02:29:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-253-to-network-check-target-ip-10-0-143-253 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-253.ec2.internal uid: d36abaa1-b807-4737-8e04-e118f50ecf4a resourceVersion: "42991" uid: d9a885ca-3672-41f2-bb3b-611f231b5e54 spec: sourcePod: network-check-source-7f44b6dd87-8457p targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T02:36:48Z" message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.209216ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:57:48Z" - latency: 1.470362ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:56:48Z" - latency: 787.257µs message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:55:48Z" - latency: 817.68µs message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:54:48Z" - latency: 832.716µs message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:53:48Z" - latency: 1.205392ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:52:48Z" - latency: 1.590267ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:51:48Z" - latency: 1.373028ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:50:48Z" - latency: 1.36555ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:49:48Z" - latency: 1.136163ms message: 'network-check-target-ip-10-0-143-253: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:48:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T02:29:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-253-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-253.ec2.internal uid: d36abaa1-b807-4737-8e04-e118f50ecf4a resourceVersion: "45168" uid: bb76bbab-c8b9-49a9-b34c-7ec31b0432f4 spec: sourcePod: network-check-source-7f44b6dd87-8457p targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-25T02:35:48Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 822.294µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:59:48Z" - latency: 1.898343ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T02:59:48Z" - latency: 803.288µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:58:48Z" - latency: 2.211454ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T02:58:48Z" - latency: 864.241µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:57:48Z" - latency: 1.598509ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T02:57:48Z" - latency: 896.081µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:56:48Z" - latency: 2.438757ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T02:56:48Z" - latency: 923.049µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T02:55:48Z" - latency: 1.938659ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T02:55:48Z" kind: List metadata: resourceVersion: ""