You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the bug?
The OpenSearch operator currently does not support AppArmor for Kubernetes version 1.30x due to the lack of support in the security context. The operator is currently using Kubernetes version 1.27.x, which doesn't support this feature.
How can one reproduce the bug?
Set up OpenSearch operator using Kubernetes version 1.30x.
Try to apply an AppArmor profile in the security context.
The AppArmor configuration will not be applied, as it is not supported in the current Kubernetes version.
What is the expected behavior?
The expected behavior is that the OpenSearch operator should support AppArmor in Kubernetes version 1.30x by upgrading the Kubernetes version and making the necessary changes to the Custom Resource Definitions (CRDs) to accommodate AppArmor profiles.
The text was updated successfully, but these errors were encountered:
[Triage]
Hey @Sugilal i feel the compatibility matrix is not updated, but is installing operator on Kubernetes version 1.30x does not work or is there any changes required from operator side to support AppArmor.
Thanks @swoehrl-mw@getsaurabh02
What is the bug?
The OpenSearch operator currently does not support AppArmor for Kubernetes version 1.30x due to the lack of support in the security context. The operator is currently using Kubernetes version 1.27.x, which doesn't support this feature.
How can one reproduce the bug?
Set up OpenSearch operator using Kubernetes version 1.30x.
Try to apply an AppArmor profile in the security context.
The AppArmor configuration will not be applied, as it is not supported in the current Kubernetes version.
What is the expected behavior?
The expected behavior is that the OpenSearch operator should support AppArmor in Kubernetes version 1.30x by upgrading the Kubernetes version and making the necessary changes to the Custom Resource Definitions (CRDs) to accommodate AppArmor profiles.
The text was updated successfully, but these errors were encountered: