Feature-Son/wordpress ingress #7
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
hungran
reviewed
Nov 18, 2025
Author
There was a problem hiding this comment.
mấy file này e tạo thừa lúc tạo folder để đẩy lên git
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 pull request adds a complete set of Kubernetes manifests to deploy a WordPress application backed by a MySQL database, including persistent storage, secrets management, and ingress configuration. The changes enable secure and scalable deployment of WordPress in a dedicated namespace, with proper separation of resources and access.
WordPress and MySQL Deployment
wordpress.yamlmanifest to deploy WordPress using aDeployment, expose it via aService, and persist content with aPersistentVolumeClaim(wordpress-pvc). Environment variables for database connection are securely sourced from secrets.mysql-deployment.yamlmanifest to deploy MySQL with aDeployment, expose it via aService, and persist data using aPersistentVolumeClaim(mysql-pvc). Database credentials are managed through Kubernetes secrets.Persistent Storage Configuration
mysql-pv-pvc.yamlmanifest to define aPersistentVolumeandPersistentVolumeClaimfor MySQL data, ensuring database persistence across pod restarts.Secrets Management
mysql-secret.yamlmanifest to securely store MySQL root and user passwords as Kubernetes secrets, referenced by both WordPress and MySQL deployments.Ingress Setup
ingress.yamlmanifest to expose the WordPress service externally via an NGINX ingress, mapping the hostnamewordpress.localto the WordPress service.