adding init #601
Merged
adding init #601
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.
Introduces the following changes:
In the
HelmRelease.yamlfile, the version of thefortiweb-ingress-controllerhas been updated to "1.0.0-1". This change ensures that the correct version is being used in the deployment process.In the
fortiweb.conffile undercloud-init, several configurations have been adjusted to enhance the settings for the FortiWeb infrastructure. Changes include enabling file uploads, adjusting system settings, configuring dashboard widgets, setting up static routers, firewall policies, and defining firewall rules for various services.These modifications aim to improve the functionality and security of the FortiWeb infrastructure by fine-tuning the configurations and ensuring that the necessary settings are in place for a more robust deployment.