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

Set tenant ID for intrusion detection #3214

Merged
merged 1 commit into from
Feb 29, 2024

Conversation

asincu
Copy link
Contributor

@asincu asincu commented Feb 29, 2024

Description

Set tenant ID in intrusion detection when installing in a multi-tenant management cluster.

Zero-tenant : tenant ID is not needed.
Single tenant with internal elastic (0.5 half tenant) : tenant ID is not needed, as we need to assume we make queries as MCM does
Single tenant with external elastic: Needs tenant ID, but talk to Linseed from tigera-elasticsearch namespace and Manager from tigera-manager namespace
Multi-tenant: Needs tenant ID, tenant namespace and per tenant services for Linseed and Manager.

For PR author

  • Tests for change.
  • If changing pkg/apis/, run make gen-files
  • If changing versions, run make gen-versions

For PR reviewers

A note for code reviewers - all pull requests must have the following:

  • Milestone set according to targeted release.
  • Appropriate labels:
    • kind/bug if this is a bugfix.
    • kind/enhancement if this is a a new feature.
    • enterprise if this PR applies to Calico Enterprise only.

@asincu asincu force-pushed the intrusion_detection_tenant_id branch from ac395bc to e315d5a Compare February 29, 2024 19:16
@asincu asincu merged commit 846bed0 into tigera:master Feb 29, 2024
5 checks passed
@asincu asincu deleted the intrusion_detection_tenant_id branch February 29, 2024 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants