adding init

[robinmordasiewicz]

Adds an Ingress resource for the application in the Kubernetes cluster. The Ingress resource defines the routing rules for incoming traffic to the application.
The Ingress resource includes annotations specifying configuration details such as Fortiweb IP, login information, port, virtual server details, server policies, and more.

Additionally, the necessary changes have been made to the kustomization.yaml files to include the new Ingress resource for the application.

This enhancement allows for proper routing and configuration of incoming traffic to the application, improving the overall accessibility and security of the application within the Kubernetes environment.

[iacbot]

🔍 [Audit-Mode] Lacework analyzed your pull request. Here is the summary.

Static Analysis: ⚠️ Found 8 violations in this pull request.

• Critical : 0
• High : 1
• Medium : 3
• Low : 4
• Info : 0

Violation	Severity	File	Guidelines
Use read-only filesystem for containers where possible	High	kustomization.yaml	VIEW
Image Pull Policy should be Always	Medium	kustomization.yaml	VIEW
Memory limits should be set	Medium	kustomization.yaml	VIEW
Minimize the admission of containers with capabilities assigned	Medium	kustomization.yaml	VIEW
Ensure that Service Account Tokens are only mounted where necessary	Low	kustomization.yaml	VIEW
Ensure that the seccomp profile is set to docker/default or runtime/default	Low	kustomization.yaml	VIEW
Liveness Probe Should be Configured	Low	kustomization.yaml	VIEW
Readiness Probe Should be Configured	Low	kustomization.yaml	VIEW

💬 Share your feedback with us.