Conversation
WalkthroughThe pull request updates the Dockerfile, docker-compose.yml, and several Kubernetes configuration files. In the Dockerfile, the Maven and OpenJDK base images are updated, the working directory is changed from Changes
Suggested reviewers
Poem
Tip ⚡💬 Agentic Chat (Pro Plan, General Availability)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
Dockerfile (2)
1-4: Updated Build Stage Configuration: Verify Base Image and Working Directory ChangesThe builder stage now uses the image
maven:3.9.6-eclipse-temurin-17-alpineand sets the working directory to/app, which is a consistent change from the previous/src. This update reflects an intentional upgrade in Maven and JDK while streamlining the working directory.
7-12: Revised Final Stage Settings: Base Image and JAR HandlingIn the final stage, the image has been updated to
openjdk:17-slim, and the working directory remains/app. TheCOPYcommand now explicitly copies the generated JAR from/app/target/*.jarto/app/target/bank.jar. Finally, the CMD instruction correctly launches the application withCMD ["java","-jar","/app/target/bank.jar"].
- Note: Ensure your Maven build produces a JAR that is correctly named or that the globbing pattern uniquely matches the intended file.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
Dockerfile(1 hunks)docker-compose.yml(1 hunks)
🔇 Additional comments (7)
Dockerfile (1)
4-5: Build Command ConfirmationThe
COPY . .instruction and the subsequent Maven build command (RUN mvn clean install -DskipTests=true) appear correct and align with the new context.docker-compose.yml (6)
6-8: MySQL Service Environment Variable UpdatesThe environment variables for the
mysqlservice have been reformatted into key-value pairs, and the database name is updated tobankappdb. This change improves readability and ensures consistency with the application’s configuration.
9-10: Exposing Ports for MySQL ServiceThe addition of the
portssection (mapping "3306:3306") is a valuable enhancement, allowing for proper port forwarding and external access during development/testing.
17-19: Main Application Service: Image and Container Name RevisionFor the
mainappservice, the image reference is now hard-coded asbankapp:latestand the container name has been enclosed in quotes. This static reference can simplify deployment consistency, but please ensure that the image is updated externally whenever a new build is available.
20-23: Environment Variable Reformatting for MainappThe environment variables under
mainappare reformatted properly and now reference the updated database name (bankappdb) in the datasource URL. This synchronization between the Dockerfile’s configurations and the docker-compose settings is essential for proper connectivity.
26-27: Simplified Dependency ConfigurationThe
depends_onsection now simply lists- mysqlwithout any health check conditions. This simplification is acceptable if the application can handle service readiness; otherwise, consider adding a wait mechanism if startup timing becomes an issue.
37-38: Volume Declaration FormattingThe volume declaration under
volumesis maintained with the updated indentation. Verify that the volumebankapp-volumeis correctly created and mapped as intended.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (4)
kubernetes/mysql-service.yaml (1)
9-15: Service Spec Formatting & Headless Service ConfigurationThe addition of
clusterIP: Nonecorrectly configures the service as headless. However, static analysis flagged a trailing space on line 11 and an indentation warning on line 13. Consider making the following adjustments to satisfy YAML formatting standards:- app: mysql + app: mysql - - protocol: TCP + - protocol: TCPThese nitpicks will help avoid potential YAML parsing issues.
🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 11-11: trailing spaces
(trailing-spaces)
[warning] 13-13: wrong indentation: expected 4 but found 3
(indentation)
kubernetes/secrets.yaml (1)
11-11: Remove Trailing Spaces.
Static analysis has flagged trailing spaces on line 11. Removing these will help maintain clean YAML formatting.🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 11-11: trailing spaces
(trailing-spaces)
kubernetes/bankapp-deployment.yml (2)
22-23: Fix Indentation and Remove Trailing Spaces in Ports Configuration.
Static analysis has flagged an indentation issue on line 22 (expected indentation of 8 spaces instead of 10) and trailing spaces on line 23. Please adjust these to conform with YAML standards. For example:- - containerPort: 8080 + - containerPort: 8080🧰 Tools
🪛 YAMLlint (1.35.1)
[warning] 22-22: wrong indentation: expected 8 but found 10
(indentation)
[error] 23-23: trailing spaces
(trailing-spaces)
45-59: Clean Up Commented Probe Sections.
The commented-out liveness and readiness probe blocks contain several trailing spaces (notably on lines 49, 50, 55, 57, and 58). Consider cleaning these up to improve file readability.🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 49-49: trailing spaces
(trailing-spaces)
[error] 50-50: trailing spaces
(trailing-spaces)
[error] 55-55: trailing spaces
(trailing-spaces)
[error] 57-57: trailing spaces
(trailing-spaces)
[error] 58-58: trailing spaces
(trailing-spaces)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (12)
kubernetes/bankapp-deployment.yml(1 hunks)kubernetes/bankapp-hpa.yml(0 hunks)kubernetes/bankapp-ingress.yml(0 hunks)kubernetes/bankapp-namespace.yaml(1 hunks)kubernetes/bankapp-service.yaml(1 hunks)kubernetes/configmap.yaml(1 hunks)kubernetes/letsencrypt-clusterissuer.yaml(0 hunks)kubernetes/mysql-deployment.yml(2 hunks)kubernetes/mysql-service.yaml(1 hunks)kubernetes/persistent-volume-claim.yaml(1 hunks)kubernetes/persistent-volume.yaml(1 hunks)kubernetes/secrets.yaml(1 hunks)
💤 Files with no reviewable changes (3)
- kubernetes/letsencrypt-clusterissuer.yaml
- kubernetes/bankapp-hpa.yml
- kubernetes/bankapp-ingress.yml
🧰 Additional context used
🪛 YAMLlint (1.35.1)
kubernetes/mysql-service.yaml
[error] 11-11: trailing spaces
(trailing-spaces)
[warning] 13-13: wrong indentation: expected 4 but found 3
(indentation)
kubernetes/secrets.yaml
[error] 11-11: trailing spaces
(trailing-spaces)
kubernetes/bankapp-deployment.yml
[warning] 22-22: wrong indentation: expected 8 but found 10
(indentation)
[error] 23-23: trailing spaces
(trailing-spaces)
[error] 49-49: trailing spaces
(trailing-spaces)
[error] 50-50: trailing spaces
(trailing-spaces)
[error] 55-55: trailing spaces
(trailing-spaces)
[error] 57-57: trailing spaces
(trailing-spaces)
[error] 58-58: trailing spaces
(trailing-spaces)
🔇 Additional comments (22)
kubernetes/bankapp-namespace.yaml (1)
1-5: Namespace Update ConfirmationThe update sets the API version explicitly to
v1and renames the namespace tobank(with the removal of previously attached labels). This simplifies the configuration. Please ensure that all dependent resources are updated to reference the new namespace.kubernetes/mysql-service.yaml (1)
2-5: Service Metadata UpdateThe update of
apiVersionand the assignment of the namespace (bank) in the metadata are correctly applied. This is consistent with the broader namespace renaming.kubernetes/persistent-volume-claim.yaml (1)
1-13: PersistentVolumeClaim (PVC) UpdateThe PVC configuration has been updated as follows:
- Renamed to
bank-pvc- Namespace updated to
bank- A new
storageClassName: standardfield is introduced- Requested storage reduced from 10Gi to 5Gi
These changes look intentional. Just verify that the reduced storage capacity meets the application’s needs and that the corresponding PersistentVolume is updated accordingly.
kubernetes/persistent-volume.yaml (1)
1-17: PersistentVolume (PV) Update and Field Removal CheckThe PV has been renamed to
bank-pv, its namespace updated tobank, storage capacity reduced to 5Gi, and the host path updated to/mnt/data. The inclusion ofstorageClassName: standardensures consistency with the PVC settings. Please confirm that the removal of fields such asvolumeModeandpersistentVolumeReclaimPolicyis intentional and aligns with your volume management strategy.kubernetes/configmap.yaml (1)
1-10: ConfigMap Update VerificationThe ConfigMap now uses the new name
bank-configmapand is assigned to thebanknamespace. TheSPRING_DATASOURCE_URLhas been simplified by removing the namespace from the JDBC URL, which is ideal for internal service resolution. Please ensure that all consuming deployments and configurations have been updated accordingly.kubernetes/secrets.yaml (4)
2-2: Set API Version Explicitly.
TheapiVersion: v1declaration now appears on line 2, ensuring consistency with Kubernetes API conventions.
4-5: Update Metadata for Secret.
The secret’s metadata has been updated with the new name (bank-secret) and namespace (bank). This change aligns with the revised resource naming conventions across the deployment files.
7-7: Secret Type Casing Adjustment.
Thetypefield is now set toopaque(all lowercase). Double-check that downstream consumers expect this casing.
9-10: Quote Data Values for Clarity.
BothMYSQL_ROOT_PASSWORDandSPRING_DATASOURCE_PASSWORDnow have their Base64 encoded values enclosed in quotes. This improves clarity and avoids YAML parsing pitfalls.kubernetes/bankapp-service.yaml (2)
2-5: Service Metadata and API Version Updates.
The service now usesapiVersion: v1, is namedbank-svc, and is placed in thebanknamespace. This update harmonizes the service’s metadata with the new naming standards.
8-14: Refined Selector and Port Configuration.
The selector has been updated toapp: bankappand the ports section now includes anodePort: 30080along with the TCP protocol declaration. These changes ensure that external access is correctly routed to the service and that the service configuration aligns with the new deployment architecture.kubernetes/mysql-deployment.yml (5)
1-10: Transition to StatefulSet for MySQL.
The deployment has been refactored from a Deployment to a StatefulSet with updates to the metadata (name changed tomysql-setand namespace tobank), and the specifications now include a dedicatedserviceName(mysql-svc) with an increased replica count of 2. This change is critical for ensuring stateful behavior and persistent storage management for MySQL.
20-23: Container Specification Update.
The container definition now reflects a new name (mysql-pod) and an updated image tag (mysql:latest). The port configuration (containerPort 3306) is maintained, but please verify that thelatesttag meets production stability requirements.
25-30: Updated Secret Reference for MySQL Root Password.
The environment variableMYSQL_ROOT_PASSWORDnow correctly sources its value from the secretbank-secret. This aligns the MySQL deployment with the updated secret configuration.
31-35: Updated ConfigMap Reference for MYSQL_DATABASE.
Similarly, theMYSQL_DATABASEenvironment variable now retrieves its value from thebank-configmapinstead of the previous configuration. This ensures consistency across the configuration files.
36-49: Volume Mount and Persistent Volume Claim Enhancements.
The volume mount name has been updated tomysql-data, and a newvolumeClaimTemplatessection is introduced with defined access modes, storage class (standard), and a storage request of5Gi. This enhances data persistence and management.kubernetes/bankapp-deployment.yml (6)
2-7: Deployment Metadata and API Version Revisions.
The deployment now declaresapiVersion: apps/v1and updates its metadata with the new name (bank-deployment), namespace (bank), and label (app: bankapp). These changes are consistent with the overall renaming and restructuring strategy.
9-12: Scaled Replica and Selector Update.
Increasing the replica count to 3 and updating the matching selector label tobankappimproves redundancy and ensures that the service selector correctly targets the intended pods.
16-20: Container Specification Modernization.
The container is now renamed tobank-podand uses the updated imageswayamnakshane/bank:latest. Verify that the new image tag is thoroughly tested in your staging environment before rolling out to production.
25-30: Secret Reference for SPRING_DATASOURCE_PASSWORD.
The environment variable now correctly referencesbank-secretforSPRING_DATASOURCE_PASSWORD, ensuring that sensitive credentials are managed consistently.
32-36: ConfigMap Reference for SPRING_DATASOURCE_USERNAME.
The change updates the reference tobank-configmapforSPRING_DATASOURCE_USERNAME, which streamlines configuration management.
38-42: ConfigMap Reference for SPRING_DATASOURCE_URL.
The environment variable now pulls theSPRING_DATASOURCE_URLfrombank-configmap, further consolidating configuration references.
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (3)
kubernetes/mysql-service.yaml (2)
11-11: Trailing Whitespace IssueA trailing space is present at the end of the selector line (
app: mysql). Removing it will resolve the YAML lint error.Apply this diff suggestion:
- app: mysql + app: mysql🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 11-11: trailing spaces
(trailing-spaces)
13-13: Indentation Issue in PortsThe YAML linter indicates that the list item under
ports:is indented with 3 spaces instead of the expected 4. Ensure consistent indentation for proper YAML parsing.A possible diff fix:
- - protocol: TCP + - protocol: TCP🧰 Tools
🪛 YAMLlint (1.35.1)
[warning] 13-13: wrong indentation: expected 4 but found 3
(indentation)
kubernetes/mysql-deployment.yml (1)
20-23: Container Image UpdateThe container specification now uses the name
"mysql-pod"and the image tag"mysql:latest". Using thelatesttag in production is not recommended due to unpredictability in versioning. Consider pinning to a specific, tested version.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
kubernetes/mysql-deployment.yml(2 hunks)kubernetes/mysql-service.yaml(1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
kubernetes/mysql-service.yaml
[error] 11-11: trailing spaces
(trailing-spaces)
[warning] 13-13: wrong indentation: expected 4 but found 3
(indentation)
🔇 Additional comments (3)
kubernetes/mysql-service.yaml (2)
2-5: Service Metadata UpdateThe service metadata now uses the name
"mysql"and namespace"bank", which aligns with your new naming conventions. Please ensure that all components referencing this service are updated accordingly.
9-9: Headless Service ConfigurationSetting
clusterIP: Noneconverts this service into a headless one. Confirm that this design meets your service discovery and load-balancing requirements within the cluster.kubernetes/mysql-deployment.yml (1)
40-50: Persistent Volume Claim ConfigurationThe
volumeClaimTemplatessection is defined correctly with the appropriate access mode (ReadWriteOnce), storage class (standard), and storage request (5Gi). Just ensure the storage class"standard"exists in your Kubernetes cluster.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
kubernetes/secrets.yaml (1)
11-11: Trailing Whitespace Detected
There are trailing spaces on line 11. Removing these extraneous spaces will help ensure adherence to YAML formatting best practices.🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 11-11: trailing spaces
(trailing-spaces)
kubernetes/mysql-deployment.yml (1)
21-22: Container Image Versioning
The container configuration now uses the namemysql-podand updates the image tomysql:latest. Using thelatesttag can introduce unpredictability if a new image is released unexpectedly. Consider pinning the image to a specific version (for example,mysql:8.0) to ensure consistent behavior across deployments.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
kubernetes/mysql-deployment.yml(2 hunks)kubernetes/secrets.yaml(1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
kubernetes/secrets.yaml
[error] 11-11: trailing spaces
(trailing-spaces)
🔇 Additional comments (5)
kubernetes/secrets.yaml (1)
2-7: Metadata and Secret Type Updates
The metadata updates—changing the secret'snametobank-secretandnamespacetobank—are consistent with the new naming conventions. Thetypefield is now set to lowercase (opaque). Please verify that using lowercase for the secret type is acceptable for your Kubernetes cluster, as the standard value is typicallyOpaque.kubernetes/mysql-deployment.yml (4)
1-12: StatefulSet Metadata and Service Configuration
The metadata updates—includingname: mysql-dep,namespace: bank, and the addition ofserviceName: mysqlwith an increased replica count of 2—are well aligned with the updated deployment architecture and naming conventions.
37-38: Volume Mount Configuration
The volume mount formysql-datais correctly configured and matches the new volume claim setup defined later in the file.
39-52: Liveness and Readiness Probes
The liveness and readiness probes are appropriately set up withmysqladmin pingcommands along with initial delay and period configurations, which should help ensure the container’s health and readiness.
53-62: Volume Claim Templates Setup
The volume claim templates formysql-datacorrectly define access modes, a storage class (standard), and a storage request of 5Gi. This configuration is consistent with the new resource requirements.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
kubernetes/bankapp-deployment.yml (2)
22-23: YAML Indentation and Trailing Whitespace
- Indentation: The YAML linter indicates an indentation issue on line 22 (expected 8 spaces but found 10). Adjust the indentation to ensure YAML correctness.
- Trailing Spaces: Line 23 contains trailing whitespace. Removing these will improve file quality.
🧰 Tools
🪛 YAMLlint (1.35.1)
[warning] 22-22: wrong indentation: expected 8 but found 10
(indentation)
[error] 23-23: trailing spaces
(trailing-spaces)
45-60: Cleanup of Commented Liveness and Readiness ProbesThe commented-out sections for liveness and readiness probes include trailing spaces (notably on lines 49, 50, 55, 57, and 58). Although commented out, cleaning these trailing spaces would improve maintainability and ensure formatting consistency.
🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 49-49: trailing spaces
(trailing-spaces)
[error] 50-50: trailing spaces
(trailing-spaces)
[error] 55-55: trailing spaces
(trailing-spaces)
[error] 57-57: trailing spaces
(trailing-spaces)
[error] 58-58: trailing spaces
(trailing-spaces)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
kubernetes/bankapp-deployment.yml(1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
kubernetes/bankapp-deployment.yml
[warning] 22-22: wrong indentation: expected 8 but found 10
(indentation)
[error] 23-23: trailing spaces
(trailing-spaces)
[error] 49-49: trailing spaces
(trailing-spaces)
[error] 50-50: trailing spaces
(trailing-spaces)
[error] 55-55: trailing spaces
(trailing-spaces)
[error] 57-57: trailing spaces
(trailing-spaces)
[error] 58-58: trailing spaces
(trailing-spaces)
🔇 Additional comments (11)
kubernetes/bankapp-deployment.yml (11)
2-2: API Version UpdateThe API version has been updated correctly to
apps/v1, aligning with current Kubernetes standards.
4-5: Metadata Naming and Namespace UpdateThe deployment name (
bank-deployment) and namespace (bank) have been updated as intended, ensuring consistency with the new naming convention.
7-7: Consistent Label UsageThe label
app: bankappin the metadata is correctly maintained. This consistency between metadata and selectors is important for Kubernetes object matching.
9-9: Replica Count IncreaseIncreasing the replicas from 2 to 3 meets the intended scaling objective and is correctly reflected in the configuration.
12-12: Selector Label UpdateThe
matchLabelsunder the selector now correctly matchesapp: bankapp, which ensures that the pod template labels align with the selector criteria.
16-16: Pod Template Label ConsistencyThe pod template maintains the label
app: bankapp, which supports proper selection and rolling updates.
19-20: Container Name and Image UpdateThe container configuration has been updated with the new name
bank-podand imageswayamnakshane/bank. This update looks correct and aligns with the overall changes.
25-30: Environment Variable for Datasource PasswordThe environment variable
SPRING_DATASOURCE_PASSWORDis correctly configured to derive its value from the secretbank-secret. This change is correctly implemented.
32-36: Environment Variable Reference for UsernameThe configuration now correctly references the
bank-configmapforSPRING_DATASOURCE_USERNAME. This change meets the updated requirements.
38-42: Reintroduction of SPRING_DATASOURCE_URLReintroducing the
SPRING_DATASOURCE_URLenvironment variable with itsconfigMapKeyReffrombank-configmapis correctly implemented and displays the desired update.
61-67: Resource ConfigurationThe requests and limits for memory and CPU are set appropriately. The configurations help ensure that the pods will run within the expected resource boundaries.
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
kubernetes/bankapp-deployment.yml (2)
26-42: Simplify environment variable injection.
Instead of enumerating each key underenv, consider usingenvFromto import all secret and ConfigMap entries at once. This reduces verbosity and the risk of key omissions:- env: - - name: SPRING_DATASOURCE_PASSWORD - valueFrom: - secretKeyRef: - name: bank-secret - key: SPRING_DATASOURCE_PASSWORD - - name: SPRING_DATASOURCE_USERNAME - valueFrom: - configMapKeyRef: - name: bank-configmap - key: SPRING_DATASOURCE_USERNAME - - name: SPRING_DATASOURCE_URL - valueFrom: - configMapKeyRef: - name: bank-configmap - key: SPRING_DATASOURCE_URL + envFrom: + - secretRef: + name: bank-secret + - configMapRef: + name: bank-configmap
22-23: Cleanup trailing spaces and fix indentation.
YAMLLint reports trailing whitespace on lines 23, 49–50, 55–58 and an indentation warning at line 22. Please remove all trailing spaces and normalize indentation to two spaces per level so the file passes lint checks.Also applies to: 49-50, 55-58
🧰 Tools
🪛 YAMLlint (1.35.1)
[warning] 22-22: wrong indentation: expected 8 but found 10
(indentation)
[error] 23-23: trailing spaces
(trailing-spaces)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
kubernetes/bankapp-deployment.yml(1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
kubernetes/bankapp-deployment.yml
[warning] 22-22: wrong indentation: expected 8 but found 10
(indentation)
[error] 23-23: trailing spaces
(trailing-spaces)
[error] 49-49: trailing spaces
(trailing-spaces)
[error] 50-50: trailing spaces
(trailing-spaces)
[error] 55-55: trailing spaces
(trailing-spaces)
[error] 57-57: trailing spaces
(trailing-spaces)
[error] 58-58: trailing spaces
(trailing-spaces)
🔇 Additional comments (2)
kubernetes/bankapp-deployment.yml (2)
2-5: Deployment metadata updated correctly.
TheapiVersionhas been bumped toapps/v1, and the Deployment’snameandnamespacenow follow the newbank*naming convention.
7-16: Consistent app labeling.
Theapp: bankapplabel is now uniformly applied undermetadata.labels,selector.matchLabels, andtemplate.metadata.labels, ensuring that your ReplicaSet and Service selectors will correctly target these Pods.
| - name: bank-pod | ||
| image: swayamnakshane/mybank:latest | ||
| ports: | ||
| - containerPort: 8080 | ||
| - containerPort: 8080 |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Verify container port matches application listener.
The container is exposing port 8080, but upstream changes (Dockerfile/Docker‑compose) reference port 8081. Please confirm which port the Spring Boot app actually listens on—mismatch here will break readiness/liveness probes and Service routing.
🏁 Script executed:
#!/bin/bash
# Verify exposed port in Dockerfile and compose files
grep -R "EXPOSE" -n .
grep -R "8081" -n .Length of output: 411
🏁 Script executed:
#!/bin/bash
# Check for Spring Boot server port configuration and any 8080 references
grep -R "server.port" -n .
grep -R "application.properties" -n .
grep -R "application.yml" -n .
grep -R "8080" -n .Length of output: 1755
Update Dockerfile EXPOSE to match Spring Boot’s default port (8080)
All Kubernetes and Helm templates target port 8080 and no server.port override was found, so the Spring Boot app listens on 8080 by default. The Dockerfile still exposes 8081, which will cause confusion (e.g. with docker run -P).
• Dockerfile (line 11): change the exposed port to 8080
Suggested diff:
- EXPOSE 8081
+ EXPOSE 8080Committable suggestion skipped: line range outside the PR's diff.
🧰 Tools
🪛 YAMLlint (1.35.1)
[warning] 22-22: wrong indentation: expected 8 but found 10
(indentation)
2 participants
Summary by CodeRabbit
Chores
Style
New Features
Bug Fixes