apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T17:37:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-221-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-221.ec2.internal uid: 0c69b15c-7a72-4c57-9f27-5e0dea615d1c resourceVersion: "19753" uid: c72334bf-85f3-4b25-bc1c-b989a1e4a66b spec: sourcePod: network-check-source-56d84b9f44-2qbp4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-29T17:44:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 815.449µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:58:02Z" - latency: 881.235µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:57:02Z" - latency: 848.866µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:56:02Z" - latency: 805.919µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:55:02Z" - latency: 1.129659ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:54:02Z" - latency: 892.83µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:53:02Z" - latency: 733.832µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:52:02Z" - latency: 1.564154ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:51:02Z" - latency: 1.302942ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:50:02Z" - latency: 890.39µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:49:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T17:37:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-221-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-221.ec2.internal uid: 0c69b15c-7a72-4c57-9f27-5e0dea615d1c resourceVersion: "20895" uid: 6372d17d-c22a-45e4-9e3c-7ca4863e06a3 spec: sourcePod: network-check-source-56d84b9f44-2qbp4 targetEndpoint: a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T17:43:02Z" message: 'load-balancer-api-external: tcp connection to a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.642957ms message: 'load-balancer-api-external: tcp connection to a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:01:02Z" - latency: 8.549308ms message: 'load-balancer-api-external: resolved host name a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T18:01:02Z" - latency: 5.897822ms message: 'load-balancer-api-external: tcp connection to a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:00:02Z" - latency: 7.93619ms message: 'load-balancer-api-external: resolved host name a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T18:00:02Z" - latency: 4.039987ms message: 'load-balancer-api-external: tcp connection to a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:59:02Z" - latency: 8.000607ms message: 'load-balancer-api-external: resolved host name a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T17:59:02Z" - latency: 4.367157ms message: 'load-balancer-api-external: tcp connection to a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:58:02Z" - latency: 7.496863ms message: 'load-balancer-api-external: resolved host name a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T17:58:02Z" - latency: 4.716166ms message: 'load-balancer-api-external: tcp connection to a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:57:02Z" - latency: 7.603426ms message: 'load-balancer-api-external: resolved host name a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T17:57:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T17:37:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-221-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-221.ec2.internal uid: 0c69b15c-7a72-4c57-9f27-5e0dea615d1c resourceVersion: "20896" uid: de053142-423e-4e05-a4e6-676714606e4a spec: sourcePod: network-check-source-56d84b9f44-2qbp4 targetEndpoint: a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T17:43:02Z" message: 'load-balancer-api-internal: tcp connection to a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.581857ms message: 'load-balancer-api-internal: tcp connection to a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:01:02Z" - latency: 8.635459ms message: 'load-balancer-api-internal: resolved host name a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T18:01:02Z" - latency: 3.653336ms message: 'load-balancer-api-internal: tcp connection to a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:00:02Z" - latency: 7.829429ms message: 'load-balancer-api-internal: resolved host name a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T18:00:02Z" - latency: 3.812057ms message: 'load-balancer-api-internal: tcp connection to a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:59:02Z" - latency: 7.955532ms message: 'load-balancer-api-internal: resolved host name a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T17:59:02Z" - latency: 4.159989ms message: 'load-balancer-api-internal: tcp connection to a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:58:02Z" - latency: 7.364868ms message: 'load-balancer-api-internal: resolved host name a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T17:58:02Z" - latency: 3.933103ms message: 'load-balancer-api-internal: tcp connection to a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:57:02Z" - latency: 7.553584ms message: 'load-balancer-api-internal: resolved host name a72a9d55474f4442ca72807284316f02-44df2974ad707608.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T17:57:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T17:37:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-221-to-network-check-target-ip-10-0-128-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-221.ec2.internal uid: 0c69b15c-7a72-4c57-9f27-5e0dea615d1c resourceVersion: "19750" uid: 1b831a4e-2464-4959-a19e-9edfb76724e8 spec: sourcePod: network-check-source-56d84b9f44-2qbp4 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-29T17:44:02Z" message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 850.475µs message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:58:02Z" - latency: 854.974µs message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:57:02Z" - latency: 874.982µs message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:56:02Z" - latency: 1.025664ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:55:02Z" - latency: 709.344µs message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:54:02Z" - latency: 787.061µs message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:53:02Z" - latency: 990.542µs message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:52:02Z" - latency: 1.791657ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:51:02Z" - latency: 1.343462ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:50:02Z" - latency: 1.12142ms message: 'network-check-target-ip-10-0-128-221: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:49:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T17:37:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-221-to-network-check-target-ip-10-0-137-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-221.ec2.internal uid: 0c69b15c-7a72-4c57-9f27-5e0dea615d1c resourceVersion: "19751" uid: e3ec73d6-235f-4aaa-b4ce-2dc464a60c16 spec: sourcePod: network-check-source-56d84b9f44-2qbp4 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-29T17:44:02Z" message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.001758ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:58:02Z" - latency: 1.928767ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:57:02Z" - latency: 1.978084ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:56:02Z" - latency: 1.629831ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:55:02Z" - latency: 2.275624ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:54:02Z" - latency: 2.39248ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:53:02Z" - latency: 2.132805ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:52:02Z" - latency: 2.219221ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:51:02Z" - latency: 2.634074ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:50:02Z" - latency: 2.053946ms message: 'network-check-target-ip-10-0-137-123: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:49:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T17:37:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-221-to-network-check-target-ip-10-0-138-69 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-221.ec2.internal uid: 0c69b15c-7a72-4c57-9f27-5e0dea615d1c resourceVersion: "19752" uid: 720e6e78-0753-45be-8227-7360acf21b1e spec: sourcePod: network-check-source-56d84b9f44-2qbp4 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-29T17:44:02Z" message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.59208ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:58:02Z" - latency: 1.606485ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:57:02Z" - latency: 1.793728ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:56:02Z" - latency: 1.813ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:55:02Z" - latency: 1.653206ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:54:02Z" - latency: 1.878475ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:53:02Z" - latency: 2.124009ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:52:02Z" - latency: 2.102576ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:51:02Z" - latency: 1.852456ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:50:02Z" - latency: 1.733675ms message: 'network-check-target-ip-10-0-138-69: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:49:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T17:37:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-221-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-221.ec2.internal uid: 0c69b15c-7a72-4c57-9f27-5e0dea615d1c resourceVersion: "20894" uid: 6c225aaf-06d8-4e73-9d93-c7ebaa838833 spec: sourcePod: network-check-source-56d84b9f44-2qbp4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-29T17:43:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 875.232µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:01:02Z" - latency: 1.983584ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T18:01:02Z" - latency: 841.85µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T18:00:02Z" - latency: 2.427904ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T18:00:02Z" - latency: 839.286µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:59:02Z" - latency: 1.801246ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T17:59:02Z" - latency: 675.608µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:58:02Z" - latency: 1.64009ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T17:58:02Z" - latency: 907.795µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T17:57:02Z" - latency: 1.812517ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T17:57:02Z" kind: List metadata: resourceVersion: ""