apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:08:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-191-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-191.ec2.internal uid: ad50a2aa-c843-45bc-baeb-a4e7978b4ff0 resourceVersion: "55164" uid: 84e34edf-b3dd-4443-80cd-dac68d2ecf7f spec: sourcePod: network-check-source-989f8b8dc-s5dzj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T19:15:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.270573ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:43:13Z" - latency: 1.326113ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:42:13Z" - latency: 1.558525ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:41:13Z" - latency: 1.11639ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:13Z" - latency: 1.027094ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:13Z" - latency: 1.354795ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:13Z" - latency: 1.317432ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:13Z" - latency: 897.173µ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:13Z" - latency: 1.146515ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:35:13Z" - latency: 1.377973ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:34:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:08:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-191-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-191.ec2.internal uid: ad50a2aa-c843-45bc-baeb-a4e7978b4ff0 resourceVersion: "56093" uid: ada32a15-765b-4091-895a-b72acb1ccfa7 spec: sourcePod: network-check-source-989f8b8dc-s5dzj targetEndpoint: ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T19:14:13Z" message: 'load-balancer-api-external: tcp connection to ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.696953ms message: 'load-balancer-api-external: tcp connection to ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:44:13Z" - latency: 8.682113ms message: 'load-balancer-api-external: resolved host name ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:44:13Z" - latency: 6.173242ms message: 'load-balancer-api-external: tcp connection to ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:43:13Z" - latency: 9.420646ms message: 'load-balancer-api-external: resolved host name ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:43:13Z" - latency: 4.789976ms message: 'load-balancer-api-external: tcp connection to ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:42:13Z" - latency: 7.319077ms message: 'load-balancer-api-external: resolved host name ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:42:13Z" - latency: 4.462478ms message: 'load-balancer-api-external: tcp connection to ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:41:13Z" - latency: 9.721335ms message: 'load-balancer-api-external: resolved host name ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:41:13Z" - latency: 4.020462ms message: 'load-balancer-api-external: tcp connection to ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:13Z" - latency: 8.729625ms message: 'load-balancer-api-external: resolved host name ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:40:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:08:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-191-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-191.ec2.internal uid: ad50a2aa-c843-45bc-baeb-a4e7978b4ff0 resourceVersion: "56092" uid: db134ab2-bc18-41e3-8c77-6a611767d4fd spec: sourcePod: network-check-source-989f8b8dc-s5dzj targetEndpoint: ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T19:14:13Z" message: 'load-balancer-api-internal: tcp connection to ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.333611ms message: 'load-balancer-api-internal: tcp connection to ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:44:13Z" - latency: 8.710179ms message: 'load-balancer-api-internal: resolved host name ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:44:13Z" - latency: 4.551258ms message: 'load-balancer-api-internal: tcp connection to ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:43:13Z" - latency: 9.341267ms message: 'load-balancer-api-internal: resolved host name ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:43:13Z" - latency: 4.79869ms message: 'load-balancer-api-internal: tcp connection to ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:42:13Z" - latency: 7.244419ms message: 'load-balancer-api-internal: resolved host name ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:42:13Z" - latency: 5.1183ms message: 'load-balancer-api-internal: tcp connection to ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:41:13Z" - latency: 9.743162ms message: 'load-balancer-api-internal: resolved host name ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:41:13Z" - latency: 4.365398ms message: 'load-balancer-api-internal: tcp connection to ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:13Z" - latency: 8.673641ms message: 'load-balancer-api-internal: resolved host name ae4c2b4d865c8448491de6cf049e81bc-1831bdb881194c39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:40:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:08:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-191-to-network-check-target-ip-10-0-131-191 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-191.ec2.internal uid: ad50a2aa-c843-45bc-baeb-a4e7978b4ff0 resourceVersion: "55161" uid: 392006af-cb17-4596-a49a-2dd2e2c7a903 spec: sourcePod: network-check-source-989f8b8dc-s5dzj targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T19:15:13Z" message: 'network-check-target-ip-10-0-131-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 931.137µs message: 'network-check-target-ip-10-0-131-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:43:13Z" - latency: 1.167996ms message: 'network-check-target-ip-10-0-131-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:42:13Z" - latency: 1.007265ms message: 'network-check-target-ip-10-0-131-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:41:13Z" - latency: 1.644296ms message: 'network-check-target-ip-10-0-131-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:13Z" - latency: 795.199µs message: 'network-check-target-ip-10-0-131-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:13Z" - latency: 1.10412ms message: 'network-check-target-ip-10-0-131-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:13Z" - latency: 1.50194ms message: 'network-check-target-ip-10-0-131-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:13Z" - latency: 1.200293ms message: 'network-check-target-ip-10-0-131-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:36:13Z" - latency: 847.223µs message: 'network-check-target-ip-10-0-131-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:35:13Z" - latency: 1.650567ms message: 'network-check-target-ip-10-0-131-191: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:34:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:08:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-191-to-network-check-target-ip-10-0-137-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-191.ec2.internal uid: ad50a2aa-c843-45bc-baeb-a4e7978b4ff0 resourceVersion: "55163" uid: 95736673-5ebe-4ed8-9e29-6656838e42f6 spec: sourcePod: network-check-source-989f8b8dc-s5dzj targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T19:15:13Z" message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.068524ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:43:13Z" - latency: 2.34281ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:42:13Z" - latency: 3.139689ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:41:13Z" - latency: 2.424395ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:13Z" - latency: 2.397842ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:13Z" - latency: 2.369625ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:13Z" - latency: 2.155899ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:13Z" - latency: 2.355588ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:36:13Z" - latency: 2.140873ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:35:13Z" - latency: 2.248908ms message: 'network-check-target-ip-10-0-137-244: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:34:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:08:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-191-to-network-check-target-ip-10-0-140-33 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-191.ec2.internal uid: ad50a2aa-c843-45bc-baeb-a4e7978b4ff0 resourceVersion: "55162" uid: c1ebd05a-f078-48c4-a7d2-208e50e7f436 spec: sourcePod: network-check-source-989f8b8dc-s5dzj targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T19:15:13Z" message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.903054ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:43:13Z" - latency: 1.87549ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:42:13Z" - latency: 1.881707ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:41:13Z" - latency: 2.05622ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:13Z" - latency: 2.038049ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:13Z" - latency: 1.893804ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:13Z" - latency: 2.11333ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:13Z" - latency: 2.085931ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:36:13Z" - latency: 1.890131ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:35:13Z" - latency: 2.190619ms message: 'network-check-target-ip-10-0-140-33: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:34:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:08:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-191-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-191.ec2.internal uid: ad50a2aa-c843-45bc-baeb-a4e7978b4ff0 resourceVersion: "56091" uid: 1f687544-7795-4437-9bbc-0e10e557af28 spec: sourcePod: network-check-source-989f8b8dc-s5dzj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T19:14:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 903.893µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:44:13Z" - latency: 2.303775ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:44:13Z" - latency: 869.997µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:43:13Z" - latency: 2.125064ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:43:13Z" - latency: 870.392µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:42:13Z" - latency: 1.967072ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:42:13Z" - latency: 968.723µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:41:13Z" - latency: 2.261874ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:41:13Z" - latency: 1.148666ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:13Z" - latency: 1.787105ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:40:13Z" kind: List metadata: resourceVersion: ""