apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:12:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-101-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-101.ec2.internal uid: fbc11870-d862-497c-ae14-3c6fdc462255 resourceVersion: "54409" uid: 8449d9c4-9f53-44b3-bb86-f1006a620a4d spec: sourcePod: network-check-source-989f8b8dc-7hbvp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T22:19:09Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 883.404µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:47:09Z" - latency: 1.198487ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:46:09Z" - latency: 1.378263ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:45:09Z" - latency: 986.404µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:44:09Z" - latency: 1.039337ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:43:09Z" - latency: 1.198474ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:42:09Z" - latency: 1.103631ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:41:09Z" - latency: 867.098µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:40:09Z" - latency: 841.982µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:39:09Z" - latency: 915.04µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:38:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:12:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-101-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-101.ec2.internal uid: fbc11870-d862-497c-ae14-3c6fdc462255 resourceVersion: "55444" uid: 60779941-9461-45cf-aa88-3c44e930fb1d spec: sourcePod: network-check-source-989f8b8dc-7hbvp targetEndpoint: a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T22:18:09Z" message: 'load-balancer-api-external: tcp connection to a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.33806ms message: 'load-balancer-api-external: tcp connection to a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:48:09Z" - latency: 6.218683ms message: 'load-balancer-api-external: resolved host name a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:48:09Z" - latency: 3.591784ms message: 'load-balancer-api-external: tcp connection to a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:47:09Z" - latency: 6.247972ms message: 'load-balancer-api-external: resolved host name a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:47:09Z" - latency: 3.81924ms message: 'load-balancer-api-external: tcp connection to a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:46:09Z" - latency: 8.906525ms message: 'load-balancer-api-external: resolved host name a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:46:09Z" - latency: 3.787909ms message: 'load-balancer-api-external: tcp connection to a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:45:09Z" - latency: 6.690503ms message: 'load-balancer-api-external: resolved host name a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:45:09Z" - latency: 3.931868ms message: 'load-balancer-api-external: tcp connection to a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:44:09Z" - latency: 12.190981ms message: 'load-balancer-api-external: resolved host name a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:44:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:12:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-101-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-101.ec2.internal uid: fbc11870-d862-497c-ae14-3c6fdc462255 resourceVersion: "55443" uid: 966a8496-b722-4c13-96e4-72b5bb2b7c5c spec: sourcePod: network-check-source-989f8b8dc-7hbvp targetEndpoint: a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T22:18:09Z" message: 'load-balancer-api-internal: tcp connection to a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.295744ms message: 'load-balancer-api-internal: tcp connection to a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:48:09Z" - latency: 6.17966ms message: 'load-balancer-api-internal: resolved host name a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:48:09Z" - latency: 3.567174ms message: 'load-balancer-api-internal: tcp connection to a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:47:09Z" - latency: 6.221339ms message: 'load-balancer-api-internal: resolved host name a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:47:09Z" - latency: 4.254316ms message: 'load-balancer-api-internal: tcp connection to a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:46:09Z" - latency: 8.996013ms message: 'load-balancer-api-internal: resolved host name a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:46:09Z" - latency: 3.630978ms message: 'load-balancer-api-internal: tcp connection to a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:45:09Z" - latency: 6.662734ms message: 'load-balancer-api-internal: resolved host name a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:45:09Z" - latency: 6.844504ms message: 'load-balancer-api-internal: tcp connection to a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:44:09Z" - latency: 12.269374ms message: 'load-balancer-api-internal: resolved host name a03b7a58be3f6403d8a21e64efe487bb-18f3e2852357330f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:44:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:12:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-101-to-network-check-target-ip-10-0-128-71 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-101.ec2.internal uid: fbc11870-d862-497c-ae14-3c6fdc462255 resourceVersion: "54407" uid: f8947562-6c7c-4ec4-9590-a9bea18304ab spec: sourcePod: network-check-source-989f8b8dc-7hbvp targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T22:19:09Z" message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.433167ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:47:09Z" - latency: 2.387521ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:46:09Z" - latency: 2.243423ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:45:09Z" - latency: 2.122294ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:44:09Z" - latency: 2.33255ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:43:09Z" - latency: 2.371184ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:42:09Z" - latency: 2.48347ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:41:09Z" - latency: 2.395883ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:40:09Z" - latency: 2.684817ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:39:09Z" - latency: 2.202652ms message: 'network-check-target-ip-10-0-128-71: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:38:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:12:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-101-to-network-check-target-ip-10-0-137-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-101.ec2.internal uid: fbc11870-d862-497c-ae14-3c6fdc462255 resourceVersion: "54406" uid: 13e70c16-4026-4ce8-ad64-6e2cdd0df3db spec: sourcePod: network-check-source-989f8b8dc-7hbvp targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T22:19:09Z" message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.539028ms message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:47:09Z" - latency: 1.021497ms message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:46:09Z" - latency: 1.281842ms message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:45:09Z" - latency: 857.22µs message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:44:09Z" - latency: 983.996µs message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:43:09Z" - latency: 941.548µs message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:42:09Z" - latency: 956.575µs message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:41:09Z" - latency: 1.170349ms message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:40:09Z" - latency: 1.073742ms message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:39:09Z" - latency: 875.92µs message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:38:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:12:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-101-to-network-check-target-ip-10-0-137-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-101.ec2.internal uid: fbc11870-d862-497c-ae14-3c6fdc462255 resourceVersion: "54408" uid: 60f98feb-aa4f-4830-ba4d-3fdc9fc6a2d9 spec: sourcePod: network-check-source-989f8b8dc-7hbvp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T22:19:09Z" message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.066694ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:47:09Z" - latency: 2.220947ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:46:09Z" - latency: 1.900386ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:45:09Z" - latency: 2.29331ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:44:09Z" - latency: 2.259045ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:43:09Z" - latency: 2.265897ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:42:09Z" - latency: 2.049845ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:41:09Z" - latency: 2.006735ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:40:09Z" - latency: 2.120602ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:39:09Z" - latency: 2.016332ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:38:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:12:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-101-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-101.ec2.internal uid: fbc11870-d862-497c-ae14-3c6fdc462255 resourceVersion: "55442" uid: 6b2d2c7d-ef01-4018-a0b4-20f8cc428beb spec: sourcePod: network-check-source-989f8b8dc-7hbvp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T22:18:09Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.141998ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:48:09Z" - latency: 1.70775ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T22:48:09Z" - latency: 1.583156ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:47:09Z" - latency: 1.809076ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T22:47:09Z" - latency: 916.624µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:46:09Z" - latency: 1.822761ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T22:46:09Z" - latency: 851.023µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:45:09Z" - latency: 1.94173ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T22:45:09Z" - latency: 902.335µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:44:09Z" - latency: 1.643776ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T22:44:09Z" kind: List metadata: resourceVersion: ""