apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:52:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-139-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-139.ec2.internal uid: 264d15ed-f321-4dd3-b292-054678b6b61f resourceVersion: "55129" uid: dd4564b4-30f8-44a7-91e1-0b07ee29ee1b spec: sourcePod: network-check-source-869dcfcdcd-t48ft targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T02:59:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.041841ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:27:35Z" - latency: 1.364473ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:26:35Z" - latency: 1.610224ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:25:35Z" - latency: 1.284637ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:24:35Z" - latency: 948.85µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:23:35Z" - latency: 1.242218ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:22:35Z" - latency: 1.355906ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:21:35Z" - latency: 986.323µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:20:35Z" - latency: 1.196696ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:19:35Z" - latency: 1.399819ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:18:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:52:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-139-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-139.ec2.internal uid: 264d15ed-f321-4dd3-b292-054678b6b61f resourceVersion: "50416" uid: 7e31961f-763c-47f0-8c95-f965c5edaf11 spec: sourcePod: network-check-source-869dcfcdcd-t48ft targetEndpoint: ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T02:58:35Z" message: 'load-balancer-api-external: tcp connection to ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.046024ms message: 'load-balancer-api-external: tcp connection to ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:22:35Z" - latency: 6.923931ms message: 'load-balancer-api-external: resolved host name ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:22:35Z" - latency: 4.713635ms message: 'load-balancer-api-external: tcp connection to ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:21:35Z" - latency: 6.07293ms message: 'load-balancer-api-external: resolved host name ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:21:35Z" - latency: 5.65266ms message: 'load-balancer-api-external: tcp connection to ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:20:35Z" - latency: 7.205661ms message: 'load-balancer-api-external: resolved host name ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:20:35Z" - latency: 5.429738ms message: 'load-balancer-api-external: tcp connection to ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:19:35Z" - latency: 6.40101ms message: 'load-balancer-api-external: resolved host name ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:19:35Z" - latency: 5.116762ms message: 'load-balancer-api-external: tcp connection to ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:18:35Z" - latency: 7.071329ms message: 'load-balancer-api-external: resolved host name ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:18:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:52:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-139-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-139.ec2.internal uid: 264d15ed-f321-4dd3-b292-054678b6b61f resourceVersion: "50417" uid: 5b2130ae-b10a-43c9-9dd3-4a43d78779e1 spec: sourcePod: network-check-source-869dcfcdcd-t48ft targetEndpoint: ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T02:58:35Z" message: 'load-balancer-api-internal: tcp connection to ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.108017ms message: 'load-balancer-api-internal: tcp connection to ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:22:35Z" - latency: 7.029171ms message: 'load-balancer-api-internal: resolved host name ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:22:35Z" - latency: 3.885043ms message: 'load-balancer-api-internal: tcp connection to ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:21:35Z" - latency: 6.021169ms message: 'load-balancer-api-internal: resolved host name ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:21:35Z" - latency: 5.641328ms message: 'load-balancer-api-internal: tcp connection to ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:20:35Z" - latency: 7.137929ms message: 'load-balancer-api-internal: resolved host name ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:20:35Z" - latency: 5.42525ms message: 'load-balancer-api-internal: tcp connection to ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:19:35Z" - latency: 6.358016ms message: 'load-balancer-api-internal: resolved host name ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:19:35Z" - latency: 5.103773ms message: 'load-balancer-api-internal: tcp connection to ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:18:35Z" - latency: 7.037999ms message: 'load-balancer-api-internal: resolved host name ae25f4532d282449ebeaa457520cdbca-d40d579dc17a302f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T03:18:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:52:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-139-to-network-check-target-ip-10-0-130-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-139.ec2.internal uid: 264d15ed-f321-4dd3-b292-054678b6b61f resourceVersion: "55126" uid: c863e15b-cc88-4773-b959-fe991367f1d6 spec: sourcePod: network-check-source-869dcfcdcd-t48ft targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T02:59:35Z" message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 937.431µs message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:27:35Z" - latency: 1.705199ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:26:35Z" - latency: 915.182µs message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:25:35Z" - latency: 1.569492ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:24:35Z" - latency: 941.581µs message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:23:35Z" - latency: 1.046151ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:22:35Z" - latency: 774.146µs message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:21:35Z" - latency: 919.012µs message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:20:35Z" - latency: 1.060512ms message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:19:35Z" - latency: 872.029µs message: 'network-check-target-ip-10-0-130-139: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:18:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:52:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-139-to-network-check-target-ip-10-0-134-61 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-139.ec2.internal uid: 264d15ed-f321-4dd3-b292-054678b6b61f resourceVersion: "55128" uid: a1e894ca-519b-477d-832d-cf0b2d6414ae spec: sourcePod: network-check-source-869dcfcdcd-t48ft targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T02:59:35Z" message: 'network-check-target-ip-10-0-134-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.911434ms message: 'network-check-target-ip-10-0-134-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:27:35Z" - latency: 1.701375ms message: 'network-check-target-ip-10-0-134-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:26:35Z" - latency: 1.856109ms message: 'network-check-target-ip-10-0-134-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:25:35Z" - latency: 1.836717ms message: 'network-check-target-ip-10-0-134-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:24:35Z" - latency: 1.614436ms message: 'network-check-target-ip-10-0-134-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:23:35Z" - latency: 2.045419ms message: 'network-check-target-ip-10-0-134-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:22:35Z" - latency: 1.882149ms message: 'network-check-target-ip-10-0-134-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:21:35Z" - latency: 1.90883ms message: 'network-check-target-ip-10-0-134-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:20:35Z" - latency: 1.816482ms message: 'network-check-target-ip-10-0-134-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:19:35Z" - latency: 1.577465ms message: 'network-check-target-ip-10-0-134-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:18:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:52:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-139-to-network-check-target-ip-10-0-137-195 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-139.ec2.internal uid: 264d15ed-f321-4dd3-b292-054678b6b61f resourceVersion: "55127" uid: 3cdaac73-92ae-4869-b010-e7ffc9f4643e spec: sourcePod: network-check-source-869dcfcdcd-t48ft targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T02:59:35Z" message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.966992ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:27:35Z" - latency: 2.444106ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:26:35Z" - latency: 2.126707ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:25:35Z" - latency: 2.087971ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:24:35Z" - latency: 2.102324ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:23:35Z" - latency: 2.150362ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:22:35Z" - latency: 2.394211ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:21:35Z" - latency: 2.121863ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:20:35Z" - latency: 1.920316ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:19:35Z" - latency: 2.202757ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:18:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T02:52:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-139-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-139.ec2.internal uid: 264d15ed-f321-4dd3-b292-054678b6b61f resourceVersion: "50415" uid: 727259a8-7742-476b-ad80-65cc837fd4f7 spec: sourcePod: network-check-source-869dcfcdcd-t48ft targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T02:58:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.205295ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:22:35Z" - latency: 1.747465ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T03:22:35Z" - latency: 921.145µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:21:35Z" - latency: 1.828202ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T03:21:35Z" - latency: 1.026433ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:20:35Z" - latency: 2.008406ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T03:20:35Z" - latency: 810.565µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:19:35Z" - latency: 1.791425ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T03:19:35Z" - latency: 964.275µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T03:18:35Z" - latency: 2.070767ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T03:18:35Z" kind: List metadata: resourceVersion: ""