apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T18:00:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-135-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-135.ec2.internal uid: 12797ba3-519f-42c2-85b8-03db1259c996 resourceVersion: "61552" uid: 610069ac-4434-4930-af33-e19f933c0b9d spec: sourcePod: network-check-source-7bc5b6bf85-cdk8s targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-20T18:07:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.382702ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:42:29Z" - latency: 1.114432ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:41:29Z" - latency: 1.16306ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:40:29Z" - latency: 1.256384ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:39:29Z" - latency: 1.210198ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:38:29Z" - latency: 1.155801ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:37:29Z" - latency: 1.225625ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:36:29Z" - latency: 993.377µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:35:29Z" - latency: 1.570366ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:34:29Z" - latency: 1.547038ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:33:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T18:00:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-135-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-135.ec2.internal uid: 12797ba3-519f-42c2-85b8-03db1259c996 resourceVersion: "61554" uid: 781c17f4-4636-4b96-9a23-4b1720c56fb0 spec: sourcePod: network-check-source-7bc5b6bf85-cdk8s targetEndpoint: a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T18:06:29Z" message: 'load-balancer-api-external: tcp connection to a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.976162ms message: 'load-balancer-api-external: tcp connection to a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:42:29Z" - latency: 7.341859ms message: 'load-balancer-api-external: resolved host name a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:42:29Z" - latency: 5.4505ms message: 'load-balancer-api-external: tcp connection to a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:41:29Z" - latency: 7.288868ms message: 'load-balancer-api-external: resolved host name a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:41:29Z" - latency: 3.784889ms message: 'load-balancer-api-external: tcp connection to a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:40:29Z" - latency: 6.244102ms message: 'load-balancer-api-external: resolved host name a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:40:29Z" - latency: 3.52792ms message: 'load-balancer-api-external: tcp connection to a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:39:29Z" - latency: 7.310958ms message: 'load-balancer-api-external: resolved host name a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:39:29Z" - latency: 4.167924ms message: 'load-balancer-api-external: tcp connection to a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:38:29Z" - latency: 6.892076ms message: 'load-balancer-api-external: resolved host name a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:38:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T18:00:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-135-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-135.ec2.internal uid: 12797ba3-519f-42c2-85b8-03db1259c996 resourceVersion: "61553" uid: bd2fbae6-b9f4-428b-82c2-3136eecf86b5 spec: sourcePod: network-check-source-7bc5b6bf85-cdk8s targetEndpoint: a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T18:06:29Z" message: 'load-balancer-api-internal: tcp connection to a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.990253ms message: 'load-balancer-api-internal: tcp connection to a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:42:29Z" - latency: 7.382714ms message: 'load-balancer-api-internal: resolved host name a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:42:29Z" - latency: 5.610795ms message: 'load-balancer-api-internal: tcp connection to a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:41:29Z" - latency: 7.321522ms message: 'load-balancer-api-internal: resolved host name a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:41:29Z" - latency: 4.952401ms message: 'load-balancer-api-internal: tcp connection to a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:40:29Z" - latency: 6.281977ms message: 'load-balancer-api-internal: resolved host name a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:40:29Z" - latency: 4.169065ms message: 'load-balancer-api-internal: tcp connection to a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:39:29Z" - latency: 7.273294ms message: 'load-balancer-api-internal: resolved host name a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:39:29Z" - latency: 4.726079ms message: 'load-balancer-api-internal: tcp connection to a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:38:29Z" - latency: 6.850567ms message: 'load-balancer-api-internal: resolved host name a4d97b2066e4d4f28b5e2fbe6daa8b95-1d5681d84a3a5c80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T18:38:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T18:00:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-135-to-network-check-target-ip-10-0-133-135 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-135.ec2.internal uid: 12797ba3-519f-42c2-85b8-03db1259c996 resourceVersion: "61548" uid: 96877042-cc64-476c-88d5-229768918fbb spec: sourcePod: network-check-source-7bc5b6bf85-cdk8s targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T18:07:29Z" message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.065239ms message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:42:29Z" - latency: 932.063µs message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:41:29Z" - latency: 1.1324ms message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:40:29Z" - latency: 1.066854ms message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:39:29Z" - latency: 987.095µs message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:38:29Z" - latency: 1.131699ms message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:37:29Z" - latency: 968.926µs message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:36:29Z" - latency: 1.093808ms message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:35:29Z" - latency: 828.46µs message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:34:29Z" - latency: 963.105µs message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:33:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T18:00:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-135-to-network-check-target-ip-10-0-137-247 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-135.ec2.internal uid: 12797ba3-519f-42c2-85b8-03db1259c996 resourceVersion: "61550" uid: 1389b809-5b2e-4dd3-9f43-17de25630308 spec: sourcePod: network-check-source-7bc5b6bf85-cdk8s targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T18:07:29Z" message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.224864ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:42:29Z" - latency: 2.168874ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:41:29Z" - latency: 2.276918ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:40:29Z" - latency: 2.179374ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:39:29Z" - latency: 2.085838ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:38:29Z" - latency: 2.133745ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:37:29Z" - latency: 2.329787ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:36:29Z" - latency: 2.208031ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:35:29Z" - latency: 2.219694ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:34:29Z" - latency: 2.165167ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:33:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T18:00:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-135-to-network-check-target-ip-10-0-138-227 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-135.ec2.internal uid: 12797ba3-519f-42c2-85b8-03db1259c996 resourceVersion: "61549" uid: dde8cd9d-5c5f-4b15-8d90-2d12031197d0 spec: sourcePod: network-check-source-7bc5b6bf85-cdk8s targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T18:07:29Z" message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.212972ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:42:29Z" - latency: 2.157751ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:41:29Z" - latency: 2.217177ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:40:29Z" - latency: 2.314135ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:39:29Z" - latency: 2.481825ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:38:29Z" - latency: 2.119027ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:37:29Z" - latency: 2.29314ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:36:29Z" - latency: 2.088591ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:35:29Z" - latency: 2.231032ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:34:29Z" - latency: 2.176503ms message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:33:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T18:00:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-135-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-135.ec2.internal uid: 12797ba3-519f-42c2-85b8-03db1259c996 resourceVersion: "61551" uid: 60b00b9e-4ff4-49ef-a862-42b55f338e9c spec: sourcePod: network-check-source-7bc5b6bf85-cdk8s targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T18:06:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.140219ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:42:29Z" - latency: 2.1856ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T18:42:29Z" - latency: 849.069µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:41:29Z" - latency: 2.3251ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T18:41:29Z" - latency: 1.119501ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:40:29Z" - latency: 1.794734ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T18:40:29Z" - latency: 815.346µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:39:29Z" - latency: 1.85344ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T18:39:29Z" - latency: 1.077711ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T18:38:29Z" - latency: 2.525502ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T18:38:29Z" kind: List metadata: resourceVersion: ""