#452 - Adding support for Kubernetes Gateway API (such as HTTPRoute) #453
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
…template with new apiGroups and resources.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 introduces updates to the Kubernetes gateway route handling and enhances RBAC configurations to ensure proper API access permissions.
Open Issue: #452
Modified Files:
useKubernetes.jsrbac.yamlDetails:
flame.pawelmalak/typeannotation to filter and surface relevant routes to the application.apiGroups,resources, andverbs. This ensures the Flame application has the appropriate permissions to access the required Kubernetes API endpoints.These changes aim to enhance the application's functionality and security by leveraging Kubernetes' native capabilities for managing access and routing.