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

Improve K8s demo setup instructions #332

Closed
wants to merge 1 commit into from
Closed

Conversation

ligaz
Copy link
Contributor

@ligaz ligaz commented Sep 12, 2024

What this PR changes/adds

This change adds small improvements to the K8s demo setup instructions.

Why it does that

I just went through the demo setup instruction from the command line and hit some of this small issues.

This change adds small tweaks to the K8s setup instructions.
Copy link
Member

@paullatzelsperger paullatzelsperger left a comment

Choose a reason for hiding this comment

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

this PR contributes no value, please close it.

@@ -328,6 +328,8 @@ Once all the deployments are up-and-running, the seed script needs to be execute
output similar to this:

```shell
# We are in `/deployment` and we need to go back to the root where the seed script resides
❯ cd ..
Copy link
Member

Choose a reason for hiding this comment

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

this is not needed, as the documentation states that "every command executes from the root directory, unless stated otherwise"

@@ -293,7 +293,7 @@ terraform init
terraform apply
```

Once Terraform has completed the deployment, type `kubectl get pods` and verify the output:
Once Terraform has completed the deployment, type `kubectl get pods --namespace mvd` and verify the output:
Copy link
Member

Choose a reason for hiding this comment

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

not needed, the subsequent code example shows exactly that.

@ligaz
Copy link
Contributor Author

ligaz commented Sep 12, 2024

Closing the PR as the maintainers believe it doesn't provide significant value at this time. However, it can still serve as a helpful reference for others encountering similar issues in the future.

@ligaz ligaz closed this Sep 12, 2024
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