apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:18:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: e0bed1fa-a6a2-4836-bb18-226c2a57d735 resourceVersion: "18855" uid: d1c67b39-beed-4a15-ab94-0f48792e9422 spec: sourcePod: network-check-source-8894fc9bd-7hlrt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T22:25:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.00743ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:32:22Z" - latency: 1.049187ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:31:22Z" - latency: 984.909µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:30:22Z" - latency: 1.389705ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:29:22Z" - latency: 964.085µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:28:22Z" - latency: 1.165695ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:27:22Z" - latency: 926.04µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:26:22Z" - latency: 990.722µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:25:22Z" - latency: 1.015659ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:24:22Z" - latency: 884.398µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:23:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:18:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: e0bed1fa-a6a2-4836-bb18-226c2a57d735 resourceVersion: "20985" uid: 5fac829d-0696-413b-a0f4-eab6750199a2 spec: sourcePod: network-check-source-8894fc9bd-7hlrt targetEndpoint: adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T22:24:22Z" message: 'load-balancer-api-external: tcp connection to adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.655515ms message: 'load-balancer-api-external: tcp connection to adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:36:22Z" - latency: 6.720663ms message: 'load-balancer-api-external: resolved host name adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:36:22Z" - latency: 4.82441ms message: 'load-balancer-api-external: tcp connection to adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:35:22Z" - latency: 7.68541ms message: 'load-balancer-api-external: resolved host name adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:35:22Z" - latency: 5.343103ms message: 'load-balancer-api-external: tcp connection to adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:34:22Z" - latency: 7.875897ms message: 'load-balancer-api-external: resolved host name adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:34:22Z" - latency: 4.455582ms message: 'load-balancer-api-external: tcp connection to adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:33:22Z" - latency: 6.843072ms message: 'load-balancer-api-external: resolved host name adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:33:22Z" - latency: 5.038548ms message: 'load-balancer-api-external: tcp connection to adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:32:22Z" - latency: 7.357783ms message: 'load-balancer-api-external: resolved host name adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:32:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:18:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: e0bed1fa-a6a2-4836-bb18-226c2a57d735 resourceVersion: "20984" uid: 5ef43ed6-f56b-45e4-9176-9be83383e2d9 spec: sourcePod: network-check-source-8894fc9bd-7hlrt targetEndpoint: adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T22:24:22Z" message: 'load-balancer-api-internal: tcp connection to adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.694ms message: 'load-balancer-api-internal: tcp connection to adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:36:22Z" - latency: 6.806117ms message: 'load-balancer-api-internal: resolved host name adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:36:22Z" - latency: 5.539222ms message: 'load-balancer-api-internal: tcp connection to adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:35:22Z" - latency: 7.708982ms message: 'load-balancer-api-internal: resolved host name adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:35:22Z" - latency: 5.354076ms message: 'load-balancer-api-internal: tcp connection to adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:34:22Z" - latency: 8.010478ms message: 'load-balancer-api-internal: resolved host name adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:34:22Z" - latency: 4.488112ms message: 'load-balancer-api-internal: tcp connection to adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:33:22Z" - latency: 6.788035ms message: 'load-balancer-api-internal: resolved host name adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:33:22Z" - latency: 5.002327ms message: 'load-balancer-api-internal: tcp connection to adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:32:22Z" - latency: 7.318762ms message: 'load-balancer-api-internal: resolved host name adc350fbef4b045a0a522b41f656d69b-9be3b128fe6eeb88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T22:32:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:18:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-network-check-target-ip-10-0-129-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: e0bed1fa-a6a2-4836-bb18-226c2a57d735 resourceVersion: "18852" uid: cba6ec99-f63b-4746-8a9c-e4274f201b8e spec: sourcePod: network-check-source-8894fc9bd-7hlrt targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T22:25:22Z" message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.061363ms message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:32:22Z" - latency: 1.516588ms message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:31:22Z" - latency: 951.244µs message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:30:22Z" - latency: 977.247µs message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:29:22Z" - latency: 893.953µs message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:28:22Z" - latency: 1.00052ms message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:27:22Z" - latency: 917.815µs message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:26:22Z" - latency: 1.427392ms message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:25:22Z" - latency: 1.195625ms message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:24:22Z" - latency: 1.502134ms message: 'network-check-target-ip-10-0-129-102: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:23:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:18:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-network-check-target-ip-10-0-140-65 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: e0bed1fa-a6a2-4836-bb18-226c2a57d735 resourceVersion: "18854" uid: 9da26e42-d61b-4c89-870d-3fdc77545e39 spec: sourcePod: network-check-source-8894fc9bd-7hlrt targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T22:25:22Z" message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.320802ms message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:32:22Z" - latency: 2.582808ms message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:31:22Z" - latency: 2.326576ms message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:30:22Z" - latency: 1.908586ms message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:29:22Z" - latency: 2.299219ms message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:28:22Z" - latency: 2.098459ms message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:27:22Z" - latency: 2.395273ms message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:26:22Z" - latency: 2.592027ms message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:25:22Z" - latency: 2.789618ms message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:24:22Z" - latency: 2.276298ms message: 'network-check-target-ip-10-0-140-65: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:23:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:18:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-network-check-target-ip-10-0-142-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: e0bed1fa-a6a2-4836-bb18-226c2a57d735 resourceVersion: "18853" uid: 30f27d9c-7bd3-4286-a4e5-d1bb5c44f055 spec: sourcePod: network-check-source-8894fc9bd-7hlrt targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T22:25:22Z" message: 'network-check-target-ip-10-0-142-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.318013ms message: 'network-check-target-ip-10-0-142-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:32:22Z" - latency: 2.466137ms message: 'network-check-target-ip-10-0-142-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:31:22Z" - latency: 2.26236ms message: 'network-check-target-ip-10-0-142-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:30:22Z" - latency: 2.394447ms message: 'network-check-target-ip-10-0-142-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:29:22Z" - latency: 2.430307ms message: 'network-check-target-ip-10-0-142-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:28:22Z" - latency: 2.168598ms message: 'network-check-target-ip-10-0-142-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:27:22Z" - latency: 2.28315ms message: 'network-check-target-ip-10-0-142-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:26:22Z" - latency: 2.37686ms message: 'network-check-target-ip-10-0-142-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:25:22Z" - latency: 2.400079ms message: 'network-check-target-ip-10-0-142-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:24:22Z" - latency: 2.396925ms message: 'network-check-target-ip-10-0-142-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:23:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T22:18:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-102-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-102.ec2.internal uid: e0bed1fa-a6a2-4836-bb18-226c2a57d735 resourceVersion: "20983" uid: 61289973-8100-43ab-8ef5-6d6a738dba03 spec: sourcePod: network-check-source-8894fc9bd-7hlrt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T22:24:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 818.824µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:36:22Z" - latency: 1.709031ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T22:36:22Z" - latency: 1.225242ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:35:22Z" - latency: 1.853245ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T22:35:22Z" - latency: 855.902µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:34:22Z" - latency: 1.628458ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T22:34:22Z" - latency: 1.012243ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:33:22Z" - latency: 1.772957ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T22:33:22Z" - latency: 792.449µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T22:32:22Z" - latency: 1.788632ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T22:32:22Z" kind: List metadata: resourceVersion: ""