apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T01:06:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-117-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-117.ec2.internal uid: a15f5d28-d4c4-41de-8165-f61832577a57 resourceVersion: "62102" uid: 15b242b9-85da-4fba-8aa9-2a9934f46741 spec: sourcePod: network-check-source-869dcfcdcd-cppnk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T01:13:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 987.672µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:48:15Z" - latency: 1.124911ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:47:15Z" - latency: 1.123611ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:46:15Z" - latency: 1.033822ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:45:15Z" - latency: 985.838µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:44:15Z" - latency: 1.079903ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:43:15Z" - latency: 928.275µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:42:15Z" - latency: 1.169634ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:41:15Z" - latency: 1.450142ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:40:15Z" - latency: 5.989641ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:39:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T01:06:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-117-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-117.ec2.internal uid: a15f5d28-d4c4-41de-8165-f61832577a57 resourceVersion: "62104" uid: fc3587ef-7f90-442d-8526-66513a4434d7 spec: sourcePod: network-check-source-869dcfcdcd-cppnk targetEndpoint: ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T01:12:15Z" message: 'load-balancer-api-external: tcp connection to ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.330687ms message: 'load-balancer-api-external: tcp connection to ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:48:15Z" - latency: 10.575029ms message: 'load-balancer-api-external: resolved host name ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:48:15Z" - latency: 3.864699ms message: 'load-balancer-api-external: tcp connection to ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:47:15Z" - latency: 8.327821ms message: 'load-balancer-api-external: resolved host name ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:47:15Z" - latency: 5.438402ms message: 'load-balancer-api-external: tcp connection to ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:46:15Z" - latency: 9.191389ms message: 'load-balancer-api-external: resolved host name ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:46:15Z" - latency: 4.02786ms message: 'load-balancer-api-external: tcp connection to ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:45:15Z" - latency: 8.206762ms message: 'load-balancer-api-external: resolved host name ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:45:15Z" - latency: 4.988033ms message: 'load-balancer-api-external: tcp connection to ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:44:15Z" - latency: 7.692912ms message: 'load-balancer-api-external: resolved host name ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:44:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T01:06:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-117-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-117.ec2.internal uid: a15f5d28-d4c4-41de-8165-f61832577a57 resourceVersion: "62103" uid: 6508aa3e-d7a5-4bb4-b674-68c43780fab5 spec: sourcePod: network-check-source-869dcfcdcd-cppnk targetEndpoint: ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T01:12:15Z" message: 'load-balancer-api-internal: tcp connection to ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.342753ms message: 'load-balancer-api-internal: tcp connection to ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:48:15Z" - latency: 10.529449ms message: 'load-balancer-api-internal: resolved host name ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:48:15Z" - latency: 5.141347ms message: 'load-balancer-api-internal: tcp connection to ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:47:15Z" - latency: 8.266616ms message: 'load-balancer-api-internal: resolved host name ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:47:15Z" - latency: 4.613153ms message: 'load-balancer-api-internal: tcp connection to ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:46:15Z" - latency: 9.249284ms message: 'load-balancer-api-internal: resolved host name ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:46:15Z" - latency: 4.007521ms message: 'load-balancer-api-internal: tcp connection to ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:45:15Z" - latency: 8.317277ms message: 'load-balancer-api-internal: resolved host name ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:45:15Z" - latency: 4.970592ms message: 'load-balancer-api-internal: tcp connection to ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:44:15Z" - latency: 7.653788ms message: 'load-balancer-api-internal: resolved host name ad22365b6989f4100b714cb69aa786c7-b8ff0974ba23dc95.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:44:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T01:06:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-117-to-network-check-target-ip-10-0-129-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-117.ec2.internal uid: a15f5d28-d4c4-41de-8165-f61832577a57 resourceVersion: "62098" uid: 218cf1e4-5ac8-4642-b175-3d2465dde73e spec: sourcePod: network-check-source-869dcfcdcd-cppnk targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-14T01:13:15Z" message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.044855ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:48:15Z" - latency: 1.227215ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:47:15Z" - latency: 1.00354ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:46:15Z" - latency: 1.014644ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:45:15Z" - latency: 1.000871ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:44:15Z" - latency: 1.532885ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:43:15Z" - latency: 950.947µs message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:42:15Z" - latency: 930.728µs message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:41:15Z" - latency: 2.148404ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:40:15Z" - latency: 5.966851ms message: 'network-check-target-ip-10-0-129-117: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:39:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T01:06:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-117-to-network-check-target-ip-10-0-137-153 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-117.ec2.internal uid: a15f5d28-d4c4-41de-8165-f61832577a57 resourceVersion: "62101" uid: cd7b58fd-c920-4217-94b2-fa69ea2c63d2 spec: sourcePod: network-check-source-869dcfcdcd-cppnk targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-14T01:13:15Z" message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.834293ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:48:15Z" - latency: 2.329093ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:47:15Z" - latency: 1.966443ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:46:15Z" - latency: 2.015822ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:45:15Z" - latency: 2.339019ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:44:15Z" - latency: 2.314276ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:43:15Z" - latency: 2.242393ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:42:15Z" - latency: 2.447063ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:41:15Z" - latency: 2.850596ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:40:15Z" - latency: 7.276335ms message: 'network-check-target-ip-10-0-137-153: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:39:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T01:06:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-117-to-network-check-target-ip-10-0-141-32 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-117.ec2.internal uid: a15f5d28-d4c4-41de-8165-f61832577a57 resourceVersion: "62099" uid: ac0b5c86-fea8-41c5-b5ec-5d3475694850 spec: sourcePod: network-check-source-869dcfcdcd-cppnk targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T01:13:15Z" message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.140131ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:48:15Z" - latency: 2.077716ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:47:15Z" - latency: 2.202974ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:46:15Z" - latency: 2.325343ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:45:15Z" - latency: 2.286833ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:44:15Z" - latency: 2.869168ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:43:15Z" - latency: 2.386328ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:42:15Z" - latency: 3.644464ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:41:15Z" - latency: 2.630065ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:40:15Z" - latency: 5.866832ms message: 'network-check-target-ip-10-0-141-32: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:39:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T01:06:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-117-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-117.ec2.internal uid: a15f5d28-d4c4-41de-8165-f61832577a57 resourceVersion: "62100" uid: 36421a83-ad09-483f-9c38-036681fbeac3 spec: sourcePod: network-check-source-869dcfcdcd-cppnk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T01:12:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.192606ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:48:15Z" - latency: 1.996292ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T01:48:15Z" - latency: 790.432µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:47:15Z" - latency: 1.94206ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T01:47:15Z" - latency: 817.255µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:46:15Z" - latency: 1.791568ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T01:46:15Z" - latency: 918.077µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:45:15Z" - latency: 1.853348ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T01:45:15Z" - latency: 938.111µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:44:15Z" - latency: 1.820745ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T01:44:15Z" kind: List metadata: resourceVersion: ""