apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:25:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-250-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-250.ec2.internal uid: 6d835f73-a33f-4300-ad93-a76ed5904e5e resourceVersion: "39884" uid: 2c1f13e4-a776-4405-b010-a1bf55e58cd8 spec: sourcePod: network-check-source-7f44b6dd87-wd2ff targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T18:32:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 895.688µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:53:08Z" - latency: 1.421849ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:52:08Z" - latency: 1.419595ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:51:08Z" - latency: 1.414048ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:50:08Z" - latency: 847.076µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:49:08Z" - latency: 1.372196ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:48:08Z" - latency: 819.527µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:47:08Z" - latency: 898.393µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:46:08Z" - latency: 1.011593ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:45:08Z" - latency: 878.235µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:44:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:25:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-250-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-250.ec2.internal uid: 6d835f73-a33f-4300-ad93-a76ed5904e5e resourceVersion: "42031" uid: 548807ce-6f8c-4a08-a1fc-fb39b590f13a spec: sourcePod: network-check-source-7f44b6dd87-wd2ff targetEndpoint: aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T18:31:08Z" message: 'load-balancer-api-external: tcp connection to aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.707761ms message: 'load-balancer-api-external: tcp connection to aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:55:08Z" - latency: 9.951834ms message: 'load-balancer-api-external: resolved host name aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:55:08Z" - latency: 6.915196ms message: 'load-balancer-api-external: tcp connection to aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:54:08Z" - latency: 6.726777ms message: 'load-balancer-api-external: resolved host name aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:54:08Z" - latency: 4.814419ms message: 'load-balancer-api-external: tcp connection to aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:53:08Z" - latency: 6.370639ms message: 'load-balancer-api-external: resolved host name aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:53:08Z" - latency: 4.287592ms message: 'load-balancer-api-external: tcp connection to aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:52:08Z" - latency: 7.482517ms message: 'load-balancer-api-external: resolved host name aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:52:08Z" - latency: 5.689442ms message: 'load-balancer-api-external: tcp connection to aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:51:08Z" - latency: 6.673515ms message: 'load-balancer-api-external: resolved host name aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:51:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:25:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-250-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-250.ec2.internal uid: 6d835f73-a33f-4300-ad93-a76ed5904e5e resourceVersion: "42032" uid: 62e0a52f-78a0-4fb0-a6f4-4c332014c30f spec: sourcePod: network-check-source-7f44b6dd87-wd2ff targetEndpoint: aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T18:31:08Z" message: 'load-balancer-api-internal: tcp connection to aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.204332ms message: 'load-balancer-api-internal: tcp connection to aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:55:08Z" - latency: 9.90122ms message: 'load-balancer-api-internal: resolved host name aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:55:08Z" - latency: 3.954418ms message: 'load-balancer-api-internal: tcp connection to aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:54:08Z" - latency: 6.690264ms message: 'load-balancer-api-internal: resolved host name aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:54:08Z" - latency: 4.779961ms message: 'load-balancer-api-internal: tcp connection to aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:53:08Z" - latency: 6.441641ms message: 'load-balancer-api-internal: resolved host name aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:53:08Z" - latency: 4.239276ms message: 'load-balancer-api-internal: tcp connection to aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:52:08Z" - latency: 7.50449ms message: 'load-balancer-api-internal: resolved host name aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:52:08Z" - latency: 4.952633ms message: 'load-balancer-api-internal: tcp connection to aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:51:08Z" - latency: 6.641ms message: 'load-balancer-api-internal: resolved host name aec37a7cae212485686764ca32c1ca73-d71d14f197e56f3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:51:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:25:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-250-to-network-check-target-ip-10-0-129-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-250.ec2.internal uid: 6d835f73-a33f-4300-ad93-a76ed5904e5e resourceVersion: "39883" uid: 544b35ab-41d3-4891-8af0-7ccad32b7205 spec: sourcePod: network-check-source-7f44b6dd87-wd2ff targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T18:32:08Z" message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.94924ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:53:08Z" - latency: 1.634067ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:52:08Z" - latency: 1.772733ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:51:08Z" - latency: 1.771494ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:50:08Z" - latency: 1.894512ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:49:08Z" - latency: 1.605563ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:48:08Z" - latency: 1.735273ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:47:08Z" - latency: 2.021531ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:46:08Z" - latency: 1.58692ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:45:08Z" - latency: 1.618369ms message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:44:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:25:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-250-to-network-check-target-ip-10-0-138-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-250.ec2.internal uid: 6d835f73-a33f-4300-ad93-a76ed5904e5e resourceVersion: "39881" uid: cd3ac992-024c-450d-ba3c-5bd4fce9f28e spec: sourcePod: network-check-source-7f44b6dd87-wd2ff targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T18:32:08Z" message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.0602ms message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:53:08Z" - latency: 1.397563ms message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:52:08Z" - latency: 1.239598ms message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:51:08Z" - latency: 928.762µs message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:50:08Z" - latency: 1.026382ms message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:49:08Z" - latency: 1.225757ms message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:48:08Z" - latency: 725.61µs message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:47:08Z" - latency: 1.221924ms message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:46:08Z" - latency: 1.065974ms message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:45:08Z" - latency: 921.039µs message: 'network-check-target-ip-10-0-138-250: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:44:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:25:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-250-to-network-check-target-ip-10-0-142-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-250.ec2.internal uid: 6d835f73-a33f-4300-ad93-a76ed5904e5e resourceVersion: "39882" uid: d3a949ee-e9aa-4f9f-b20e-bdd084e0f7b4 spec: sourcePod: network-check-source-7f44b6dd87-wd2ff targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T18:32:08Z" message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.025094ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:53:08Z" - latency: 1.95935ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:52:08Z" - latency: 2.194797ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:51:08Z" - latency: 1.984861ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:50:08Z" - latency: 1.924951ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:49:08Z" - latency: 2.114641ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:48:08Z" - latency: 2.433241ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:47:08Z" - latency: 2.351096ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:46:08Z" - latency: 2.134972ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:45:08Z" - latency: 2.22359ms message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:44:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:25:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-250-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-250.ec2.internal uid: 6d835f73-a33f-4300-ad93-a76ed5904e5e resourceVersion: "42030" uid: 8b0b5379-0c02-479e-8986-6854bf106de6 spec: sourcePod: network-check-source-7f44b6dd87-wd2ff targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T18:31:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 891.278µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:55:08Z" - latency: 1.531703ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:55:08Z" - latency: 770.107µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:54:08Z" - latency: 1.954111ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:54:08Z" - latency: 872.578µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:53:08Z" - latency: 1.93687ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:53:08Z" - latency: 818.339µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:52:08Z" - latency: 1.699907ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:52:08Z" - latency: 831.648µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:51:08Z" - latency: 1.938786ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:51:08Z" kind: List metadata: resourceVersion: ""