apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T00:58:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-32-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-32.ec2.internal uid: 41238b11-2412-4299-bc40-1e4afd2f6373 resourceVersion: "47385" uid: 2378874d-274f-497d-9d9a-f6cb8120bba1 spec: sourcePod: network-check-source-7bc5b6bf85-tkb76 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-18T01:05:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.916967ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:26:02Z" - latency: 940.115µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:25:02Z" - latency: 1.333283ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:24:02Z" - latency: 1.219513ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:23:02Z" - latency: 1.17814ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:22:02Z" - latency: 933.211µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:21:02Z" - latency: 1.196876ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:20:02Z" - latency: 1.373131ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:19:02Z" - latency: 1.298868ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:18:02Z" - latency: 1.108096ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:17:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T00:58:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-32-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-32.ec2.internal uid: 41238b11-2412-4299-bc40-1e4afd2f6373 resourceVersion: "42155" uid: fdd614c0-ec89-40db-b825-ac56f05f3a8f spec: sourcePod: network-check-source-7bc5b6bf85-tkb76 targetEndpoint: a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-18T01:04:02Z" message: 'load-balancer-api-external: tcp connection to a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.01537ms message: 'load-balancer-api-external: tcp connection to a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:22:02Z" - latency: 7.391758ms message: 'load-balancer-api-external: resolved host name a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:22:02Z" - latency: 5.306637ms message: 'load-balancer-api-external: tcp connection to a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:21:02Z" - latency: 6.277252ms message: 'load-balancer-api-external: resolved host name a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:21:02Z" - latency: 4.445565ms message: 'load-balancer-api-external: tcp connection to a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:20:02Z" - latency: 6.874379ms message: 'load-balancer-api-external: resolved host name a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:20:02Z" - latency: 5.606773ms message: 'load-balancer-api-external: tcp connection to a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:19:02Z" - latency: 8.023864ms message: 'load-balancer-api-external: resolved host name a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:19:02Z" - latency: 5.258948ms message: 'load-balancer-api-external: tcp connection to a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:18:02Z" - latency: 7.722727ms message: 'load-balancer-api-external: resolved host name a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:18:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T00:58:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-32-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-32.ec2.internal uid: 41238b11-2412-4299-bc40-1e4afd2f6373 resourceVersion: "42156" uid: 47353528-e943-4f76-8dfd-4eeecb3f4a30 spec: sourcePod: network-check-source-7bc5b6bf85-tkb76 targetEndpoint: a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-18T01:04:02Z" message: 'load-balancer-api-internal: tcp connection to a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.677263ms message: 'load-balancer-api-internal: tcp connection to a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:22:02Z" - latency: 7.469758ms message: 'load-balancer-api-internal: resolved host name a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:22:02Z" - latency: 4.127729ms message: 'load-balancer-api-internal: tcp connection to a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:21:02Z" - latency: 6.345051ms message: 'load-balancer-api-internal: resolved host name a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:21:02Z" - latency: 4.433349ms message: 'load-balancer-api-internal: tcp connection to a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:20:02Z" - latency: 6.908755ms message: 'load-balancer-api-internal: resolved host name a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:20:02Z" - latency: 5.590677ms message: 'load-balancer-api-internal: tcp connection to a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:19:02Z" - latency: 8.063041ms message: 'load-balancer-api-internal: resolved host name a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:19:02Z" - latency: 4.419095ms message: 'load-balancer-api-internal: tcp connection to a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:18:02Z" - latency: 7.745563ms message: 'load-balancer-api-internal: resolved host name a3d41fadae4c540a595666ae97214385-1ba28fa955153e82.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T01:18:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T00:58:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-32-to-network-check-target-ip-10-0-129-13 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-32.ec2.internal uid: 41238b11-2412-4299-bc40-1e4afd2f6373 resourceVersion: "47383" uid: 6932effa-2028-41a8-8082-c0fb7736d42a spec: sourcePod: network-check-source-7bc5b6bf85-tkb76 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-18T01:05:02Z" message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.137634ms message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:26:02Z" - latency: 2.224576ms message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:25:02Z" - latency: 2.622996ms message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:24:02Z" - latency: 2.230361ms message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:23:02Z" - latency: 2.229862ms message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:22:02Z" - latency: 2.071709ms message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:21:02Z" - latency: 2.377996ms message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:20:02Z" - latency: 2.42406ms message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:19:02Z" - latency: 2.485999ms message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:18:02Z" - latency: 2.089108ms message: 'network-check-target-ip-10-0-129-13: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:17:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T00:58:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-32-to-network-check-target-ip-10-0-132-32 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-32.ec2.internal uid: 41238b11-2412-4299-bc40-1e4afd2f6373 resourceVersion: "47381" uid: 56e8e405-21d7-4516-ae03-70af4d53ade3 spec: sourcePod: network-check-source-7bc5b6bf85-tkb76 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-18T01:05:02Z" message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 997.7µs message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:26:02Z" - latency: 1.302347ms message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:25:02Z" - latency: 1.147278ms message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:24:02Z" - latency: 1.492628ms message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:23:02Z" - latency: 882.139µs message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:22:02Z" - latency: 1.007738ms message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:21:02Z" - latency: 1.669771ms message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:20:02Z" - latency: 1.566975ms message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:19:02Z" - latency: 1.603022ms message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:18:02Z" - latency: 1.077515ms message: 'network-check-target-ip-10-0-132-32: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:17:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T00:58:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-32-to-network-check-target-ip-10-0-133-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-32.ec2.internal uid: 41238b11-2412-4299-bc40-1e4afd2f6373 resourceVersion: "47382" uid: bf7189e4-d85b-4ad0-8a58-220d821fbd84 spec: sourcePod: network-check-source-7bc5b6bf85-tkb76 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-18T01:05:02Z" message: 'network-check-target-ip-10-0-133-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.354592ms message: 'network-check-target-ip-10-0-133-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:26:02Z" - latency: 2.25943ms message: 'network-check-target-ip-10-0-133-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:25:02Z" - latency: 2.557938ms message: 'network-check-target-ip-10-0-133-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:24:02Z" - latency: 2.253387ms message: 'network-check-target-ip-10-0-133-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:23:02Z" - latency: 2.249456ms message: 'network-check-target-ip-10-0-133-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:22:02Z" - latency: 2.050379ms message: 'network-check-target-ip-10-0-133-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:21:02Z" - latency: 2.280293ms message: 'network-check-target-ip-10-0-133-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:20:02Z" - latency: 2.742657ms message: 'network-check-target-ip-10-0-133-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:19:02Z" - latency: 2.548846ms message: 'network-check-target-ip-10-0-133-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:18:02Z" - latency: 2.191629ms message: 'network-check-target-ip-10-0-133-101: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:17:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T00:58:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-32-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-32.ec2.internal uid: 41238b11-2412-4299-bc40-1e4afd2f6373 resourceVersion: "42153" uid: 5f820655-795f-427a-9b0f-edbb0c844cfc spec: sourcePod: network-check-source-7bc5b6bf85-tkb76 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-18T01:04:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 870.309µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:22:02Z" - latency: 2.747546ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T01:22:02Z" - latency: 1.016385ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:21:02Z" - latency: 1.980144ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T01:21:02Z" - latency: 1.273553ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:20:02Z" - latency: 1.866088ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T01:20:02Z" - latency: 1.287191ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:19:02Z" - latency: 1.926965ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T01:19:02Z" - latency: 1.226709ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T01:18:02Z" - latency: 2.384482ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T01:18:02Z" kind: List metadata: resourceVersion: ""