apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T03:51:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-121-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-121.ec2.internal uid: 6f914adf-739b-4e2a-807f-e34fd81e5973 resourceVersion: "62340" uid: 2dffa304-9394-4f98-ae36-aaf42cd8e8a2 spec: sourcePod: network-check-source-869dcfcdcd-979wl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-11T03:58:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.114529ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:33:23Z" - latency: 959.578µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:32:23Z" - latency: 1.494614ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:31:23Z" - latency: 893.513µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:30:23Z" - latency: 985.51µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:29:23Z" - latency: 1.473147ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:28:23Z" - latency: 1.109612ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:27:23Z" - latency: 944.031µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:26:23Z" - latency: 912.47µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:25:23Z" - latency: 1.031226ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:24:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T03:51:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-121-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-121.ec2.internal uid: 6f914adf-739b-4e2a-807f-e34fd81e5973 resourceVersion: "62342" uid: 47835cfd-fe60-4b83-8c30-9eecc23f9fc7 spec: sourcePod: network-check-source-869dcfcdcd-979wl targetEndpoint: a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-11T03:57:23Z" message: 'load-balancer-api-external: tcp connection to a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.434515ms message: 'load-balancer-api-external: tcp connection to a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:33:23Z" - latency: 6.847472ms message: 'load-balancer-api-external: resolved host name a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:33:23Z" - latency: 3.394606ms message: 'load-balancer-api-external: tcp connection to a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:32:23Z" - latency: 7.48046ms message: 'load-balancer-api-external: resolved host name a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:32:23Z" - latency: 3.911797ms message: 'load-balancer-api-external: tcp connection to a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:31:23Z" - latency: 7.149905ms message: 'load-balancer-api-external: resolved host name a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:31:23Z" - latency: 4.939177ms message: 'load-balancer-api-external: tcp connection to a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:30:23Z" - latency: 7.542585ms message: 'load-balancer-api-external: resolved host name a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:30:23Z" - latency: 4.845025ms message: 'load-balancer-api-external: tcp connection to a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:29:23Z" - latency: 6.592266ms message: 'load-balancer-api-external: resolved host name a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:29:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T03:51:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-121-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-121.ec2.internal uid: 6f914adf-739b-4e2a-807f-e34fd81e5973 resourceVersion: "62341" uid: 3f790756-c9ad-4ef6-b1e1-a26127fdaf41 spec: sourcePod: network-check-source-869dcfcdcd-979wl targetEndpoint: a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-11T03:57:23Z" message: 'load-balancer-api-internal: tcp connection to a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.363161ms message: 'load-balancer-api-internal: tcp connection to a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:33:23Z" - latency: 6.819752ms message: 'load-balancer-api-internal: resolved host name a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:33:23Z" - latency: 7.657311ms message: 'load-balancer-api-internal: tcp connection to a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:32:23Z" - latency: 7.561929ms message: 'load-balancer-api-internal: resolved host name a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:32:23Z" - latency: 4.604252ms message: 'load-balancer-api-internal: tcp connection to a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:31:23Z" - latency: 7.182801ms message: 'load-balancer-api-internal: resolved host name a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:31:23Z" - latency: 4.492632ms message: 'load-balancer-api-internal: tcp connection to a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:30:23Z" - latency: 7.594938ms message: 'load-balancer-api-internal: resolved host name a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:30:23Z" - latency: 4.804186ms message: 'load-balancer-api-internal: tcp connection to a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:29:23Z" - latency: 6.62666ms message: 'load-balancer-api-internal: resolved host name a6e748b4705d245e0ad2deb5fa53b333-a62c3687ebdbf091.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-11T04:29:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T03:51:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-121-to-network-check-target-ip-10-0-134-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-121.ec2.internal uid: 6f914adf-739b-4e2a-807f-e34fd81e5973 resourceVersion: "62339" uid: bd5bd908-d651-4b11-a9f3-a0932fb7f0ce spec: sourcePod: network-check-source-869dcfcdcd-979wl targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-11T03:58:23Z" message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.504904ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:33:23Z" - latency: 2.229236ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:32:23Z" - latency: 2.162035ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:31:23Z" - latency: 2.027432ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:30:23Z" - latency: 2.780852ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:29:23Z" - latency: 2.483679ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:28:23Z" - latency: 2.393928ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:27:23Z" - latency: 2.305915ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:26:23Z" - latency: 2.300147ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:25:23Z" - latency: 2.200444ms message: 'network-check-target-ip-10-0-134-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:24:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T03:51:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-121-to-network-check-target-ip-10-0-135-235 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-121.ec2.internal uid: 6f914adf-739b-4e2a-807f-e34fd81e5973 resourceVersion: "62338" uid: 5b32b2be-d942-4501-89c0-dda81ac3feee spec: sourcePod: network-check-source-869dcfcdcd-979wl targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-11T03:58:23Z" message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.446797ms message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:33:23Z" - latency: 2.594384ms message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:32:23Z" - latency: 2.520339ms message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:31:23Z" - latency: 2.833973ms message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:30:23Z" - latency: 2.333161ms message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:29:23Z" - latency: 2.484119ms message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:28:23Z" - latency: 2.04782ms message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:27:23Z" - latency: 2.397827ms message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:26:23Z" - latency: 2.313503ms message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:25:23Z" - latency: 2.433952ms message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:24:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T03:51:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-121-to-network-check-target-ip-10-0-138-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-121.ec2.internal uid: 6f914adf-739b-4e2a-807f-e34fd81e5973 resourceVersion: "62336" uid: 9ef70454-daf9-462e-a0bd-5c4fdfaebf7a spec: sourcePod: network-check-source-869dcfcdcd-979wl targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-11T03:58:23Z" message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 906.795µs message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:33:23Z" - latency: 907.792µs message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:32:23Z" - latency: 946.028µs message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:31:23Z" - latency: 1.076295ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:30:23Z" - latency: 1.215838ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:29:23Z" - latency: 938.171µs message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:28:23Z" - latency: 960.57µs message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:27:23Z" - latency: 974.102µs message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:26:23Z" - latency: 948.992µs message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:25:23Z" - latency: 1.091907ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:24:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-11T03:51:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-121-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-121.ec2.internal uid: 6f914adf-739b-4e2a-807f-e34fd81e5973 resourceVersion: "62337" uid: ebe4be02-33e7-48ee-b8d2-f88cca877d72 spec: sourcePod: network-check-source-869dcfcdcd-979wl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-11T03:57:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 932.462µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:33:23Z" - latency: 1.697584ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-11T04:33:23Z" - latency: 1.009778ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:32:23Z" - latency: 2.473503ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-11T04:32:23Z" - latency: 1.260702ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:31:23Z" - latency: 1.870295ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-11T04:31:23Z" - latency: 1.239116ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:30:23Z" - latency: 1.611956ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-11T04:30:23Z" - latency: 1.295373ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-11T04:29:23Z" - latency: 1.794246ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-11T04:29:23Z" kind: List metadata: resourceVersion: ""