Skip to content

CFP: Recreate CNP CRDs based on feature enablement #27459

@aanm

Description

@aanm

Currently, Cilium Operator installs all CNP CRD in the cluster upon initialization. Since this CRD is defined with kubemarkers, its configuration is hardcoded here. This causes some issues as pointed out in #17880 and can be confusing for users.

To prevent these issues, we could perform some conditional checking while we are constructing the CRD in here and define the CEP column views based on the features that are enabled. For example, if IPv6 is not enabled then we shouldn't display the IPv6 column, or, if we start Cilium agent with --endpoint-status=policy then we should show the column for policy enforcement status otherwise it should be omitted.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/agentCilium agent related.area/k8sImpacts the kubernetes API, or kubernetes -> cilium internals translation layers.good-first-issueGood starting point for new developers, which requires minimal understanding of Cilium.help-wantedPlease volunteer for this by adding yourself as an assignee!kind/featureThis introduces new functionality.

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions