Skip to content

Updating deployment guide#126

Open
chethanuk wants to merge 1 commit into
fintechstudios:masterfrom
chethanuk:deploy
Open

Updating deployment guide#126
chethanuk wants to merge 1 commit into
fintechstudios:masterfrom
chethanuk:deploy

Conversation

@chethanuk
Copy link
Copy Markdown

No description provided.

@chethanuk chethanuk requested a review from austince as a code owner April 30, 2020 20:14
@austince
Copy link
Copy Markdown
Contributor

Thanks so much @chethanuk - I'll review this by tomorrow, just need to finish up a few other things today!

@austince
Copy link
Copy Markdown
Contributor

austince commented May 1, 2020

Looks like CI won't run because we only mirror the fintechstudios repo to GitLab, not yours. I'm not sure how to solve this without either moving entirely to GitLab or to another CI provider, but since these are just doc changes I don't think it's a big issue to add them without CI runs.

Update: #127

Copy link
Copy Markdown
Contributor

@austince austince left a comment

Choose a reason for hiding this comment

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

Thanks so much for this! Just have some small notes.

Comment thread README.md
Please have a look at the [`docs`](docs/README.md) for information on getting started using
the operator.

To deploying and using the operator look at [`deploying`](docs/guides/deployment.md)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

What do you think about this slight tweak?

Suggested change
To deploying and using the operator look at [`deploying`](docs/guides/deployment.md)
For deploying and using the operator, look at [`deploying`](docs/guides/deployment.md)

Comment thread docs/guides/deployment.md
# In this case, add the `top-speed` namespace associated with the sample manifests in `/config/samples`.

# Create the `top-speed` namespace if it doesn't exist
kubectl create namespace top-speed || true
Copy link
Copy Markdown
Contributor

@austince austince May 1, 2020

Choose a reason for hiding this comment

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

Do you think we could keep this in? Installing the VVP with the additional namespace support was failing for me yesterday if the namespace didn't already exist.

@@ -0,0 +1,55 @@
# Install cert-manager

Install the CustomResourceDefinition resources separately.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This is great! Could we also just add a link to their official install guide in case this becomes outdated?

Comment thread docs/guides/deployment.md
# Using the Cert created by the operator chart for serving webhooks.
# Pointed at the webhook conversion service of the operator.
### For helm 3:
# Try dryrun to check the rendered templates
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks for adding the Helm 3 docs! Do you think we could remove the dry run bits though? I think it would be best if people could just run each of these commands and have it deploy without modification.

Comment thread docs/guides/deployment.md
Comment on lines +59 to +65
NOTE: If you don't have cert-manager you may get following error:

```bash
Error: Internal error occurred: failed calling webhook "webhook.cert-manager.io": Post https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=30s: no endpoints available for service "cert-manager-webhook"
```

To deploy cert-manager[`check out this guide`](./cert-manager.md)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

What do you think about moving this to the top of the guide where Cert-Manager is mentioned?

Comment thread docs/guides/deployment.md
## Or, for the Community Edition
For helm 2:

```bash
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think these extra ```bash sections are throwing off something with rendering. Could we remove them and just keep the whole thing in the ```shell block?

@austince austince linked an issue May 1, 2020 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants