separate deployments

[Nurlan199206]

i made separate Alertmanager-bot deployments. Kind: List not working on 1.18 version.

====================SERVICE==========================

apiVersion: v1
kind: Service
metadata:
  labels:
  app.kubernetes.io/name: alertmanager-bot
  name: alertmanager-bot
  namespace: monitoring
spec:
  ports:
  - name: http
    port: 8080
    targetPort: 8080
selector:
  app.kubernetes.io/name: alertmanager-bot

=======================Secret=====================

apiVersion: v1
data:
  admin: MTIzNA==
  token: WFhYWFhYWA==
kind: Secret
metadata:
  labels:
  app.kubernetes.io/name: alertmanager-bot
  name: alertmanager-bot
  namespace: monitoring
type: Opaque

============================StatefulSet====================

kind: StatefulSet
apiVersion: apps/v1
metadata:
  name: alertmanager-bot
  namespace: monitoring
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: alertmanager-bot
  template:
    metadata:
      labels:
        app.kubernetes.io/name: alertmanager-bot
    spec:
      containers:
        - name: alertmanager-bot
          image: 'metalmatze/alertmanager-bot:0.4.2'
          args:
            - '--alertmanager.url=http://localhost:9093'
            - '--log.level=info'
            - '--store=bolt'
            - '--bolt.path=/data/bot.db'
          env:
            - name: TELEGRAM_ADMIN
              value: your_ID
            - name: TELEGRAM_TOKEN
              value: your_TOKEN
          imagePullPolicy: IfNotPresent
      restartPolicy: Always
      securityContext: {}
      schedulerName: default-scheduler
  serviceName: alertmanager-bot

=============PVC======================

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  labels:
    app.kubernetes.io/name: alertmanager-bot
  name: data
  namespace: monitoring
spec:
  storageClassName: standard
  accessModes:
  - ReadWriteOnce
  resources:
     requests:
       storage: 1Gi