open-feature/open-feature-operator

CRD Naming?

Open

#753 opened on Mar 13, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (58 forks)github user discovery
help wantedquestion

Repository metrics

Stars
 (300 stars)
PR merge metrics
 (Avg merge 43d 10h) (5 merged PRs in 30d)

Description

Finally got around to using the OFO. I was initially confused because a FeatureFlag contains many flags as sub-resources. Per this brief conversation, I believe that what we're actually creating is a FlagSet which contains feature flags.

I assume the answer is yes, but is it too late to change names? Would an alias help or hurt?

Contributor guide

Research direction
Review Kubernetes CRD naming conventions and provide a recommendation on whether to rename 'FeatureFlag' to 'FlagSet' or use an alias. Consider backward compatibility and community conventions.
Tech stack
gokubernetes
Domain
backend
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Kubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80