apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:22:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-79-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-79.ec2.internal uid: 14b75969-d42c-4a3a-9630-70436066e697 resourceVersion: "54633" uid: 58245555-4574-48ce-ab33-4860561a7588 spec: sourcePod: network-check-source-869dcfcdcd-n4qmz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T17:29:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 944.911µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:57:33Z" - latency: 1.01687ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:56:33Z" - latency: 1.470759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:55:33Z" - latency: 1.114044ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:54:33Z" - latency: 965.537µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:53:33Z" - latency: 901.113µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:52:33Z" - latency: 1.039209ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:51:33Z" - latency: 1.100956ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:50:33Z" - latency: 1.117713ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:49:33Z" - latency: 1.378793ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:48:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:22:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-79-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-79.ec2.internal uid: 14b75969-d42c-4a3a-9630-70436066e697 resourceVersion: "55552" uid: f49d10d2-3c79-4a42-998f-7a3da2f17d52 spec: sourcePod: network-check-source-869dcfcdcd-n4qmz targetEndpoint: a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T17:28:33Z" message: 'load-balancer-api-external: tcp connection to a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.749022ms message: 'load-balancer-api-external: tcp connection to a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:58:33Z" - latency: 8.905065ms message: 'load-balancer-api-external: resolved host name a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:58:33Z" - latency: 3.908198ms message: 'load-balancer-api-external: tcp connection to a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:57:33Z" - latency: 8.131284ms message: 'load-balancer-api-external: resolved host name a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:57:33Z" - latency: 3.886572ms message: 'load-balancer-api-external: tcp connection to a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:56:33Z" - latency: 8.412704ms message: 'load-balancer-api-external: resolved host name a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:56:33Z" - latency: 5.558856ms message: 'load-balancer-api-external: tcp connection to a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:55:33Z" - latency: 8.609308ms message: 'load-balancer-api-external: resolved host name a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:55:33Z" - latency: 6.303896ms message: 'load-balancer-api-external: tcp connection to a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:54:33Z" - latency: 7.96825ms message: 'load-balancer-api-external: resolved host name a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:54:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:22:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-79-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-79.ec2.internal uid: 14b75969-d42c-4a3a-9630-70436066e697 resourceVersion: "55553" uid: 02896d68-7462-4119-8297-ac7e9f48ca00 spec: sourcePod: network-check-source-869dcfcdcd-n4qmz targetEndpoint: a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T17:28:33Z" message: 'load-balancer-api-internal: tcp connection to a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.63294ms message: 'load-balancer-api-internal: tcp connection to a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:58:33Z" - latency: 8.818902ms message: 'load-balancer-api-internal: resolved host name a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:58:33Z" - latency: 5.546703ms message: 'load-balancer-api-internal: tcp connection to a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:57:33Z" - latency: 8.186248ms message: 'load-balancer-api-internal: resolved host name a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:57:33Z" - latency: 4.924963ms message: 'load-balancer-api-internal: tcp connection to a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:56:33Z" - latency: 8.361134ms message: 'load-balancer-api-internal: resolved host name a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:56:33Z" - latency: 5.564233ms message: 'load-balancer-api-internal: tcp connection to a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:55:33Z" - latency: 8.560247ms message: 'load-balancer-api-internal: resolved host name a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:55:33Z" - latency: 6.349313ms message: 'load-balancer-api-internal: tcp connection to a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:54:33Z" - latency: 7.863936ms message: 'load-balancer-api-internal: resolved host name a0d9f8baa4dfd4d80a4e01bc23a6f899-a8258d2e898e93fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T17:54:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:22:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-79-to-network-check-target-ip-10-0-131-79 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-79.ec2.internal uid: 14b75969-d42c-4a3a-9630-70436066e697 resourceVersion: "54630" uid: 786f6de5-0907-42ad-99f8-2891e1d9fffe spec: sourcePod: network-check-source-869dcfcdcd-n4qmz targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:29:33Z" message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 866.449µs message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:57:33Z" - latency: 786.059µs message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:56:33Z" - latency: 820.281µs message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:55:33Z" - latency: 1.271112ms message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:54:33Z" - latency: 782.308µs message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:53:33Z" - latency: 1.565665ms message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:52:33Z" - latency: 861.296µs message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:51:33Z" - latency: 1.28535ms message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:50:33Z" - latency: 1.487135ms message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:49:33Z" - latency: 783.269µs message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:48:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:22:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-79-to-network-check-target-ip-10-0-137-153 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-79.ec2.internal uid: 14b75969-d42c-4a3a-9630-70436066e697 resourceVersion: "54632" uid: d3b63b8e-3cb6-4f5b-81d1-71413c347223 spec: sourcePod: network-check-source-869dcfcdcd-n4qmz targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:29:33Z" message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.395446ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:57:33Z" - latency: 2.041159ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:56:33Z" - latency: 2.062948ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:55:33Z" - latency: 2.079986ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:54:33Z" - latency: 2.26186ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:53:33Z" - latency: 2.041429ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:52:33Z" - latency: 1.964065ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:51:33Z" - latency: 2.475387ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:50:33Z" - latency: 2.25848ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:49:33Z" - latency: 2.238406ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:48:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:22:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-79-to-network-check-target-ip-10-0-137-28 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-79.ec2.internal uid: 14b75969-d42c-4a3a-9630-70436066e697 resourceVersion: "54631" uid: 6f3bc80d-d067-419c-81c6-e9644d3ce78a spec: sourcePod: network-check-source-869dcfcdcd-n4qmz targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:29:33Z" message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.601562ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:57:33Z" - latency: 2.67482ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:56:33Z" - latency: 2.306464ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:55:33Z" - latency: 2.367181ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:54:33Z" - latency: 2.583178ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:53:33Z" - latency: 2.737068ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:52:33Z" - latency: 2.560559ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:51:33Z" - latency: 2.58232ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:50:33Z" - latency: 2.692795ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:49:33Z" - latency: 2.216287ms message: 'network-check-target-ip-10-0-137-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:48:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:22:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-79-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-79.ec2.internal uid: 14b75969-d42c-4a3a-9630-70436066e697 resourceVersion: "55551" uid: 366cc0c5-8592-4a62-b683-206faa80abdf spec: sourcePod: network-check-source-869dcfcdcd-n4qmz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T17:28:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.050683ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:58:33Z" - latency: 2.310811ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T17:58:33Z" - latency: 829.862µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:57:33Z" - latency: 1.752218ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T17:57:33Z" - latency: 969.29µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:56:33Z" - latency: 2.029192ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T17:56:33Z" - latency: 775.322µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:55:33Z" - latency: 1.787659ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T17:55:33Z" - latency: 1.119537ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T17:54:33Z" - latency: 1.660406ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T17:54:33Z" kind: List metadata: resourceVersion: ""