apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:43:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-248-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-248.ec2.internal uid: 20f8c846-044f-481b-a9df-60604bdf567d resourceVersion: "54738" uid: b46e3696-6684-4288-9f6b-877cebc85814 spec: sourcePod: network-check-source-989f8b8dc-ss2mx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T15:50:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.2687ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:17Z" - latency: 899.725µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:17Z" - latency: 980.625µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:16:17Z" - latency: 1.249819ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:15:17Z" - latency: 862.68µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:14:17Z" - latency: 1.541517ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:13:17Z" - latency: 880.024µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:12:17Z" - latency: 910.462µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:11:17Z" - latency: 1.254326ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:10:17Z" - latency: 984.432µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:09:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:43:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-248-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-248.ec2.internal uid: 20f8c846-044f-481b-a9df-60604bdf567d resourceVersion: "55838" uid: 46dd396f-f756-412d-a7a0-6ed84c26bac9 spec: sourcePod: network-check-source-989f8b8dc-ss2mx targetEndpoint: aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T15:49:17Z" message: 'load-balancer-api-external: tcp connection to aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.03897ms message: 'load-balancer-api-external: tcp connection to aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:19:17Z" - latency: 9.966634ms message: 'load-balancer-api-external: resolved host name aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:19:17Z" - latency: 5.548124ms message: 'load-balancer-api-external: tcp connection to aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:17Z" - latency: 9.816785ms message: 'load-balancer-api-external: resolved host name aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:18:17Z" - latency: 6.37496ms message: 'load-balancer-api-external: tcp connection to aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:17Z" - latency: 9.571376ms message: 'load-balancer-api-external: resolved host name aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:17:17Z" - latency: 4.456325ms message: 'load-balancer-api-external: tcp connection to aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:16:17Z" - latency: 12.248905ms message: 'load-balancer-api-external: resolved host name aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:16:17Z" - latency: 4.323918ms message: 'load-balancer-api-external: tcp connection to aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:15:17Z" - latency: 11.060749ms message: 'load-balancer-api-external: resolved host name aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:15:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:43:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-248-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-248.ec2.internal uid: 20f8c846-044f-481b-a9df-60604bdf567d resourceVersion: "55839" uid: 405ba55c-dae8-418d-9520-6db79314b766 spec: sourcePod: network-check-source-989f8b8dc-ss2mx targetEndpoint: aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T15:49:17Z" message: 'load-balancer-api-internal: tcp connection to aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.786876ms message: 'load-balancer-api-internal: tcp connection to aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:19:17Z" - latency: 9.934626ms message: 'load-balancer-api-internal: resolved host name aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:19:17Z" - latency: 5.57265ms message: 'load-balancer-api-internal: tcp connection to aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:17Z" - latency: 9.75589ms message: 'load-balancer-api-internal: resolved host name aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:18:17Z" - latency: 6.396601ms message: 'load-balancer-api-internal: tcp connection to aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:17Z" - latency: 9.642697ms message: 'load-balancer-api-internal: resolved host name aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:17:17Z" - latency: 3.8003ms message: 'load-balancer-api-internal: tcp connection to aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:16:17Z" - latency: 12.165088ms message: 'load-balancer-api-internal: resolved host name aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:16:17Z" - latency: 4.076346ms message: 'load-balancer-api-internal: tcp connection to aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:15:17Z" - latency: 11.138367ms message: 'load-balancer-api-internal: resolved host name aa97e877da53f48b3ad455336f201635-596d58ee1ee84f94.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T16:15:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:43:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-248-to-network-check-target-ip-10-0-137-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-248.ec2.internal uid: 20f8c846-044f-481b-a9df-60604bdf567d resourceVersion: "54737" uid: 4595c8c4-924e-479c-9dd6-959f1f2e347a spec: sourcePod: network-check-source-989f8b8dc-ss2mx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:50:17Z" message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.26733ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:17Z" - latency: 2.357712ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:17Z" - latency: 2.355558ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:16:17Z" - latency: 2.402596ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:15:17Z" - latency: 2.106076ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:14:17Z" - latency: 2.281897ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:13:17Z" - latency: 2.177387ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:12:17Z" - latency: 2.10822ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:11:17Z" - latency: 2.249956ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:10:17Z" - latency: 2.076369ms message: 'network-check-target-ip-10-0-137-175: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:09:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:43:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-248-to-network-check-target-ip-10-0-138-64 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-248.ec2.internal uid: 20f8c846-044f-481b-a9df-60604bdf567d resourceVersion: "54736" uid: 7567c367-6507-41ec-81ef-5e49279f32dc spec: sourcePod: network-check-source-989f8b8dc-ss2mx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:50:17Z" message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.074115ms message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:17Z" - latency: 1.934069ms message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:17Z" - latency: 2.036417ms message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:16:17Z" - latency: 1.850752ms message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:15:17Z" - latency: 1.736454ms message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:14:17Z" - latency: 2.018207ms message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:13:17Z" - latency: 2.024825ms message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:12:17Z" - latency: 1.9725ms message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:11:17Z" - latency: 2.008261ms message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:10:17Z" - latency: 1.986565ms message: 'network-check-target-ip-10-0-138-64: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:09:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:43:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-248-to-network-check-target-ip-10-0-139-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-248.ec2.internal uid: 20f8c846-044f-481b-a9df-60604bdf567d resourceVersion: "54735" uid: f5d3163e-75a0-4ebc-8333-3dbc61c5c23a spec: sourcePod: network-check-source-989f8b8dc-ss2mx targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T15:50:17Z" message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 923.025µs message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:17Z" - latency: 1.196721ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:17Z" - latency: 1.147837ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:16:17Z" - latency: 1.063944ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:15:17Z" - latency: 1.642891ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:14:17Z" - latency: 1.053105ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:13:17Z" - latency: 1.134655ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:12:17Z" - latency: 954.335µs message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:11:17Z" - latency: 1.739265ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:10:17Z" - latency: 1.133494ms message: 'network-check-target-ip-10-0-139-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:09:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T15:43:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-248-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-248.ec2.internal uid: 20f8c846-044f-481b-a9df-60604bdf567d resourceVersion: "55837" uid: 63b8c74a-27f0-4fc7-ae7a-cba31cdfaffb spec: sourcePod: network-check-source-989f8b8dc-ss2mx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T15:49:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.14766ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:19:17Z" - latency: 1.922436ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T16:19:17Z" - latency: 875.502µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:18:17Z" - latency: 2.393055ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T16:18:17Z" - latency: 957.64µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:17:17Z" - latency: 1.823868ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T16:17:17Z" - latency: 1.04747ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:16:17Z" - latency: 1.981789ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T16:16:17Z" - latency: 859.561µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T16:15:17Z" - latency: 1.840485ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T16:15:17Z" kind: List metadata: resourceVersion: ""