apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:04:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-102-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-102.ec2.internal uid: 4b987eb5-3e03-4610-99bc-4deba2e75b79 resourceVersion: "48909" uid: c452b988-b3e7-4413-a126-cb08fc589e4c spec: sourcePod: network-check-source-989f8b8dc-hq4zg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T19:11:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.039154ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:08Z" - latency: 1.086087ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:08Z" - latency: 1.136949ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:08Z" - latency: 842.671µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:36:08Z" - latency: 962.956µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:35:08Z" - latency: 1.275043ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:34:08Z" - latency: 1.069783ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:33:08Z" - latency: 1.683337ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:32:08Z" - latency: 925.887µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:31:08Z" - latency: 1.093949ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:30:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:04:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-102-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-102.ec2.internal uid: 4b987eb5-3e03-4610-99bc-4deba2e75b79 resourceVersion: "49508" uid: 5cd9b8ab-3efe-4b48-8686-74e108368abd spec: sourcePod: network-check-source-989f8b8dc-hq4zg targetEndpoint: a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T19:10:08Z" message: 'load-balancer-api-external: tcp connection to a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.92033ms message: 'load-balancer-api-external: tcp connection to a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:08Z" - latency: 8.480138ms message: 'load-balancer-api-external: resolved host name a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:40:08Z" - latency: 5.399552ms message: 'load-balancer-api-external: tcp connection to a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:08Z" - latency: 7.260342ms message: 'load-balancer-api-external: resolved host name a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:39:08Z" - latency: 3.919798ms message: 'load-balancer-api-external: tcp connection to a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:08Z" - latency: 9.410691ms message: 'load-balancer-api-external: resolved host name a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:38:08Z" - latency: 5.480779ms message: 'load-balancer-api-external: tcp connection to a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:08Z" - latency: 9.771607ms message: 'load-balancer-api-external: resolved host name a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:37:08Z" - latency: 5.443029ms message: 'load-balancer-api-external: tcp connection to a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:36:08Z" - latency: 6.82697ms message: 'load-balancer-api-external: resolved host name a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:36:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:04:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-102-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-102.ec2.internal uid: 4b987eb5-3e03-4610-99bc-4deba2e75b79 resourceVersion: "49509" uid: 47b96cb0-7863-46f0-b943-7418757f76b1 spec: sourcePod: network-check-source-989f8b8dc-hq4zg targetEndpoint: a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T19:10:08Z" message: 'load-balancer-api-internal: tcp connection to a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.959152ms message: 'load-balancer-api-internal: tcp connection to a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:08Z" - latency: 8.430435ms message: 'load-balancer-api-internal: resolved host name a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:40:08Z" - latency: 5.344985ms message: 'load-balancer-api-internal: tcp connection to a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:08Z" - latency: 7.30665ms message: 'load-balancer-api-internal: resolved host name a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:39:08Z" - latency: 3.884241ms message: 'load-balancer-api-internal: tcp connection to a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:08Z" - latency: 9.321498ms message: 'load-balancer-api-internal: resolved host name a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:38:08Z" - latency: 5.52677ms message: 'load-balancer-api-internal: tcp connection to a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:08Z" - latency: 9.673569ms message: 'load-balancer-api-internal: resolved host name a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:37:08Z" - latency: 5.429752ms message: 'load-balancer-api-internal: tcp connection to a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:36:08Z" - latency: 6.879002ms message: 'load-balancer-api-internal: resolved host name a1617d7d0ed9443e388eabcf661dbef0-de4e6b144ae9c3e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:36:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:04:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-102-to-network-check-target-ip-10-0-128-32 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-102.ec2.internal uid: 4b987eb5-3e03-4610-99bc-4deba2e75b79 resourceVersion: "48906" uid: 31331075-a495-43be-8ed0-0debd52419f1 spec: sourcePod: network-check-source-989f8b8dc-hq4zg targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T19:11:08Z" message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.764461ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:08Z" - latency: 2.058004ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:08Z" - latency: 2.052794ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:08Z" - latency: 1.922584ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:36:08Z" - latency: 1.892606ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:35:08Z" - latency: 2.031592ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:34:08Z" - latency: 2.019845ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:33:08Z" - latency: 1.88388ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:32:08Z" - latency: 1.831224ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:31:08Z" - latency: 1.96338ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:30:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:04:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-102-to-network-check-target-ip-10-0-129-210 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-102.ec2.internal uid: 4b987eb5-3e03-4610-99bc-4deba2e75b79 resourceVersion: "48907" uid: 2479c2b0-0dec-4fee-821b-82adf4919185 spec: sourcePod: network-check-source-989f8b8dc-hq4zg targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T19:11:08Z" message: 'network-check-target-ip-10-0-129-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.273463ms message: 'network-check-target-ip-10-0-129-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:08Z" - latency: 2.416689ms message: 'network-check-target-ip-10-0-129-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:08Z" - latency: 2.147448ms message: 'network-check-target-ip-10-0-129-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:08Z" - latency: 2.002583ms message: 'network-check-target-ip-10-0-129-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:36:08Z" - latency: 2.295536ms message: 'network-check-target-ip-10-0-129-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:35:08Z" - latency: 2.439211ms message: 'network-check-target-ip-10-0-129-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:34:08Z" - latency: 2.234509ms message: 'network-check-target-ip-10-0-129-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:33:08Z" - latency: 2.470219ms message: 'network-check-target-ip-10-0-129-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:32:08Z" - latency: 2.269526ms message: 'network-check-target-ip-10-0-129-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:31:08Z" - latency: 2.163646ms message: 'network-check-target-ip-10-0-129-210: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:30:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:04:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-102-to-network-check-target-ip-10-0-130-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-102.ec2.internal uid: 4b987eb5-3e03-4610-99bc-4deba2e75b79 resourceVersion: "48908" uid: f4911b9a-2a0d-4df4-8013-a5f134740c58 spec: sourcePod: network-check-source-989f8b8dc-hq4zg targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T19:11:08Z" message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 946.289µs message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:08Z" - latency: 911.112µs message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:08Z" - latency: 905.181µs message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:08Z" - latency: 1.085295ms message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:36:08Z" - latency: 1.186646ms message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:35:08Z" - latency: 1.470972ms message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:34:08Z" - latency: 1.005405ms message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:33:08Z" - latency: 797.748µs message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:32:08Z" - latency: 1.031284ms message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:31:08Z" - latency: 1.221134ms message: 'network-check-target-ip-10-0-130-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:30:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:04:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-102-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-102.ec2.internal uid: 4b987eb5-3e03-4610-99bc-4deba2e75b79 resourceVersion: "49507" uid: d6f573f1-a2e6-4405-af77-44097fb9ed23 spec: sourcePod: network-check-source-989f8b8dc-hq4zg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T19:10:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 890.097µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:08Z" - latency: 1.844756ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:40:08Z" - latency: 866.631µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:08Z" - latency: 1.88759ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:39:08Z" - latency: 811.761µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:08Z" - latency: 2.692805ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:38:08Z" - latency: 923.924µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:08Z" - latency: 2.430299ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:37:08Z" - latency: 1.155611ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:36:08Z" - latency: 1.721178ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:36:08Z" kind: List metadata: resourceVersion: ""