apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T03:26:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-190-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-190.ec2.internal uid: c9a5d198-b056-49a4-a3da-10c45ec80e5b resourceVersion: "55593" uid: cd9e8d46-d6f0-4408-bdf4-7520eb82a6b3 spec: sourcePod: network-check-source-989f8b8dc-75bj4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T03:33:43Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.001585ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T04:01:43Z" - latency: 1.211654ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T04:00:43Z" - latency: 1.104967ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:59:43Z" - latency: 793.761µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:58:43Z" - latency: 1.128876ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:57:43Z" - latency: 1.206169ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:56:43Z" - latency: 1.106815ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:55:43Z" - latency: 844.607µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:54:43Z" - latency: 808.796µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:53:43Z" - latency: 834.296µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:52:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T03:26:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-190-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-190.ec2.internal uid: c9a5d198-b056-49a4-a3da-10c45ec80e5b resourceVersion: "56649" uid: 6406fb4a-566d-4c32-870b-9ab537a963a4 spec: sourcePod: network-check-source-989f8b8dc-75bj4 targetEndpoint: a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T03:32:43Z" message: 'load-balancer-api-external: tcp connection to a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.601638ms message: 'load-balancer-api-external: tcp connection to a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T04:02:43Z" - latency: 8.073426ms message: 'load-balancer-api-external: resolved host name a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T04:02:43Z" - latency: 4.152145ms message: 'load-balancer-api-external: tcp connection to a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T04:01:43Z" - latency: 8.258114ms message: 'load-balancer-api-external: resolved host name a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T04:01:43Z" - latency: 3.634145ms message: 'load-balancer-api-external: tcp connection to a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T04:00:43Z" - latency: 8.284948ms message: 'load-balancer-api-external: resolved host name a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T04:00:43Z" - latency: 3.890477ms message: 'load-balancer-api-external: tcp connection to a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:59:43Z" - latency: 7.210407ms message: 'load-balancer-api-external: resolved host name a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T03:59:43Z" - latency: 3.940457ms message: 'load-balancer-api-external: tcp connection to a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:58:43Z" - latency: 8.83835ms message: 'load-balancer-api-external: resolved host name a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T03:58:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T03:26:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-190-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-190.ec2.internal uid: c9a5d198-b056-49a4-a3da-10c45ec80e5b resourceVersion: "56650" uid: 5bac2807-e483-4c0c-bed8-c10ccf6fc973 spec: sourcePod: network-check-source-989f8b8dc-75bj4 targetEndpoint: a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T03:32:43Z" message: 'load-balancer-api-internal: tcp connection to a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.635747ms message: 'load-balancer-api-internal: tcp connection to a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T04:02:43Z" - latency: 8.14651ms message: 'load-balancer-api-internal: resolved host name a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T04:02:43Z" - latency: 3.096543ms message: 'load-balancer-api-internal: tcp connection to a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T04:01:43Z" - latency: 8.233911ms message: 'load-balancer-api-internal: resolved host name a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T04:01:43Z" - latency: 3.552841ms message: 'load-balancer-api-internal: tcp connection to a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T04:00:43Z" - latency: 8.361512ms message: 'load-balancer-api-internal: resolved host name a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T04:00:43Z" - latency: 5.787337ms message: 'load-balancer-api-internal: tcp connection to a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:59:43Z" - latency: 7.264688ms message: 'load-balancer-api-internal: resolved host name a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T03:59:43Z" - latency: 3.985554ms message: 'load-balancer-api-internal: tcp connection to a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:58:43Z" - latency: 8.927323ms message: 'load-balancer-api-internal: resolved host name a4418177c45904339962883f8016fd02-3bce23e17ea8bd2e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T03:58:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T03:26:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-190-to-network-check-target-ip-10-0-129-190 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-190.ec2.internal uid: c9a5d198-b056-49a4-a3da-10c45ec80e5b resourceVersion: "55590" uid: e3f48617-1dce-4839-a330-2614f7f496e0 spec: sourcePod: network-check-source-989f8b8dc-75bj4 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T03:33:43Z" message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 839.631µs message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T04:01:43Z" - latency: 832.289µs message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T04:00:43Z" - latency: 1.407582ms message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:59:43Z" - latency: 807.017µs message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:58:43Z" - latency: 1.627109ms message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:57:43Z" - latency: 853.434µs message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:56:43Z" - latency: 845.423µs message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:55:43Z" - latency: 822.743µs message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:54:43Z" - latency: 1.298234ms message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:53:43Z" - latency: 798.702µs message: 'network-check-target-ip-10-0-129-190: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:52:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T03:26:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-190-to-network-check-target-ip-10-0-137-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-190.ec2.internal uid: c9a5d198-b056-49a4-a3da-10c45ec80e5b resourceVersion: "55592" uid: 5ef96261-f8a9-4e68-b124-2c94e8606ac0 spec: sourcePod: network-check-source-989f8b8dc-75bj4 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T03:33:43Z" message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.859355ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T04:01:43Z" - latency: 2.942575ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T04:00:43Z" - latency: 2.308505ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:59:43Z" - latency: 2.664452ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:58:43Z" - latency: 2.633094ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:57:43Z" - latency: 2.366899ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:56:43Z" - latency: 2.311055ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:55:43Z" - latency: 2.294152ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:54:43Z" - latency: 2.570863ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:53:43Z" - latency: 2.882358ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:52:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T03:26:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-190-to-network-check-target-ip-10-0-140-212 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-190.ec2.internal uid: c9a5d198-b056-49a4-a3da-10c45ec80e5b resourceVersion: "55591" uid: e460c49b-9320-4266-b878-37243ba4ae52 spec: sourcePod: network-check-source-989f8b8dc-75bj4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T03:33:43Z" message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.22961ms message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T04:01:43Z" - latency: 2.212247ms message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T04:00:43Z" - latency: 2.280388ms message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:59:43Z" - latency: 2.315279ms message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:58:43Z" - latency: 2.238483ms message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:57:43Z" - latency: 2.027407ms message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:56:43Z" - latency: 1.949126ms message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:55:43Z" - latency: 2.426578ms message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:54:43Z" - latency: 2.146235ms message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:53:43Z" - latency: 2.167418ms message: 'network-check-target-ip-10-0-140-212: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:52:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T03:26:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-190-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-190.ec2.internal uid: c9a5d198-b056-49a4-a3da-10c45ec80e5b resourceVersion: "56647" uid: 91fb57a0-be1d-4a0d-a7f6-64f467966d1c spec: sourcePod: network-check-source-989f8b8dc-75bj4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T03:32:43Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 827.803µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T04:02:43Z" - latency: 1.689951ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T04:02:43Z" - latency: 1.224211ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T04:01:43Z" - latency: 1.779031ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T04:01:43Z" - latency: 958.227µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T04:00:43Z" - latency: 1.82837ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T04:00:43Z" - latency: 861.257µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:59:43Z" - latency: 1.953417ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T03:59:43Z" - latency: 760.09µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:58:43Z" - latency: 1.690834ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T03:58:43Z" kind: List metadata: resourceVersion: ""