apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T13:52:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-163-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-163.ec2.internal uid: 45142e9d-c89b-42ae-a4cd-8811e7fa8bc7 resourceVersion: "71500" uid: ed17b917-878d-4d99-82d0-8354f023d033 spec: sourcePod: network-check-source-7bc5b6bf85-5t9qw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-17T13:59:03Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 848.555µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:41:03Z" - latency: 829.488µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:40:03Z" - latency: 975.621µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:39:03Z" - latency: 886.305µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:38:03Z" - latency: 913.06µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:37:03Z" - latency: 873.902µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:36:03Z" - latency: 1.352545ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:35:03Z" - latency: 1.300364ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:34:03Z" - latency: 941.476µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:33:03Z" - latency: 789.955µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:32:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T13:52:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-163-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-163.ec2.internal uid: 45142e9d-c89b-42ae-a4cd-8811e7fa8bc7 resourceVersion: "70167" uid: 86bdf3c3-badd-487e-9d69-283b536ecc0e spec: sourcePod: network-check-source-7bc5b6bf85-5t9qw targetEndpoint: a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T13:58:03Z" message: 'load-balancer-api-external: tcp connection to a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.644914ms message: 'load-balancer-api-external: tcp connection to a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:40:03Z" - latency: 7.096704ms message: 'load-balancer-api-external: resolved host name a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:40:03Z" - latency: 4.965095ms message: 'load-balancer-api-external: tcp connection to a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:39:03Z" - latency: 6.872353ms message: 'load-balancer-api-external: resolved host name a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:39:03Z" - latency: 4.245948ms message: 'load-balancer-api-external: tcp connection to a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:38:03Z" - latency: 8.035678ms message: 'load-balancer-api-external: resolved host name a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:38:03Z" - latency: 3.889527ms message: 'load-balancer-api-external: tcp connection to a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:37:03Z" - latency: 6.574425ms message: 'load-balancer-api-external: resolved host name a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:37:03Z" - latency: 3.812549ms message: 'load-balancer-api-external: tcp connection to a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:36:03Z" - latency: 7.946467ms message: 'load-balancer-api-external: resolved host name a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:36:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T13:52:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-163-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-163.ec2.internal uid: 45142e9d-c89b-42ae-a4cd-8811e7fa8bc7 resourceVersion: "70166" uid: c8172448-86d2-4026-a1ce-c3499b100f1e spec: sourcePod: network-check-source-7bc5b6bf85-5t9qw targetEndpoint: a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-17T13:58:03Z" message: 'load-balancer-api-internal: tcp connection to a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.449894ms message: 'load-balancer-api-internal: tcp connection to a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:40:03Z" - latency: 7.058632ms message: 'load-balancer-api-internal: resolved host name a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:40:03Z" - latency: 4.276098ms message: 'load-balancer-api-internal: tcp connection to a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:39:03Z" - latency: 6.755092ms message: 'load-balancer-api-internal: resolved host name a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:39:03Z" - latency: 3.724277ms message: 'load-balancer-api-internal: tcp connection to a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:38:03Z" - latency: 8.055394ms message: 'load-balancer-api-internal: resolved host name a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:38:03Z" - latency: 4.398738ms message: 'load-balancer-api-internal: tcp connection to a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:37:03Z" - latency: 6.542088ms message: 'load-balancer-api-internal: resolved host name a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:37:03Z" - latency: 3.837498ms message: 'load-balancer-api-internal: tcp connection to a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:36:03Z" - latency: 7.925621ms message: 'load-balancer-api-internal: resolved host name a4bb23157ab5c4774a928474065a92c9-71924dde8c51fe5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-17T14:36:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T13:52:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-163-to-network-check-target-ip-10-0-129-191 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-163.ec2.internal uid: 45142e9d-c89b-42ae-a4cd-8811e7fa8bc7 resourceVersion: "71498" uid: ae25af47-aa29-4cb9-a945-8c5dc4012586 spec: sourcePod: network-check-source-7bc5b6bf85-5t9qw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T13:59:03Z" message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.018183ms message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:41:03Z" - latency: 2.048538ms message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:40:03Z" - latency: 2.101201ms message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:39:03Z" - latency: 1.978263ms message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:38:03Z" - latency: 1.758697ms message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:37:03Z" - latency: 2.122483ms message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:36:03Z" - latency: 1.722525ms message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:35:03Z" - latency: 2.012172ms message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:34:03Z" - latency: 1.906055ms message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:33:03Z" - latency: 1.812079ms message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:32:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T13:52:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-163-to-network-check-target-ip-10-0-133-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-163.ec2.internal uid: 45142e9d-c89b-42ae-a4cd-8811e7fa8bc7 resourceVersion: "71499" uid: 9572c74a-cce4-4a44-9e88-c7bbcf5b441a spec: sourcePod: network-check-source-7bc5b6bf85-5t9qw targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-17T13:59:03Z" message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.030317ms message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:41:03Z" - latency: 2.236038ms message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:40:03Z" - latency: 2.529852ms message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:39:03Z" - latency: 2.100053ms message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:38:03Z" - latency: 2.230632ms message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:37:03Z" - latency: 2.217411ms message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:36:03Z" - latency: 2.037132ms message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:35:03Z" - latency: 2.242967ms message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:34:03Z" - latency: 2.119571ms message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:33:03Z" - latency: 2.555743ms message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:32:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T13:52:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-163-to-network-check-target-ip-10-0-137-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-163.ec2.internal uid: 45142e9d-c89b-42ae-a4cd-8811e7fa8bc7 resourceVersion: "71497" uid: 397d028f-9b8c-46b4-93ca-5c2636f86da2 spec: sourcePod: network-check-source-7bc5b6bf85-5t9qw targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-17T13:59:03Z" message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.189174ms message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:41:03Z" - latency: 919.449µs message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:40:03Z" - latency: 899.338µs message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:39:03Z" - latency: 821.284µs message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:38:03Z" - latency: 1.023113ms message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:37:03Z" - latency: 1.008685ms message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:36:03Z" - latency: 917.09µs message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:35:03Z" - latency: 1.047158ms message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:34:03Z" - latency: 876.203µs message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:33:03Z" - latency: 1.138848ms message: 'network-check-target-ip-10-0-137-163: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:32:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-17T13:52:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-163-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-163.ec2.internal uid: 45142e9d-c89b-42ae-a4cd-8811e7fa8bc7 resourceVersion: "70164" uid: 3006dcfb-b820-4ce3-8f16-42fbac266e7d spec: sourcePod: network-check-source-7bc5b6bf85-5t9qw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-17T13:58:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 959.98µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:40:03Z" - latency: 1.756477ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T14:40:03Z" - latency: 1.222495ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:39:03Z" - latency: 1.67115ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T14:39:03Z" - latency: 870.791µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:38:03Z" - latency: 1.679158ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T14:38:03Z" - latency: 845.635µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:37:03Z" - latency: 1.815377ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T14:37:03Z" - latency: 1.34993ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-17T14:36:03Z" - latency: 1.735522ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-17T14:36:03Z" kind: List metadata: resourceVersion: ""