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: cluster-autoscaler/expander/grpcplugin/README.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -16,12 +16,12 @@ There are a wide variety of use cases here. Some examples are as follows:
16
16
## Configuration options
17
17
As using this expander requires communication with another service, users must specify a few options as CLI arguments.
18
18
19
-
```yaml
20
-
--grpcExpanderUrl
19
+
```bash
20
+
--grpc-expander-url
21
21
```
22
22
URL of the gRPC Expander server, for CA to communicate with.
23
-
```yaml
24
-
--grpcExpanderCert
23
+
```bash
24
+
--grpc-expander-cert
25
25
```
26
26
Location of the volume mounted certificate of the gRPC server if it is configured to communicate over TLS
27
27
@@ -32,7 +32,7 @@ service. Note that the `protos/expander.pb.go` generated protobuf code will also
32
32
Communication between Cluster Autoscaler and the gRPC Server will occur over native kube-proxy. To use this, note the Service and Namespace the gRPC server is deployed in.
33
33
34
34
Deploy the gRPC Expander Server as a separate app, listening on a specifc port number.
35
-
Start Cluster Autoscaler with the `--grpcExapnderURl=SERVICE_NAME.NAMESPACE_NAME.svc.cluster.local:PORT_NUMBER` flag, as well as `--grpcExpanderCert` pointed at the location of the volume mounted certificate of the gRPC server.
35
+
Start Cluster Autoscaler with the `--grpc-expander-url=SERVICE_NAME.NAMESPACE_NAME.svc.cluster.local:PORT_NUMBER` flag, as well as `--grpc-expander-cert` pointed at the location of the volume mounted certificate of the gRPC server.
0 commit comments