apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T19:35:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-26-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-26.ec2.internal uid: 85ac600a-ed1c-414b-a7b8-5fdcdabf4d0b resourceVersion: "33843" uid: b8d1ac5e-69cc-46dc-9de1-93658fb4ecff spec: sourcePod: network-check-source-dbd9cf844-mghx7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T19:42:34Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.044124ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:56:34Z" - latency: 924.364µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:55:34Z" - latency: 1.335796ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:54:34Z" - latency: 1.897836ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:53:34Z" - latency: 960.997µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:52:34Z" - latency: 1.066028ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:51:34Z" - latency: 1.141733ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:50:34Z" - latency: 1.079063ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:49:34Z" - latency: 1.061917ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:48:34Z" - latency: 1.639761ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:47:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T19:35:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-26-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-26.ec2.internal uid: 85ac600a-ed1c-414b-a7b8-5fdcdabf4d0b resourceVersion: "36747" uid: d4c43ce7-f3ac-46f5-8d6b-fbc3174549ef spec: sourcePod: network-check-source-dbd9cf844-mghx7 targetEndpoint: abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T19:41:34Z" message: 'load-balancer-api-external: tcp connection to abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.654573ms message: 'load-balancer-api-external: tcp connection to abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:59:34Z" - latency: 6.408148ms message: 'load-balancer-api-external: resolved host name abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T19:59:34Z" - latency: 5.430855ms message: 'load-balancer-api-external: tcp connection to abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:58:34Z" - latency: 6.686212ms message: 'load-balancer-api-external: resolved host name abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T19:58:34Z" - latency: 4.545309ms message: 'load-balancer-api-external: tcp connection to abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:57:34Z" - latency: 5.580079ms message: 'load-balancer-api-external: resolved host name abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T19:57:34Z" - latency: 5.741445ms message: 'load-balancer-api-external: tcp connection to abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:56:34Z" - latency: 7.20436ms message: 'load-balancer-api-external: resolved host name abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T19:56:34Z" - latency: 2.972591ms message: 'load-balancer-api-external: tcp connection to abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:55:34Z" - latency: 6.542201ms message: 'load-balancer-api-external: resolved host name abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T19:55:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T19:35:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-26-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-26.ec2.internal uid: 85ac600a-ed1c-414b-a7b8-5fdcdabf4d0b resourceVersion: "36746" uid: 7bb13727-25b0-4794-9b83-6b8eba8722f3 spec: sourcePod: network-check-source-dbd9cf844-mghx7 targetEndpoint: abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T19:41:34Z" message: 'load-balancer-api-internal: tcp connection to abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.631999ms message: 'load-balancer-api-internal: tcp connection to abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:59:34Z" - latency: 6.459264ms message: 'load-balancer-api-internal: resolved host name abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T19:59:34Z" - latency: 5.157408ms message: 'load-balancer-api-internal: tcp connection to abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:58:34Z" - latency: 6.737563ms message: 'load-balancer-api-internal: resolved host name abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T19:58:34Z" - latency: 6.114614ms message: 'load-balancer-api-internal: tcp connection to abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:57:34Z" - latency: 5.652098ms message: 'load-balancer-api-internal: resolved host name abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T19:57:34Z" - latency: 5.247691ms message: 'load-balancer-api-internal: tcp connection to abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:56:34Z" - latency: 7.270387ms message: 'load-balancer-api-internal: resolved host name abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T19:56:34Z" - latency: 5.243943ms message: 'load-balancer-api-internal: tcp connection to abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:55:34Z" - latency: 6.627467ms message: 'load-balancer-api-internal: resolved host name abfe9afec60754e3ab0898308fb1db36-da8118ca7a1dece0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T19:55:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T19:35:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-26-to-network-check-target-ip-10-0-132-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-26.ec2.internal uid: 85ac600a-ed1c-414b-a7b8-5fdcdabf4d0b resourceVersion: "33841" uid: 8cfd95df-818c-4c78-ab2e-f1ca37f94b1c spec: sourcePod: network-check-source-dbd9cf844-mghx7 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-08T19:42:34Z" message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.471735ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:56:34Z" - latency: 1.010637ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:55:34Z" - latency: 1.272041ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:54:34Z" - latency: 1.137039ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:53:34Z" - latency: 1.670615ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:52:34Z" - latency: 1.349171ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:51:34Z" - latency: 983.895µs message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:50:34Z" - latency: 1.204549ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:49:34Z" - latency: 1.019767ms message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:48:34Z" - latency: 929.347µs message: 'network-check-target-ip-10-0-132-26: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:47:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T19:35:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-26-to-network-check-target-ip-10-0-136-208 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-26.ec2.internal uid: 85ac600a-ed1c-414b-a7b8-5fdcdabf4d0b resourceVersion: "33842" uid: 6a522b03-5802-4a2f-b581-551bc83dba03 spec: sourcePod: network-check-source-dbd9cf844-mghx7 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T19:42:34Z" message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.279914ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:56:34Z" - latency: 2.184881ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:55:34Z" - latency: 2.01773ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:54:34Z" - latency: 2.188351ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:53:34Z" - latency: 1.957277ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:52:34Z" - latency: 1.962401ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:51:34Z" - latency: 1.895371ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:50:34Z" - latency: 2.082356ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:49:34Z" - latency: 2.10637ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:48:34Z" - latency: 2.603326ms message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:47:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T19:35:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-26-to-network-check-target-ip-10-0-141-14 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-26.ec2.internal uid: 85ac600a-ed1c-414b-a7b8-5fdcdabf4d0b resourceVersion: "33840" uid: b7798ade-7350-42d5-8f1d-8aa8ad938d84 spec: sourcePod: network-check-source-dbd9cf844-mghx7 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-08T19:42:34Z" message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.646367ms message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:56:34Z" - latency: 1.769554ms message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:55:34Z" - latency: 2.014191ms message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:54:34Z" - latency: 2.029634ms message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:53:34Z" - latency: 1.573912ms message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:52:34Z" - latency: 2.064825ms message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:51:34Z" - latency: 2.056187ms message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:50:34Z" - latency: 1.99591ms message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:49:34Z" - latency: 2.123541ms message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:48:34Z" - latency: 2.39653ms message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:47:34Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T19:35:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-26-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-26.ec2.internal uid: 85ac600a-ed1c-414b-a7b8-5fdcdabf4d0b resourceVersion: "36744" uid: feb4c9f7-60a5-4597-9f94-5d80c1906eab spec: sourcePod: network-check-source-dbd9cf844-mghx7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T19:41:34Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 860.647µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:59:34Z" - latency: 1.781941ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T19:59:34Z" - latency: 892.972µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:58:34Z" - latency: 1.620031ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T19:58:34Z" - latency: 1.049064ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:57:34Z" - latency: 1.588432ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T19:57:34Z" - latency: 837.568µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:56:34Z" - latency: 1.523893ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T19:56:34Z" - latency: 765.929µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T19:55:34Z" - latency: 2.098741ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T19:55:34Z" kind: List metadata: resourceVersion: ""