chore(gitops): delete orphaned leads manifests
All checks were successful
sync-to-forgejo / sync (push) Successful in 5s

leads-deployment.yaml and leads-service.yaml were already removed from
kustomization.yaml's resources list in the prior commit (e51f199) —
these were just the leftover, unreferenced files themselves.
This commit is contained in:
sync-test 2026-07-21 05:34:01 +05:30
parent e51f199d07
commit d277ddfa33
2 changed files with 0 additions and 72 deletions

View file

@ -1,56 +0,0 @@
apiVersion: apps/v1
kind: Deployment
metadata:
name: nxtgauge-rust-leads
labels:
app: nxtgauge-rust-leads
spec:
replicas: 1
selector:
matchLabels:
app: nxtgauge-rust-leads
template:
metadata:
labels:
app: nxtgauge-rust-leads
spec:
imagePullSecrets:
- name: forgejo-regcred
containers:
- name: leads
image: ci.nxtgauge.com/ashwin/nxtgauge-rust-leads:latest
imagePullPolicy: Always
ports:
- containerPort: 9118
name: http
envFrom:
- configMapRef:
name: nxtgauge-backend-rust-config
- secretRef:
name: nxtgauge-backend-rust-secrets
env:
- name: PORT
value: "9118"
readinessProbe:
httpGet:
path: /health
port: 9118
initialDelaySeconds: 10
periodSeconds: 10
timeoutSeconds: 3
failureThreshold: 3
livenessProbe:
httpGet:
path: /health
port: 9118
initialDelaySeconds: 20
periodSeconds: 20
timeoutSeconds: 3
failureThreshold: 5
resources:
requests:
cpu: 50m
memory: 64Mi
limits:
cpu: 500m
memory: 256Mi

View file

@ -1,16 +0,0 @@
apiVersion: v1
kind: Service
metadata:
name: nxtgauge-rust-leads
namespace: nxtgauge
labels:
app: nxtgauge-rust-leads
spec:
type: ClusterIP
selector:
app: nxtgauge-rust-leads
ports:
- name: http
port: 9118
targetPort: 9118
protocol: TCP