apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:13:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-222-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-222.ec2.internal uid: 7a91abb6-5062-4b8d-b174-3eda2054194a resourceVersion: "74852" uid: 7f5bf0a5-6aa7-44de-9dcd-03fd0bcefdb3 spec: sourcePod: network-check-source-65bdbbff45-xkj75 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T18:20:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.159015ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:09:37Z" - latency: 1.23339ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:08:37Z" - latency: 1.033773ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:07:37Z" - latency: 1.357713ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:06:37Z" - latency: 1.029469ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:05:37Z" - latency: 1.396245ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:04:37Z" - latency: 1.01611ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:03:37Z" - latency: 1.218141ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:02:37Z" - latency: 1.188753ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:01:37Z" - latency: 965.845µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:00:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:13:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-222-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-222.ec2.internal uid: 7a91abb6-5062-4b8d-b174-3eda2054194a resourceVersion: "70943" uid: e27b4ff9-fc07-4d07-80ad-49bebe1e051d spec: sourcePod: network-check-source-65bdbbff45-xkj75 targetEndpoint: aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T18:19:37Z" message: 'load-balancer-api-external: tcp connection to aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.118729ms message: 'load-balancer-api-external: tcp connection to aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:07:37Z" - latency: 7.499731ms message: 'load-balancer-api-external: resolved host name aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:07:37Z" - latency: 6.617296ms message: 'load-balancer-api-external: tcp connection to aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:06:37Z" - latency: 8.830238ms message: 'load-balancer-api-external: resolved host name aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:06:37Z" - latency: 3.894615ms message: 'load-balancer-api-external: tcp connection to aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:05:37Z" - latency: 11.669613ms message: 'load-balancer-api-external: resolved host name aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:05:37Z" - latency: 5.837956ms message: 'load-balancer-api-external: tcp connection to aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:04:37Z" - latency: 9.188706ms message: 'load-balancer-api-external: resolved host name aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:04:37Z" - latency: 6.372312ms message: 'load-balancer-api-external: tcp connection to aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:03:37Z" - latency: 8.318408ms message: 'load-balancer-api-external: resolved host name aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:03:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:13:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-222-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-222.ec2.internal uid: 7a91abb6-5062-4b8d-b174-3eda2054194a resourceVersion: "70944" uid: 3bc315c4-f951-41e3-8e50-e09df9de6bbc spec: sourcePod: network-check-source-65bdbbff45-xkj75 targetEndpoint: aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T18:19:37Z" message: 'load-balancer-api-internal: tcp connection to aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.993363ms message: 'load-balancer-api-internal: tcp connection to aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:07:37Z" - latency: 7.590147ms message: 'load-balancer-api-internal: resolved host name aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:07:37Z" - latency: 6.650677ms message: 'load-balancer-api-internal: tcp connection to aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:06:37Z" - latency: 8.696959ms message: 'load-balancer-api-internal: resolved host name aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:06:37Z" - latency: 4.213608ms message: 'load-balancer-api-internal: tcp connection to aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:05:37Z" - latency: 11.751925ms message: 'load-balancer-api-internal: resolved host name aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:05:37Z" - latency: 3.672654ms message: 'load-balancer-api-internal: tcp connection to aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:04:37Z" - latency: 9.247187ms message: 'load-balancer-api-internal: resolved host name aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:04:37Z" - latency: 3.857677ms message: 'load-balancer-api-internal: tcp connection to aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:03:37Z" - latency: 8.365195ms message: 'load-balancer-api-internal: resolved host name aeb9e022d670540fdaf7590f6abafc97-f9f04794ff9f3669.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T19:03:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:13:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-222-to-network-check-target-ip-10-0-136-165 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-222.ec2.internal uid: 7a91abb6-5062-4b8d-b174-3eda2054194a resourceVersion: "74851" uid: 83e0d200-0880-4f8c-9e3d-0910cd2e993b spec: sourcePod: network-check-source-65bdbbff45-xkj75 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:20:37Z" message: 'network-check-target-ip-10-0-136-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.406581ms message: 'network-check-target-ip-10-0-136-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:09:37Z" - latency: 2.27967ms message: 'network-check-target-ip-10-0-136-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:08:37Z" - latency: 2.436285ms message: 'network-check-target-ip-10-0-136-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:07:37Z" - latency: 2.525741ms message: 'network-check-target-ip-10-0-136-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:06:37Z" - latency: 2.486524ms message: 'network-check-target-ip-10-0-136-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:05:37Z" - latency: 3.29101ms message: 'network-check-target-ip-10-0-136-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:04:37Z" - latency: 2.134142ms message: 'network-check-target-ip-10-0-136-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:03:37Z" - latency: 2.368055ms message: 'network-check-target-ip-10-0-136-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:02:37Z" - latency: 2.324299ms message: 'network-check-target-ip-10-0-136-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:01:37Z" - latency: 2.01699ms message: 'network-check-target-ip-10-0-136-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:00:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:13:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-222-to-network-check-target-ip-10-0-137-226 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-222.ec2.internal uid: 7a91abb6-5062-4b8d-b174-3eda2054194a resourceVersion: "74850" uid: 6b65cdfe-ce4c-4b25-bfba-4c2a2b8ca762 spec: sourcePod: network-check-source-65bdbbff45-xkj75 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:20:37Z" message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.335126ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:09:37Z" - latency: 2.534404ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:08:37Z" - latency: 2.193911ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:07:37Z" - latency: 2.51927ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:06:37Z" - latency: 2.267146ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:05:37Z" - latency: 2.467243ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:04:37Z" - latency: 2.264234ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:03:37Z" - latency: 2.838044ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:02:37Z" - latency: 2.350628ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:01:37Z" - latency: 2.791612ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:00:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:13:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-222-to-network-check-target-ip-10-0-142-222 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-222.ec2.internal uid: 7a91abb6-5062-4b8d-b174-3eda2054194a resourceVersion: "74848" uid: f8a03047-e62a-4a4a-ae8d-6ec0d7454f7a spec: sourcePod: network-check-source-65bdbbff45-xkj75 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-04T18:20:37Z" message: 'network-check-target-ip-10-0-142-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.095751ms message: 'network-check-target-ip-10-0-142-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:09:37Z" - latency: 975.914µs message: 'network-check-target-ip-10-0-142-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:08:37Z" - latency: 1.534345ms message: 'network-check-target-ip-10-0-142-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:07:37Z" - latency: 1.347089ms message: 'network-check-target-ip-10-0-142-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:06:37Z" - latency: 1.136007ms message: 'network-check-target-ip-10-0-142-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:05:37Z" - latency: 1.543323ms message: 'network-check-target-ip-10-0-142-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:04:37Z" - latency: 1.330228ms message: 'network-check-target-ip-10-0-142-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:03:37Z" - latency: 1.460869ms message: 'network-check-target-ip-10-0-142-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:02:37Z" - latency: 1.307455ms message: 'network-check-target-ip-10-0-142-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:01:37Z" - latency: 964.555µs message: 'network-check-target-ip-10-0-142-222: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:00:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T18:13:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-222-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-222.ec2.internal uid: 7a91abb6-5062-4b8d-b174-3eda2054194a resourceVersion: "70942" uid: f9785f1b-934e-4239-a082-07a450866652 spec: sourcePod: network-check-source-65bdbbff45-xkj75 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T18:19:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 945.274µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:07:37Z" - latency: 1.812099ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T19:07:37Z" - latency: 932.271µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:06:37Z" - latency: 1.863863ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T19:06:37Z" - latency: 1.041328ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:05:37Z" - latency: 2.039909ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T19:05:37Z" - latency: 1.074407ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:04:37Z" - latency: 2.178571ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T19:04:37Z" - latency: 1.126012ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T19:03:37Z" - latency: 2.001332ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T19:03:37Z" kind: List metadata: resourceVersion: ""