Kubernetes traditionally uses Ingress to manage external access to services within a cluster. While effective, Ingress has some limitations in terms of extensibility and standardization across different implementations.
To address this, Kubernetes introduced the Gateway API, which includes resources like, GatewayClass , Gateway and HTTPRoute. These provide more flexibility, better separation of concerns, and improved support for modern networking features.
#With stage1+2 DR Policy
1. First you need to create a Stage1+2 DR policy. For this go to the 'DR Policy' under 'Busineness Continuity and DR' > click on 'New' button.
2. Once you click on the 'New' button, a prompt will appear where you need to enter the DR Policy name and select the Sync type. In the example below, we have selected 'Stage1+2' as the sync type. Additionally, we chose Stage2 execution and provided an email ID for receiving alerts.
3. Once you create a DR Policy then it will looks like as below.
4. Currently it is in IDLE state, once you applied then it will became Active state. Now apply the DR policy. Select the DR Policy> click on 'Apply' > Click on 'Replication Replication'.
5. Once you select 'Application Replication' , then you have to select the source and destination cluster and namespace and choose rest of the things as per your environment. Please refer this KB to get an idea of this.
6. Now you have to click on 'Advanced Option for new Stage1 and Stage2 replication' .
7. Now, please navigate to 'Kubernetes Ingress Config' > 'Ingress GatewayClass Mapping'. First, select the Target section, as the conversion from Ingress to GatewayClass needs to happen first. Once this is done, you can proceed to the Source section for reverse sync.
This is necessary because, unless the conversion is completed, the Gateway name required for reverse sync will not be available.
Please refer to the snippet below.
##As you can see below, in the Source section, only one option is available in the dropdown. Once you click on the '+' sign, the Gateway name on the source side will be displayed.
Please refer to the snippets below for your reference.
8. Now that we have configured both the Target and Source, the Target will be used for forward sync, and the Source will be used for reverse sync.
9. Now click on 'Apply' button to start the Policy and sync as well.
10. Once you apply the Policy, then it will start the sync and will be conpleted stage1 and stage2.
11. Now, let’s verify whether the Ingress has been successfully converted to a Gateway, and if the HTTPRoute has been created in the target cluster.
As shown below, the conversion was successful, and the Gateway has obtained an Address.
12. And Able to access the nginx application with that same 'Address'.
