apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T22:27:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-146-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-146.ec2.internal uid: 85b66551-a1bd-470c-b4c7-cfeb302ff94f resourceVersion: "72241" uid: d76394ae-ffdf-4472-9847-dee85e187cb6 spec: sourcePod: network-check-source-65bdbbff45-52mv9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T22:34:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 812.186µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:16:39Z" - latency: 810.123µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:15:39Z" - latency: 966.265µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:14:39Z" - latency: 1.037233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:13:39Z" - latency: 1.007597ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:12:39Z" - latency: 870.104µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:11:39Z" - latency: 956.66µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:10:39Z" - latency: 961.624µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:09:39Z" - latency: 1.169309ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:08:39Z" - latency: 880.574µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:07:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T22:27:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-146-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-146.ec2.internal uid: 85b66551-a1bd-470c-b4c7-cfeb302ff94f resourceVersion: "77432" uid: b5918198-1187-4baa-b83a-042b16ba61c8 spec: sourcePod: network-check-source-65bdbbff45-52mv9 targetEndpoint: aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T22:33:39Z" message: 'load-balancer-api-external: tcp connection to aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.2124ms message: 'load-balancer-api-external: tcp connection to aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:21:39Z" - latency: 9.004456ms message: 'load-balancer-api-external: resolved host name aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T23:21:39Z" - latency: 4.871328ms message: 'load-balancer-api-external: tcp connection to aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:20:39Z" - latency: 8.97042ms message: 'load-balancer-api-external: resolved host name aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T23:20:39Z" - latency: 4.497705ms message: 'load-balancer-api-external: tcp connection to aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:19:39Z" - latency: 6.707084ms message: 'load-balancer-api-external: resolved host name aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T23:19:39Z" - latency: 5.091713ms message: 'load-balancer-api-external: tcp connection to aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:18:39Z" - latency: 8.614738ms message: 'load-balancer-api-external: resolved host name aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T23:18:39Z" - latency: 5.468365ms message: 'load-balancer-api-external: tcp connection to aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:17:39Z" - latency: 8.02976ms message: 'load-balancer-api-external: resolved host name aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T23:17:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T22:27:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-146-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-146.ec2.internal uid: 85b66551-a1bd-470c-b4c7-cfeb302ff94f resourceVersion: "77431" uid: 8cddbe1d-9447-4e16-8c91-a2beaf4593fa spec: sourcePod: network-check-source-65bdbbff45-52mv9 targetEndpoint: aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T22:33:39Z" message: 'load-balancer-api-internal: tcp connection to aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.207308ms message: 'load-balancer-api-internal: tcp connection to aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:21:39Z" - latency: 8.984508ms message: 'load-balancer-api-internal: resolved host name aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T23:21:39Z" - latency: 4.861492ms message: 'load-balancer-api-internal: tcp connection to aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:20:39Z" - latency: 8.928202ms message: 'load-balancer-api-internal: resolved host name aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T23:20:39Z" - latency: 4.478465ms message: 'load-balancer-api-internal: tcp connection to aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:19:39Z" - latency: 6.743975ms message: 'load-balancer-api-internal: resolved host name aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T23:19:39Z" - latency: 5.042714ms message: 'load-balancer-api-internal: tcp connection to aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:18:39Z" - latency: 8.692226ms message: 'load-balancer-api-internal: resolved host name aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T23:18:39Z" - latency: 3.35084ms message: 'load-balancer-api-internal: tcp connection to aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:17:39Z" - latency: 8.050212ms message: 'load-balancer-api-internal: resolved host name aacc6ab0974f04fdc93b9dbf6c698a68-050955e1758287d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T23:17:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T22:27:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-146-to-network-check-target-ip-10-0-137-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-146.ec2.internal uid: 85b66551-a1bd-470c-b4c7-cfeb302ff94f resourceVersion: "72240" uid: a6fb55e8-816e-4a37-9140-0026c30318fe spec: sourcePod: network-check-source-65bdbbff45-52mv9 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T22:34:39Z" message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.027049ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:16:39Z" - latency: 2.577547ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:15:39Z" - latency: 2.238446ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:14:39Z" - latency: 2.283935ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:13:39Z" - latency: 2.397119ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:12:39Z" - latency: 2.53388ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:11:39Z" - latency: 2.631231ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:10:39Z" - latency: 2.102212ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:09:39Z" - latency: 2.310099ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:08:39Z" - latency: 2.590455ms message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:07:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T22:27:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-146-to-network-check-target-ip-10-0-137-148 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-146.ec2.internal uid: 85b66551-a1bd-470c-b4c7-cfeb302ff94f resourceVersion: "72239" uid: 211d5372-e94e-43f6-9309-341d33477149 spec: sourcePod: network-check-source-65bdbbff45-52mv9 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T22:34:39Z" message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.044208ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:16:39Z" - latency: 2.072615ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:15:39Z" - latency: 2.328762ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:14:39Z" - latency: 2.714486ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:13:39Z" - latency: 2.1413ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:12:39Z" - latency: 2.419318ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:11:39Z" - latency: 2.269432ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:10:39Z" - latency: 2.13441ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:09:39Z" - latency: 2.311557ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:08:39Z" - latency: 2.454945ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:07:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T22:27:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-146-to-network-check-target-ip-10-0-142-146 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-146.ec2.internal uid: 85b66551-a1bd-470c-b4c7-cfeb302ff94f resourceVersion: "72238" uid: 0ec64f10-7a9e-4560-a47d-32d3ffacaca4 spec: sourcePod: network-check-source-65bdbbff45-52mv9 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T22:34:39Z" message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 918.401µs message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:16:39Z" - latency: 1.0992ms message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:15:39Z" - latency: 927.402µs message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:14:39Z" - latency: 1.675931ms message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:13:39Z" - latency: 1.171215ms message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:12:39Z" - latency: 1.050398ms message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:11:39Z" - latency: 1.684876ms message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:10:39Z" - latency: 753.579µs message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:09:39Z" - latency: 2.489091ms message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:08:39Z" - latency: 1.285891ms message: 'network-check-target-ip-10-0-142-146: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:07:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T22:27:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-146-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-146.ec2.internal uid: 85b66551-a1bd-470c-b4c7-cfeb302ff94f resourceVersion: "77430" uid: 1d050397-aa74-4cee-968f-f8806d02fabd spec: sourcePod: network-check-source-65bdbbff45-52mv9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T22:33:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.092079ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:21:39Z" - latency: 2.087791ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T23:21:39Z" - latency: 1.040896ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:20:39Z" - latency: 1.886933ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T23:20:39Z" - latency: 937.325µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:19:39Z" - latency: 1.957694ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T23:19:39Z" - latency: 1.295722ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:18:39Z" - latency: 1.769189ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T23:18:39Z" - latency: 1.062818ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T23:17:39Z" - latency: 1.996526ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T23:17:39Z" kind: List metadata: resourceVersion: ""