apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:50:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-118-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-118.ec2.internal uid: 6f3c9f12-c2f3-40db-ba81-c9f068580ea2 resourceVersion: "73876" uid: af91f16e-43c1-4673-896c-560bdb1a3891 spec: sourcePod: network-check-source-7d88cb55d8-zb52t targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T15:57:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.170269ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:39:29Z" - latency: 1.36571ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:38:29Z" - latency: 1.084078ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:37:29Z" - latency: 734.908µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:36:29Z" - latency: 1.154576ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:35:29Z" - latency: 1.214164ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:34:29Z" - latency: 901.563µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:33:29Z" - latency: 749.381µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:32:29Z" - latency: 994.372µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:31:29Z" - latency: 1.145013ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:30:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:50:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-118-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-118.ec2.internal uid: 6f3c9f12-c2f3-40db-ba81-c9f068580ea2 resourceVersion: "71429" uid: b8dbb6f0-a07c-4094-9126-cd35e09c348c spec: sourcePod: network-check-source-7d88cb55d8-zb52t targetEndpoint: a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T15:56:29Z" message: 'load-balancer-api-external: tcp connection to a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.78722ms message: 'load-balancer-api-external: tcp connection to a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:38:29Z" - latency: 11.554324ms message: 'load-balancer-api-external: resolved host name a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:38:29Z" - latency: 4.150296ms message: 'load-balancer-api-external: tcp connection to a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:37:29Z" - latency: 11.799382ms message: 'load-balancer-api-external: resolved host name a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:37:29Z" - latency: 5.544398ms message: 'load-balancer-api-external: tcp connection to a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:36:29Z" - latency: 8.560434ms message: 'load-balancer-api-external: resolved host name a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:36:29Z" - latency: 5.689468ms message: 'load-balancer-api-external: tcp connection to a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:35:29Z" - latency: 6.376118ms message: 'load-balancer-api-external: resolved host name a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:35:29Z" - latency: 4.754513ms message: 'load-balancer-api-external: tcp connection to a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:34:29Z" - latency: 8.471879ms message: 'load-balancer-api-external: resolved host name a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:34:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:50:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-118-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-118.ec2.internal uid: 6f3c9f12-c2f3-40db-ba81-c9f068580ea2 resourceVersion: "71430" uid: 81c5f10c-91d3-4880-bf13-29ab6e8a8aa0 spec: sourcePod: network-check-source-7d88cb55d8-zb52t targetEndpoint: a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T15:56:29Z" message: 'load-balancer-api-internal: tcp connection to a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.420882ms message: 'load-balancer-api-internal: tcp connection to a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:38:29Z" - latency: 11.500818ms message: 'load-balancer-api-internal: resolved host name a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:38:29Z" - latency: 6.123503ms message: 'load-balancer-api-internal: tcp connection to a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:37:29Z" - latency: 11.718071ms message: 'load-balancer-api-internal: resolved host name a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:37:29Z" - latency: 5.152386ms message: 'load-balancer-api-internal: tcp connection to a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:36:29Z" - latency: 8.51215ms message: 'load-balancer-api-internal: resolved host name a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:36:29Z" - latency: 5.722883ms message: 'load-balancer-api-internal: tcp connection to a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:35:29Z" - latency: 6.338603ms message: 'load-balancer-api-internal: resolved host name a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:35:29Z" - latency: 4.003044ms message: 'load-balancer-api-internal: tcp connection to a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:34:29Z" - latency: 8.535313ms message: 'load-balancer-api-internal: resolved host name a6af6ef07b56244ce8fc28505f86d4ae-6d926bb661d34484.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T16:34:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:50:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-118-to-network-check-target-ip-10-0-133-118 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-118.ec2.internal uid: 6f3c9f12-c2f3-40db-ba81-c9f068580ea2 resourceVersion: "73872" uid: 9bc282e9-5c89-461f-b582-5b7caed88e2d spec: sourcePod: network-check-source-7d88cb55d8-zb52t targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T15:57:29Z" message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 941.728µs message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:39:29Z" - latency: 779.444µs message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:38:29Z" - latency: 1.323616ms message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:37:29Z" - latency: 873.96µs message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:36:29Z" - latency: 910.095µs message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:35:29Z" - latency: 934.776µs message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:34:29Z" - latency: 1.161842ms message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:33:29Z" - latency: 875.422µs message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:32:29Z" - latency: 1.045933ms message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:31:29Z" - latency: 1.358255ms message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:30:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:50:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-118-to-network-check-target-ip-10-0-136-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-118.ec2.internal uid: 6f3c9f12-c2f3-40db-ba81-c9f068580ea2 resourceVersion: "73875" uid: 56b72815-d78c-4c96-bded-9a6c64929c42 spec: sourcePod: network-check-source-7d88cb55d8-zb52t targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T15:57:29Z" message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.237197ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:39:29Z" - latency: 2.198717ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:38:29Z" - latency: 2.257217ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:37:29Z" - latency: 1.981093ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:36:29Z" - latency: 2.176163ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:35:29Z" - latency: 2.233584ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:34:29Z" - latency: 2.176512ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:33:29Z" - latency: 1.901375ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:32:29Z" - latency: 2.162557ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:31:29Z" - latency: 2.174084ms message: 'network-check-target-ip-10-0-136-199: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:30:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:50:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-118-to-network-check-target-ip-10-0-140-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-118.ec2.internal uid: 6f3c9f12-c2f3-40db-ba81-c9f068580ea2 resourceVersion: "73874" uid: 766ccf10-5aa0-4ce7-8aee-01156108a343 spec: sourcePod: network-check-source-7d88cb55d8-zb52t targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T15:57:29Z" message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.284156ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:39:29Z" - latency: 2.147551ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:38:29Z" - latency: 2.251642ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:37:29Z" - latency: 2.212271ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:36:29Z" - latency: 2.250702ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:35:29Z" - latency: 2.109001ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:34:29Z" - latency: 2.208069ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:33:29Z" - latency: 1.837584ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:32:29Z" - latency: 2.17711ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:31:29Z" - latency: 2.250724ms message: 'network-check-target-ip-10-0-140-155: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:30:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:50:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-118-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-118.ec2.internal uid: 6f3c9f12-c2f3-40db-ba81-c9f068580ea2 resourceVersion: "71427" uid: e6a31ed6-2966-415d-86ec-5b3df427ff7b spec: sourcePod: network-check-source-7d88cb55d8-zb52t targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T15:56:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.219038ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:38:29Z" - latency: 1.8014ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T16:38:29Z" - latency: 1.03331ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:37:29Z" - latency: 1.86913ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T16:37:29Z" - latency: 1.253488ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:36:29Z" - latency: 1.79056ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T16:36:29Z" - latency: 1.126845ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:35:29Z" - latency: 1.701941ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T16:35:29Z" - latency: 1.050221ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T16:34:29Z" - latency: 2.244169ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T16:34:29Z" kind: List metadata: resourceVersion: ""