apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T07:58:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-3-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-3.ec2.internal uid: 25ba7ba6-01ea-405f-b3a1-2bc1b1bbe76f resourceVersion: "14210" uid: 9377031d-9545-4d89-8e39-17a996186c14 spec: sourcePod: network-check-source-56d84b9f44-sz75r targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T08:05:49Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 800.508µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:05:49Z" - latency: 1.061954ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:04:49Z" - latency: 663.635µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:03:49Z" - latency: 845.388µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:02:49Z" - latency: 916.255µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:01:49Z" - latency: 1.022796ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:00:49Z" - latency: 891.229µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T07:59:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T07:58:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-3-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-3.ec2.internal uid: 25ba7ba6-01ea-405f-b3a1-2bc1b1bbe76f resourceVersion: "13874" uid: 47616b36-c2a3-472f-b663-c54429d3d617 spec: sourcePod: network-check-source-56d84b9f44-sz75r targetEndpoint: a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T08:04:49Z" message: 'load-balancer-api-external: tcp connection to a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.214599ms message: 'load-balancer-api-external: tcp connection to a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:04:49Z" - latency: 7.767165ms message: 'load-balancer-api-external: resolved host name a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T08:04:49Z" - latency: 5.234928ms message: 'load-balancer-api-external: tcp connection to a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:03:49Z" - latency: 11.481185ms message: 'load-balancer-api-external: resolved host name a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T08:03:49Z" - latency: 7.197189ms message: 'load-balancer-api-external: tcp connection to a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:02:49Z" - latency: 7.660186ms message: 'load-balancer-api-external: resolved host name a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T08:02:49Z" - latency: 5.848185ms message: 'load-balancer-api-external: tcp connection to a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:01:49Z" - latency: 10.049746ms message: 'load-balancer-api-external: resolved host name a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T08:01:49Z" - latency: 6.568734ms message: 'load-balancer-api-external: tcp connection to a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:00:49Z" - latency: 8.352395ms message: 'load-balancer-api-external: resolved host name a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T08:00:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T07:58:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-3-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-3.ec2.internal uid: 25ba7ba6-01ea-405f-b3a1-2bc1b1bbe76f resourceVersion: "13873" uid: d063557f-c59b-4fd4-908a-7fa5ff3a9fa4 spec: sourcePod: network-check-source-56d84b9f44-sz75r targetEndpoint: a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T08:04:49Z" message: 'load-balancer-api-internal: tcp connection to a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.220025ms message: 'load-balancer-api-internal: tcp connection to a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:04:49Z" - latency: 7.740383ms message: 'load-balancer-api-internal: resolved host name a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T08:04:49Z" - latency: 3.516424ms message: 'load-balancer-api-internal: tcp connection to a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:03:49Z" - latency: 11.498219ms message: 'load-balancer-api-internal: resolved host name a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T08:03:49Z" - latency: 7.163126ms message: 'load-balancer-api-internal: tcp connection to a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:02:49Z" - latency: 7.72431ms message: 'load-balancer-api-internal: resolved host name a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T08:02:49Z" - latency: 5.82916ms message: 'load-balancer-api-internal: tcp connection to a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:01:49Z" - latency: 10.028089ms message: 'load-balancer-api-internal: resolved host name a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T08:01:49Z" - latency: 6.549528ms message: 'load-balancer-api-internal: tcp connection to a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:00:49Z" - latency: 8.328101ms message: 'load-balancer-api-internal: resolved host name a8c903b7165914b3e8018ddfa7dd659c-55afc8a35ca778c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T08:00:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T07:58:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-3-to-network-check-target-ip-10-0-132-52 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-3.ec2.internal uid: 25ba7ba6-01ea-405f-b3a1-2bc1b1bbe76f resourceVersion: "14208" uid: d3dfa6c5-023b-466b-83c9-9ff0e9d0e320 spec: sourcePod: network-check-source-56d84b9f44-sz75r targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T08:05:49Z" message: 'network-check-target-ip-10-0-132-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.968979ms message: 'network-check-target-ip-10-0-132-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:05:49Z" - latency: 1.48393ms message: 'network-check-target-ip-10-0-132-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:04:49Z" - latency: 1.793851ms message: 'network-check-target-ip-10-0-132-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:03:49Z" - latency: 1.913871ms message: 'network-check-target-ip-10-0-132-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:02:49Z" - latency: 1.364815ms message: 'network-check-target-ip-10-0-132-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:01:49Z" - latency: 1.807979ms message: 'network-check-target-ip-10-0-132-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:00:49Z" - latency: 1.864276ms message: 'network-check-target-ip-10-0-132-52: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T07:59:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T07:58:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-3-to-network-check-target-ip-10-0-135-3 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-3.ec2.internal uid: 25ba7ba6-01ea-405f-b3a1-2bc1b1bbe76f resourceVersion: "14207" uid: 5b256477-426f-43d8-9853-b1af6480a380 spec: sourcePod: network-check-source-56d84b9f44-sz75r targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T08:05:49Z" message: 'network-check-target-ip-10-0-135-3: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 956.95µs message: 'network-check-target-ip-10-0-135-3: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:05:49Z" - latency: 675.38µs message: 'network-check-target-ip-10-0-135-3: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:04:49Z" - latency: 768.976µs message: 'network-check-target-ip-10-0-135-3: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:03:49Z" - latency: 1.091866ms message: 'network-check-target-ip-10-0-135-3: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:02:49Z" - latency: 710.138µs message: 'network-check-target-ip-10-0-135-3: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:01:49Z" - latency: 1.070816ms message: 'network-check-target-ip-10-0-135-3: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:00:49Z" - latency: 1.2947ms message: 'network-check-target-ip-10-0-135-3: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T07:59:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T07:58:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-3-to-network-check-target-ip-10-0-137-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-3.ec2.internal uid: 25ba7ba6-01ea-405f-b3a1-2bc1b1bbe76f resourceVersion: "14209" uid: da6394c5-7a68-4f0e-ba26-41eb5a3f747f spec: sourcePod: network-check-source-56d84b9f44-sz75r targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T08:05:49Z" message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.186368ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:05:49Z" - latency: 2.060811ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:04:49Z" - latency: 1.971372ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:03:49Z" - latency: 2.036887ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:02:49Z" - latency: 1.657501ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:01:49Z" - latency: 1.95108ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:00:49Z" - latency: 2.422478ms message: 'network-check-target-ip-10-0-137-47: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T07:59:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T07:58:47Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-3-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-3.ec2.internal uid: 25ba7ba6-01ea-405f-b3a1-2bc1b1bbe76f resourceVersion: "13872" uid: 0624e4d9-3b6e-41cf-b969-21a7cce62370 spec: sourcePod: network-check-source-56d84b9f44-sz75r targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T08:04:49Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 895.84µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:04:49Z" - latency: 1.853395ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T08:04:49Z" - latency: 749.434µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:03:49Z" - latency: 2.112785ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T08:03:49Z" - latency: 969.854µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:02:49Z" - latency: 1.579998ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T08:02:49Z" - latency: 905.429µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:01:49Z" - latency: 1.633243ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T08:01:49Z" - latency: 829.898µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T08:00:49Z" - latency: 1.934445ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T08:00:49Z" kind: List metadata: resourceVersion: ""