apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:10:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-173-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-173.ec2.internal uid: c4a75fb0-bfb7-4c26-9f37-69ccd77c613c resourceVersion: "73594" uid: c326796e-9f06-4cda-a905-42106d0a007c spec: sourcePod: network-check-source-7d88cb55d8-8wq8w targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T01:17:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.061222ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:59:22Z" - latency: 909.978µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:58:22Z" - latency: 945.164µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:57:22Z" - latency: 965.062µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:56:22Z" - latency: 1.135403ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:55:22Z" - latency: 928.737µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:54:22Z" - latency: 1.157629ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:53:22Z" - latency: 1.075071ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:52:22Z" - latency: 914.994µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:51:22Z" - latency: 842.994µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:50:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:10:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-173-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-173.ec2.internal uid: c4a75fb0-bfb7-4c26-9f37-69ccd77c613c resourceVersion: "71116" uid: bbdb84b4-458d-441c-8e66-3084a254d2b1 spec: sourcePod: network-check-source-7d88cb55d8-8wq8w targetEndpoint: ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T01:16:22Z" message: 'load-balancer-api-external: tcp connection to ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.069353ms message: 'load-balancer-api-external: tcp connection to ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:58:22Z" - latency: 9.082411ms message: 'load-balancer-api-external: resolved host name ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:58:22Z" - latency: 5.577689ms message: 'load-balancer-api-external: tcp connection to ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:57:22Z" - latency: 7.957097ms message: 'load-balancer-api-external: resolved host name ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:57:22Z" - latency: 4.379879ms message: 'load-balancer-api-external: tcp connection to ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:56:22Z" - latency: 8.350761ms message: 'load-balancer-api-external: resolved host name ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:56:22Z" - latency: 4.06879ms message: 'load-balancer-api-external: tcp connection to ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:55:22Z" - latency: 8.376802ms message: 'load-balancer-api-external: resolved host name ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:55:22Z" - latency: 3.728664ms message: 'load-balancer-api-external: tcp connection to ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:54:22Z" - latency: 7.261097ms message: 'load-balancer-api-external: resolved host name ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:54:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:10:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-173-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-173.ec2.internal uid: c4a75fb0-bfb7-4c26-9f37-69ccd77c613c resourceVersion: "71117" uid: 9d461190-288f-4b32-906f-0c75c49e19e2 spec: sourcePod: network-check-source-7d88cb55d8-8wq8w targetEndpoint: ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T01:16:22Z" message: 'load-balancer-api-internal: tcp connection to ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.083533ms message: 'load-balancer-api-internal: tcp connection to ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:58:22Z" - latency: 9.060053ms message: 'load-balancer-api-internal: resolved host name ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:58:22Z" - latency: 4.2066ms message: 'load-balancer-api-internal: tcp connection to ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:57:22Z" - latency: 8.009617ms message: 'load-balancer-api-internal: resolved host name ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:57:22Z" - latency: 7.448001ms message: 'load-balancer-api-internal: tcp connection to ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:56:22Z" - latency: 8.435319ms message: 'load-balancer-api-internal: resolved host name ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:56:22Z" - latency: 4.776336ms message: 'load-balancer-api-internal: tcp connection to ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:55:22Z" - latency: 8.322225ms message: 'load-balancer-api-internal: resolved host name ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:55:22Z" - latency: 3.734586ms message: 'load-balancer-api-internal: tcp connection to ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:54:22Z" - latency: 7.229117ms message: 'load-balancer-api-internal: resolved host name ad9c9178f8f2140dfb54eb362f5de157-fd55fe6ce5abec12.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T01:54:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:10:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-173-to-network-check-target-ip-10-0-131-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-173.ec2.internal uid: c4a75fb0-bfb7-4c26-9f37-69ccd77c613c resourceVersion: "73592" uid: 433d873c-70f0-4512-b502-9a236547e88b spec: sourcePod: network-check-source-7d88cb55d8-8wq8w targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T01:17:22Z" message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.028695ms message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:59:22Z" - latency: 2.310092ms message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:58:22Z" - latency: 2.262988ms message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:57:22Z" - latency: 2.177545ms message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:56:22Z" - latency: 2.2768ms message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:55:22Z" - latency: 2.312252ms message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:54:22Z" - latency: 2.463267ms message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:53:22Z" - latency: 2.366065ms message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:52:22Z" - latency: 2.236021ms message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:51:22Z" - latency: 2.433011ms message: 'network-check-target-ip-10-0-131-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:50:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:10:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-173-to-network-check-target-ip-10-0-137-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-173.ec2.internal uid: c4a75fb0-bfb7-4c26-9f37-69ccd77c613c resourceVersion: "73593" uid: 3a9cf321-1744-4bef-9175-780b11d94571 spec: sourcePod: network-check-source-7d88cb55d8-8wq8w targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T01:17:22Z" message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.330852ms message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:59:22Z" - latency: 2.578947ms message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:58:22Z" - latency: 2.429627ms message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:57:22Z" - latency: 2.114801ms message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:56:22Z" - latency: 2.343186ms message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:55:22Z" - latency: 2.2616ms message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:54:22Z" - latency: 2.476494ms message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:53:22Z" - latency: 2.265722ms message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:52:22Z" - latency: 2.177394ms message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:51:22Z" - latency: 2.37063ms message: 'network-check-target-ip-10-0-137-121: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:50:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:10:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-173-to-network-check-target-ip-10-0-138-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-173.ec2.internal uid: c4a75fb0-bfb7-4c26-9f37-69ccd77c613c resourceVersion: "73591" uid: c40c350b-3321-42ae-8a6e-03c326aebf04 spec: sourcePod: network-check-source-7d88cb55d8-8wq8w targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T01:17:22Z" message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 924.487µs message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:59:22Z" - latency: 923.902µs message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:58:22Z" - latency: 982.423µs message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:57:22Z" - latency: 816.959µs message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:56:22Z" - latency: 818.806µs message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:55:22Z" - latency: 947.209µs message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:54:22Z" - latency: 813.452µs message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:53:22Z" - latency: 877.5µs message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:52:22Z" - latency: 1.014327ms message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:51:22Z" - latency: 1.250831ms message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:50:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T01:10:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-173-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-173.ec2.internal uid: c4a75fb0-bfb7-4c26-9f37-69ccd77c613c resourceVersion: "71114" uid: b11f2ce2-dfd5-4990-91f7-60b912f14d65 spec: sourcePod: network-check-source-7d88cb55d8-8wq8w targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T01:16:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.030082ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:58:22Z" - latency: 2.477889ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T01:58:22Z" - latency: 1.146848ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:57:22Z" - latency: 1.646968ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T01:57:22Z" - latency: 853.797µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:56:22Z" - latency: 1.77063ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T01:56:22Z" - latency: 858.452µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:55:22Z" - latency: 1.745914ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T01:55:22Z" - latency: 822.714µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T01:54:22Z" - latency: 1.737315ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T01:54:22Z" kind: List metadata: resourceVersion: ""