062261562f
Starting with kubernetes 1.30 apparmor profiles are specified in the security_context instead of annotations: https://kubernetes.io/docs/tutorials/security/apparmor/ This PS: 1: updates apparmor value overrides to use security_context 2: removes apparmor annotations from top level values where found 3: removes non apparmor values from apparmor value overrides where found End users can still use annotations by setting values appropriately. Change-Id: I2c1a473e81d0904cbb1f96ee6ffb08b0d68e8651
39 lines
881 B
YAML
39 lines
881 B
YAML
---
|
|
pod:
|
|
security_context:
|
|
glance:
|
|
container:
|
|
glance_api:
|
|
appArmorProfile:
|
|
type: RuntimeDefault
|
|
glance_perms:
|
|
appArmorProfile:
|
|
type: RuntimeDefault
|
|
nginx:
|
|
appArmorProfile:
|
|
type: RuntimeDefault
|
|
metadefs_load:
|
|
container:
|
|
glance_metadefs_load:
|
|
appArmorProfile:
|
|
type: RuntimeDefault
|
|
storage_init:
|
|
container:
|
|
glance_storage_init:
|
|
appArmorProfile:
|
|
type: RuntimeDefault
|
|
test:
|
|
container:
|
|
glance_test_ks_user:
|
|
appArmorProfile:
|
|
type: RuntimeDefault
|
|
glance_test:
|
|
appArmorProfile:
|
|
type: RuntimeDefault
|
|
kubernetes_entrypoint:
|
|
container:
|
|
kubernetes_entrypoint:
|
|
appArmorProfile:
|
|
type: RuntimeDefault
|
|
...
|