One operator-owned object per configured provider will carry the periodic check result: a Ready condition, per-target verdicts with their own transition times, and a ready/total count for kubectl get. There is no spec; only a viewer role is shipped since the operator is the sole writer. Written by hand (kubebuilder is not installed), registered in the existing AddKnownTypes call rather than a second init(). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
29 lines
810 B
Plaintext
29 lines
810 B
Plaintext
# Code generated by tool. DO NOT EDIT.
|
|
# This file is used to track the info used to scaffold your project
|
|
# and allow the plugins properly work.
|
|
# More info: https://book.kubebuilder.io/reference/project-config.html
|
|
cliVersion: 4.15.0
|
|
domain: example.com
|
|
layout:
|
|
- go.kubebuilder.io/v4
|
|
projectName: egress-proxies-operator
|
|
repo: gitea.home.hrajfrisbee.cz/kacerr/egress-proxies-operator
|
|
resources:
|
|
- api:
|
|
crdVersion: v1
|
|
namespaced: true
|
|
controller: true
|
|
domain: example.com
|
|
group: crawl
|
|
kind: Proxy
|
|
path: gitea.home.hrajfrisbee.cz/kacerr/egress-proxies-operator/api/v1alpha1
|
|
version: v1alpha1
|
|
- api:
|
|
crdVersion: v1
|
|
domain: example.com
|
|
group: crawl
|
|
kind: ProviderHealth
|
|
path: gitea.home.hrajfrisbee.cz/kacerr/egress-proxies-operator/api/v1alpha1
|
|
version: v1alpha1
|
|
version: "3"
|