You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: app/_how-tos/operator-get-started-gateway-api-create-gateway.md
+46-19Lines changed: 46 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,27 +30,28 @@ search_aliases:
30
30
- konnect hybrid gateway
31
31
32
32
tldr:
33
-
q: How do I configure a Hybrid Gateway in {{site.konnect_short_name}}?
34
-
a: Fill Konnect related fields in `GatewayConfiguration` for `GatewayClass` that will be used for Hybrid Gateways.
33
+
q: How can I create a Gateway with {{site.operator_product_name }} with self-managed Control Plane?
34
+
a: Create a `GatewayConfiguration` object, then create a `GatewayClass` instance and a `Gateway` resource.
35
35
36
36
prereqs:
37
-
skip_product: true
37
+
skip_product: false
38
38
operator:
39
39
konnect:
40
40
auth: true
41
41
42
42
---
43
43
44
-
## Create a `GatewayClass` for a Hybrid Gateway
44
+
## Create a `GatewayConfiguration`
45
45
46
+
{: data-deployment-topology="konnect" }
46
47
Use the `GatewayConfiguration` resource to configure a `GatewayClass` for Hybrid Gateways. `GatewayConfiguration` is for Hybrid Gateways when field `spec.konnect.authRef` is set.
47
48
48
49
<!-- vale off -->
49
50
{% konnect_crd %}
50
51
kind: GatewayConfiguration
51
52
apiVersion: gateway-operator.konghq.com/v2beta1
52
53
metadata:
53
-
name: hybrid-configuration
54
+
name: gateway-configuration
54
55
namespace: kong
55
56
spec:
56
57
konnect:
@@ -66,49 +67,75 @@ spec:
66
67
{% endkonnect_crd %}
67
68
<!-- vale on -->
68
69
69
-
Next configure respective `GatewayClass` to use the above `GatewayConfiguration`.
70
+
{: data-deployment-topology="on-prem" }
71
+
Use the `GatewayConfiguration` resource to configure a `GatewayClass` for on-premise Gateways.
70
72
71
73
<!-- vale off -->
72
-
{% konnect_crd %}
74
+
{% on_prem_crd %}
75
+
kind: GatewayConfiguration
76
+
apiVersion: gateway-operator.konghq.com/v2beta1
77
+
metadata:
78
+
name: kong-configuration
79
+
namespace: kong
80
+
spec:
81
+
dataPlaneOptions:
82
+
deployment:
83
+
podTemplateSpec:
84
+
spec:
85
+
containers:
86
+
- name: proxy
87
+
image: kong/kong-gateway:3.12
88
+
{% endon_prem_crd %}
89
+
<!-- vale on -->
90
+
91
+
## Create a `GatewayClass`
92
+
93
+
Next configure respective `GatewayClass` to use the above `GatewayConfiguration`.
94
+
95
+
```yaml
73
96
kind: GatewayClass
74
97
apiVersion: gateway.networking.k8s.io/v1
75
98
metadata:
76
-
name: hybrid-class
99
+
name: kong
77
100
spec:
78
101
controllerName: konghq.com/gateway-operator
79
102
parametersRef:
80
103
group: gateway-operator.konghq.com
81
104
kind: GatewayConfiguration
82
-
name: hybrid-configuration
105
+
name: kong-configuration
83
106
namespace: kong
84
-
{% endkonnect_crd %}
85
-
<!-- vale on -->
107
+
```
86
108
87
109
## Create a `Gateway` Resource
88
110
89
111
Now create a `Gateway` resource that references the `GatewayClass` you just created.
90
112
91
-
<!-- vale off -->
92
-
{% konnect_crd %}
113
+
```yaml
93
114
kind: Gateway
94
115
apiVersion: gateway.networking.k8s.io/v1
95
116
metadata:
96
-
name: hybrid-gateway
117
+
name: kong
97
118
namespace: kong
98
119
spec:
99
-
gatewayClassName: hybrid-class
120
+
gatewayClassName: kong
100
121
listeners:
101
122
- name: http
102
123
protocol: HTTP
103
124
port: 80
104
-
{% endkonnect_crd %}
105
-
<!-- vale on -->
125
+
```
106
126
107
127
## Validation
108
128
109
129
{% validation kubernetes-resource %}
110
130
kind: Gateway
111
-
name: hybrid-gateway
131
+
name: kong
132
+
namespace: kong
112
133
{% endvalidation %}
113
134
114
-
The respective `DataPlane` and `KonnectGatewayControlPlane` are created automatically by the Gateway Operator.
135
+
{: data-deployment-topology="konnect" }
136
+
The respective `DataPlane`, `KonnectExtension`, and `KonnectGatewayControlPlane` are created automatically by the Gateway Operator.
137
+
{: data-deployment-topology="konnect" }
138
+
139
+
{: data-deployment-topology="on-prem" }
140
+
The respective `DataPlane` and `ControlPlane` are created automatically by the Gateway Operator.
0 commit comments