apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T12:18:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-55-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-55.ec2.internal uid: e9fa3d73-4781-4ff2-88b8-e6fc22d262a6 resourceVersion: "24268" uid: 83d7d815-fff9-4c54-9fe7-f1372ad554c5 spec: sourcePod: network-check-source-8894fc9bd-48fqr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-20T12:25:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 849.849µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:53:15Z" - latency: 1.05593ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:52:15Z" - latency: 1.113217ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:51:15Z" - latency: 982.033µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:50:15Z" - latency: 826.611µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:49:15Z" - latency: 822.492µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:48:15Z" - latency: 848.56µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:47:15Z" - latency: 830.151µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:46:15Z" - latency: 759.401µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:45:15Z" - latency: 762.978µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:44:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T12:18:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-55-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-55.ec2.internal uid: e9fa3d73-4781-4ff2-88b8-e6fc22d262a6 resourceVersion: "24597" uid: 773503a0-aee4-4016-a4fd-be0c0f6aa779 spec: sourcePod: network-check-source-8894fc9bd-48fqr targetEndpoint: abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T12:24:15Z" message: 'load-balancer-api-external: tcp connection to abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.504326ms message: 'load-balancer-api-external: tcp connection to abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:54:15Z" - latency: 8.102359ms message: 'load-balancer-api-external: resolved host name abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T12:54:15Z" - latency: 5.219843ms message: 'load-balancer-api-external: tcp connection to abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:53:15Z" - latency: 11.254937ms message: 'load-balancer-api-external: resolved host name abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T12:53:15Z" - latency: 3.642686ms message: 'load-balancer-api-external: tcp connection to abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:52:15Z" - latency: 7.597996ms message: 'load-balancer-api-external: resolved host name abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T12:52:15Z" - latency: 4.348966ms message: 'load-balancer-api-external: tcp connection to abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:51:15Z" - latency: 7.923059ms message: 'load-balancer-api-external: resolved host name abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T12:51:15Z" - latency: 4.924662ms message: 'load-balancer-api-external: tcp connection to abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:50:15Z" - latency: 8.205612ms message: 'load-balancer-api-external: resolved host name abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T12:50:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T12:18:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-55-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-55.ec2.internal uid: e9fa3d73-4781-4ff2-88b8-e6fc22d262a6 resourceVersion: "24596" uid: f0ecbf50-c348-45ad-8707-d4eb5ce82449 spec: sourcePod: network-check-source-8894fc9bd-48fqr targetEndpoint: abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T12:24:15Z" message: 'load-balancer-api-internal: tcp connection to abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.486345ms message: 'load-balancer-api-internal: tcp connection to abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:54:15Z" - latency: 8.031656ms message: 'load-balancer-api-internal: resolved host name abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T12:54:15Z" - latency: 5.236584ms message: 'load-balancer-api-internal: tcp connection to abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:53:15Z" - latency: 11.218413ms message: 'load-balancer-api-internal: resolved host name abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T12:53:15Z" - latency: 4.415707ms message: 'load-balancer-api-internal: tcp connection to abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:52:15Z" - latency: 7.70766ms message: 'load-balancer-api-internal: resolved host name abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T12:52:15Z" - latency: 4.067988ms message: 'load-balancer-api-internal: tcp connection to abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:51:15Z" - latency: 7.936317ms message: 'load-balancer-api-internal: resolved host name abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T12:51:15Z" - latency: 4.910358ms message: 'load-balancer-api-internal: tcp connection to abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:50:15Z" - latency: 8.254589ms message: 'load-balancer-api-internal: resolved host name abfff2348aca8429495cdf20e3c66e7e-9e72cbad1064ad01.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T12:50:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T12:18:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-55-to-network-check-target-ip-10-0-131-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-55.ec2.internal uid: e9fa3d73-4781-4ff2-88b8-e6fc22d262a6 resourceVersion: "24266" uid: add98aa7-093d-4d27-b0cd-26911e574252 spec: sourcePod: network-check-source-8894fc9bd-48fqr targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-20T12:25:15Z" message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 754.919µs message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:53:15Z" - latency: 766.965µs message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:52:15Z" - latency: 664.672µs message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:51:15Z" - latency: 961.257µs message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:50:15Z" - latency: 1.013122ms message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:49:15Z" - latency: 988.822µs message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:48:15Z" - latency: 693.157µs message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:47:15Z" - latency: 1.114582ms message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:46:15Z" - latency: 921.665µs message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:45:15Z" - latency: 1.121577ms message: 'network-check-target-ip-10-0-131-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:44:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T12:18:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-55-to-network-check-target-ip-10-0-135-187 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-55.ec2.internal uid: e9fa3d73-4781-4ff2-88b8-e6fc22d262a6 resourceVersion: "24267" uid: 19f09a01-46dc-428d-8147-9122e6e55e6f spec: sourcePod: network-check-source-8894fc9bd-48fqr targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-20T12:25:15Z" message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.79734ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:53:15Z" - latency: 1.902827ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:52:15Z" - latency: 1.87693ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:51:15Z" - latency: 1.844608ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:50:15Z" - latency: 1.768157ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:49:15Z" - latency: 1.642643ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:48:15Z" - latency: 1.717668ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:47:15Z" - latency: 2.038958ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:46:15Z" - latency: 1.918566ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:45:15Z" - latency: 1.985193ms message: 'network-check-target-ip-10-0-135-187: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:44:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T12:18:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-55-to-network-check-target-ip-10-0-137-91 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-55.ec2.internal uid: e9fa3d73-4781-4ff2-88b8-e6fc22d262a6 resourceVersion: "24265" uid: a886d3b4-a837-48d0-ac59-88bf81bfb579 spec: sourcePod: network-check-source-8894fc9bd-48fqr targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-20T12:25:15Z" message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.593387ms message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:53:15Z" - latency: 1.403212ms message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:52:15Z" - latency: 1.770026ms message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:51:15Z" - latency: 1.643662ms message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:50:15Z" - latency: 1.847805ms message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:49:15Z" - latency: 1.909622ms message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:48:15Z" - latency: 1.593013ms message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:47:15Z" - latency: 1.59001ms message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:46:15Z" - latency: 1.896384ms message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:45:15Z" - latency: 1.654797ms message: 'network-check-target-ip-10-0-137-91: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:44:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T12:18:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-55-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-55.ec2.internal uid: e9fa3d73-4781-4ff2-88b8-e6fc22d262a6 resourceVersion: "24595" uid: 7c1f5204-00f3-4bf5-b18e-53d7029590aa spec: sourcePod: network-check-source-8894fc9bd-48fqr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-20T12:24:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 873.777µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:54:15Z" - latency: 1.57101ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T12:54:15Z" - latency: 763.031µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:53:15Z" - latency: 1.466425ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T12:53:15Z" - latency: 739.195µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:52:15Z" - latency: 2.144417ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T12:52:15Z" - latency: 798.381µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:51:15Z" - latency: 1.734856ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T12:51:15Z" - latency: 861.624µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T12:50:15Z" - latency: 1.688392ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T12:50:15Z" kind: List metadata: resourceVersion: ""