Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Falco Sidekick UI Ingress not functional #704

Open
benglewis opened this issue Jul 7, 2024 · 2 comments
Open

Falco Sidekick UI Ingress not functional #704

benglewis opened this issue Jul 7, 2024 · 2 comments
Assignees
Labels
kind/bug Something isn't working lifecycle/stale

Comments

@benglewis
Copy link

Describe the bug

When using the Helm chart to use Falco Sidekick UI with an Ingress, the resulting endpoint results in 404 on all resource requests.

How to reproduce it

Run Helm chart with Falco Sidekick UI with an Ingress on GCP. Please see: #402 (comment)

Expected behaviour

Falco Sidekick UI should work on the address indicated by the Ingress.

Screenshots

Please see:
#402 (comment)

Environment

  • Falco version:
    0.38.1
  • System info:
Sun Jul  7 15:33:38 2024: Using deprecated config key 'rules_file' (singular form). Please use new 'rules_files' config key (plural form).
Sun Jul  7 15:33:38 2024: Falco version: 0.38.1 (x86_64)
Sun Jul  7 15:33:38 2024: Falco initialized with configuration files:
Sun Jul  7 15:33:38 2024:    /etc/falco/falco.yaml
Sun Jul  7 15:33:38 2024: System info: Linux version 6.1.85+ (builder@faf02fc191fd) (Chromium OS 16.0_pre484197_p20230405-r10 clang version 16.0.0 (/var/tmp/portage/sys-devel/llvm-16.0_pre484197_p20230405-r10/work/llvm-16.0_pre484197_p20230405/clang 2916b99182752b1aece8cc4479d8d6a20b5e02da), LLD 16.0.0) #1 SMP PREEMPT_DYNAMIC Thu Jun 27 21:05:47 UTC 2024
Sun Jul  7 15:33:38 2024: Loading rules from file /etc/falco/falco_rules.yaml
{
  "machine": "x86_64",
  "nodename": "falco-pqft2",
  "release": "6.1.85+",
  "sysname": "Linux",
  "version": "#1 SMP PREEMPT_DYNAMIC Thu Jun 27 21:05:47 UTC 2024"
}
  • Cloud provider or hardware configuration:
    GCP GKE
  • OS:
    Node is running on GCP Container-Optimized OS. Falco image seems to be Ubuntu based-based.
  • Kernel:
    6.1.85+
  • Installation method:
    Helm chart via Pulumi.

Additional context

N/A

@benglewis benglewis added the kind/bug Something isn't working label Jul 7, 2024
@Issif Issif self-assigned this Jul 8, 2024
@Issif
Copy link
Member

Issif commented Sep 17, 2024

Can you try to set the pathType to Prefix to check if it works better please.

falcosidekick: 
  enabled: true
  webui: 
    enabled: true
    user: "REDACTED:REDACTED"
    service: 
      type: "NodePort"
      annotations: 
        cloud.google.com/neg: "{\"ingress\": true}"
        cloud.google.com/app-protocols: "{\"http\": \"HTTP\"}"
    ingress: 
      enabled: true
      annotations: 
        kubernetes.io/ingress.class: "gce-internal"
        kubernetes.io/ingress.allow-http: true
        networking.gke.io/v1beta1.FrontendConfig: "frontend-config"
      hosts: 
        - host: "falcosidekick-ui.falco.mvp.dev.hirundo.io"
          paths: 
          - path: "/
            pathType: Prefix

@poiana
Copy link
Contributor

poiana commented Dec 16, 2024

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working lifecycle/stale
Projects
None yet
Development

No branches or pull requests

3 participants