How Can I Determine Which Ingress the Listener Settings Have Been Applied To?

The query command is as follows: (Replace the load balancer ID and port number as needed.)

elb_id=${1}
elb_port=${2}
kubectl get ingress --all-namespaces --sort-by='.metadata.creationTimestamp' -o=custom-columns=Name:'metadata.name',Namespace:'metadata.namespace',elbID:'metadata.annotations.kubernetes\.io\/elb\.id',elbPort:'metadata.annotations.kubernetes\.io\/elb\.port',elbPorts:'metadata.annotations.kubernetes\.io\/elb\.listen-ports' | awk 'NR==1 {print; next} {if ($5 != "<none>") $4 = "<none>"; print}' | grep -E "^Name|${elb_id}" | grep -E "^Name|${elb_port}" | awk '{printf "%-30s %-30s %-38s %-10s %-10s\n", $1, $2, $3, $4, $5}'

In the command output, the first column specifies the ingress names, the second specifies the namespaces, the third specifies the load balancer IDs, the fourth specifies the listener ports, and the fifth specifies the ports of multiple listeners. (If multiple listener port numbers are configured, they will replace the listener port numbers and become effective.)

Name             Namespace   elbID                                  elbPort   elbPorts
ingress-first    default     be56202a-c2cb-40d5-900e-d7a007a4b054   443       <none>
ingress-second   default     be56202a-c2cb-40d5-900e-d7a007a4b054   443       <none>
ingress-third    test        be56202a-c2cb-40d5-900e-d7a007a4b054   443       <none>

ELB server certificates are also maintained on the ELB console, so you do not need to import the certificate content to CCE secrets. This allows for unified cross-namespace configuration. It is recommended that you use ELB server certificates to configure the certificates for ingresses.

ELB server certificates are supported in clusters of versions v1.19.16-r2, v1.21.5-r0, and v1.23.3-r0.

1. Log in to the CCE console and click the cluster name to access the cluster console.
2. In the navigation pane, choose Services, click the Ingresses tab, and choose More > Update in the Operation column.
3. Click Synchronize to automatically synchronize the server certificate. This option is available when the listener settings of the ingress are inconsistent with those of the load balancer.
   

   If you synchronize a server certificate and an SNI certificate, and the current ingress is using a TLS key, the certificate will be replaced with an ELB server certificate. If the cluster version is earlier than v1.19.16-r2, v1.21.5-r0, v1.23.3-r0 and does not support ELB server certificates, you need to manually synchronize the configurations using YAML.

   

4. Click OK to apply the modification.

1. Check the command in Obtaining the First Ingress and obtain all ingresses associated with the same listener.

   Name             Namespace   elbID                                  elbPort   elbPorts
   ingress-first    default     be56202a-c2cb-40d5-900e-d7a007a4b054   443       <none>
   ingress-second   default     be56202a-c2cb-40d5-900e-d7a007a4b054   443       <none>
   ingress-third    test        be56202a-c2cb-40d5-900e-d7a007a4b054   443       <none>

2. Before deleting some ingresses such as ingress-first and ingress-second, synchronize the listener settings of ingress-first to the annotations of ingress-third.

   If the listener server certificate was created using a TLS key, you need to synchronize the configurations saved in the ingress' spec.tls to ingress-third.

   apiVersion: networking.k8s.io/v1
   kind: Ingress
   metadata:
     name: ingress-first
     namespace: default
     ...
   spec:
     tls:
       - secretName: default-ns-secret-1
       - hosts:
           - 'example.com'
         secretName: default-ns-secret-2
   ...