apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T20:00:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-178-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-178.ec2.internal uid: d24fcfa6-dd2c-4862-b892-23ad23a86797 resourceVersion: "62963" uid: 2ea87161-fe05-4fb4-9bee-a81d7f45a888 spec: sourcePod: network-check-source-7bc5b6bf85-m8dc4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-20T20:07:34Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.268174ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:42:34Z" - latency: 1.37245ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:41:34Z" - latency: 1.210129ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:40:34Z" - latency: 1.918211ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:39:34Z" - latency: 1.390782ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:38:34Z" - latency: 1.299512ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:37:34Z" - latency: 1.038409ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:36:34Z" - latency: 1.272225ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:35:34Z" - latency: 1.69348ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:34:34Z" - latency: 1.083382ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:33:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T20:00:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-178-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-178.ec2.internal uid: d24fcfa6-dd2c-4862-b892-23ad23a86797 resourceVersion: "62966" uid: 9c7b39a3-3199-45b8-8848-add964d90520 spec: sourcePod: network-check-source-7bc5b6bf85-m8dc4 targetEndpoint: a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T20:06:34Z" message: 'load-balancer-api-external: tcp connection to a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.450969ms message: 'load-balancer-api-external: tcp connection to a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:42:34Z" - latency: 9.259997ms message: 'load-balancer-api-external: resolved host name a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:42:34Z" - latency: 3.829087ms message: 'load-balancer-api-external: tcp connection to a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:41:34Z" - latency: 8.255649ms message: 'load-balancer-api-external: resolved host name a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:41:34Z" - latency: 4.256917ms message: 'load-balancer-api-external: tcp connection to a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:40:34Z" - latency: 7.757257ms message: 'load-balancer-api-external: resolved host name a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:40:34Z" - latency: 5.292138ms message: 'load-balancer-api-external: tcp connection to a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:39:34Z" - latency: 10.628602ms message: 'load-balancer-api-external: resolved host name a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:39:34Z" - latency: 4.050555ms message: 'load-balancer-api-external: tcp connection to a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:38:34Z" - latency: 8.689507ms message: 'load-balancer-api-external: resolved host name a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:38:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T20:00:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-178-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-178.ec2.internal uid: d24fcfa6-dd2c-4862-b892-23ad23a86797 resourceVersion: "62965" uid: 9b77a6ea-cc7a-4048-8337-4a17163f1b90 spec: sourcePod: network-check-source-7bc5b6bf85-m8dc4 targetEndpoint: a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T20:06:34Z" message: 'load-balancer-api-internal: tcp connection to a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.471828ms message: 'load-balancer-api-internal: tcp connection to a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:42:34Z" - latency: 9.279904ms message: 'load-balancer-api-internal: resolved host name a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:42:34Z" - latency: 5.228835ms message: 'load-balancer-api-internal: tcp connection to a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:41:34Z" - latency: 8.305775ms message: 'load-balancer-api-internal: resolved host name a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:41:34Z" - latency: 4.266475ms message: 'load-balancer-api-internal: tcp connection to a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:40:34Z" - latency: 7.809017ms message: 'load-balancer-api-internal: resolved host name a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:40:34Z" - latency: 7.292163ms message: 'load-balancer-api-internal: tcp connection to a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:39:34Z" - latency: 10.692258ms message: 'load-balancer-api-internal: resolved host name a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:39:34Z" - latency: 4.10917ms message: 'load-balancer-api-internal: tcp connection to a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:38:34Z" - latency: 8.741372ms message: 'load-balancer-api-internal: resolved host name a0b43f72dbba6433791c70ea509ff148-529453f4d29efa82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T20:38:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T20:00:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-178-to-network-check-target-ip-10-0-128-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-178.ec2.internal uid: d24fcfa6-dd2c-4862-b892-23ad23a86797 resourceVersion: "62959" uid: d99a403e-bbd6-49ab-b20c-6a1e8a715109 spec: sourcePod: network-check-source-7bc5b6bf85-m8dc4 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T20:07:34Z" message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 972.324µs message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:42:34Z" - latency: 1.029079ms message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:41:34Z" - latency: 1.099927ms message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:40:34Z" - latency: 1.365132ms message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:39:34Z" - latency: 1.08095ms message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:38:34Z" - latency: 1.647352ms message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:37:34Z" - latency: 1.127662ms message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:36:34Z" - latency: 971.237µs message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:35:34Z" - latency: 1.041639ms message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:34:34Z" - latency: 1.339587ms message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:33:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T20:00:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-178-to-network-check-target-ip-10-0-132-157 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-178.ec2.internal uid: d24fcfa6-dd2c-4862-b892-23ad23a86797 resourceVersion: "62960" uid: 8082f52f-efea-4543-ac8d-c9cc61d627af spec: sourcePod: network-check-source-7bc5b6bf85-m8dc4 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T20:07:34Z" message: 'network-check-target-ip-10-0-132-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.046835ms message: 'network-check-target-ip-10-0-132-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:42:34Z" - latency: 1.945068ms message: 'network-check-target-ip-10-0-132-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:41:34Z" - latency: 1.809322ms message: 'network-check-target-ip-10-0-132-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:40:34Z" - latency: 2.461744ms message: 'network-check-target-ip-10-0-132-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:39:34Z" - latency: 2.15204ms message: 'network-check-target-ip-10-0-132-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:38:34Z" - latency: 2.304924ms message: 'network-check-target-ip-10-0-132-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:37:34Z" - latency: 2.040899ms message: 'network-check-target-ip-10-0-132-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:36:34Z" - latency: 2.052631ms message: 'network-check-target-ip-10-0-132-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:35:34Z" - latency: 1.843431ms message: 'network-check-target-ip-10-0-132-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:34:34Z" - latency: 2.117292ms message: 'network-check-target-ip-10-0-132-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:33:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T20:00:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-178-to-network-check-target-ip-10-0-143-191 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-178.ec2.internal uid: d24fcfa6-dd2c-4862-b892-23ad23a86797 resourceVersion: "62961" uid: b3ab007d-c2f2-4e47-a5c5-7a829dea54fc spec: sourcePod: network-check-source-7bc5b6bf85-m8dc4 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T20:07:34Z" message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.363578ms message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:42:34Z" - latency: 2.36409ms message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:41:34Z" - latency: 2.238888ms message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:40:34Z" - latency: 2.615905ms message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:39:34Z" - latency: 2.120746ms message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:38:34Z" - latency: 2.526699ms message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:37:34Z" - latency: 2.303387ms message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:36:34Z" - latency: 2.436ms message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:35:34Z" - latency: 2.375714ms message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:34:34Z" - latency: 2.14713ms message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:33:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T20:00:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-178-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-178.ec2.internal uid: d24fcfa6-dd2c-4862-b892-23ad23a86797 resourceVersion: "62962" uid: 63c8a2bb-08dc-417b-b0fb-b0f3f843e185 spec: sourcePod: network-check-source-7bc5b6bf85-m8dc4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T20:06:34Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 881.335µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:42:34Z" - latency: 2.106337ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T20:42:34Z" - latency: 1.232464ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:41:34Z" - latency: 1.812427ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T20:41:34Z" - latency: 915.281µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:40:34Z" - latency: 1.851695ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T20:40:34Z" - latency: 1.050165ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:39:34Z" - latency: 2.542231ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T20:39:34Z" - latency: 905.758µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T20:38:34Z" - latency: 1.94645ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T20:38:34Z" kind: List metadata: resourceVersion: ""