apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T09:57:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-125-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-125.ec2.internal uid: d39d22b8-603a-4715-890c-65829b1f1154 resourceVersion: "63817" uid: 456a3fc1-5a1b-4aa8-836c-30143e111acc spec: sourcePod: network-check-source-7bc5b6bf85-8fqmr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T10:04:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.075102ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:39:37Z" - latency: 988.401µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:38:38Z" - latency: 938.05µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:37:37Z" - latency: 918.881µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:36:37Z" - latency: 1.181671ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:35:37Z" - latency: 1.067618ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:34:37Z" - latency: 1.076134ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:33:37Z" - latency: 889.905µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:32:38Z" - latency: 1.07184ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:31:37Z" - latency: 912.389µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:30:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T09:57:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-125-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-125.ec2.internal uid: d39d22b8-603a-4715-890c-65829b1f1154 resourceVersion: "63819" uid: a69aa2a4-8560-481e-8b32-eb0abf61bf96 spec: sourcePod: network-check-source-7bc5b6bf85-8fqmr targetEndpoint: ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T10:03:38Z" message: 'load-balancer-api-external: tcp connection to ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.473666ms message: 'load-balancer-api-external: tcp connection to ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:39:38Z" - latency: 7.056475ms message: 'load-balancer-api-external: resolved host name ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T10:39:37Z" - latency: 3.701119ms message: 'load-balancer-api-external: tcp connection to ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:38:38Z" - latency: 6.98825ms message: 'load-balancer-api-external: resolved host name ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T10:38:38Z" - latency: 3.735587ms message: 'load-balancer-api-external: tcp connection to ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:37:38Z" - latency: 12.374462ms message: 'load-balancer-api-external: resolved host name ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T10:37:37Z" - latency: 4.269295ms message: 'load-balancer-api-external: tcp connection to ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:36:38Z" - latency: 6.628416ms message: 'load-balancer-api-external: resolved host name ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T10:36:37Z" - latency: 3.467593ms message: 'load-balancer-api-external: tcp connection to ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:35:38Z" - latency: 7.233256ms message: 'load-balancer-api-external: resolved host name ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T10:35:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T09:57:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-125-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-125.ec2.internal uid: d39d22b8-603a-4715-890c-65829b1f1154 resourceVersion: "63818" uid: d14e5822-bc39-406c-99ac-7583223c6951 spec: sourcePod: network-check-source-7bc5b6bf85-8fqmr targetEndpoint: ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T10:03:38Z" message: 'load-balancer-api-internal: tcp connection to ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.911728ms message: 'load-balancer-api-internal: tcp connection to ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:39:38Z" - latency: 7.141594ms message: 'load-balancer-api-internal: resolved host name ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T10:39:37Z" - latency: 3.68754ms message: 'load-balancer-api-internal: tcp connection to ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:38:38Z" - latency: 7.063821ms message: 'load-balancer-api-internal: resolved host name ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T10:38:37Z" - latency: 3.693588ms message: 'load-balancer-api-internal: tcp connection to ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:37:38Z" - latency: 12.397436ms message: 'load-balancer-api-internal: resolved host name ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T10:37:37Z" - latency: 4.802894ms message: 'load-balancer-api-internal: tcp connection to ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:36:38Z" - latency: 6.706927ms message: 'load-balancer-api-internal: resolved host name ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T10:36:37Z" - latency: 3.381757ms message: 'load-balancer-api-internal: tcp connection to ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:35:38Z" - latency: 7.359821ms message: 'load-balancer-api-internal: resolved host name ae7af0db20aad418d8d37218e7f785eb-39e9301776b1ec60.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T10:35:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T09:57:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-125-to-network-check-target-ip-10-0-139-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-125.ec2.internal uid: d39d22b8-603a-4715-890c-65829b1f1154 resourceVersion: "63815" uid: 6c8b3270-cd39-45fc-9057-47618b878434 spec: sourcePod: network-check-source-7bc5b6bf85-8fqmr targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-23T10:04:38Z" message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.444969ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:39:37Z" - latency: 2.344806ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:38:37Z" - latency: 2.276027ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:37:37Z" - latency: 2.01402ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:36:37Z" - latency: 2.572196ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:35:37Z" - latency: 2.370296ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:34:37Z" - latency: 2.217469ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:33:37Z" - latency: 2.325975ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:32:37Z" - latency: 2.228146ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:31:37Z" - latency: 2.386035ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:30:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T09:57:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-125-to-network-check-target-ip-10-0-141-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-125.ec2.internal uid: d39d22b8-603a-4715-890c-65829b1f1154 resourceVersion: "63814" uid: 04a8186c-28ba-444b-9b4d-7e33cebeee3a spec: sourcePod: network-check-source-7bc5b6bf85-8fqmr targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T10:04:38Z" message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.597675ms message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:39:37Z" - latency: 1.321295ms message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:38:37Z" - latency: 1.547069ms message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:37:37Z" - latency: 978.408µs message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:36:37Z" - latency: 1.00111ms message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:35:37Z" - latency: 1.416456ms message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:34:37Z" - latency: 1.021228ms message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:33:37Z" - latency: 1.171226ms message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:32:37Z" - latency: 780.104µs message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:31:37Z" - latency: 985.482µs message: 'network-check-target-ip-10-0-141-125: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:30:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T09:57:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-125-to-network-check-target-ip-10-0-141-187 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-125.ec2.internal uid: d39d22b8-603a-4715-890c-65829b1f1154 resourceVersion: "63813" uid: b0e20c5f-b8cf-4f21-8921-e23652f6bd60 spec: sourcePod: network-check-source-7bc5b6bf85-8fqmr targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T10:04:38Z" message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.458455ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:39:37Z" - latency: 2.745755ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:38:37Z" - latency: 2.246547ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:37:37Z" - latency: 2.004596ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:36:37Z" - latency: 2.412522ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:35:37Z" - latency: 2.15423ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:34:37Z" - latency: 2.285306ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:33:37Z" - latency: 2.07394ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:32:37Z" - latency: 2.246814ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:31:37Z" - latency: 2.491431ms message: 'network-check-target-ip-10-0-141-187: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:30:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T09:57:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-125-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-125.ec2.internal uid: d39d22b8-603a-4715-890c-65829b1f1154 resourceVersion: "63816" uid: 36be19aa-d494-47b7-a901-8f49fb61d11f spec: sourcePod: network-check-source-7bc5b6bf85-8fqmr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T10:03:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 901.192µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:39:38Z" - latency: 1.700778ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T10:39:37Z" - latency: 1.272911ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:38:38Z" - latency: 1.808269ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T10:38:37Z" - latency: 926.552µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:37:38Z" - latency: 1.888043ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T10:37:37Z" - latency: 1.228408ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:36:38Z" - latency: 1.595197ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T10:36:37Z" - latency: 778.529µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T10:35:38Z" - latency: 1.768028ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T10:35:37Z" kind: List metadata: resourceVersion: ""