apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:38:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-213-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-213.ec2.internal uid: f98a7cfd-f027-49e7-8dff-85af71c4cf52 resourceVersion: "22171" uid: 9dbadda8-e8b1-4f31-bbe7-6fb7efd38ca4 spec: sourcePod: network-check-source-989f8b8dc-2rwms targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T09:45:12Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.031823ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:59:12Z" - latency: 955.123µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:58:12Z" - latency: 1.015163ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:57:12Z" - latency: 996.53µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:56:12Z" - latency: 1.022193ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:55:12Z" - latency: 886.564µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:54:12Z" - latency: 1.073111ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:53:12Z" - latency: 1.056069ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:52:12Z" - latency: 1.282878ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:51:12Z" - latency: 1.118448ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:50:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:38:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-213-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-213.ec2.internal uid: f98a7cfd-f027-49e7-8dff-85af71c4cf52 resourceVersion: "20671" uid: d6f7fa65-c7fc-49b8-a83d-9c096634e193 spec: sourcePod: network-check-source-989f8b8dc-2rwms targetEndpoint: a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T09:44:12Z" message: 'load-balancer-api-external: tcp connection to a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.910646ms message: 'load-balancer-api-external: tcp connection to a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:56:12Z" - latency: 8.479553ms message: 'load-balancer-api-external: resolved host name a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T09:56:12Z" - latency: 4.934316ms message: 'load-balancer-api-external: tcp connection to a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:55:12Z" - latency: 8.28487ms message: 'load-balancer-api-external: resolved host name a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T09:55:12Z" - latency: 5.074511ms message: 'load-balancer-api-external: tcp connection to a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:54:12Z" - latency: 8.263325ms message: 'load-balancer-api-external: resolved host name a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T09:54:12Z" - latency: 5.324467ms message: 'load-balancer-api-external: tcp connection to a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:53:12Z" - latency: 8.359281ms message: 'load-balancer-api-external: resolved host name a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T09:53:12Z" - latency: 5.136709ms message: 'load-balancer-api-external: tcp connection to a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:52:12Z" - latency: 11.736691ms message: 'load-balancer-api-external: resolved host name a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T09:52:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:38:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-213-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-213.ec2.internal uid: f98a7cfd-f027-49e7-8dff-85af71c4cf52 resourceVersion: "20670" uid: e49559de-ef7e-404a-8963-7a1005236a87 spec: sourcePod: network-check-source-989f8b8dc-2rwms targetEndpoint: a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T09:44:12Z" message: 'load-balancer-api-internal: tcp connection to a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.961196ms message: 'load-balancer-api-internal: tcp connection to a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:56:12Z" - latency: 8.539813ms message: 'load-balancer-api-internal: resolved host name a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T09:56:12Z" - latency: 4.879457ms message: 'load-balancer-api-internal: tcp connection to a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:55:12Z" - latency: 8.339064ms message: 'load-balancer-api-internal: resolved host name a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T09:55:12Z" - latency: 5.036988ms message: 'load-balancer-api-internal: tcp connection to a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:54:12Z" - latency: 8.229481ms message: 'load-balancer-api-internal: resolved host name a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T09:54:12Z" - latency: 5.275737ms message: 'load-balancer-api-internal: tcp connection to a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:53:12Z" - latency: 8.397593ms message: 'load-balancer-api-internal: resolved host name a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T09:53:12Z" - latency: 5.142353ms message: 'load-balancer-api-internal: tcp connection to a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:52:12Z" - latency: 11.624034ms message: 'load-balancer-api-internal: resolved host name a48ca241910cf4ef88cf31aa675a4a24-9ca4e8ad02106c60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T09:52:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:38:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-213-to-network-check-target-ip-10-0-134-170 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-213.ec2.internal uid: f98a7cfd-f027-49e7-8dff-85af71c4cf52 resourceVersion: "22170" uid: c7a157aa-fc35-4faa-b038-e33c24b3ad85 spec: sourcePod: network-check-source-989f8b8dc-2rwms targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T09:45:12Z" message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.193336ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:59:12Z" - latency: 1.982718ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:58:12Z" - latency: 2.129621ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:57:12Z" - latency: 1.973837ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:56:12Z" - latency: 2.267162ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:55:12Z" - latency: 2.123172ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:54:12Z" - latency: 2.154012ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:53:12Z" - latency: 2.100957ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:52:12Z" - latency: 2.306901ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:51:12Z" - latency: 1.944302ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:50:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:38:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-213-to-network-check-target-ip-10-0-135-213 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-213.ec2.internal uid: f98a7cfd-f027-49e7-8dff-85af71c4cf52 resourceVersion: "22168" uid: 054a2c43-6001-402b-bdd9-5ca91f30f20b spec: sourcePod: network-check-source-989f8b8dc-2rwms targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T09:45:12Z" message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 874.444µs message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:59:12Z" - latency: 1.433142ms message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:58:12Z" - latency: 945.54µs message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:57:12Z" - latency: 991.718µs message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:56:12Z" - latency: 843.81µs message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:55:12Z" - latency: 971.204µs message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:54:12Z" - latency: 805.311µs message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:53:12Z" - latency: 1.060788ms message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:52:12Z" - latency: 1.602648ms message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:51:12Z" - latency: 862.13µs message: 'network-check-target-ip-10-0-135-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:50:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:38:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-213-to-network-check-target-ip-10-0-137-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-213.ec2.internal uid: f98a7cfd-f027-49e7-8dff-85af71c4cf52 resourceVersion: "22169" uid: 1d74f65b-7724-42db-b9cf-823be416d909 spec: sourcePod: network-check-source-989f8b8dc-2rwms targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T09:45:12Z" message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.942984ms message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:59:12Z" - latency: 1.630709ms message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:58:12Z" - latency: 1.706722ms message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:57:12Z" - latency: 1.892824ms message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:56:12Z" - latency: 1.836603ms message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:55:12Z" - latency: 1.920737ms message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:54:12Z" - latency: 2.099504ms message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:53:12Z" - latency: 1.926942ms message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:52:12Z" - latency: 2.098113ms message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:51:12Z" - latency: 1.863483ms message: 'network-check-target-ip-10-0-137-199: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:50:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T09:38:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-213-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-213.ec2.internal uid: f98a7cfd-f027-49e7-8dff-85af71c4cf52 resourceVersion: "20669" uid: 2f6fb51a-003f-4e0a-a151-d2909f5a62d9 spec: sourcePod: network-check-source-989f8b8dc-2rwms targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T09:44:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.083306ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:56:12Z" - latency: 1.779687ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T09:56:12Z" - latency: 1.011834ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:55:12Z" - latency: 1.73172ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T09:55:12Z" - latency: 913.72µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:54:12Z" - latency: 1.948211ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T09:54:12Z" - latency: 853.812µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:53:12Z" - latency: 1.726898ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T09:53:12Z" - latency: 907.492µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T09:52:12Z" - latency: 1.931024ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T09:52:12Z" kind: List metadata: resourceVersion: ""