Struct RndcKeyConfig 

pub struct RndcKeyConfig {
    pub auto_rotate: bool,
    pub rotate_after: String,
    pub secret_ref: Option<RndcSecretRef>,
    pub secret: Option<SecretSpec>,
    pub algorithm: RndcAlgorithm,
}

RNDC key lifecycle configuration with automatic rotation support.

Provides three configuration modes:

1. Auto-generated with optional rotation (default) - Operator creates and manages keys
2. Reference to existing Secret - Use pre-existing Kubernetes Secret (no rotation)
3. Inline Secret specification - Define Secret inline with optional rotation

When auto_rotate is enabled, the operator automatically rotates keys after the rotate_after duration has elapsed. Rotation timestamps are tracked in Secret annotations.

Examples

# Auto-generated with 30-day rotation
rndcKeys:
  autoRotate: true
  rotateAfter: 720h
  algorithm: hmac-sha256

# Reference existing Secret (no rotation)
rndcKeys:
  secretRef:
    name: my-rndc-key
    algorithm: hmac-sha256

# Inline Secret with rotation
rndcKeys:
  autoRotate: true
  rotateAfter: 2160h  # 90 days
  secret:
    metadata:
      name: custom-rndc-key
      labels:
        app: bindy

Fields

auto_rotate: bool

Enable automatic key rotation (default: false for backward compatibility).

When true, the operator automatically rotates the RNDC key after the rotate_after interval. When false, keys are generated once and never rotated.

Important: Rotation only applies to operator-managed Secrets. If you specify secret_ref, that Secret will NOT be rotated automatically.

Default: false

rotate_after: String

Duration after which to rotate the key (Go duration format: “720h”, “30d”).

Supported units:

• h (hours): “720h” = 30 days
• d (days): “30d” = 30 days
• w (weeks): “4w” = 28 days

Constraints:

• Minimum: 1h (1 hour)
• Maximum: 8760h (365 days / 1 year)

Only applies when auto_rotate is true.

Default: "720h" (30 days)

secret_ref: Option<RndcSecretRef>

Reference to an existing Kubernetes Secret containing RNDC credentials.

When specified, the operator uses this existing Secret instead of auto-generating one. The Secret must contain the rndc.key field with BIND9 key file content.

Mutually exclusive with secret - if both are specified, secret_ref takes precedence and secret is ignored.

Rotation note: User-managed Secrets (via secret_ref) are NOT automatically rotated even if auto_rotate is true. You must rotate these manually.

Default: None (auto-generate key)

secret: Option<SecretSpec>

Inline Secret specification for operator-managed Secret with optional rotation.

Embeds a full Kubernetes Secret specification. The operator will create and manage this Secret, and rotate it if auto_rotate is true.

Mutually exclusive with secret_ref - if both are specified, secret_ref takes precedence and this field is ignored.

Default: None (auto-generate key)

algorithm: RndcAlgorithm

HMAC algorithm for the RNDC key.

Only used when auto-generating keys (when neither secret_ref nor secret are specified). If using secret_ref, the algorithm is specified in that reference.

Default: hmac-sha256

Trait Implementations

impl Clone for RndcKeyConfig

fn clone(&self) -> RndcKeyConfig

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for RndcKeyConfig

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for RndcKeyConfig

fn default() -> RndcKeyConfig

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for RndcKeyConfig

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl JsonSchema for RndcKeyConfig

fn schema_name() -> Cow<'static, str>

The name of the generated JSON Schema.

fn schema_id() -> Cow<'static, str>

Returns a string that uniquely identifies the schema produced by this type.

fn json_schema(generator: &mut SchemaGenerator) -> Schema

Generates a JSON Schema for this type.

fn inline_schema() -> bool

Whether JSON Schemas generated for this type should be included directly in parent schemas, rather than being re-used where possible using the $ref keyword.

impl PartialEq for RndcKeyConfig

fn eq(&self, other: &RndcKeyConfig) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for RndcKeyConfig

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for RndcKeyConfig