Skip to content
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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

rkpattnaik780
Copy link
Contributor

No description provided.

```
$ helm install . --generate-name --set-string rhoas.config=<configmap-name>,rhoas.secret=<secret-name>
```
5. Deploy the helm chart with the appropriate values:
Copy link
Contributor Author

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

Copy link
Contributor

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!


`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

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make this a bullet list:

* `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 are various ways to provide values:

1. The default method is specifying values in the `values.yaml` file.
2. Specifying a yaml file with defined values using the `--values` flag:
Copy link
Contributor

@jbyrne-redhat jbyrne-redhat Oct 13, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Specifying a YAML file of another name using the the --values flag:


There are various ways to provide values:

1. The default method is specifying values in the `values.yaml` file.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of comments:

  • Make this a bullet list (*) rather than a numbered list
  • After the first item, maybe show an example of the values.yaml file you configured?

So, putting that all together:

* The default method is specifying values in a YAML file called `values.yaml`. An example is shown below.

## Example values.yaml file
rhoas: 
   config: my-service-context-configuration
   secret: service-account-credentials

```
helm install . --generate-name --values my-values.yaml
```
3. Passing values from the command line using the `--set-string` flag:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Passing values directly from the command line using the --set-string flag:

```
$ helm install . --generate-name --set-string rhoas.config=<configmap-name>,rhoas.secret=<secret-name>
```
5. Deploy the helm chart with the appropriate values:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deploy the Helm chart.... (capitalize Helm)

Copy link
Contributor

@jbyrne-redhat jbyrne-redhat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updates, look good, @rkpattnaik780. Just a few things to suggest.

@rkpattnaik780
Copy link
Contributor Author

Thanks for the suggestions @jbyrne-redhat !
Have made the changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants