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(self-managed): update OpenShift routes instructions #3997

Merged
merged 23 commits into from
Jul 23, 2024

Conversation

hamza-m-masood
Copy link
Contributor

Description

Related issue: https://github.com/camunda/distribution/issues/253
This PR updates the OpenShift routes page for 8.5.

When should this change go live?

  • This is a bug fix, security concern, or something that needs urgent release support.
  • This is already available but undocumented and should be released within a week.
  • This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
  • This is part of a scheduled alpha or minor. (apply alpha or minor label)
  • There is no urgency with this change and can be released at any time.

PR Checklist

  • My changes are for an already released minor and are in /versioned_docs directory.
  • My changes are for the next minor and are in /docs directory (aka /next/).

Copy link
Contributor

github-actions bot commented Jun 27, 2024

👋 🤖 ✅ Looks like the changes were ported across versions, nice job! 🎉

You can read more about the versioning within our docs in our documentation guidelines.

@hamza-m-masood hamza-m-masood self-assigned this Jun 27, 2024
@hamza-m-masood
Copy link
Contributor Author

hamza-m-masood commented Jun 27, 2024

The connector changes are only being added to 8.5 since within 8.6, zeebe gateway will have full support for rest. I will then open another PR to recommend the customer to use rest in zeebe gateway when openshift routes are configured. I can only create that PR once I have tested 8.6 zeebe.

@leiicamundi leiicamundi self-requested a review June 28, 2024 06:25
Copy link
Contributor

@leiicamundi leiicamundi left a comment

Choose a reason for hiding this comment

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

lgtm, I'll try the setup instructions later

good work, wp :)


```bash
#grab OpenShift generated tls crt
kubectl get secret -n camunda camunda-zeebe-gateway -o jsonpath="{.data['tls\.crt']}" | base64 --decode > tls.crt
Copy link
Contributor

Choose a reason for hiding this comment

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

As discussed in https://github.com/camunda/distribution/issues/254#issuecomment-2196227345, could we integrate this directly at the startup of the container?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@conceptualshark We continued our discussion and noticed that instead we should put a reference to a github issue in the docs: camunda/connectors#2806

Is it a good idea to put a link to a github issue in the docs or should I just mention that we are working on a fix that will not require this manual workaround and not add a link?

For now I will add a link and you can remove it if you think it's not appropriate.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

added link to github issue ✅

Copy link
Contributor

Choose a reason for hiding this comment

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

I think this reference is fine - we can make a note to remove it once the issue is closed.

@hamza-m-masood hamza-m-masood marked this pull request as ready for review June 28, 2024 14:41
@hamza-m-masood
Copy link
Contributor Author

@conceptualshark Please wait for @aabouzaid to approve the PR before you start your review. Thanks.

leiicamundi
leiicamundi previously approved these changes Jun 28, 2024
Copy link
Contributor

@leiicamundi leiicamundi left a comment

Choose a reason for hiding this comment

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

I checked both the content and the rendering, looks good!
nice work @hamza-m-masood 🚀

@christinaausley christinaausley added component:self-managed Docs and issues related to Camunda Platform 8 Self-Managed labels Jun 28, 2024
@akeller
Copy link
Member

akeller commented Jul 1, 2024

This PR updates the OpenShift routes page for 8.5.

Is there anything in this PR that should be ported to 8.6 (/next/)?

@aabouzaid aabouzaid changed the title feat: changes for routes docs(self-managed): update OpenShift routes instructions Jul 1, 2024
@aabouzaid
Copy link
Member

@akeller No change in the content, so Hamza will copy the same content to other versions once all reviewers are done.

@akeller akeller removed the target:8.5 label Jul 1, 2024
@@ -157,7 +157,7 @@ If you deploy Camunda 8 (and related infrastructure) with permissive SCCs out of

## Ingress Configuration

Before exposing services outside the cluster, we need an ingress component. Here's how you can configure it:
Before exposing services outside the cluster, we need an Ingress component. Here's how you can configure it:
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think we're consistent with ingress/Ingress casing across our docs. @conceptualshark WDYT? Do you think this warrants an issue for the backlog? Would you like to take a look at this across the SM docs?

Copy link
Contributor

Choose a reason for hiding this comment

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

👍 I can spin something off to go through this. I think the capitalization does a lot of work here.

@leiicamundi leiicamundi requested a review from Langleu July 16, 2024 12:08
aabouzaid
aabouzaid previously approved these changes Jul 18, 2024
Copy link
Member

@aabouzaid aabouzaid left a comment

Choose a reason for hiding this comment

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

LGTM, thank you 👍

@hamza-m-masood
Copy link
Contributor Author

hamza-m-masood commented Jul 18, 2024

@conceptualshark I am ready for your review. Thanks for waiting.
Please feel free to merge the PR when you are happy.

@Langleu
Copy link
Member

Langleu commented Jul 18, 2024

@hamza-m-masood I'm curious whether there's anything in place that regularly tests what's described in the docs?
So we don't get surprised by either OpenShift or Camunda changes.

@hamza-m-masood
Copy link
Contributor Author

Hi @Langleu good question! I have a PR for getting routes working on our CI. It's currently on pause at the moment because of the reasons listed in the PR. I will start working on it again when the routes operator is functional in our OpenShfit CI cluster.

@Langleu
Copy link
Member

Langleu commented Jul 18, 2024

awesome, great to see!

@christinaausley
Copy link
Contributor

@hamza-m-masood Ready to merge here, or waiting on additional review?

Copy link
Contributor

@conceptualshark conceptualshark left a comment

Choose a reason for hiding this comment

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

I made a few formatting adjustments that should hopefully improve readability, and updated a few lines. If these changes work for you, this is good to go from me, so I'm preemptively approving. 👍

@hamza-m-masood
Copy link
Contributor Author

@conceptualshark I'm happy with the changes you made. Looks great!
@christinaausley Please feel free to merge.

@christinaausley christinaausley merged commit 4370d92 into main Jul 23, 2024
7 checks passed
@christinaausley christinaausley deleted the routes-modification branch July 23, 2024 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component:self-managed Docs and issues related to Camunda Platform 8 Self-Managed
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

7 participants