-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: update README of helm-example #591
base: main
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -33,10 +33,28 @@ $ oc apply -f ./rhoas-secrets.yaml | |
$ oc apply -f ./rhoas-services.yaml | ||
``` | ||
|
||
5. Deploy the helm chart setting the appropriate values: | ||
|
||
``` | ||
$ helm install . --generate-name --set-string rhoas.config=<configmap-name>,rhoas.secret=<secret-name> | ||
``` | ||
5. Deploy the helm chart with the appropriate values: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Deploy the Helm chart.... (capitalize Helm) |
||
|
||
`helm install` command is used to install a chart to the OpenShift cluster. | ||
`Values` is a built-in object that provides access to values passed in the chart. | ||
|
||
The Helm chart uses the follwing values in the templates: | ||
|
||
`rhoas.config` - Name of the ConfigMap object containing configurations deployed in the OpenShift cluster | ||
`rhoas.secret` - Name of the Secret object containing service-account credentials deployed in the OpenShift cluster | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Make this a bullet list:
|
||
|
||
|
||
There are various ways to provide values: | ||
|
||
1. The default method is specifying values in the `values.yaml` file. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. A couple of comments:
So, putting that all together:
|
||
2. Specifying a yaml file with defined values using the `--values` flag: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Specifying a YAML file of another name using the the |
||
``` | ||
helm install . --generate-name --values my-values.yaml | ||
``` | ||
3. Passing values from the command line using the `--set-string` flag: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Passing values directly from the command line using the |
||
``` | ||
helm install . --generate-name --set-string rhoas.config=my-context-3-configuration | ||
``` | ||
|
||
To see how to use this code example follow the [guide](../../docs/rhoas/rhoas-helm-guide/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It made more sense to include more details in the step itself rather than having a separate sub-heading for it. Let me know if you feel if it should be moved to a higher level @jbyrne-redhat
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that makes sense to me!