apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T21:20:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-133-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-133.ec2.internal uid: e38f4f9f-4190-484a-81eb-10a59af628a8 resourceVersion: "68354" uid: 63b22d87-fb16-46a4-a89b-098c602cc92f spec: sourcePod: network-check-source-6f8b768455-7sw87 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-11T21:27:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 687.256µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:55:30Z" - latency: 1.036719ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:54:30Z" - latency: 854.524µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:53:30Z" - latency: 963.239µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:52:30Z" - latency: 1.14031ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:51:30Z" - latency: 1.052835ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:50:30Z" - latency: 1.214915ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:49:30Z" - latency: 1.119968ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:48:30Z" - latency: 1.058252ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:47:30Z" - latency: 863.991µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:46:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T21:20:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-133-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-133.ec2.internal uid: e38f4f9f-4190-484a-81eb-10a59af628a8 resourceVersion: "64027" uid: 1798f2ef-f6fa-46d0-a9c0-23b42d24cd7e spec: sourcePod: network-check-source-6f8b768455-7sw87 targetEndpoint: adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T21:26:30Z" message: 'load-balancer-api-external: tcp connection to adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.567916ms message: 'load-balancer-api-external: tcp connection to adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:50:30Z" - latency: 6.20184ms message: 'load-balancer-api-external: resolved host name adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T21:50:30Z" - latency: 5.367195ms message: 'load-balancer-api-external: tcp connection to adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:49:30Z" - latency: 6.694385ms message: 'load-balancer-api-external: resolved host name adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T21:49:30Z" - latency: 4.10012ms message: 'load-balancer-api-external: tcp connection to adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:48:30Z" - latency: 6.761469ms message: 'load-balancer-api-external: resolved host name adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T21:48:30Z" - latency: 4.496441ms message: 'load-balancer-api-external: tcp connection to adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:47:30Z" - latency: 9.978439ms message: 'load-balancer-api-external: resolved host name adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T21:47:30Z" - latency: 5.409765ms message: 'load-balancer-api-external: tcp connection to adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:46:30Z" - latency: 6.730372ms message: 'load-balancer-api-external: resolved host name adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T21:46:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T21:20:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-133-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-133.ec2.internal uid: e38f4f9f-4190-484a-81eb-10a59af628a8 resourceVersion: "64026" uid: c15e089c-692f-4b12-8819-cc110ede0a3f spec: sourcePod: network-check-source-6f8b768455-7sw87 targetEndpoint: adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T21:26:30Z" message: 'load-balancer-api-internal: tcp connection to adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.558356ms message: 'load-balancer-api-internal: tcp connection to adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:50:30Z" - latency: 6.290168ms message: 'load-balancer-api-internal: resolved host name adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T21:50:30Z" - latency: 4.971766ms message: 'load-balancer-api-internal: tcp connection to adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:49:30Z" - latency: 6.635869ms message: 'load-balancer-api-internal: resolved host name adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T21:49:30Z" - latency: 4.73015ms message: 'load-balancer-api-internal: tcp connection to adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:48:30Z" - latency: 6.841068ms message: 'load-balancer-api-internal: resolved host name adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T21:48:30Z" - latency: 4.362338ms message: 'load-balancer-api-internal: tcp connection to adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:47:30Z" - latency: 9.909321ms message: 'load-balancer-api-internal: resolved host name adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T21:47:30Z" - latency: 5.472807ms message: 'load-balancer-api-internal: tcp connection to adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:46:30Z" - latency: 6.811311ms message: 'load-balancer-api-internal: resolved host name adac863aeb96342689e9a9e4031f9261-54c163eb5fe0c03b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T21:46:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T21:20:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-133-to-network-check-target-ip-10-0-135-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-133.ec2.internal uid: e38f4f9f-4190-484a-81eb-10a59af628a8 resourceVersion: "68351" uid: f0709171-19f2-4001-8327-0288445bda10 spec: sourcePod: network-check-source-6f8b768455-7sw87 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-11T21:27:30Z" message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 853.95µs message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:55:30Z" - latency: 853.617µs message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:54:30Z" - latency: 734.03µs message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:53:30Z" - latency: 873.575µs message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:52:30Z" - latency: 877.083µs message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:51:30Z" - latency: 831.116µs message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:50:30Z" - latency: 1.307029ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:49:30Z" - latency: 751.395µs message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:48:30Z" - latency: 945.869µs message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:47:30Z" - latency: 843.098µs message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:46:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T21:20:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-133-to-network-check-target-ip-10-0-136-69 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-133.ec2.internal uid: e38f4f9f-4190-484a-81eb-10a59af628a8 resourceVersion: "68353" uid: 73a30356-bd7f-4636-b8ef-f2c26343ed9d spec: sourcePod: network-check-source-6f8b768455-7sw87 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-11T21:27:30Z" message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.177444ms message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:55:30Z" - latency: 2.214291ms message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:54:30Z" - latency: 2.264274ms message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:53:30Z" - latency: 2.211252ms message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:52:30Z" - latency: 2.352408ms message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:51:30Z" - latency: 1.955036ms message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:50:30Z" - latency: 2.380761ms message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:49:30Z" - latency: 2.233502ms message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:48:30Z" - latency: 2.130437ms message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:47:30Z" - latency: 2.425536ms message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:46:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T21:20:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-133-to-network-check-target-ip-10-0-141-71 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-133.ec2.internal uid: e38f4f9f-4190-484a-81eb-10a59af628a8 resourceVersion: "68352" uid: fd13a28b-fe3e-4a81-9e93-239e4ba5634a spec: sourcePod: network-check-source-6f8b768455-7sw87 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-11T21:27:30Z" message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.093078ms message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:55:30Z" - latency: 2.162444ms message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:54:30Z" - latency: 2.029962ms message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:53:30Z" - latency: 1.885179ms message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:52:30Z" - latency: 2.151088ms message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:51:30Z" - latency: 1.938081ms message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:50:30Z" - latency: 2.108757ms message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:49:30Z" - latency: 2.174137ms message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:48:30Z" - latency: 2.025635ms message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:47:30Z" - latency: 2.001177ms message: 'network-check-target-ip-10-0-141-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:46:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T21:20:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-133-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-133.ec2.internal uid: e38f4f9f-4190-484a-81eb-10a59af628a8 resourceVersion: "64025" uid: e1b82a77-ed25-49ba-b21d-475e339def2e spec: sourcePod: network-check-source-6f8b768455-7sw87 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-11T21:26:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.051845ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:50:30Z" - latency: 1.830422ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T21:50:30Z" - latency: 1.102069ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:49:30Z" - latency: 1.742917ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T21:49:30Z" - latency: 1.08726ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:48:30Z" - latency: 2.122921ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T21:48:30Z" - latency: 943.031µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:47:30Z" - latency: 1.736695ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T21:47:30Z" - latency: 1.000328ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T21:46:30Z" - latency: 1.81371ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T21:46:30Z" kind: List metadata: resourceVersion: ""