apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:23:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-162-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-162.ec2.internal uid: 2b1113f4-3719-42cc-af8b-6a6b04da3b15 resourceVersion: "60209" uid: b67f30bd-c2c4-4ad6-b40f-26960aa25e1c spec: sourcePod: network-check-source-869dcfcdcd-8rxpf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T16:30:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.229576ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:05:35Z" - latency: 1.097085ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:04:35Z" - latency: 1.104053ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:03:35Z" - latency: 1.222703ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:02:35Z" - latency: 964.1µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:01:35Z" - latency: 1.394413ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:00:35Z" - latency: 971.862µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:59:35Z" - latency: 1.045118ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:58:35Z" - latency: 1.091068ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:57:35Z" - latency: 1.577749ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:56:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:23:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-162-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-162.ec2.internal uid: 2b1113f4-3719-42cc-af8b-6a6b04da3b15 resourceVersion: "60210" uid: 14ea5ebf-b56e-47d9-97c8-cf95c4d06a1f spec: sourcePod: network-check-source-869dcfcdcd-8rxpf targetEndpoint: a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T16:29:35Z" message: 'load-balancer-api-external: tcp connection to a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.615762ms message: 'load-balancer-api-external: tcp connection to a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:05:35Z" - latency: 7.296447ms message: 'load-balancer-api-external: resolved host name a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:05:35Z" - latency: 5.145306ms message: 'load-balancer-api-external: tcp connection to a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:04:35Z" - latency: 7.06275ms message: 'load-balancer-api-external: resolved host name a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:04:35Z" - latency: 4.650387ms message: 'load-balancer-api-external: tcp connection to a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:03:35Z" - latency: 6.16118ms message: 'load-balancer-api-external: resolved host name a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:03:35Z" - latency: 5.918934ms message: 'load-balancer-api-external: tcp connection to a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:02:35Z" - latency: 7.535537ms message: 'load-balancer-api-external: resolved host name a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:02:35Z" - latency: 4.680066ms message: 'load-balancer-api-external: tcp connection to a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:01:35Z" - latency: 7.155551ms message: 'load-balancer-api-external: resolved host name a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:01:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:23:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-162-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-162.ec2.internal uid: 2b1113f4-3719-42cc-af8b-6a6b04da3b15 resourceVersion: "60211" uid: 4eb3d5a4-1372-468d-bb34-ca55a73b6ba4 spec: sourcePod: network-check-source-869dcfcdcd-8rxpf targetEndpoint: a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T16:29:35Z" message: 'load-balancer-api-internal: tcp connection to a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.568079ms message: 'load-balancer-api-internal: tcp connection to a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:05:35Z" - latency: 7.321574ms message: 'load-balancer-api-internal: resolved host name a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:05:35Z" - latency: 5.890794ms message: 'load-balancer-api-internal: tcp connection to a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:04:35Z" - latency: 7.083322ms message: 'load-balancer-api-internal: resolved host name a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:04:35Z" - latency: 4.657998ms message: 'load-balancer-api-internal: tcp connection to a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:03:35Z" - latency: 6.227331ms message: 'load-balancer-api-internal: resolved host name a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:03:35Z" - latency: 4.366533ms message: 'load-balancer-api-internal: tcp connection to a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:02:35Z" - latency: 7.45861ms message: 'load-balancer-api-internal: resolved host name a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:02:35Z" - latency: 4.696517ms message: 'load-balancer-api-internal: tcp connection to a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:01:35Z" - latency: 7.252079ms message: 'load-balancer-api-internal: resolved host name a23e96e1c1fdc4e27a2be6796a74c110-941cc6666836533d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:01:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:23:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-162-to-network-check-target-ip-10-0-133-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-162.ec2.internal uid: 2b1113f4-3719-42cc-af8b-6a6b04da3b15 resourceVersion: "60205" uid: 820f092f-8b4c-4cab-af61-6fcf3d28449a spec: sourcePod: network-check-source-869dcfcdcd-8rxpf targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T16:30:35Z" message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.412379ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:05:35Z" - latency: 1.615225ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:04:35Z" - latency: 805.622µs message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:03:35Z" - latency: 883.067µs message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:02:35Z" - latency: 966.069µs message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:01:35Z" - latency: 974.663µs message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:00:35Z" - latency: 937.285µs message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:59:35Z" - latency: 1.048522ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:58:35Z" - latency: 957.06µs message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:57:35Z" - latency: 981.988µs message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:56:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:23:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-162-to-network-check-target-ip-10-0-136-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-162.ec2.internal uid: 2b1113f4-3719-42cc-af8b-6a6b04da3b15 resourceVersion: "60206" uid: b4273278-d028-44d8-b530-23fcdf459f16 spec: sourcePod: network-check-source-869dcfcdcd-8rxpf targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T16:30:35Z" message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.221613ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:05:35Z" - latency: 2.326777ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:04:35Z" - latency: 2.497653ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:03:35Z" - latency: 2.695365ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:02:35Z" - latency: 2.358505ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:01:35Z" - latency: 2.599878ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:00:35Z" - latency: 2.073063ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:59:35Z" - latency: 2.145297ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:58:35Z" - latency: 2.592511ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:57:35Z" - latency: 2.583647ms message: 'network-check-target-ip-10-0-136-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:56:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:23:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-162-to-network-check-target-ip-10-0-139-176 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-162.ec2.internal uid: 2b1113f4-3719-42cc-af8b-6a6b04da3b15 resourceVersion: "60208" uid: 7a27eda9-b200-493e-b025-dd9f04a65706 spec: sourcePod: network-check-source-869dcfcdcd-8rxpf targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T16:30:35Z" message: 'network-check-target-ip-10-0-139-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.560709ms message: 'network-check-target-ip-10-0-139-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:05:35Z" - latency: 2.731443ms message: 'network-check-target-ip-10-0-139-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:04:35Z" - latency: 2.467143ms message: 'network-check-target-ip-10-0-139-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:03:35Z" - latency: 2.656596ms message: 'network-check-target-ip-10-0-139-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:02:35Z" - latency: 2.372729ms message: 'network-check-target-ip-10-0-139-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:01:35Z" - latency: 2.612294ms message: 'network-check-target-ip-10-0-139-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:00:35Z" - latency: 2.508571ms message: 'network-check-target-ip-10-0-139-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:59:35Z" - latency: 2.746007ms message: 'network-check-target-ip-10-0-139-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:58:35Z" - latency: 2.599279ms message: 'network-check-target-ip-10-0-139-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:57:35Z" - latency: 2.438503ms message: 'network-check-target-ip-10-0-139-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:56:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:23:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-162-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-162.ec2.internal uid: 2b1113f4-3719-42cc-af8b-6a6b04da3b15 resourceVersion: "60207" uid: eeb9afc5-6352-4ab8-8083-f6f47609b8c9 spec: sourcePod: network-check-source-869dcfcdcd-8rxpf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T16:29:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 755.847µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:05:35Z" - latency: 1.969836ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:05:35Z" - latency: 846.889µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:04:35Z" - latency: 1.731105ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:04:35Z" - latency: 894.066µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:03:35Z" - latency: 1.765955ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:03:35Z" - latency: 921.278µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:02:35Z" - latency: 2.080075ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:02:35Z" - latency: 944.806µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:01:35Z" - latency: 1.735328ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:01:35Z" kind: List metadata: resourceVersion: ""