このコンテンツは選択した言語では利用できません。
Chapter 6. Create your Gateway instance
This section shows how you can deploy a Gateway in your OpenShift cluster. This task is typically performed by platform engineers when setting up the infrastructure to be used by application developers.
In a multicluster environment, for Connectivity Link to balance traffic by using DNS across clusters, you must define a Gateway with a shared hostname. You can define this by using an HTTPS listener with a wildcard hostname based on the root domain. As mentioned previously, you must apply these resources to all clusters.
Prerequisites
Procedure
Enter the following command to create the Gateway:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Check the status of your Gateway as follows:
kubectl get gateway ${KUADRANT_GATEWAY_NAME} -n ${KUADRANT_GATEWAY_NS} -o=jsonpath='{.status.conditions[?(@.type=="Accepted")].message}{"\n"}{.status.conditions[?(@.type=="Programmed")].message}'kubectl get gateway ${KUADRANT_GATEWAY_NAME} -n ${KUADRANT_GATEWAY_NS} -o=jsonpath='{.status.conditions[?(@.type=="Accepted")].message}{"\n"}{.status.conditions[?(@.type=="Programmed")].message}'Copy to Clipboard Copied! Toggle word wrap Toggle overflow Your Gateway should be
AcceptedandProgrammed, which means that it is valid and assigned an external address.Check the status of your HTTPS listener as follows:
kubectl get gateway ${KUADRANT_GATEWAY_NAME} -n ${KUADRANT_GATEWAY_NS} -o=jsonpath='{.status.listeners[0].conditions[?(@.type=="Programmed")].message}'kubectl get gateway ${KUADRANT_GATEWAY_NAME} -n ${KUADRANT_GATEWAY_NS} -o=jsonpath='{.status.listeners[0].conditions[?(@.type=="Programmed")].message}'Copy to Clipboard Copied! Toggle word wrap Toggle overflow You will see that the HTTPS listener is not yet programmed or ready to accept traffic due to bad TLS configuration. Connectivity Link can help with this by using a TLSPolicy, which is described in the next step.