Installation: Add Helm Parameter for Ingress

[elliotxx]

What would you like to be added?

Propose a new Helm parameter to optionally enable Ingress during installation.

Why is this needed?

Currently, users need to manually create an Ingress for Karpor. This enhancement would allow users to enable Ingress via a Helm flag, reducing manual steps and improving deployment flexibility.

Expected Benefits:

• Simplified Ingress setup during installation
• Better out-of-the-box experience
• Reduced manual configuration needed

Proposed Implementation:

• Add a new boolean flag in the Helm chart (e.g., --enable-ingress)
• Generate Ingress YAML automatically if flag is set
• Provide default configuration with reasonable settings
• Allow additional customizations if needed

This would streamline the deployment process and improve the overall user experience.

[ashwini897]

i would like to help on this task

[fanfan-yu]

Welcome! You can help on this task according to [https://www.kusionstack.io/karpor/developer-guide/contribution-guide/](contribution guide)

[ashwini897]

Proposed Changes:
Create an ingress.yml template file to define the Ingress resource.
Add an ingress.enabled flag in values.yaml to control whether Ingress is deployed
ingress:
enabled: true
host: karpor.example.com
paths:
- path: /
pathType: Prefix
backend:
serviceName: karpor-server
servicePort: 7443
annotations: {}
tls:
enabled: false
secretName:

Could you confirm if this approach aligns with best practices for the Karpor Helm Chart? Also, any guidance on additional parameters or implementation considerations would be appreciated.

[suyanhj]

@ashwini897
Can I provide a web http port? I am using istio gateway to expose the host, but since the backend already uses its own https, it always prompts: "Client sent an HTTP request to an HTTPS server." Or provide a backend tls switch function to allow me to turn off the backend tls. I will configure tls at the gateway.

I want to configure reverse proxy access externally

[fanfan-yu]

Proposed Changes: Create an ingress.yml template file to define the Ingress resource. Add an ingress.enabled flag in values.yaml to control whether Ingress is deployed ingress: enabled: true host: karpor.example.com paths: - path: / pathType: Prefix backend: serviceName: karpor-server servicePort: 7443 annotations: {} tls: enabled: false secretName:

Could you confirm if this approach aligns with best practices for the Karpor Helm Chart? Also, any guidance on additional parameters or implementation considerations would be appreciated.

Cool! I think it is good idea.