docs: port removal of ControllerConfig refs in troubleshooting guide to v1.18 #854
Conversation
This file contains 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
…to v1.18 This was missed in crossplane#822. Signed-off-by: Jared Watts <[email protected]>
✅ Deploy Preview for crossplane ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
tr0njavolta
approved these changes
Jan 16, 2025
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.
This PR simply ports the removal of
ControllerConfigrefs in troubleshooting guide to v1.18. This was missed in #822, which may have accidentally ported it to v1.17 instead of v1.18. The date on that PR was after the v1.18 release, so I think it was just an accident.I noticed this today when trying to reference how to enable DEBUG logs for providers in https://docs.crossplane.io/v1.18/guides/troubleshoot-crossplane/#provider-logs today for someone and being surprised there was still a
ControllerConfigreference in there.