adding init #497
Merged
adding init #497
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
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.
Involves commenting out the existing initContainer configuration in the Deployment.yaml file for the dvwa application. The initContainer was responsible for initializing the service with specific configuration data.
The reason for this change is to temporarily disable the initContainer functionality. By commenting out this section, we prevent the initContainer from executing during the deployment process. This can be useful for troubleshooting or testing purposes where the initContainer functionality is not required.
Overall, this change provides flexibility in managing the initialization process of the dvwa application by allowing the initContainer to be easily enabled or disabled as needed.