apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.ec2.internal uid: 909345f8-1b1d-4471-9c2e-f5ad74142a58 resourceVersion: "52812" uid: 5fb1dabe-f958-4e4e-8761-f3833768ee4a spec: sourcePod: network-check-source-7d88cb55d8-zw8t7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T10:39:10Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 920.491µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:56:10Z" - latency: 1.001323ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:55:10Z" - latency: 1.078703ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:54:10Z" - latency: 1.033216ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:53:10Z" - latency: 1.082631ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:52:10Z" - latency: 1.790376ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:51:10Z" - latency: 1.085573ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:50:10Z" - latency: 981.509µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:49:10Z" - latency: 1.040744ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:48:10Z" - latency: 954.139µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:47:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.ec2.internal uid: 909345f8-1b1d-4471-9c2e-f5ad74142a58 resourceVersion: "52816" uid: 6da00ef7-b0f4-4508-ba0b-192bd28daa12 spec: sourcePod: network-check-source-7d88cb55d8-zw8t7 targetEndpoint: a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T10:38:10Z" message: 'load-balancer-api-external: tcp connection to a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.646489ms message: 'load-balancer-api-external: tcp connection to a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:56:10Z" - latency: 9.000274ms message: 'load-balancer-api-external: resolved host name a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T11:56:10Z" - latency: 3.721933ms message: 'load-balancer-api-external: tcp connection to a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:55:10Z" - latency: 8.153867ms message: 'load-balancer-api-external: resolved host name a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T11:55:10Z" - latency: 4.298785ms message: 'load-balancer-api-external: tcp connection to a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:54:10Z" - latency: 7.791623ms message: 'load-balancer-api-external: resolved host name a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T11:54:10Z" - latency: 5.681805ms message: 'load-balancer-api-external: tcp connection to a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:53:10Z" - latency: 7.967046ms message: 'load-balancer-api-external: resolved host name a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T11:53:10Z" - latency: 4.952102ms message: 'load-balancer-api-external: tcp connection to a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:52:10Z" - latency: 7.633138ms message: 'load-balancer-api-external: resolved host name a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T11:52:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.ec2.internal uid: 909345f8-1b1d-4471-9c2e-f5ad74142a58 resourceVersion: "52815" uid: 08e402b4-43ce-4950-9bbb-ae7a227237e1 spec: sourcePod: network-check-source-7d88cb55d8-zw8t7 targetEndpoint: a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T10:38:10Z" message: 'load-balancer-api-internal: tcp connection to a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.520752ms message: 'load-balancer-api-internal: tcp connection to a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:56:10Z" - latency: 9.04956ms message: 'load-balancer-api-internal: resolved host name a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T11:56:10Z" - latency: 4.04789ms message: 'load-balancer-api-internal: tcp connection to a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:55:10Z" - latency: 8.125616ms message: 'load-balancer-api-internal: resolved host name a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T11:55:10Z" - latency: 4.951776ms message: 'load-balancer-api-internal: tcp connection to a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:54:10Z" - latency: 7.732797ms message: 'load-balancer-api-internal: resolved host name a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T11:54:10Z" - latency: 5.691767ms message: 'load-balancer-api-internal: tcp connection to a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:53:10Z" - latency: 7.892256ms message: 'load-balancer-api-internal: resolved host name a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T11:53:10Z" - latency: 3.988107ms message: 'load-balancer-api-internal: tcp connection to a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:52:10Z" - latency: 7.561146ms message: 'load-balancer-api-internal: resolved host name a7664ace7df9042fd9efbaef4ecb5fad-2cf4d181dde39cdf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T11:52:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-network-check-target-ip-10-0-134-91 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.ec2.internal uid: 909345f8-1b1d-4471-9c2e-f5ad74142a58 resourceVersion: "52810" uid: 523e06f5-ea36-4c69-af02-1ae0a41c9521 spec: sourcePod: network-check-source-7d88cb55d8-zw8t7 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T10:39:10Z" message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.326347ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:56:10Z" - latency: 2.060486ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:55:10Z" - latency: 2.116868ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:54:10Z" - latency: 2.017071ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:53:10Z" - latency: 1.674775ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:52:10Z" - latency: 2.424549ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:51:10Z" - latency: 1.958519ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:50:10Z" - latency: 2.734442ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:49:10Z" - latency: 2.151849ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:48:10Z" - latency: 2.185715ms message: 'network-check-target-ip-10-0-134-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:47:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-network-check-target-ip-10-0-138-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.ec2.internal uid: 909345f8-1b1d-4471-9c2e-f5ad74142a58 resourceVersion: "52814" uid: 8f35affd-4a9b-4e4f-b930-539ea5ca5a27 spec: sourcePod: network-check-source-7d88cb55d8-zw8t7 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T10:39:10Z" message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.166055ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:56:10Z" - latency: 2.629584ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:55:10Z" - latency: 2.294756ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:54:10Z" - latency: 2.203246ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:53:10Z" - latency: 2.200622ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:52:10Z" - latency: 2.341785ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:51:10Z" - latency: 2.219911ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:50:10Z" - latency: 2.778006ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:49:10Z" - latency: 2.248289ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:48:10Z" - latency: 2.280466ms message: 'network-check-target-ip-10-0-138-159: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:47:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-network-check-target-ip-10-0-138-52 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.ec2.internal uid: 909345f8-1b1d-4471-9c2e-f5ad74142a58 resourceVersion: "52811" uid: 6f3c9a2c-8689-471b-81b2-b3a64bcea90a spec: sourcePod: network-check-source-7d88cb55d8-zw8t7 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T10:39:10Z" message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 844.061µs message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:56:10Z" - latency: 850.608µs message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:55:10Z" - latency: 898.008µs message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:54:10Z" - latency: 805.013µs message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:53:10Z" - latency: 1.343806ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:52:10Z" - latency: 1.103187ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:51:10Z" - latency: 896.452µs message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:50:10Z" - latency: 1.439388ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:49:10Z" - latency: 1.445675ms message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:48:10Z" - latency: 953.103µs message: 'network-check-target-ip-10-0-138-52: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:47:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T10:32:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-52-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-52.ec2.internal uid: 909345f8-1b1d-4471-9c2e-f5ad74142a58 resourceVersion: "52813" uid: 48202a73-6e4a-439f-9a69-feed4d4351de spec: sourcePod: network-check-source-7d88cb55d8-zw8t7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T10:38:10Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 922.041µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:56:10Z" - latency: 1.981158ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T11:56:10Z" - latency: 1.241035ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:55:10Z" - latency: 1.556055ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T11:55:10Z" - latency: 1.101069ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:54:10Z" - latency: 1.66235ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T11:54:10Z" - latency: 839.478µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:53:10Z" - latency: 1.64298ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T11:53:10Z" - latency: 828.282µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T11:52:10Z" - latency: 1.689594ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T11:52:10Z" kind: List metadata: resourceVersion: ""