operator [N] cert-monitor-operator (0.1.0)

[nachoperator]

New Operator Submission: Certificate Monitor Operator v0.1.0

Description about the managed Application

The Certificate Monitor Operator automatically monitors SSL/TLS certificates stored in Kubernetes secrets and sends notifications when they approach expiration. This operator helps prevent service outages caused by expired certificates by providing proactive monitoring and alerting.

More information: https://github.com/nachoperator/nacho-operators

Features and capabilities

• 🔍 Automatic certificate monitoring: Continuously scans TLS secrets across namespaces
• ⏰ Configurable expiration thresholds: Set custom warning periods (1-365 days before expiration)
• 📢 Multiple notification channels: Slack webhooks and OpsGenie integration
• 🏷️ Namespace-scoped monitoring: Monitor certificates in specific namespaces
• 📊 Rich status information: Detailed status reporting with conditions and metrics
• 🔄 Automatic reconciliation: Continuous monitoring with configurable intervals

Usage

1. Install the operator from OperatorHub
2. Create a CertificateMonitor resource pointing to your TLS secret
3. Configure notification channels (Slack, OpsGenie)
4. Set renewal threshold (days before expiration to alert)
5. Monitor receives automatic notifications when certificates approach expiration

Manual pre-requisites

• Kubernetes cluster with TLS secrets containing certificates to monitor
• Valid webhook URLs for Slack notifications (if using Slack)
• Valid API keys for OpsGenie (if using OpsGenie)

Images

• Operator: ghcr.io/nachoperator/cert-monitor-operator:v0.1.0
• Bundle: ghcr.io/nachoperator/cert-monitor-operator-bundle:v0.1.0

Testing

• ✅ Bundle validation passed with operator-sdk bundle validate
• ✅ Local testing completed with sample certificates
• ✅ All container images are publicly available
• ✅ Tested with both Slack and OpsGenie notifications

---

New Submissions Checklist

• Are you familiar with our contribution guidelines?
• Have you packaged and deployed your Operator for Operator Framework?
• Have you tested your Operator with all Custom Resource Definitions?
• Have you tested your Operator in all supported installation modes?
• Have you considered whether you want use semantic versioning order?
• Is your submission signed?
• Is operator icon set?

Your submission should not

• Modify more than one operator
• Modify an Operator you don't own
• Rename an operator
• Modify any files outside the above mentioned folders
• Contain more than one commit ✅

Operator Description contains (in order)

1. Description about the managed Application and where to find more information
2. Features and capabilities of your Operator and how to use it
3. Manual steps about potential pre-requisites for using your Operator

Operator Metadata contains

• Human readable name and 1-liner description about your Operator
• Valid category name (Security, Monitoring)
• Pre-defined capability level (Basic Install)
• Links to the maintainer, source code and documentation
• Example templates for all Custom Resource Definitions
• A quadratic logo

---

Note: The operator icon will be added in a future update. All other requirements are met.

Maintainer: @nachoperator
Source: https://github.com/nachoperator/nacho-operators (private repository)

[github-actions]

Dear @nachoperator,
Your forked procject is not rebased

To fix this issue please rebase or execute following commands:

git clone https://github.com/nachoperator/community-operators /tmp/operators-repo
cd /tmp/operators-repo
git checkout origin/add-cert-monitor-operator-v0.1.0
git remote add upstream https://github.com/k8s-operatorhub/community-operators -f
git pull --rebase upstream main

[github-actions]

Dear @nachoperator,
Your forked procject is not rebased

To fix this issue please rebase or execute following commands:

git clone https://github.com/nachoperator/community-operators /tmp/operators-repo
cd /tmp/operators-repo
git checkout origin/add-cert-monitor-operator-v0.1.0
git remote add upstream https://github.com/k8s-operatorhub/community-operators -f
git pull --rebase upstream main

[github-actions]

Dear @nachoperator,
Your forked procject is not rebased

To fix this issue please rebase or execute following commands:

git clone https://github.com/nachoperator/community-operators /tmp/operators-repo
cd /tmp/operators-repo
git checkout origin/add-cert-monitor-operator-v0.1.0
git remote add upstream https://github.com/k8s-operatorhub/community-operators -f
git pull --rebase upstream main

[github-actions]

Dear @nachoperator,
Your forked procject is not rebased

To fix this issue please rebase or execute following commands:

git clone https://github.com/nachoperator/community-operators /tmp/operators-repo
cd /tmp/operators-repo
git checkout origin/add-cert-monitor-operator-v0.1.0
git remote add upstream https://github.com/k8s-operatorhub/community-operators -f
git pull --rebase upstream main

[github-actions]

Dear @nachoperator,
Your forked procject is not rebased

To fix this issue please rebase or execute following commands:

git clone https://github.com/nachoperator/community-operators /tmp/operators-repo
cd /tmp/operators-repo
git checkout origin/add-cert-monitor-operator-v0.1.0
git remote add upstream https://github.com/k8s-operatorhub/community-operators -f
git pull --rebase upstream main

[github-actions]

Dear @nachoperator,
Your forked procject is not rebased

To fix this issue please rebase or execute following commands:

git clone https://github.com/nachoperator/community-operators /tmp/operators-repo
cd /tmp/operators-repo
git checkout origin/add-cert-monitor-operator-v0.1.0
git remote add upstream https://github.com/k8s-operatorhub/community-operators -f
git pull --rebase upstream main

[github-actions]

Dear @nachoperator,
Your forked procject is not rebased

To fix this issue please rebase or execute following commands:

git clone https://github.com/nachoperator/community-operators /tmp/operators-repo
cd /tmp/operators-repo
git checkout origin/add-cert-monitor-operator-v0.1.0
git remote add upstream https://github.com/k8s-operatorhub/community-operators -f
git pull --rebase upstream main

[github-actions]

Dear @nachoperator,
Your forked procject is not rebased

To fix this issue please rebase or execute following commands:

git clone https://github.com/nachoperator/community-operators /tmp/operators-repo
cd /tmp/operators-repo
git checkout origin/add-cert-monitor-operator-v0.1.0
git remote add upstream https://github.com/k8s-operatorhub/community-operators -f
git pull --rebase upstream main

[github-actions]

Dear @nachoperator,
Your forked procject is not rebased

To fix this issue please rebase or execute following commands:

git clone https://github.com/nachoperator/community-operators /tmp/operators-repo
cd /tmp/operators-repo
git checkout origin/add-cert-monitor-operator-v0.1.0
git remote add upstream https://github.com/k8s-operatorhub/community-operators -f
git pull --rebase upstream main

[framework-automation]

/merge possible

[framework-automation]

/merge possible