docs: Add port to cloudAddr in Helm install command #298
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: jaehanbyun <[email protected]>
👷 Deploy request for docs-px-dev pending review.Visit the deploys page to approve it
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #297
This PR addresses an issue where the official Helm installation guide for the Pixie Operator provides a cloudAddr value without a port. This misconfiguration leads to gRPC connection failures in the vizier-operator, with errors such as
Consequently, the Pixie Edge Module (PEM) and Agent fail to deploy correctly.
To resolve this, the example Helm commands in the documentation have been updated to include the standard :443 port with the cloudAddr value. This ensures that users can follow the guide without encountering connection errors during installation.