kacerrandClaude Opus 5
1c773c24ad
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>
30 lines
777 B
YAML
30 lines
777 B
YAML
# This rule is not used by the project egress-proxies-operator itself.
|
|
# It is provided to allow the cluster admin to help manage permissions for users.
|
|
#
|
|
# Grants read-only access to ProviderHealth objects, the results of the
|
|
# operator's periodic provider checks. The operator creates, updates and
|
|
# deletes them itself, so no admin or editor role is provided.
|
|
|
|
apiVersion: rbac.authorization.k8s.io/v1
|
|
kind: ClusterRole
|
|
metadata:
|
|
labels:
|
|
app.kubernetes.io/name: egress-proxies-operator
|
|
app.kubernetes.io/managed-by: kustomize
|
|
name: providerhealth-viewer-role
|
|
rules:
|
|
- apiGroups:
|
|
- crawl.example.com
|
|
resources:
|
|
- providerhealths
|
|
verbs:
|
|
- get
|
|
- list
|
|
- watch
|
|
- apiGroups:
|
|
- crawl.example.com
|
|
resources:
|
|
- providerhealths/status
|
|
verbs:
|
|
- get
|