Skip to content

Make additional validation for configmap of cozystack #284

Closed as not planned
Closed as not planned

Description

@gecube

Hi!

Right now it is easy to make a typo when preparing the cozy-stack configmap:

apiVersion: v1
kind: ConfigMap
metadata:
  name: cozystack
  namespace: cozy-system
data:
  bundle-name: "paas-full"
  ipv4-pod-cidr: "100.64.0.0/16"
  ipv4-pod-gateway: "10.64.0.1"
  ipv4-svc-cidr: "10.65.0.0/16"
  ipv4-join-cidr: "100.66.0.0/16"

I think it could be beneficial to install before applying some kind of webhook which will check the parameters and write meaningful errors (like "bundle name is not supported") or even switch from CM to our own CRD with a proper schema.

Activity

  1. mrkhachaturov commented on Aug 27, 2024

    @mrkhachaturov
    Contributor

    George Gaál (@gecube)

    I am working on operator for cozystack.

  2. changed the title [-]Make additional validation for CM of cozystack[/-] [+]Make additional validation for configmap of cozystack[/+] on Mar 25, 2025
  3. kvaps commented on Mar 25, 2025

    @kvaps
    Member

    It seems we need to fail installer binary on start in case of any errors in configmap, thanks added to backlog

  4. dosubot commented on Oct 20, 2025

    @dosubot

    Hi, George Gaál (@gecube). I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.

    Issue Summary:

    • You suggested adding validation for the cozy-stack ConfigMap to prevent typos and misconfigurations.
    • A webhook or replacing the ConfigMap with a CRD was proposed for schema enforcement.
    • Contributor mrkhachaturov is working on an operator for cozy-stack, which you and others supported.
    • Maintainer kvaps agreed on failing the installer binary on startup if ConfigMap errors exist and added this to the backlog.
    • Progress is being made toward improving configuration validation and error handling.

    Next Steps:

    • Please confirm if this issue is still relevant with the latest version of cozystack; if so, you can keep the discussion open by commenting here.
    • Otherwise, I will automatically close this issue in 7 days.

    Thanks for your understanding and contribution!

  5. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale
    on Oct 20, 2025
  6. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale
    on Oct 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions