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
41 lines
967 B
YAML
41 lines
967 B
YAML
---
|
|
pod:
|
|
security_context:
|
|
keystone:
|
|
container:
|
|
keystone_api:
|
|
appArmorProfile:
|
|
type: RuntimeDefault
|
|
credential_setup:
|
|
container:
|
|
keystone_credential_setup:
|
|
appArmorProfile:
|
|
type: RuntimeDefault
|
|
fernet_setup:
|
|
container:
|
|
keystone_fernet_setup:
|
|
appArmorProfile:
|
|
type: RuntimeDefault
|
|
domain_manage:
|
|
container:
|
|
keystone_domain_manage:
|
|
appArmorProfile:
|
|
type: RuntimeDefault
|
|
keystone_domain_manage_init:
|
|
appArmorProfile:
|
|
type: RuntimeDefault
|
|
test:
|
|
container:
|
|
keystone_test:
|
|
appArmorProfile:
|
|
type: RuntimeDefault
|
|
keystone_test_ks_user:
|
|
appArmorProfile:
|
|
type: RuntimeDefault
|
|
kubernetes_entrypoint:
|
|
container:
|
|
kubernetes_entrypoint:
|
|
appArmorProfile:
|
|
type: RuntimeDefault
|
|
...
|