apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T16:02:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-210-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-210.ec2.internal uid: 1d4b8663-b728-48a8-b015-818ee5225fac resourceVersion: "77125" uid: 1b324cc5-039b-4ea8-bc97-e3de6dcde1a9 spec: sourcePod: network-check-source-65bdbbff45-gkbnm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T16:09:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.113181ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:58:17Z" - latency: 1.144122ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:57:17Z" - latency: 1.150505ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:56:17Z" - latency: 1.081892ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:55:17Z" - latency: 1.498505ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:54:17Z" - latency: 1.037868ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:53:17Z" - latency: 1.217089ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:52:17Z" - latency: 1.129449ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:51:17Z" - latency: 836.373µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:50:17Z" - latency: 1.01414ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:49:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T16:02:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-210-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-210.ec2.internal uid: 1d4b8663-b728-48a8-b015-818ee5225fac resourceVersion: "75147" uid: ba92f078-8365-4b31-a0f7-4bf297da9073 spec: sourcePod: network-check-source-65bdbbff45-gkbnm targetEndpoint: a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T16:08:17Z" message: 'load-balancer-api-external: tcp connection to a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.782326ms message: 'load-balancer-api-external: tcp connection to a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:56:17Z" - latency: 7.130487ms message: 'load-balancer-api-external: resolved host name a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:56:17Z" - latency: 4.735815ms message: 'load-balancer-api-external: tcp connection to a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:55:17Z" - latency: 8.383305ms message: 'load-balancer-api-external: resolved host name a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:55:17Z" - latency: 5.617044ms message: 'load-balancer-api-external: tcp connection to a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:54:17Z" - latency: 8.525593ms message: 'load-balancer-api-external: resolved host name a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:54:17Z" - latency: 5.113466ms message: 'load-balancer-api-external: tcp connection to a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:53:17Z" - latency: 6.906305ms message: 'load-balancer-api-external: resolved host name a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:53:17Z" - latency: 4.227914ms message: 'load-balancer-api-external: tcp connection to a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:52:17Z" - latency: 7.236215ms message: 'load-balancer-api-external: resolved host name a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:52:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T16:02:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-210-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-210.ec2.internal uid: 1d4b8663-b728-48a8-b015-818ee5225fac resourceVersion: "75148" uid: 1127baa2-dc7c-400d-81ac-2aa9bebe7360 spec: sourcePod: network-check-source-65bdbbff45-gkbnm targetEndpoint: a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T16:08:17Z" message: 'load-balancer-api-internal: tcp connection to a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.795777ms message: 'load-balancer-api-internal: tcp connection to a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:56:17Z" - latency: 7.018189ms message: 'load-balancer-api-internal: resolved host name a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:56:17Z" - latency: 4.808619ms message: 'load-balancer-api-internal: tcp connection to a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:55:17Z" - latency: 8.456812ms message: 'load-balancer-api-internal: resolved host name a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:55:17Z" - latency: 5.252004ms message: 'load-balancer-api-internal: tcp connection to a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:54:17Z" - latency: 8.498038ms message: 'load-balancer-api-internal: resolved host name a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:54:17Z" - latency: 5.105486ms message: 'load-balancer-api-internal: tcp connection to a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:53:17Z" - latency: 6.986594ms message: 'load-balancer-api-internal: resolved host name a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:53:17Z" - latency: 4.222223ms message: 'load-balancer-api-internal: tcp connection to a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:52:17Z" - latency: 7.19184ms message: 'load-balancer-api-internal: resolved host name a56726e7207a24e30a302ccd50bba6ee-7377c9387ea4b95e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:52:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T16:02:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-210-to-network-check-target-ip-10-0-132-227 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-210.ec2.internal uid: 1d4b8663-b728-48a8-b015-818ee5225fac resourceVersion: "77124" uid: c3838717-9787-444a-b39a-bd46109b3169 spec: sourcePod: network-check-source-65bdbbff45-gkbnm targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T16:09:17Z" message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.894899ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:58:17Z" - latency: 2.577522ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:57:17Z" - latency: 2.579317ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:56:17Z" - latency: 2.455742ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:55:17Z" - latency: 2.508881ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:54:17Z" - latency: 2.611859ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:53:17Z" - latency: 2.014679ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:52:17Z" - latency: 3.132207ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:51:17Z" - latency: 2.431276ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:50:17Z" - latency: 2.425366ms message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:49:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T16:02:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-210-to-network-check-target-ip-10-0-137-14 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-210.ec2.internal uid: 1d4b8663-b728-48a8-b015-818ee5225fac resourceVersion: "77123" uid: df53927e-ab58-4d50-bd71-f35264cc5b90 spec: sourcePod: network-check-source-65bdbbff45-gkbnm targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T16:09:17Z" message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.366369ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:58:17Z" - latency: 2.231899ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:57:17Z" - latency: 2.585278ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:56:17Z" - latency: 2.327472ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:55:17Z" - latency: 2.389717ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:54:17Z" - latency: 2.284745ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:53:17Z" - latency: 2.36857ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:52:17Z" - latency: 2.334181ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:51:17Z" - latency: 2.48344ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:50:17Z" - latency: 2.238762ms message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:49:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T16:02:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-210-to-network-check-target-ip-10-0-141-210 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-210.ec2.internal uid: 1d4b8663-b728-48a8-b015-818ee5225fac resourceVersion: "77122" uid: 300eaba3-f240-4623-a8cc-bd02f3b9ad28 spec: sourcePod: network-check-source-65bdbbff45-gkbnm targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T16:09:17Z" message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.531937ms message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:58:17Z" - latency: 975.29µs message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:57:17Z" - latency: 1.07888ms message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:56:17Z" - latency: 972.161µs message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:55:17Z" - latency: 982.975µs message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:54:17Z" - latency: 1.005589ms message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:53:17Z" - latency: 1.150257ms message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:52:17Z" - latency: 1.063495ms message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:51:17Z" - latency: 1.302976ms message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:50:17Z" - latency: 997.213µs message: 'network-check-target-ip-10-0-141-210: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:49:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T16:02:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-210-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-210.ec2.internal uid: 1d4b8663-b728-48a8-b015-818ee5225fac resourceVersion: "75146" uid: 3e816b69-00b1-4aae-bf05-f1db67740335 spec: sourcePod: network-check-source-65bdbbff45-gkbnm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T16:08:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 997.306µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:56:17Z" - latency: 1.757174ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T16:56:17Z" - latency: 1.269903ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:55:17Z" - latency: 1.909133ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T16:55:17Z" - latency: 1.014287ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:54:17Z" - latency: 1.812658ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T16:54:17Z" - latency: 1.122068ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:53:17Z" - latency: 1.885701ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T16:53:17Z" - latency: 1.129049ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:52:17Z" - latency: 1.934313ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T16:52:17Z" kind: List metadata: resourceVersion: ""