MS-SQL Operator not deployed on K8S version 1.18 and 1.20? also issue with leader election in HA mode?

Hi , Please provide yours's comments on following questions:-

1. I was able to deploy MSSQL K8S Operator on K8S version 1.13 but unable to deploy on K8S version 1.18 and 1.20. I was using sample manifest file for deployments given here - "https://github.com/microsoft/sql-server-samples/tree/master/samples/features/high%20availability/Kubernetes/sample-manifest-files".
   Error : getting similar error, sql pods are not coming up, discussed in this threads - "https://stackoverflow.com/questions/63405840/k8s-sql2019-ha-containers-dude-where-are-my-pods".

for deployment, I used following images-

1. agentsContainerImage: mcr.microsoft.com/mssql/ha:2019-CTP2.1-ubuntu

2. sqlServerContainer: mcr.microsoft.com/mssql/server:2019-latest

3. My second question was, once I add any database to AG, after than in any case further redeployment causing issue for failover and ag1-primary is not able to find primary pods among mssql1-0, mssql2-0, mssql3-0 . I guess there is some issue with leader election method which I was able to observe with pod ha-supervisor container logs. due to this issue client connection affected with ag-primary service.

Please let me know on these two issues?

Start with the sample manifest files linked in the issue and compare deployment behavior on Kubernetes 1.13, 1.18, and 1.20 using the listed container images. Inspect why the SQL pods do not start and review the ha-supervisor container logs after AG redeployment. Done means identifying reproducible causes for both deployment and leader-election failures, including the effect on the ag-primary service.