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: website/docs/r/eks_addon.html.markdown
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,13 +38,14 @@ Custom add-on configuration can be passed using `configuration_values` as a sing
38
38
39
39
~> **Note:**`configuration_values` is a single JSON string should match the valid JSON schema for each add-on with specific version.
40
40
41
-
To find the correct JSON schema for each add-on can be extracted using [describe-addon-configuration](https://docs.aws.amazon.com/cli/latest/reference/eks/describe-addon-configuration.html)call.
42
-
This below is an example for extracting the `configuration_values` schema for `coredns`.
41
+
You can use [describe-addon-configuration](https://docs.aws.amazon.com/cli/latest/reference/eks/describe-addon-configuration.html)to extract each add-on's JSON schema.
42
+
Here's an example command to extract the `configuration_values` schema for `coredns`.
43
43
44
44
```bash
45
-
aws eks describe-addon-configuration \
46
-
--addon-name coredns \
47
-
--addon-version v1.10.1-eksbuild.1
45
+
aws eks describe-addon-configuration \
46
+
--addon-name coredns \
47
+
--addon-version v1.10.1-eksbuild.1 \
48
+
| jq -r .configurationSchema | jq .
48
49
```
49
50
50
51
Example to create a `coredns` managed addon with custom `configuration_values`.
0 commit comments