Skip to content

Commit 96b1319

Browse files
committed
Fix typo in expander/grpcplugin/README.md
Signed-off-by: aleskandro <[email protected]>
1 parent bb8fe52 commit 96b1319

File tree

1 file changed

+5
-5
lines changed
  • cluster-autoscaler/expander/grpcplugin

1 file changed

+5
-5
lines changed

cluster-autoscaler/expander/grpcplugin/README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,12 +16,12 @@ There are a wide variety of use cases here. Some examples are as follows:
1616
## Configuration options
1717
As using this expander requires communication with another service, users must specify a few options as CLI arguments.
1818

19-
```yaml
20-
--grpcExpanderUrl
19+
```bash
20+
--grpc-expander-url
2121
```
2222
URL of the gRPC Expander server, for CA to communicate with.
23-
```yaml
24-
--grpcExpanderCert
23+
```bash
24+
--grpc-expander-cert
2525
```
2626
Location of the volume mounted certificate of the gRPC server if it is configured to communicate over TLS
2727

@@ -32,7 +32,7 @@ service. Note that the `protos/expander.pb.go` generated protobuf code will also
3232
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.
3333

3434
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.
3636

3737
## Details
3838

0 commit comments

Comments
 (0)