apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:49:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-132-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-132.ec2.internal uid: 13ed98da-8614-4697-8ad3-a2efb09be001 resourceVersion: "70677" uid: 0b1e762c-214b-46e1-8f1b-e73327baf31c spec: sourcePod: network-check-source-7d88cb55d8-ssxfv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T15:56:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.074953ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:38:36Z" - latency: 1.213645ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:37:36Z" - latency: 1.40614ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:36:36Z" - latency: 1.254528ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:35:36Z" - latency: 1.700299ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:34:36Z" - latency: 1.02934ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:33:36Z" - latency: 980.026µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:32:36Z" - latency: 1.236498ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:31:36Z" - latency: 958.486µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:30:36Z" - latency: 1.021944ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:29:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:49:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-132-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-132.ec2.internal uid: 13ed98da-8614-4697-8ad3-a2efb09be001 resourceVersion: "69572" uid: 0f493d90-a2f8-44ca-9b4c-3b339ad3a432 spec: sourcePod: network-check-source-7d88cb55d8-ssxfv targetEndpoint: ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T15:55:36Z" message: 'load-balancer-api-external: tcp connection to ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.210093ms message: 'load-balancer-api-external: tcp connection to ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:37:36Z" - latency: 10.03396ms message: 'load-balancer-api-external: resolved host name ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:37:36Z" - latency: 5.230807ms message: 'load-balancer-api-external: tcp connection to ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:36:36Z" - latency: 8.776017ms message: 'load-balancer-api-external: resolved host name ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:36:36Z" - latency: 5.654212ms message: 'load-balancer-api-external: tcp connection to ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:35:36Z" - latency: 8.278786ms message: 'load-balancer-api-external: resolved host name ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:35:36Z" - latency: 4.218293ms message: 'load-balancer-api-external: tcp connection to ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:34:36Z" - latency: 9.776087ms message: 'load-balancer-api-external: resolved host name ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:34:36Z" - latency: 4.48566ms message: 'load-balancer-api-external: tcp connection to ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:33:36Z" - latency: 7.19025ms message: 'load-balancer-api-external: resolved host name ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:33:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:49:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-132-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-132.ec2.internal uid: 13ed98da-8614-4697-8ad3-a2efb09be001 resourceVersion: "69573" uid: c428dac3-6261-4b1e-99ee-e36c7cc3c497 spec: sourcePod: network-check-source-7d88cb55d8-ssxfv targetEndpoint: ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T15:55:36Z" message: 'load-balancer-api-internal: tcp connection to ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.526971ms message: 'load-balancer-api-internal: tcp connection to ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:37:36Z" - latency: 10.01143ms message: 'load-balancer-api-internal: resolved host name ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:37:36Z" - latency: 4.282098ms message: 'load-balancer-api-internal: tcp connection to ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:36:36Z" - latency: 8.642249ms message: 'load-balancer-api-internal: resolved host name ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:36:36Z" - latency: 5.63298ms message: 'load-balancer-api-internal: tcp connection to ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:35:36Z" - latency: 8.32429ms message: 'load-balancer-api-internal: resolved host name ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:35:36Z" - latency: 4.499036ms message: 'load-balancer-api-internal: tcp connection to ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:34:36Z" - latency: 9.651844ms message: 'load-balancer-api-internal: resolved host name ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:34:36Z" - latency: 4.444795ms message: 'load-balancer-api-internal: tcp connection to ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:33:36Z" - latency: 7.22403ms message: 'load-balancer-api-internal: resolved host name ae85e1f1935b44fa4b2dfae45f16dd59-aeec2b6cc3b2baf5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T16:33:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:49:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-132-to-network-check-target-ip-10-0-130-132 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-132.ec2.internal uid: 13ed98da-8614-4697-8ad3-a2efb09be001 resourceVersion: "70674" uid: 69f772c1-00f0-4d82-b9a9-71eea4b2e57f spec: sourcePod: network-check-source-7d88cb55d8-ssxfv targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T15:56:36Z" message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 856.063µs message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:38:36Z" - latency: 1.090504ms message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:37:36Z" - latency: 1.623861ms message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:36:36Z" - latency: 1.386526ms message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:35:36Z" - latency: 935.44µs message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:34:36Z" - latency: 1.13686ms message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:33:36Z" - latency: 927.226µs message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:32:36Z" - latency: 1.472571ms message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:31:36Z" - latency: 870.693µs message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:30:36Z" - latency: 1.784015ms message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:29:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:49:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-132-to-network-check-target-ip-10-0-130-153 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-132.ec2.internal uid: 13ed98da-8614-4697-8ad3-a2efb09be001 resourceVersion: "70675" uid: 1cf3b10f-8c99-48ba-9dfc-24aeb61700b9 spec: sourcePod: network-check-source-7d88cb55d8-ssxfv targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T15:56:36Z" message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.133117ms message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:38:36Z" - latency: 2.381569ms message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:37:36Z" - latency: 2.129271ms message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:36:36Z" - latency: 2.238219ms message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:35:36Z" - latency: 2.17236ms message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:34:36Z" - latency: 1.962998ms message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:33:36Z" - latency: 2.004176ms message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:32:36Z" - latency: 2.31627ms message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:31:36Z" - latency: 1.927781ms message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:30:36Z" - latency: 2.093138ms message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:29:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:49:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-132-to-network-check-target-ip-10-0-143-118 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-132.ec2.internal uid: 13ed98da-8614-4697-8ad3-a2efb09be001 resourceVersion: "70676" uid: 40ecf535-e1f7-4e74-84f3-19b57c102e3e spec: sourcePod: network-check-source-7d88cb55d8-ssxfv targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T15:56:36Z" message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.072189ms message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:38:36Z" - latency: 1.969532ms message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:37:36Z" - latency: 2.151529ms message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:36:36Z" - latency: 2.247434ms message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:35:36Z" - latency: 2.251283ms message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:34:36Z" - latency: 2.181263ms message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:33:36Z" - latency: 1.937503ms message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:32:36Z" - latency: 2.435659ms message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:31:36Z" - latency: 1.884144ms message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:30:36Z" - latency: 2.23928ms message: 'network-check-target-ip-10-0-143-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:29:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T15:49:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-132-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-132.ec2.internal uid: 13ed98da-8614-4697-8ad3-a2efb09be001 resourceVersion: "69570" uid: e6b3be1f-d99e-4443-9e19-91b331d189d8 spec: sourcePod: network-check-source-7d88cb55d8-ssxfv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T15:55:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 817.694µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:37:36Z" - latency: 1.972151ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T16:37:36Z" - latency: 1.00508ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:36:36Z" - latency: 2.243781ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T16:36:36Z" - latency: 1.093817ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:35:36Z" - latency: 2.015027ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T16:35:36Z" - latency: 1.201968ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:34:36Z" - latency: 2.298384ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T16:34:36Z" - latency: 913.2µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T16:33:36Z" - latency: 1.996603ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T16:33:36Z" kind: List metadata: resourceVersion: ""