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
// InPlaceUpdateStrategy contains strategies for in-place update.
@@ -199,7 +199,7 @@ type GameServerSetStatus struct {
199
199
//+genclient
200
200
//+kubebuilder:object:root=true
201
201
//+kubebuilder:printcolumn:name="DESIRED",type="integer",JSONPath=".spec.replicas",description="The desired number of GameServers."
202
-
//+kubebuilder:printcolumn:name="CURRENT",type="integer",JSONPath=".status.currentReplicas",description="The number of currently all GameServers."
202
+
//+kubebuilder:printcolumn:name="CURRENT",type="integer",JSONPath=".status.currentReplicas",description="The total number of current GameServers."
203
203
//+kubebuilder:printcolumn:name="UPDATED",type="integer",JSONPath=".status.updatedReplicas",description="The number of GameServers updated."
204
204
//+kubebuilder:printcolumn:name="READY",type="integer",JSONPath=".status.readyReplicas",description="The number of GameServers ready."
205
205
//+kubebuilder:printcolumn:name="Maintaining",type="integer",JSONPath=".status.maintainingReplicas",description="The number of GameServers Maintaining."
Copy file name to clipboardExpand all lines: cloudprovider/amazonswebservices/README.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,11 +15,11 @@ enable = true
15
15
max_port = 32050
16
16
min_port = 32001
17
17
```
18
-
### Preparation： ###
18
+
### Preparation: ###
19
19
20
20
Due to the difference in AWS design, to achieve NLB port-to-Pod port mapping, three types of CRD resources need to be created: Listener/TargetGroup/TargetGroupBinding
21
21
22
-
#### Deploy elbv2-controller：
22
+
#### Deploy elbv2-controller:
23
23
24
24
Definition and controller for Listener/TargetGroup CRDs: https://github.com/aws-controllers-k8s/elbv2-controller. This project links k8s resources with AWS cloud resources. Download the chart: https://gallery.ecr.aws/aws-controllers-k8s/elbv2-chart, example value.yaml:
25
25
@@ -34,14 +34,14 @@ aws:
34
34
35
35
The key to deploying this project lies in authorizing the k8s ServiceAccount to access the NLB SDK, which is recommended to be done through an IAM role:
36
36
37
-
##### Step 1：Enable OIDC provider for the EKS cluster
37
+
##### Step 1:Enable OIDC provider for the EKS cluster
38
38
39
39
1. Sign in to the AWS Management Console.
40
-
2. Navigate to the EKS console：https://console.aws.amazon.com/eks/
40
+
2. Navigate to the EKS console:https://console.aws.amazon.com/eks/
41
41
3. Select your cluster.
42
42
4. On the cluster details page, ensure that the OIDC provider is enabled. Obtain the OIDC provider URL for the EKS cluster. In the "Configuration" section of the cluster details page, find the "OpenID Connect provider URL".
43
43
44
-
##### Step 2：Configure the IAM role trust policy
44
+
##### Step 2:Configure the IAM role trust policy
45
45
1. In the IAM console, create a new identity provider and select "OpenID Connect".
46
46
- For the Provider URL, enter the OIDC provider URL of your EKS cluster.
47
47
- For Audience, enter: `sts.amazonaws.com`
@@ -68,12 +68,12 @@ The key to deploying this project lies in authorizing the k8s ServiceAccount to
68
68
]
69
69
}
70
70
```
71
-
- Replace `<AWS_ACCOUNT_ID>`、`<REGION>`、`<OIDC_ID>`、`<NAMESPACE>` and `<SERVICE_ACCOUNT_NAME>` with your actual values.
71
+
- Replace `<AWS_ACCOUNT_ID>`,`<REGION>`,`<OIDC_ID>`,`<NAMESPACE>` and `<SERVICE_ACCOUNT_NAME>` with your actual values.
72
72
- Add the permission `ElasticLoadBalancingFullAccess`
73
73
74
74
75
75
76
-
#### Deploy AWS Load Balancer Controller：
76
+
#### Deploy AWS Load Balancer Controller:
77
77
78
78
CRD and controller for TargetGroupBinding: https://github.com/kubernetes-sigs/aws-load-balancer-controller/
79
79
@@ -97,15 +97,15 @@ Official deployment documentation: https://docs.aws.amazon.com/eks/latest/usergu
97
97
- Meaning: Fill in the health check parameters for the nlb target group, can be left blank to use default values.
98
98
- Format: Separate each configuration with a comma. For example: "healthCheckEnabled:true,healthCheckIntervalSeconds:30,healthCheckPath:/health,healthCheckPort:8081,healthCheckProtocol:HTTP,healthCheckTimeoutSeconds:10,healthyThresholdCount:5,unhealthyThresholdCount:2"
99
99
- Support for change: Yes
100
-
- Parameter explanation：
101
-
- **healthCheckEnabled**：Indicates whether health checks are enabled. If the target type is lambda, health checks are disabled by default but can be enabled. If the target type is instance, ip, or alb, health checks are always enabled and cannot be disabled.
102
-
- **healthCheckIntervalSeconds**：The approximate amount of time, in seconds, between health checks of an individual target. The range is 5-300. If the target group protocol is TCP, TLS, UDP, TCP_UDP, HTTP, or HTTPS, the default is 30 seconds. If the target group protocol is GENEVE, the default is 10 seconds. If the target type is lambda, the default is 35 seconds.
103
-
- **healthCheckPath**：The destination for health checks on the targets. For HTTP/HTTPS health checks, this is the path. For GRPC protocol version, this is the path of a custom health check method with the format /package.service/method. The default is /Amazon Web Services.ALB/healthcheck.
104
-
- **healthCheckPort**：The port the load balancer uses when performing health checks on targets. The default is traffic-port, which is the port on which each target receives traffic from the load balancer. If the protocol is GENEVE, the default is port 80.
105
-
- **healthCheckProtocol**：The protocol the load balancer uses when performing health checks on targets. For Application Load Balancers, the default is HTTP. For Network Load Balancers and Gateway Load Balancers, the default is TCP. The GENEVE, TLS, UDP, and TCP_UDP protocols are not supported for health checks.
106
-
- **healthCheckTimeoutSeconds**：The amount of time, in seconds, during which no response from a target means a failed health check. The range is 2–120 seconds. For target groups with a protocol of HTTP, the default is 6 seconds. For target groups with a protocol of TCP, TLS, or HTTPS, the default is 10 seconds. For target groups with a protocol of GENEVE, the default is 5 seconds. If the target type is lambda, the default is 30 seconds.
107
-
- **healthyThresholdCount**：The number of consecutive health check successes required before considering a target healthy. The range is 2-10. If the target group protocol is TCP, TCP_UDP, UDP, TLS, HTTP, or HTTPS, the default is 5. For target groups with a protocol of GENEVE, the default is 5. If the target type is lambda, the default is 5.
108
-
- **unhealthyThresholdCount**：The number of consecutive health check failures required before considering a target unhealthy. The range is 2-10. If the target group protocol is TCP, TCP_UDP, UDP, TLS, HTTP, or HTTPS, the default is 2. For target groups with a protocol of GENEVE, the default is 2. If the target type is lambda, the default is 5.
100
+
- Parameter explanation:
101
+
- **healthCheckEnabled**: Indicates whether health checks are enabled. If the target type is lambda, health checks are disabled by default but can be enabled. If the target type is instance, ip, or alb, health checks are always enabled and cannot be disabled.
102
+
- **healthCheckIntervalSeconds**: The approximate amount of time, in seconds, between health checks of an individual target. The range is 5-300. If the target group protocol is TCP, TLS, UDP, TCP_UDP, HTTP, or HTTPS, the default is 30 seconds. If the target group protocol is GENEVE, the default is 10 seconds. If the target type is lambda, the default is 35 seconds.
103
+
- **healthCheckPath**: The destination for health checks on the targets. For HTTP/HTTPS health checks, this is the path. For GRPC protocol version, this is the path of a custom health check method with the format /package.service/method. The default is /Amazon Web Services.ALB/healthcheck.
104
+
- **healthCheckPort**: The port the load balancer uses when performing health checks on targets. The default is traffic-port, which is the port on which each target receives traffic from the load balancer. If the protocol is GENEVE, the default is port 80.
105
+
- **healthCheckProtocol**: The protocol the load balancer uses when performing health checks on targets. For Application Load Balancers, the default is HTTP. For Network Load Balancers and Gateway Load Balancers, the default is TCP. The GENEVE, TLS, UDP, and TCP_UDP protocols are not supported for health checks.
106
+
- **healthCheckTimeoutSeconds**: The amount of time, in seconds, during which no response from a target means a failed health check. The range is 2–120 seconds. For target groups with a protocol of HTTP, the default is 6 seconds. For target groups with a protocol of TCP, TLS, or HTTPS, the default is 10 seconds. For target groups with a protocol of GENEVE, the default is 5 seconds. If the target type is lambda, the default is 30 seconds.
107
+
- **healthyThresholdCount**: The number of consecutive health check successes required before considering a target healthy. The range is 2-10. If the target group protocol is TCP, TCP_UDP, UDP, TLS, HTTP, or HTTPS, the default is 5. For target groups with a protocol of GENEVE, the default is 5. If the target type is lambda, the default is 5.
108
+
- **unhealthyThresholdCount**: The number of consecutive health check failures required before considering a target unhealthy. The range is 2-10. If the target group protocol is TCP, TCP_UDP, UDP, TLS, HTTP, or HTTPS, the default is 2. For target groups with a protocol of GENEVE, the default is 2. If the target type is lambda, the default is 5.
109
109
110
110
#### PortProtocols
111
111
- Meaning: Ports and protocols exposed by the pod, supports specifying multiple ports/protocols.
Copy file name to clipboardExpand all lines: cloudprovider/jdcloud/README.md
+39-39Lines changed: 39 additions & 39 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,36 +16,36 @@ max_port = 700
16
16
min_port = 500
17
17
```
18
18
19
-
### Parameter
19
+
### Parameters
20
20
#### NlbIds
21
-
- Meaning：fill in the id of the clb. You can fill in more than one. You need to create the clb in [JdCloud].
22
-
- Value：each clbId is divided by `,` . For example：`netlb-aaa,netlb-bbb,...`
23
-
- Configurable：Y
21
+
- Meaning: fill in the id of the clb. You can fill in more than one. You need to create the clb in [JdCloud].
22
+
- Value: each clbId is divided by `,` . For example:`netlb-aaa,netlb-bbb,...`
23
+
- Configurable: Y
24
24
25
25
#### PortProtocols
26
-
- Meaning：the ports and protocols exposed by the pod, support filling in multiple ports/protocols
27
-
- Value：`port1/protocol1`,`port2/protocol2`,... The protocol names must be in uppercase letters.
28
-
- Configurable：Y
26
+
- Meaning: the ports and protocols exposed by the pod, support filling in multiple ports/protocols
27
+
- Value: `port1/protocol1`,`port2/protocol2`,... The protocol names must be in uppercase letters.
28
+
- Configurable: Y
29
29
30
30
#### Fixed
31
-
- Meaning：whether the mapping relationship is fixed. If the mapping relationship is fixed, the mapping relationship remains unchanged even if the pod is deleted and recreated.
32
-
- Value：false / true
33
-
- Configurable：Y
31
+
- Meaning: whether the mapping relationship is fixed. If the mapping relationship is fixed, the mapping relationship remains unchanged even if the pod is deleted and recreated.
32
+
- Value: false / true
33
+
- Configurable: Y
34
34
35
35
#### AllocateLoadBalancerNodePorts
36
-
- Meaning：Whether the generated service is assigned nodeport, this can be set to false only in nlb passthrough mode
37
-
- Value：false / true
38
-
- Configurable：Y
36
+
- Meaning: Whether the generated service is assigned nodeport, this can be set to false only in nlb passthrough mode
37
+
- Value: false / true
38
+
- Configurable: Y
39
39
40
40
#### AllowNotReadyContainers
41
-
- Meaning：the container names that are allowed not ready when inplace updating, when traffic will not be cut.
- Meaning：Whether to fixed the Elastic Public IP,if so, the EIP will not be changed when the pod is recreated.
141
-
- Value：string, "false" / "true"
142
-
- Configurable：Y
140
+
- Meaning: Whether to fixed the Elastic Public IP,if so, the EIP will not be changed when the pod is recreated.
141
+
- Value: string, "false" / "true"
142
+
- Configurable: Y
143
143
144
144
#### AssignEIPConfigName
145
-
- Meaning：Whether to designate a specific Elastic Public IP. If true, provide the ID of the Elastic Public IP; otherwise, an EIP will be automatically allocated.
146
-
- Value：string, "false" / "true"
145
+
- Meaning: Whether to designate a specific Elastic Public IP. If true, provide the ID of the Elastic Public IP; otherwise, an EIP will be automatically allocated.
146
+
- Value: string, "false" / "true"
147
147
148
148
#### EIPIdConfigName
149
-
- Meaning：If a specific Elastic Public IP is designated, the ID of the Elastic Public IP must be provided, and the component will automatically perform the lookup and binding.
150
-
- Value：string，for example：`fip-xxxxxxxx`
149
+
- Meaning: If a specific Elastic Public IP is designated, the ID of the Elastic Public IP must be provided, and the component will automatically perform the lookup and binding.
0 commit comments