chore: Fixed namespace doc for Crossplane Example #1068
Merged
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.
Instruction to list pods in
crossplane
namespace does not work, as the namespace created through blueprint iscrossplane-system
.What does this PR do?
This [minor] PR updates the Readme.md file to fix the specified namespace name to
crossplane-system
.$ kubectl get pods -n crossplane No resources found in crossplane namespace. $ kubectl get pods -n crossplane-system NAME READY STATUS RESTARTS AGE aws-provider-f78664a342f1-b56dc7c4b-m2q49 1/1 Running 0 3m20s crossplane-5696d784b8-26xps 1/1 Running 0 5m57s crossplane-rbac-manager-8466dfb7fc-4l8tr 1/1 Running 0 5m57s jet-aws-provider-b42c59584ad8-6b4c7685dc-8bdj7 1/1 Running 0 3m41s
Motivation
More
pre-commit run -a
with this PRNote: Not all the PRs require a new example and/or doc page. In general:
docs/add-ons/*
is required for new a new addonFor Moderators
Additional Notes
I stan EKS Blueprints ❤️