PODs are not getting the annotations about helm-charts

[PingDavidR]

Thanks @zerowebcorp ! We've reviewed your input, and given the relatively minor change that will be required, we should be able to squeeze this in for our next release cycle late next week or early the following.

I'll keep you posted in this issue.

[PingDavidR]

@zerowebcorp in researching, it seems our charts support the following that might not require us to make changes. I tested this and I think it meets your needs.

global:
  envs:
    PING_IDENTITY_ACCEPT_EULA: "YES"

#############################################################
# pingfederate-admin values
#############################################################
pingfederate-admin:
  enabled: true
  envs:
    SERVER_PROFILE_URL: https://github.com/pingidentity/pingidentity-server-profiles.git
    SERVER_PROFILE_PATH: getting-started/pingfederate

#############################################################
# pingfederate-engine values
#############################################################
pingfederate-engine:
  enabled: true
  envs:
    SERVER_PROFILE_URL: https://github.com/pingidentity/pingidentity-server-profiles.git
    SERVER_PROFILE_PATH: getting-started/pingfederate
  workload:
    annotations:
      backup.velero.io/backup-volumes: data

and what rendered was:

# Source: ping-devops/templates/pingfederate-engine/workload.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app.kubernetes.io/instance: test
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: pingfederate-engine
    helm.sh/chart: ping-devops-0.10.1
  name: test-pingfederate-engine
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/instance: test
      app.kubernetes.io/name: pingfederate-engine
  strategy:
<stuff here>
  template:
    metadata:
      annotations:
        backup.velero.io/backup-volumes: data
        checksum/config: e14182d42c4cbf0a29371f868ecdd12e8520dc2256de1b66a472b1ef77a808aa

Would you mind giving that a go and see if it works for you?

[PingDavidR]

it is the workload.annotations block that our charts know how to handle

[PingDavidR]

@zerowebcorp We are planning a chart release in the next day or so, and if the workload.annotations block doesn't meet your needs, we can get this in, but we need your feedback to know for sure.

Thanks!

[zerowebcorp]

@PingDavidR Just tested this by adding the annotation under the pingfederate-admin block and it gets added. This satisfies my requirement.

However, since this works for Deployment and not for Statefulset this could be classified as a bug. I would expect that anything under global would be applied for all the components ( pingfederate-admin/pingfederate-runtime) and don't have to specify them individually. Would be great to have this fixed for both the workload type.

[PingDavidR]

aha! I wasn't as clear as I thought, @zerowebcorp: Try this - this should do what I think you are looking for - specify workload at the global level:

global:
  envs:
    PING_IDENTITY_ACCEPT_EULA: "YES"
  workload:
    annotations:
      backup.velero.io/backup-volumes: data

This will attach the annotation to SS and Deployment both, at the Pod level

[zerowebcorp]

ohk, thank you for clarifying. Adding the annotations under global.workload instead of global works.

[PingDavidR]

Glad to hear it! And thanks again for using our charts!