Birdhk 这个是没问题的，我也改了钉钉接收者的使用的模版啥的都能生效。但是模版的configmap没有挂在容器上。
下面是3.4.1的notification-manager的yaml，并没有将模版挂载上去
kind: Deployment
apiVersion: apps/v1
metadata:
name: notification-manager-deployment
namespace: kubesphere-monitoring-system
labels:
app: notification-manager
notification-manager: notification-manager
annotations:
deployment.kubernetes.io/revision: '15'
spec:
replicas: 2
selector:
matchLabels:
app: notification-manager
notification-manager: notification-manager
template:
metadata:
creationTimestamp: null
labels:
app: notification-manager
notification-manager: notification-manager
spec:
containers:
- name: notification-manager
image: 'kubesphere/notification-manager:v2.3.0'
args:
- '--log.level=debug'
ports:
- name: webhook
containerPort: 19093
protocol: TCP
env:
- name: NAMESPACE
value: kubesphere-monitoring-federated
resources:
limits:
cpu: 500m
memory: 500Mi
requests:
cpu: 5m
memory: 20Mi
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
imagePullPolicy: IfNotPresent
restartPolicy: Always
terminationGracePeriodSeconds: 30
dnsPolicy: ClusterFirst
serviceAccountName: notification-manager-sa
serviceAccount: notification-manager-sa
securityContext: {}
affinity: {}
schedulerName: default-scheduler
strategy:
type: RollingUpdate
rollingUpdate:
maxUnavailable: 25%
maxSurge: 25%
revisionHistoryLimit: 10
progressDeadlineSeconds: 600
