Skip to content

Conversation

@VajiraPrabuddhaka
Copy link
Contributor

@VajiraPrabuddhaka VajiraPrabuddhaka commented Dec 14, 2025

Purpose

$subject

Related Issues

openchoreo/openchoreo#698

Checklist

  • Updated sidebars.ts if adding a new documentation page
  • Run npm run start to preview the changes locally
  • Run npm run build to ensure the build passes without errors
  • Verified all links are working (no broken links)

sidebars.ts Outdated
{
type: 'category',
label: 'Operations Guide',
label: 'Operational Guides',
Copy link
Contributor

Choose a reason for hiding this comment

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

How about Operator Manual, as this is an in-depth technical documentation?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

+1 for Operator Manual

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated as Operator Manual


Before you begin, ensure you have:

- An OpenChoreo installation (see "Get Started" section for installation options)
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we add the link to the installation page?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I tried, but we can't add link because, here we can't specifically say which type of installation we follow. Also can't link to the top level "Get Started" section.


```text
.
├── organization/ # organization and namespace
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this the same when organization units are introduced?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, I think we have to change this when org units are introduced.

│ SecretReference │
│ (OpenChoreo abstraction) │
└──────────────────┬──────────────────┘
│ Controller converts to
Copy link
Contributor

Choose a reason for hiding this comment

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

Not all secret references are converted to. Therefore, we need to modify this slightly.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated this as just Coverts to (removed Controller part). Any way we have to somehow conver that to ExternalSecret right? I think we should have a proper documentation for Secret management and point from here to there. Until that shall we keep this?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, but we need to mention that not all secret references are converted to external secrets when the secret reference is created. It might be created by different controllers when needed/referenced in other CRs.

@chalindukodikara
Copy link
Contributor

If we have a sample repository in OpenChoreo Org, it would be easy for users to get an idea. wdyt? @VajiraPrabuddhaka

@VajiraPrabuddhaka
Copy link
Contributor Author

If we have a sample repository in OpenChoreo Org, it would be easy for users to get an idea. wdyt? @VajiraPrabuddhaka

Yes we can provide a sample repository. Will do it.

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.

3 participants