apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T22:50:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-130-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-130.ec2.internal uid: 1f571223-e4e2-4c62-a750-a56e86954a70 resourceVersion: "71589" uid: 2af35b27-309a-4fa2-8b21-c626b9e5b14f spec: sourcePod: network-check-source-65bdbbff45-g4fxw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-30T22:57:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 967.085µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:39:58Z" - latency: 1.22234ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:38:58Z" - latency: 961.22µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:37:58Z" - latency: 995.344µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:36:58Z" - latency: 1.0408ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:35:58Z" - latency: 1.686952ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:34:58Z" - latency: 1.088133ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:33:58Z" - latency: 1.192551ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:32:58Z" - latency: 1.193072ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:31:58Z" - latency: 1.11627ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:30:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T22:50:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-130-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-130.ec2.internal uid: 1f571223-e4e2-4c62-a750-a56e86954a70 resourceVersion: "77164" uid: 0a98e6a5-57ec-4cac-81a2-07320bd38464 spec: sourcePod: network-check-source-65bdbbff45-g4fxw targetEndpoint: aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T22:56:58Z" message: 'load-balancer-api-external: tcp connection to aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.947979ms message: 'load-balancer-api-external: tcp connection to aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:44:58Z" - latency: 8.308677ms message: 'load-balancer-api-external: resolved host name aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T23:44:58Z" - latency: 6.044641ms message: 'load-balancer-api-external: tcp connection to aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:43:58Z" - latency: 9.197879ms message: 'load-balancer-api-external: resolved host name aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T23:43:58Z" - latency: 4.892002ms message: 'load-balancer-api-external: tcp connection to aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:42:58Z" - latency: 9.097054ms message: 'load-balancer-api-external: resolved host name aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T23:42:58Z" - latency: 4.739946ms message: 'load-balancer-api-external: tcp connection to aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:41:58Z" - latency: 8.85092ms message: 'load-balancer-api-external: resolved host name aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T23:41:58Z" - latency: 3.796204ms message: 'load-balancer-api-external: tcp connection to aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:40:58Z" - latency: 8.620165ms message: 'load-balancer-api-external: resolved host name aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T23:40:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T22:50:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-130-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-130.ec2.internal uid: 1f571223-e4e2-4c62-a750-a56e86954a70 resourceVersion: "77163" uid: 9f3c2385-a157-403d-9aa4-1b2643967ab6 spec: sourcePod: network-check-source-65bdbbff45-g4fxw targetEndpoint: aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T22:56:58Z" message: 'load-balancer-api-internal: tcp connection to aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.978219ms message: 'load-balancer-api-internal: tcp connection to aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:44:58Z" - latency: 8.340066ms message: 'load-balancer-api-internal: resolved host name aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T23:44:58Z" - latency: 3.827132ms message: 'load-balancer-api-internal: tcp connection to aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:43:58Z" - latency: 9.153474ms message: 'load-balancer-api-internal: resolved host name aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T23:43:58Z" - latency: 5.101544ms message: 'load-balancer-api-internal: tcp connection to aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:42:58Z" - latency: 9.135984ms message: 'load-balancer-api-internal: resolved host name aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T23:42:58Z" - latency: 4.703048ms message: 'load-balancer-api-internal: tcp connection to aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:41:58Z" - latency: 8.91847ms message: 'load-balancer-api-internal: resolved host name aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T23:41:58Z" - latency: 3.78213ms message: 'load-balancer-api-internal: tcp connection to aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:40:58Z" - latency: 8.576878ms message: 'load-balancer-api-internal: resolved host name aaad0a717800744a6b810ad901997004-69a8d8a9bc789dd7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T23:40:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T22:50:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-130-to-network-check-target-ip-10-0-131-130 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-130.ec2.internal uid: 1f571223-e4e2-4c62-a750-a56e86954a70 resourceVersion: "71586" uid: 328102a2-f888-43e4-b4ed-8a5a8522b98d spec: sourcePod: network-check-source-65bdbbff45-g4fxw targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-30T22:57:58Z" message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.227556ms message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:39:58Z" - latency: 863.478µs message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:38:58Z" - latency: 1.607584ms message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:37:58Z" - latency: 905.522µs message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:36:58Z" - latency: 1.603103ms message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:35:58Z" - latency: 925.491µs message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:34:58Z" - latency: 955.079µs message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:33:58Z" - latency: 826.989µs message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:32:58Z" - latency: 844.432µs message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:31:58Z" - latency: 793.95µs message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:30:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T22:50:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-130-to-network-check-target-ip-10-0-135-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-130.ec2.internal uid: 1f571223-e4e2-4c62-a750-a56e86954a70 resourceVersion: "71587" uid: 6fc7d0cb-36b8-41bb-9967-7a9fc96d29b7 spec: sourcePod: network-check-source-65bdbbff45-g4fxw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-30T22:57:58Z" message: 'network-check-target-ip-10-0-135-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.467183ms message: 'network-check-target-ip-10-0-135-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:39:58Z" - latency: 2.329945ms message: 'network-check-target-ip-10-0-135-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:38:58Z" - latency: 2.423633ms message: 'network-check-target-ip-10-0-135-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:37:58Z" - latency: 2.45457ms message: 'network-check-target-ip-10-0-135-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:36:58Z" - latency: 2.286646ms message: 'network-check-target-ip-10-0-135-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:35:58Z" - latency: 2.310125ms message: 'network-check-target-ip-10-0-135-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:34:58Z" - latency: 2.569411ms message: 'network-check-target-ip-10-0-135-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:33:58Z" - latency: 2.116245ms message: 'network-check-target-ip-10-0-135-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:32:58Z" - latency: 2.204543ms message: 'network-check-target-ip-10-0-135-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:31:58Z" - latency: 2.35312ms message: 'network-check-target-ip-10-0-135-246: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:30:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T22:50:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-130-to-network-check-target-ip-10-0-142-10 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-130.ec2.internal uid: 1f571223-e4e2-4c62-a750-a56e86954a70 resourceVersion: "71588" uid: 633cc041-4374-4a82-aab2-17273deaa1db spec: sourcePod: network-check-source-65bdbbff45-g4fxw targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-30T22:57:58Z" message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.246407ms message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:39:58Z" - latency: 2.705645ms message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:38:58Z" - latency: 2.168112ms message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:37:58Z" - latency: 2.147906ms message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:36:58Z" - latency: 2.380932ms message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:35:58Z" - latency: 2.136399ms message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:34:58Z" - latency: 2.2967ms message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:33:58Z" - latency: 2.2171ms message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:32:58Z" - latency: 2.638783ms message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:31:58Z" - latency: 2.381796ms message: 'network-check-target-ip-10-0-142-10: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:30:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T22:50:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-130-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-130.ec2.internal uid: 1f571223-e4e2-4c62-a750-a56e86954a70 resourceVersion: "77161" uid: 8c00e518-df9d-4745-95cc-1a65cfe80a34 spec: sourcePod: network-check-source-65bdbbff45-g4fxw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-30T22:56:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 914.324µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:44:58Z" - latency: 1.776224ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T23:44:58Z" - latency: 879.661µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:43:58Z" - latency: 2.150332ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T23:43:58Z" - latency: 985.724µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:42:58Z" - latency: 2.39344ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T23:42:58Z" - latency: 938.652µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:41:58Z" - latency: 1.713127ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T23:41:58Z" - latency: 971.536µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T23:40:58Z" - latency: 1.920753ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T23:40:58Z" kind: List metadata: resourceVersion: ""