-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Solution RBC #34
base: main
Are you sure you want to change the base?
Solution RBC #34
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your hard work on this pull request! 😊 While your implementation is mostly correct and meets many of the task requirements, there is a critical issue that needs to be addressed before we can approve it. The Role
in your RBAC configuration currently only grants access to 'pods'. If the intention is to allow the service account to read secrets, you should include 'secrets' in the resources list. This is essential for the functionality of your solution. Please make this adjustment, and feel free to reach out if you need any assistance. Keep up the great work! 🚀
✨ Please rate this review in the Platform's notification center. I will be grateful for your feedback! ✨
🔄 Fix the issues, commit the changes, and then re-request my review using the Re-request review
button in the Reviewers tab.
.infrastructure/security/rbac.yml
Outdated
namespace: todoapp | ||
rules: | ||
- apiGroups: [""] | ||
resources: ["pods"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The current role only grants access to 'pods'. If the intention is to allow the service account to read secrets, you should include 'secrets' in the resources list. For example: resources: ["pods", "secrets"].
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job on configuring the deployment for the todoapp
! 🎉 Your setup is mostly correct, with appropriate use of volumes, environment variables, and probes. However, ensure that the serviceAccountName
(secrets-reader
) has the necessary permissions to access the secrets and config maps, which is crucial for the application's functionality.
Your RBAC configuration is spot on, including both 'pods' and 'secrets' in the resources list for the secrets-reader
role, and the RoleBinding is correctly set up. The bootstrap script is well-structured, but double-check that all referenced files exist and are correctly configured to avoid deployment issues.
Overall, your code meets the task requirements and constraints, and all necessary files are present and correctly configured. No further changes are needed. Keep up the good work and continue to refine your skills! 🚀
Remember, addressing any issues mentioned will help you improve and avoid similar problems in the future. Keep learning and growing! 🌟
✨ Please rate this review in the Platform's notification center. I will be grateful for your feedback! ✨
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGMT!
No description provided.