apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T15:12:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-141-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-141.ec2.internal uid: a20462f6-d5d4-415b-b74a-b2903e5cc5a6 resourceVersion: "43697" uid: 2f270873-cf17-4335-a9b3-662e70f639c7 spec: sourcePod: network-check-source-7f44b6dd87-rjwvn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T15:19:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.053611ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:40:07Z" - latency: 875.797µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:39:07Z" - latency: 927.346µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:38:07Z" - latency: 1.664134ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:37:07Z" - latency: 803.476µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:36:07Z" - latency: 1.035249ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:35:07Z" - latency: 1.028361ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:34:07Z" - latency: 806.437µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:33:07Z" - latency: 1.522171ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:32:07Z" - latency: 917.777µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:31:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T15:12:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-141-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-141.ec2.internal uid: a20462f6-d5d4-415b-b74a-b2903e5cc5a6 resourceVersion: "46187" uid: 2ca4739f-99bf-467f-921f-b3f7da2a6212 spec: sourcePod: network-check-source-7f44b6dd87-rjwvn targetEndpoint: a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T15:18:07Z" message: 'load-balancer-api-external: tcp connection to a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.636035ms message: 'load-balancer-api-external: tcp connection to a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:42:07Z" - latency: 6.590291ms message: 'load-balancer-api-external: resolved host name a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:42:07Z" - latency: 3.37852ms message: 'load-balancer-api-external: tcp connection to a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:41:07Z" - latency: 8.553914ms message: 'load-balancer-api-external: resolved host name a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:41:07Z" - latency: 5.822043ms message: 'load-balancer-api-external: tcp connection to a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:40:07Z" - latency: 8.281397ms message: 'load-balancer-api-external: resolved host name a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:40:07Z" - latency: 5.800769ms message: 'load-balancer-api-external: tcp connection to a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:39:07Z" - latency: 9.577496ms message: 'load-balancer-api-external: resolved host name a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:39:07Z" - latency: 4.625569ms message: 'load-balancer-api-external: tcp connection to a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:38:07Z" - latency: 8.191461ms message: 'load-balancer-api-external: resolved host name a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:38:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T15:12:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-141-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-141.ec2.internal uid: a20462f6-d5d4-415b-b74a-b2903e5cc5a6 resourceVersion: "46186" uid: 229f0994-f843-4c92-8a65-c30710aba833 spec: sourcePod: network-check-source-7f44b6dd87-rjwvn targetEndpoint: a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T15:18:07Z" message: 'load-balancer-api-internal: tcp connection to a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.635076ms message: 'load-balancer-api-internal: tcp connection to a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:42:07Z" - latency: 6.535055ms message: 'load-balancer-api-internal: resolved host name a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:42:07Z" - latency: 3.469784ms message: 'load-balancer-api-internal: tcp connection to a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:41:07Z" - latency: 8.518111ms message: 'load-balancer-api-internal: resolved host name a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:41:07Z" - latency: 5.840716ms message: 'load-balancer-api-internal: tcp connection to a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:40:07Z" - latency: 8.186551ms message: 'load-balancer-api-internal: resolved host name a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:40:07Z" - latency: 5.37632ms message: 'load-balancer-api-internal: tcp connection to a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:39:07Z" - latency: 9.501386ms message: 'load-balancer-api-internal: resolved host name a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:39:07Z" - latency: 4.613588ms message: 'load-balancer-api-internal: tcp connection to a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:38:07Z" - latency: 8.008614ms message: 'load-balancer-api-internal: resolved host name a8d37c88945444e299fad5bb84c7b5af-b9a6895647539898.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T15:38:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T15:12:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-141-to-network-check-target-ip-10-0-135-61 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-141.ec2.internal uid: a20462f6-d5d4-415b-b74a-b2903e5cc5a6 resourceVersion: "43695" uid: cf35d9da-b4ca-42ef-86f0-57632e67d792 spec: sourcePod: network-check-source-7f44b6dd87-rjwvn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T15:19:07Z" message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.986443ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:40:07Z" - latency: 2.111859ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:39:07Z" - latency: 1.752863ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:38:07Z" - latency: 2.089038ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:37:07Z" - latency: 1.9962ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:36:07Z" - latency: 1.961927ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:35:07Z" - latency: 2.308993ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:34:07Z" - latency: 2.170386ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:33:07Z" - latency: 1.919625ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:32:07Z" - latency: 2.267904ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:31:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T15:12:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-141-to-network-check-target-ip-10-0-137-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-141.ec2.internal uid: a20462f6-d5d4-415b-b74a-b2903e5cc5a6 resourceVersion: "43694" uid: 00de3603-7fbf-456c-8f84-cae672a86e15 spec: sourcePod: network-check-source-7f44b6dd87-rjwvn targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-28T15:19:07Z" message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.667419ms message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:40:07Z" - latency: 2.018279ms message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:39:07Z" - latency: 1.607138ms message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:38:07Z" - latency: 2.055316ms message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:37:07Z" - latency: 1.802706ms message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:36:07Z" - latency: 1.95472ms message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:35:07Z" - latency: 1.843042ms message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:34:07Z" - latency: 1.852151ms message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:33:07Z" - latency: 2.178472ms message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:32:07Z" - latency: 2.019192ms message: 'network-check-target-ip-10-0-137-0: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:31:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T15:12:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-141-to-network-check-target-ip-10-0-140-141 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-141.ec2.internal uid: a20462f6-d5d4-415b-b74a-b2903e5cc5a6 resourceVersion: "43693" uid: 2d4d7404-1e8b-4dc7-9067-b773dca36b96 spec: sourcePod: network-check-source-7f44b6dd87-rjwvn targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-28T15:19:07Z" message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 739.896µs message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:40:07Z" - latency: 1.339144ms message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:39:07Z" - latency: 932.032µs message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:38:07Z" - latency: 977.993µs message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:37:07Z" - latency: 807.314µs message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:36:07Z" - latency: 1.198061ms message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:35:07Z" - latency: 893.301µs message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:34:07Z" - latency: 934.459µs message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:33:07Z" - latency: 831.674µs message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:32:07Z" - latency: 1.391288ms message: 'network-check-target-ip-10-0-140-141: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:31:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T15:12:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-141-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-141.ec2.internal uid: a20462f6-d5d4-415b-b74a-b2903e5cc5a6 resourceVersion: "46184" uid: de5ed189-f482-4d05-8bf5-f5bbfce8c789 spec: sourcePod: network-check-source-7f44b6dd87-rjwvn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T15:18:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 863.2µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:42:07Z" - latency: 1.906308ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T15:42:07Z" - latency: 840.008µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:41:07Z" - latency: 1.465622ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T15:41:07Z" - latency: 861.887µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:40:07Z" - latency: 1.697729ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T15:40:07Z" - latency: 1.299689ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:39:07Z" - latency: 1.691995ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T15:39:07Z" - latency: 786.271µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T15:38:07Z" - latency: 1.765164ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T15:38:07Z" kind: List metadata: resourceVersion: ""