Skip to content

Conversation

@paigecalvert
Copy link
Contributor

@paigecalvert paigecalvert commented Nov 21, 2024

@replicated-ci replicated-ci added type::docs Improvements or additions to documentation type::feature labels Nov 21, 2024
@netlify
Copy link

netlify bot commented Nov 21, 2024

Deploy Preview for replicated-docs ready!

Name Link
🔨 Latest commit 6e58bf0
🔍 Latest deploy log https://app.netlify.com/sites/replicated-docs/deploys/675214c8ed84760008771c43
😎 Deploy Preview https://deploy-preview-2849--replicated-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@netlify
Copy link

netlify bot commented Nov 21, 2024

Deploy Preview for replicated-docs-upgrade ready!

Name Link
🔨 Latest commit 6e58bf0
🔍 Latest deploy log https://app.netlify.com/sites/replicated-docs-upgrade/deploys/675214c8f9130600083a55b7
😎 Deploy Preview https://deploy-preview-2849--replicated-docs-upgrade.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

{
type: 'category',
label: 'Vendor Portal Teams and Accounts',
label: 'Vendor Portal',
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Nest all the vendor portal features (like channels and releases, customers, teams and accounts, etc) under a Vendor Portal drop down

{
type: 'category',
label: 'Channels and Releases',
label: 'Compatibility Matrix',
Copy link
Contributor Author

@paigecalvert paigecalvert Nov 21, 2024

Choose a reason for hiding this comment

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

^ Figured we'd want this to be at its own level rather than nesting under VP

{
type: 'category',
label: 'Querying License Entitlements',
label: 'Installing with Embedded Cluster',
Copy link
Contributor Author

Choose a reason for hiding this comment

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

EC install docs are under Embedded Cluster section instead of under KOTS

{
type: 'category',
label: 'Packaging KOTS Releases',
label: 'Configuring KOTS',
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Packaging KOTS Releases --> Configuring KOTS

"Configuring KOTS" seemed like it would be less loaded and more just directly explaining the contents of the topics in this section. "Packaging KOTS Releases" came about when the Vendor Portal have you the option to create a KOTS Release or Helm-Only Release

{
type: 'category',
label: 'Distributing Helm Charts with KOTS',
label: 'Configuring the HelmChart Custom Resource',
Copy link
Contributor Author

@paigecalvert paigecalvert Nov 21, 2024

Choose a reason for hiding this comment

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

^ Same here, these topics are just how to configure the HelmChart custom resource. "Distributing Helm Charts with KOTS" might imply that you are doing this for KOTS existing cluster installs specifically

{
type: 'category',
label: 'Admin Console Config Screen',
label: 'Configuring the Admin Console Config Screen',
Copy link
Contributor Author

Choose a reason for hiding this comment

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

^ Verb-ify

label: 'Exposing Services',
items: [
'vendor/admin-console-port-forward',
'vendor/kurl-nodeport-services',
Copy link
Contributor Author

Choose a reason for hiding this comment

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

'vendor/admin-console-port-forward',

Moved this to the Customizing the Admin Console section

'vendor/kurl-nodeport-services',

Moved this to the kURL section

sidebars.js Outdated
'vendor/packaging-ingress',
],
},
'vendor/packaging-using-tls-certs',
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Didn't have a great home for this one yet, but left it under KOTS. Follow up story to split this topic up because it contains both KOTS existing and kURL info

import ConfigValuesExample from "../partials/configValues/_configValuesExample.mdx"
import ConfigValuesProcedure from "../partials/configValues/_config-values-procedure.mdx"

# Installing with Embedded Cluster from the Command Line
Copy link
Contributor Author

@paigecalvert paigecalvert Nov 21, 2024

Choose a reason for hiding this comment

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

EC gets its own install automation topic in its own section

In a follow up PR, could also consider making sure that each of the command line install topics are discoverable from the CI/CD section of the docs where people might need the info


<ConfigValuesExample/>

<ConfigValuesProcedure/>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

^ info about generating the configvalues file is added to a partial rather than being in its own topic. This solved the problem of trying to find a home for a topic that cut across three different installers


## Firewall Openings for Online Installations

<FirewallOpenings/> No newline at end of file
Copy link
Contributor Author

Choose a reason for hiding this comment

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

^ note that I decided to just put the firewall openings for online installs in a partial for now. It appears in each of the installer requirements topics

import EmbeddedClusterPortRequirements from "../partials/embedded-cluster/_port-reqs.mdx"
import FirewallOpenings from "../partials/install/_firewall-openings.mdx"

# Embedded Cluster Installation Requirements
Copy link
Contributor Author

Choose a reason for hiding this comment

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

New embedded cluster-specific installation requirements topic

import FirewallOpenings from "../partials/install/_firewall-openings.mdx"

# Installation Requirements
# KOTS Installation Requirements
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removed all the EC and kURL stuff and called this KOTS Install Reqs

import DownloadkURLBundle from "../partials/install/_download-kurl-bundle.mdx"
import ExtractKurlBundle from "../partials/install/_extract-kurl-bundle.mdx"

# Installing with kURL from the Command Line
Copy link
Contributor Author

Choose a reason for hiding this comment

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

kURL also gets its own command line install topic


For more information about installing from the command line, see [Installing from the Command Line](/enterprise/installing-existing-cluster-automation).

## Get the ConfigValues File
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This procedure was moved to a partial to be used in each of the topics on installing from the command line

value: hello world
```
## Share a Sample ConfigValues File
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 didn't put this content anywhere else yet (ie, this would just get deleted). Not sure if people are using it, but if they are, this could go in a section in the Onboarding docs about "supporting CLI installs for your users" or something like that

@@ -0,0 +1,29 @@
# Reset a kURL Cluster
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Moved this existing content out of a kots topic about deleting the admin console. Could also just remove this content all together rather than creating this new topic. Not sure if we really recommend the reset command for kurl anyway

{
type: 'category',
label: 'Distributing and Installing with KOTS',
label: 'KOTS',
Copy link
Contributor Author

Choose a reason for hiding this comment

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

^ KOTS section = docs for things that are features of the KOTS product (snapshots, KOTS custom resources, KOTS template functions, Status Informers, etc). Additionally, the docs for how to install with KOTS in an existing cluster will also appear here.

@@ -1,59 +1,41 @@
# About Installing an Application
# Considerations Before Installing
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Some MVP edits to this topic to remove the info about "embedded" stuff

import GenerateBundle from "../partials/support-bundles/_generate-bundle.mdx"
import GenerateBundleAdminConsole from "../partials/support-bundles/_generate-bundle-admin-console.mdx"

# Generating Support Bundles from the Admin Console
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 so this is just Admin Console related to differentiate from the other existing topics on generating SBs

@paigecalvert paigecalvert marked this pull request as ready for review December 2, 2024 15:40
@paigecalvert paigecalvert requested a review from a team as a code owner December 2, 2024 15:40
sidebars.js Outdated
'enterprise/delete-admin-console',
{
type: 'category',
label: 'Using a GitOps Workflow (Deprecated)',
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 "deprecated" label but I don't think that's accurate (yet?)

@paigecalvert paigecalvert merged commit 709d72d into main Dec 5, 2024
5 checks passed
@paigecalvert paigecalvert deleted the move-ec branch December 5, 2024 21:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type::docs Improvements or additions to documentation type::feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants