docs(orc8r): improve Minikube deployment guide - #80
Open
AmraniCh wants to merge 1 commit into
Open
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
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.
Context
This PR follows #16032 and updates the existing Orc8r Minikube deployment guide.
The current documentation uses Kubernetes v1.20, which is no longer supported by modern Minikube releases. The guide has been updated to use Kubernetes v1.28 and to reflect the steps required to deploy Orc8r successfully on a current Minikube environment.
Summary
This PR improves the Orc8r Minikube deployment guide by:
Test Plan
Followed the updated guide and validated the deployment on Kubernetes v1.28.0 using Minikube.
Verified that the Orc8r Helm charts can be installed and the required pods reach the
Runningstate.Additional Information
The Kubernetes v1.28 deployment relies on the Helm chart API updates introduced in #16032.
Security Considerations
No security impact.