apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:04:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-84-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-84.ec2.internal uid: 18a5b2a0-7b68-42de-9119-f35178c150b5 resourceVersion: "18815" uid: 631a3a10-e93c-4fe9-a3d4-f33d491ea764 spec: sourcePod: network-check-source-7b678d77c7-7fbbk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T14:11:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.061957ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:18:31Z" - latency: 1.128302ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:17:31Z" - latency: 1.056885ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:16:31Z" - latency: 813.235µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:15:31Z" - latency: 937.312µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:14:31Z" - latency: 1.088439ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:13:31Z" - latency: 1.253382ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:12:31Z" - latency: 1.100394ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:11:31Z" - latency: 1.56888ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:10:31Z" - latency: 990.139µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:09:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:04:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-84-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-84.ec2.internal uid: 18a5b2a0-7b68-42de-9119-f35178c150b5 resourceVersion: "20920" uid: 301baa03-36e7-4c24-862b-781adcd33c89 spec: sourcePod: network-check-source-7b678d77c7-7fbbk targetEndpoint: a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T14:10:31Z" message: 'load-balancer-api-external: tcp connection to a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.581516ms message: 'load-balancer-api-external: tcp connection to a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:22:31Z" - latency: 9.881758ms message: 'load-balancer-api-external: resolved host name a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:22:31Z" - latency: 4.416315ms message: 'load-balancer-api-external: tcp connection to a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:21:31Z" - latency: 7.491615ms message: 'load-balancer-api-external: resolved host name a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:21:31Z" - latency: 4.543946ms message: 'load-balancer-api-external: tcp connection to a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:20:31Z" - latency: 8.138304ms message: 'load-balancer-api-external: resolved host name a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:20:31Z" - latency: 5.18365ms message: 'load-balancer-api-external: tcp connection to a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:19:31Z" - latency: 5.905842ms message: 'load-balancer-api-external: resolved host name a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:19:31Z" - latency: 4.552817ms message: 'load-balancer-api-external: tcp connection to a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:18:31Z" - latency: 8.659008ms message: 'load-balancer-api-external: resolved host name a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:18:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:04:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-84-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-84.ec2.internal uid: 18a5b2a0-7b68-42de-9119-f35178c150b5 resourceVersion: "20921" uid: 533010d8-0e43-4735-b246-839808084cc7 spec: sourcePod: network-check-source-7b678d77c7-7fbbk targetEndpoint: a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T14:10:31Z" message: 'load-balancer-api-internal: tcp connection to a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.59361ms message: 'load-balancer-api-internal: tcp connection to a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:22:31Z" - latency: 9.858017ms message: 'load-balancer-api-internal: resolved host name a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:22:31Z" - latency: 4.405851ms message: 'load-balancer-api-internal: tcp connection to a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:21:31Z" - latency: 7.460921ms message: 'load-balancer-api-internal: resolved host name a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:21:31Z" - latency: 5.581377ms message: 'load-balancer-api-internal: tcp connection to a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:20:31Z" - latency: 8.047236ms message: 'load-balancer-api-internal: resolved host name a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:20:31Z" - latency: 5.187402ms message: 'load-balancer-api-internal: tcp connection to a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:19:31Z" - latency: 5.871337ms message: 'load-balancer-api-internal: resolved host name a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:19:31Z" - latency: 4.113318ms message: 'load-balancer-api-internal: tcp connection to a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:18:31Z" - latency: 8.61936ms message: 'load-balancer-api-internal: resolved host name a204c63c2fbb3419fa8f72c3b490ac3f-d6beaa4520e874b8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:18:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:04:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-84-to-network-check-target-ip-10-0-129-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-84.ec2.internal uid: 18a5b2a0-7b68-42de-9119-f35178c150b5 resourceVersion: "18813" uid: d520bcd0-6342-4936-bff9-a373ae40676a spec: sourcePod: network-check-source-7b678d77c7-7fbbk targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:11:31Z" message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 745.104µs message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:18:31Z" - latency: 870.641µs message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:17:31Z" - latency: 879.083µs message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:16:31Z" - latency: 802.246µs message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:15:31Z" - latency: 825.135µs message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:14:31Z" - latency: 891.019µs message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:13:31Z" - latency: 929.441µs message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:12:31Z" - latency: 1.047136ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:11:31Z" - latency: 2.388213ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:10:31Z" - latency: 884.341µs message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:09:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:04:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-84-to-network-check-target-ip-10-0-130-98 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-84.ec2.internal uid: 18a5b2a0-7b68-42de-9119-f35178c150b5 resourceVersion: "18814" uid: a45810c6-ef0a-4add-adf6-f755140c6851 spec: sourcePod: network-check-source-7b678d77c7-7fbbk targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:11:31Z" message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.981895ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:18:31Z" - latency: 2.035606ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:17:31Z" - latency: 1.881774ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:16:31Z" - latency: 2.077963ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:15:31Z" - latency: 2.108998ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:14:31Z" - latency: 1.814557ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:13:31Z" - latency: 2.039276ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:12:31Z" - latency: 1.963594ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:11:31Z" - latency: 2.930852ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:10:31Z" - latency: 2.188416ms message: 'network-check-target-ip-10-0-130-98: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:09:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:04:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-84-to-network-check-target-ip-10-0-140-59 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-84.ec2.internal uid: 18a5b2a0-7b68-42de-9119-f35178c150b5 resourceVersion: "18812" uid: 65279d3f-504e-4703-afbb-2d7966cdb412 spec: sourcePod: network-check-source-7b678d77c7-7fbbk targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:11:31Z" message: 'network-check-target-ip-10-0-140-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.858257ms message: 'network-check-target-ip-10-0-140-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:18:31Z" - latency: 1.777814ms message: 'network-check-target-ip-10-0-140-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:17:31Z" - latency: 1.856657ms message: 'network-check-target-ip-10-0-140-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:16:31Z" - latency: 1.877036ms message: 'network-check-target-ip-10-0-140-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:15:31Z" - latency: 1.94833ms message: 'network-check-target-ip-10-0-140-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:14:31Z" - latency: 1.861853ms message: 'network-check-target-ip-10-0-140-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:13:31Z" - latency: 1.875059ms message: 'network-check-target-ip-10-0-140-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:12:31Z" - latency: 1.762206ms message: 'network-check-target-ip-10-0-140-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:11:31Z" - latency: 1.901929ms message: 'network-check-target-ip-10-0-140-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:10:31Z" - latency: 1.789148ms message: 'network-check-target-ip-10-0-140-59: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:09:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:04:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-84-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-84.ec2.internal uid: 18a5b2a0-7b68-42de-9119-f35178c150b5 resourceVersion: "20919" uid: 6f0fb0c8-b8b6-4c78-ab69-cb5a1286bb86 spec: sourcePod: network-check-source-7b678d77c7-7fbbk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T14:10:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.01604ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:22:31Z" - latency: 1.73146ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:22:31Z" - latency: 790.216µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:21:31Z" - latency: 1.516541ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:21:31Z" - latency: 1.066574ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:20:31Z" - latency: 1.642842ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:20:31Z" - latency: 761.069µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:19:31Z" - latency: 1.612341ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:19:31Z" - latency: 807.054µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:18:31Z" - latency: 1.814343ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:18:31Z" kind: List metadata: resourceVersion: ""