1
0
Fork 0
forked from infra/ansible

[hotness] Fix the service for deployment

According to what I found the service selector app needs to match the
deployment app, which is pointing to the-new-hotness instead of
the-new-hotness redis. Hopefully this will fix the network issue between
the-new-hotness pod and redis pod.

Signed-off-by: Michal Konecny <mkonecny@redhat.com>
This commit is contained in:
Michal Konečný 2026-04-02 12:41:03 +02:00
commit 6933510d42
2 changed files with 4 additions and 16 deletions

View file

@ -2,9 +2,8 @@
apiVersion: v1
kind: Service
metadata:
labels:
app: the-new-hotness
name: the-new-hotness-redis
namespace: the-new-hotness
spec:
ports:
- name: 6379-tcp
@ -12,5 +11,4 @@ spec:
protocol: TCP
targetPort: 6379
selector:
app: the-new-hotness
deploymentconfig: the-new-hotness-redis
app: the-new-hotness-redis

View file

@ -2,23 +2,18 @@
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: the-new-hotness
service: the-new-hotness
name: the-new-hotness
spec:
replicas: 1
selector:
matchLabels:
app: the-new-hotness
service: the-new-hotness
strategy:
type: Recreate
template:
metadata:
labels:
app: the-new-hotness
service: the-new-hotness
annotations:
image.openshift.io/triggers: '[{"from":{"kind":"ImageStreamTag","name":"the-new-hotness:latest","namespace":"the-new-hotness"},"fieldPath":"spec.template.spec.containers[?(@.name==\"the-new-hotness\")].image"}]'
spec:
@ -75,22 +70,17 @@ spec:
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: the-new-hotness
service: the-new-hotness-redis
name: the-new-hotness-redis
spec:
replicas: 1
selector:
matchLabels:
app: the-new-hotness
service: the-new-hotness-redis
app: the-new-hotness-redis
strategy: {}
template:
metadata:
labels:
app: the-new-hotness
service: the-new-hotness-redis
app: the-new-hotness-redis
annotations:
image.openshift.io/triggers: '[{"from":{"kind":"ImageStreamTag","name":"the-new-hotness-redis:latest"},"fieldPath":"spec.template.spec.containers[?(@.name==\"the-new-hotness-redis\")].image"}]'
spec: