apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T10:30:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-178-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-178.ec2.internal uid: 720aa6e1-61c8-43ba-8687-ba0bc9e27fb6 resourceVersion: "42787" uid: 8ad04d20-9fc0-4215-8d3c-695829646884 spec: sourcePod: network-check-source-7f44b6dd87-ppbkm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T10:37:26Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.133708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:58:26Z" - latency: 1.029669ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:57:26Z" - latency: 997.79µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:56:26Z" - latency: 1.02112ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:55:26Z" - latency: 1.135242ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:54:26Z" - latency: 1.240879ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:53:26Z" - latency: 1.086425ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:52:26Z" - latency: 1.114395ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:51:26Z" - latency: 881.181µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:50:26Z" - latency: 1.190235ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:49:26Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T10:30:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-178-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-178.ec2.internal uid: 720aa6e1-61c8-43ba-8687-ba0bc9e27fb6 resourceVersion: "38702" uid: bdeba310-2b42-4fac-b91d-a95a9f7f873d spec: sourcePod: network-check-source-7f44b6dd87-ppbkm targetEndpoint: a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T10:36:26Z" message: 'load-balancer-api-external: tcp connection to a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.102575ms message: 'load-balancer-api-external: tcp connection to a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:54:26Z" - latency: 8.365845ms message: 'load-balancer-api-external: resolved host name a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:54:26Z" - latency: 5.400624ms message: 'load-balancer-api-external: tcp connection to a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:53:26Z" - latency: 5.983149ms message: 'load-balancer-api-external: resolved host name a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:53:26Z" - latency: 5.428947ms message: 'load-balancer-api-external: tcp connection to a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:52:26Z" - latency: 7.805466ms message: 'load-balancer-api-external: resolved host name a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:52:26Z" - latency: 5.629799ms message: 'load-balancer-api-external: tcp connection to a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:51:26Z" - latency: 7.924102ms message: 'load-balancer-api-external: resolved host name a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:51:26Z" - latency: 6.063832ms message: 'load-balancer-api-external: tcp connection to a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:50:26Z" - latency: 8.27504ms message: 'load-balancer-api-external: resolved host name a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:50:26Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T10:30:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-178-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-178.ec2.internal uid: 720aa6e1-61c8-43ba-8687-ba0bc9e27fb6 resourceVersion: "38703" uid: f2a29c82-c1c8-4303-ae24-96d4289700dd spec: sourcePod: network-check-source-7f44b6dd87-ppbkm targetEndpoint: a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T10:36:26Z" message: 'load-balancer-api-internal: tcp connection to a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.684059ms message: 'load-balancer-api-internal: tcp connection to a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:54:26Z" - latency: 8.385591ms message: 'load-balancer-api-internal: resolved host name a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:54:26Z" - latency: 5.375953ms message: 'load-balancer-api-internal: tcp connection to a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:53:26Z" - latency: 5.898222ms message: 'load-balancer-api-internal: resolved host name a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:53:26Z" - latency: 4.618202ms message: 'load-balancer-api-internal: tcp connection to a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:52:26Z" - latency: 7.864034ms message: 'load-balancer-api-internal: resolved host name a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:52:26Z" - latency: 5.232592ms message: 'load-balancer-api-internal: tcp connection to a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:51:26Z" - latency: 7.894596ms message: 'load-balancer-api-internal: resolved host name a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:51:26Z" - latency: 6.00137ms message: 'load-balancer-api-internal: tcp connection to a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:50:26Z" - latency: 8.321206ms message: 'load-balancer-api-internal: resolved host name a3e6927905e6240959a1cae288205f2f-ae930edadb6675da.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:50:26Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T10:30:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-178-to-network-check-target-ip-10-0-137-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-178.ec2.internal uid: 720aa6e1-61c8-43ba-8687-ba0bc9e27fb6 resourceVersion: "42786" uid: e25e384e-b728-4cb1-ad82-d42cb20a9fa5 spec: sourcePod: network-check-source-7f44b6dd87-ppbkm targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T10:37:26Z" message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.634068ms message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:58:26Z" - latency: 1.745617ms message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:57:26Z" - latency: 1.803436ms message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:56:26Z" - latency: 1.770606ms message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:55:26Z" - latency: 1.595721ms message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:54:26Z" - latency: 1.853428ms message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:53:26Z" - latency: 1.793784ms message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:52:26Z" - latency: 1.839625ms message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:51:26Z" - latency: 1.837692ms message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:50:26Z" - latency: 1.791412ms message: 'network-check-target-ip-10-0-137-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:49:26Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T10:31:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-178-to-network-check-target-ip-10-0-137-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-178.ec2.internal uid: 720aa6e1-61c8-43ba-8687-ba0bc9e27fb6 resourceVersion: "43567" uid: 0e1d928d-52a5-41cd-8f01-7193468f3379 spec: sourcePod: network-check-source-7f44b6dd87-ppbkm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T10:38:05Z" message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.092408ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:59:05Z" - latency: 2.120458ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:58:05Z" - latency: 2.428584ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:57:05Z" - latency: 2.488872ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:56:05Z" - latency: 2.322159ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:55:05Z" - latency: 2.226376ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:54:05Z" - latency: 2.336504ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:53:05Z" - latency: 1.823555ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:52:05Z" - latency: 2.402667ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:51:05Z" - latency: 2.183521ms message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:50:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T10:30:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-178-to-network-check-target-ip-10-0-141-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-178.ec2.internal uid: 720aa6e1-61c8-43ba-8687-ba0bc9e27fb6 resourceVersion: "42785" uid: 69097157-808c-44eb-9b67-ba53b7ae349b spec: sourcePod: network-check-source-7f44b6dd87-ppbkm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T10:37:26Z" message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.054247ms message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:58:26Z" - latency: 1.144687ms message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:57:26Z" - latency: 847.635µs message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:56:26Z" - latency: 982.104µs message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:55:26Z" - latency: 1.284033ms message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:54:26Z" - latency: 843.219µs message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:53:26Z" - latency: 1.300169ms message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:52:26Z" - latency: 849.8µs message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:51:26Z" - latency: 793.641µs message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:50:26Z" - latency: 1.378864ms message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:49:26Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T10:30:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-178-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-178.ec2.internal uid: 720aa6e1-61c8-43ba-8687-ba0bc9e27fb6 resourceVersion: "38701" uid: f1cf3210-3cf7-4dab-8ec2-f7eaf9684502 spec: sourcePod: network-check-source-7f44b6dd87-ppbkm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T10:36:26Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.947964ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:54:26Z" - latency: 1.698764ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T10:54:26Z" - latency: 823.369µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:53:26Z" - latency: 1.803353ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T10:53:26Z" - latency: 862.851µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:52:26Z" - latency: 1.68272ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T10:52:26Z" - latency: 977.503µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:51:26Z" - latency: 1.578681ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T10:51:26Z" - latency: 732.816µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:50:26Z" - latency: 1.733941ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T10:50:26Z" kind: List metadata: resourceVersion: ""